Indexing HP's Trim Context with the Google Search Appliance


Published on

Overview of Adhere Solutions' HP TRIM content management system indexing connector for the Google Search Appliance.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Indexing HP's Trim Context with the Google Search Appliance

  1. 1. All Access Connector Suite for Google Search Appliance:    HP TRIM Connectors Jim Orris
  2. 2. About Adhere Solutions Enterprise Search Experience All Access Connector Platform Certified Google Search Partner Software platform for enabling the Proven enterprise search GSA to index or federate structured implementation and management and unstructured content from methodology complex enterprise and database Performed more than 50 GSA systems. implementations Central point of GSA and Adhere Clients include: Connector integration Configuration and Management Wal-Mart Supports over 30 indexing connectors Department of Energy ECM, ERP, PLM, CRM, DAM American Library Association And, over 6000 federated search, or Federal Trade Commission OneBox connectors U.S. Health and Human Services Google Through partnerships w/ leading Voice of America News OEM data access suppliers National Education Association Provides bi-lateral data integration LexisNexis Optimized for GSA
  3. 3. All Access Connector Platform Old model of accessing information
  4. 4. 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 systems Supplier only writes and maintains connectors, expert in the practice Licensed by Adhere Solutions and optimized for GSA Leveraging Google's connector framework Plug and play, configurable from GSA web browser interface Supports HP TRIM 6.2.x
  5. 5. The GSA Connector GSA Admin
  6. 6. 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 space Search box as a toolbar, or separate search page
  7. 7. The GSA Connector Framework 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 All Access Connector is a suite of Java the connector to perform work. applications containing methods and classes 4. The connector communicates through the API to the CMS to acquire documents, that Google's connector manager calls to metadata on each document, and a URLs perform the tasks of acquiring documents that point to a document's location in the from a content system and authenticates and content management system. authorizes end users to view search results 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.
  8. 8. The GSA Connector GSA Admin
  9. 9. Connector Crawl Status Report
  10. 10. Installation: TRIM Connector for GSA The TRIM connector does not require any special libraries to be installed
  11. 11. Features: TRIM Connector for GSA Supports locking and unlocking of documents Supports retrieval of permissions No additional libraries required Unsupported features: workflow and versioning Unsupported methods: getContainers, referenceinContainer, unreferrenceinContainer Supported Search Operators: AND, OR, NOT FOLDER(), =, <>, >, >=, <, <=, IN, LIKE(), CONTAINS()
  12. 12. 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
  13. 13. Standard Record Properties name auto renditions creation date TRIM Barcode update date blueprint access control checked out on, path, to accession number classification all actions client all contacts consignment all holds creator all meetings disposition all versions current action alternative containers assignee author assignee status auto part rule latest version doc size, type, details date assigned, closed, due, finalized flags date inactive, modified, published edit status date registered, date due
  14. 14. Standard Record Properties (cont.) document store is container store ID is electronic extensions is part external ID is first part foreign barcode signature declare as final thesaurus terms title last action date email attachment latest part audit events latest version home space, location expanded number home number next part checked out next task record number notes number of renditions and more...... record class, type, form related records
  15. 15. Mapping Permissions TRIM Permission Connector Permission View Document viewContent View Metadata viewProperties Update Document writeContent Update Record Metadata writeProperties Modify Record Access changePermissions Destroy Record delete
  16. 16. 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 security The 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.