Embed Size (px)
DESCRIPTION
Adhere Solutions is a Google Enterprise Partner providing products and services that help organizations accelerate their adoption of Google technologies. Adhere's team of consultants help customers leverage Google's Enterprise Search products, Google Maps, and Google Apps to improve access to information, productivity, and collaboration.Through our All Access Connector Suite, Adhere Solutions has a portfolio of over 30 Google Search Appliance indexing connectors for major enterprise content management applications, including EMC, Documentum, eRoom, IBM FileNet, Lotus Notes, Interwoven's TeamSite and Work Site, Microsoft Sharepoint, SQL, Opentext, Oracle Stellent, Xerox Docushare and more.. With the All Access Connector Suite companies can now access all of their enterprise data and intelligence from one search box.The All Access Connector suite for the Google Search Appliance allows users to find information stored in disparate data sources and applications with Google's user interface, relieving users from having to separately search within each application and database. The Google Search Appliance combined with the All Access Connector empowers companies to efficiently unify information access and help users quickly find information to effectively perform their job.
Citation preview
Jim Orris [email protected]
All Access Connector Suite for Google Search Appliance:
IBM Content Manager Connector
About Adhere Solutions
Enterprise Search Experience
Certified Google Search PartnerProven enterprise search implementation and management methodologyClients include:
Wal-MartDepartment of EnergyAmerican Library AssociationFederal Trade CommissionU.S. Health and Human ServicesPacific Northwest National LabU.S. Department of CommerceVoice 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 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: 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 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 IBM Content Manager 8.3 or later versions
The GSA Connector GSA Admin
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 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.
Connector Crawl Status Report
Features: IBM Content Manager Connector for GSA
Supports all item types, whatever their classificationResource, Document or Document Part, Type, ItemCan 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 supportedConnector does not support links between items
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
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
The GSA Connector GSA Admin
Mapping Permissions
IBM Content ManagerItem QueryItem DeleteItem AddItem User SetItem AddItem Add Link
Connector PermissionView PropertiesDeleteWrite PropertiesWrite PropertiesWrite ContentCreate Subfolders
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 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.
