© 2010 IBM Corporation WebSphere Adapter for Enterprise Content Management Systems

© 2010 IBM Corporation Persona and Scenario Philip Pearson, Process Developer Philip has to develop a process, part of which needs to access content from FileNet P8 Content Engine and perform actions on the content. While developing the process he is looking for a means to connect to content engine, browse through the content repositories of the FileNet P8 Content Engine, select the document classes and properties that are of interest and then generate a service import or export as required. 2

© 2010 IBM Corporation WebSphere Adapter for ECM  Adapter makes use of WebService bindings and ReST bindings of CMIS for interaction with the target content management systems  Supports discovery, outbound and inbound functionality  Provides a flexible Business Object model that permits working either with a document’s properties only or with the document’s properties and it’s content  Supports IBM FileNet P8 Content Engine (v 5.0) which must be enabled for the CMIS WebServices and ReST bindings –Although riding on CMIS enables the Adapter to interoperate with any Content Management System that complies with CMIS, FileNet P8 CE v5.0 is alone officially supported  Enabled in WebSphere Integration Developer for WebSphere Process Server and WebSphere ESB  Supported on many Operating Systems : AIX, Linux, Windows, HP-UX, Solaris 3 The Adapter enables bidirectional exchange of business content (document or folder) and it’s properties between business applications and the FileNet Content Management Repository and rides on the interoperability protocol specified by Content Management Interoperability Services (CMIS) v1.0 specification.

© 2010 IBM Corporation Outbound Interactions … where WPS/WESB applications access perform CRUD operations on the FileNet CE 4 FileNet P8 FooFolder WID ECM Adapter CMIS Bindings Discover & Select Content Types and it’s properties, generate BO and service imports WPS / WESB ECM Adapter Service Import invokes appropriate operations CMIS WS Bindings

© 2010 IBM Corporation Outbound support for ‘document’ and supported operations  Create - Creates document on the target system  Update - Updates both content and properties of the document  Delete – Deletes the document for the given ID or absolute path  Retrieve – Retrieves both content and properties of the document  RetrieveAll – Retrieves documents that match a specified criteria –Uses CMIS Query service. Query criteria to be defined as specified by CMIS  UpdateProperties - Updates document properties and not content  RetrieveProperties - Retrieves document properties and not content 5 During service discovery Adapter allows the user to select the document class and it’s properties and derives Business Object definitions out of these selections

© 2010 IBM Corporation Outbound flow – a quick view Moving the object to selected objects list will popup a new window where user has to enter target folder name and select the associated properties Display document class related information User can filter object store or documents based on criteria

© 2010 IBM Corporation Outbound flow - continues… Destination folder (optional) for document creation Required can’t be deselect by the user Custom properties provided by adapter (ex: remoteUrl, etc) Query to be used for RetrieveAll operation

© 2010 IBM Corporation Sample Outbound Service Interface - document 8

© 2010 IBM Corporation Sample Outbound Business Object Model - document Absolute URI for the remote document (ReST standard) Select and Where clauses to be used for RetrieveAll. Under the cover adapter to use CMIS Query interface to return matching documents

© 2010 IBM Corporation Outbound support for ‘folder’ and supported operations  Create - Creates folder on the target system  Update - Updates both content and properties of the folder  Delete – Deletes the folder for the given ID or absolute path  Retrieve - Retrieves both content and properties of the folder  RetrieveAll – Retrieves all folders that match a specified criteria –Uses CMIS Query service. Query criteria to be defined as specified by CMIS 10 During service discovery Adapter allows the user to select the select the target folder type and it’s properties and derives Business Object definitions out of these selections.

© 2010 IBM Corporation11 Sample Outbound Business Object Model - folder Select and Where clauses to be used for RetrieveAll. Under the cover adapter to use CMIS Query interface to return matching documents

© 2010 IBM Corporation Inbound Interactions … where WPS/WESB applications receive notifications about changes to document content residing in FileNet CE 12 WID ECM Adapter Discover, Select Content Types and it’s properties, choose document/folder change event types, generate BO and service exports WPS / WESB During startup… …Deploys the EventHandler …Makes event subscriptions …Creates Event Folder Starts polling for events as configured intervals Delivers events to endpoints by invoking the appropriate ‘emit’ methods of service exports CMIS WS Bindings Event handler event events Event folder FileNet P8 CMIS Bindings Whenever there is new event (like CREATE document, DELETE etc) event handler creates appropriate event docuements in the event folder FileNet Java APIs ECM Adapter CMIS does not specify for events subscriptions and handling. Hence to support the inbound scenario seamlessly with least intervention from user, FileNet Java APIs are leveraged. These APIs are used for making event subscriptions during Application deployment. After deployment the CMIS WS Bindings are used for the runtime behaviour. Persistent Event Store

© 2010 IBM Corporation Inbound Interaction (contd.)  Supports notification model for both Document and Folder  Supports AssuredOnceDelivery of events  Provides recovery management via persistence event store 13 Sample Inbound Business Object Model for a Folder

© 2010 IBM Corporation14 Sample Inbound Service Interface for Folder Sample Inbound Service Interface for Document

© 2010 IBM Corporation Iterative development support (for outbound and inbound)  Support for regeneration and reconfiguration of artifacts (import and export) that were previously generated during outbound and inbound process  Helps in addition of new object and removal of discovered object using the external service wizard via multiple launch points.

© 2010 IBM Corporation Highlights of the ECM adapter  Easy to configure and use – no coding required  Relieves the user of having to deal with content management semantics (such as repositories, folders, metadata etc.) and providers abstractions wherein Business applications model around Business Objects and operations on them  Provides the flexibility to model Business Objects with a select subset of properties and Services with a select set of operations that could either work with just document properties OR with document properties + content  Extensible to other content management systems in future 16

© 2010 IBM Corporation Back up

© 2010 IBM Corporation18 What is CMIS standard? Content Management Interoperability Service (CMIS) is a new specification which allows interoperability between Content Management Systems. The specification was approved by OASIS in May 2010.The standard currently defines a domain model and set of bindings that includes WebServices and ReSTful Atom Pub that can be used by applications to work with one or more Content Management repositories. TB VendorProductCMIS Support Timeline AlfrescoAlfresco 3.2Available for testing EMCDocumentumFirst half of 2010 IBMContent ManagerSecond First half of 2010 IBMFileNet P8Second First half of 2010 KnowledgeTreeKnowledgeTree 3.7Available for testing MicrosoftSharePoint Server 2010First half of 2010 NuxeoNuxeo DMS 5.3Available for testing Open TextEnterprise Library Services (ELS-Beta)CMIS connector available now Open TextOpen Text ECM 10Mid 2010 OracleOracle Universal Content ManagementNot known SAPSAP DMSNot known Sense/NetSense/Net 6.0Available for testing CMIS Support Timeline for various vendors from the market

© 2010 IBM Corporation Sample Outbound Service Interface - folder 19