Jim Orris jim@adheresolutions.com

All Access Connector Suite for Google Search Appliance:  

HP TRIM Connectors

About Adhere Solutions

Enterprise Search Experience

Certified Google Search PartnerProven enterprise search implementation and management methodologyPerformed more than 50 GSA implementationsClients include:

Wal-MartDepartment of EnergyAmerican Library AssociationFederal Trade CommissionU.S. Health and Human ServicesGoogleVoice of America NewsNational Education AssociationLexisNexis

All Access Connector Platform

Software platform for enabling the GSA to index or federate structured and unstructured content from complex enterprise and database systems.Central point of GSA and Adhere Connector integration

Configuration and ManagementSupports over 30 indexing connectors

ECM, ERP, PLM, CRM, DAMAnd, over 6000 federated search, or OneBox connectors

Through partnerships w/ leading OEM data access suppliers

Provides bi-lateral data integrationOptimized for GSA

All Access Connector Platform

Old model of accessing information

Background: HP TRIM Connector for GSA

Core technology developed by leading OEM supplier of information access and content integration tools

Battle tested: same technology is built in to major enterprise search and ECM systemsSupplier only writes and maintains connectors, expert in the practice

Licensed by Adhere Solutions and optimized for GSALeveraging Google's connector framework Plug and play, configurable from GSA web browser interface

Supports HP TRIM 6.2.x

The GSA Connector GSA Admin

Value: HP TRIM Connector for GSA

Extends the simplicity and familiarity of Google Search to TRIM content

Google Keyword search, result page interface

Delivers a single point of access, to data stored in TRIM modules and disparate systems and file shares indexed by the Google Search Appliance

GSA can index 200+ file types and some, but not, all ECM, database and other enterprise systems

Provides a platform for accessing and distributing contextually relevant content both with in, and outside of business applications

Search box integrated with in a portal or team spaceSearch box as a toolbar, or separate search page

The GSA Connector Framework

The All Access Connector is a suite of Java applications containing methods and classes that Google's connector manager calls to perform the tasks of acquiring documents from a content system and authenticates and authorizes end users to view search results

Common Steps: 1. The GSA provides a feed interface from

which the search appliance receives documents to index.

2. The AAC communicates with the search appliance over HTTP and with the connectors, and creates feed sources from the documents, metadata, and URLs from a content management system (CMS).

3. The AAC creates instances of a connector through its service provider interface (SPI) and then calls the classes and methods of the connector to perform work.

4. The connector communicates through the API to the CMS to acquire documents, metadata on each document, and a URLs that point to a document's location in the content management system.

5. The connector communicates through the API over HTTP to the web client on the content management system.

6. A CMS also provides a content server that stores documents in a storage system known as a repository.

The GSA Connector GSA Admin

Connector Crawl Status Report

Installation: TRIM Connector for GSA

The TRIM connector does not require any special libraries to be installed

Features: TRIM Connector for GSA

Supports locking and unlocking of documentsSupports retrieval of permissionsNo additional libraries requiredUnsupported features: workflow and versioningUnsupported methods:

getContainers, referenceinContainer, unreferrenceinContainer

Supported Search Operators: AND, OR, NOT FOLDER(), =, <>, >, >=, <, <=, IN, LIKE(), CONTAINS()

Defining a Repository

Repository Name: A unique identifier for the repository.Display Name: An optional label for this repository displayed to user. Web Service URL: The URL of the TRIM Web Service

Standard Record Properties

namecreation dateupdate dateaccess controlaccession numberall actionsall contactsall holdsall meetingsall versionsalternative containersauthorauto part ruledoc size, type, detailsflagsedit status

auto renditionsTRIM Barcodeblueprintchecked out on, path, toclassificationclientconsignmentcreatordispositioncurrent actionassigneeassignee statuslatest versiondate assigned, closed, due, finalized date inactive, modified, publisheddate registered, date due

Standard Record Properties (cont.)

document storestore IDextensionsexternal IDforeign barcodedeclare as finaltitleemail attachmentaudit eventshome space, locationhome numberchecked outrecord numbernumber of renditionsrecord class, type, formrelated records

is containeris electronicis partis first partsignaturethesaurus termslast action datelatest partlatest versionexpanded numbernext partnext tasknotesand more......

Mapping Permissions

TRIM Permission

View DocumentView MetadataUpdate DocumentUpdate Record MetadataModify Record AccessDestroy Record

Connector Permission

viewContentviewPropertieswriteContentwritePropertieschangePermissionsdelete

Security: HP TRIM Connector for GSA

It is possible through our connector API to retrieve the ACL of each item of the repository (document or folder).

Provided that the connector supports securityThe ACL lists every user and group that has some permissions on the item, along with the granted rights. The connector takes care of repository-specific security features, like

Security inheritance, shared ACLs, superuser/administrator roles, etc. so that the returned list is the effective ACL of the item.

Repository-specific permissions are mapped onto well-known permissions such as "view content", "write content", "delete", etc.The connector API provides methods to navigate group membership to find out which groups a given user, or group, is a member. When replicating ACLs (early binding), the list of user and groups that can view the document is stored in each document metadata.It is also possible to replicate the user directory (users and groups). At runtime, when a user performs a search, the system can obtain the list of groups of which the user is a member, and use this list to perform the search, thus limiting the results to what the user is authorized to see.