Ibm Content Manager Connector Overview0001 1
0 likes935 views
The IBM Content Manager Connector for Google Search Appliance enables the integration and indexing of structured and unstructured content from various enterprise systems, enhancing enterprise search capabilities. It supports a wide range of data types and offers a straightforward interface for searching across content management and disparate systems. The connector leverages Google's framework for seamless operation, allowing organizations to retrieve and manage information efficiently while maintaining repository-specific security features.
Ibm Content Manager Connector Overview0001 1
- 1. All Access Connector Suite for Google Search Appliance: IBM Content Manager Connector Jim Orris jim@adheresolutions.com
- 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 systems. Clients include: Central point of GSA and Adhere Connector integration Wal-Mart Configuration and Management Department of Energy Supports over 30 indexing connectors American Library Association ECM, ERP, PLM, CRM, DAM Federal Trade Commission And, over 6000 federated search, or U.S. Health and Human Services Pacific Northwest National Lab OneBox connectors U.S. Department of Commerce 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. All Access Connector Platform Old model of accessing information
- 4. Background: IBM Content Manager Connector 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 IBM Content Manager 8.3 or later versions
- 5. The GSA Connector GSA Admin
- 6. Value: IBM Content Manager Connector for GSA Extends the simplicity and familiarity of Google Search to Livelink content Google Keyword search, result page interface Delivers a single point of access, to data stored in ECM applications along with disparate systems and file shares indexed by the Google Search Appliance GSA can index 200+ file types and enterprise systems, but not all ECM 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. 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. Connector Crawl Status Report
- 9. Features: IBM Content Manager Connector for GSA Supports all item types, whatever their classification Resource, Document or Document Part, Type, Item Can discover description of unknown types at runtime. Hidden views do not appear by default, but can be exposed Supports Attribute Groups and Child Components (to one level) Deep search of an item in a folder is not supported Connector does not support links between items
- 10. Installation: IBM Content Manager Connector Must run on the same server as Content Manager Leverages IBM Information Integration for Content (II4C) Needs to be installed on server The files cmbcm.jar and cmbicm.jar from II4C must be present in the class path of the connector Supports remote access and RMI
- 11. Defining a Repository Repository Name: A unique identifier for this repository. Display Name: A name displayed to user. Library Server: The name of the Library server to connect to
- 12. The GSA Connector GSA Admin
- 13. Mapping Permissions IBM Content Manager Connector Permission Item Query View Properties Item Delete Delete Item Add Write Properties Item User Set Write Properties Item Add Write Content Item Add Link Create Subfolders
- 14. Security: General Notes 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.