IBM BPM, V8.0.1, All platforms > Create processes in IBM Process Designer > Modeling processes > Integrating with Enterprise Content Management (ECM) systems

Adding an Enterprise Content Management server

You need at least one Enterprise Content Management (ECM) server for the service you develop. You specify the connection properties to access an ECM server on the Process App Settings Servers page for a process application or on the Toolkit Settings Servers page for a toolkit. Adding the server to the Toolkit Settings Servers page allows the connection properties to be reused.

To add a server, follow these steps.

Procedure

1. Select the Servers tab from the Process App Settings editor. You see the Process App Settings editor when you first click Open in Designer from a newly created process application in the Process Center. Alternatively you can select Process App Settings from the drop-down list on the toolbar in Process Designer.
2. Beneath the Servers heading click Add. Beneath the Server Details heading, enter a meaningful name for server. From the drop-down list in the Type field, select Enterprise Content Management Server. Enter a meaningful description of the server in the Description field. This field is optional.
3. Beneath the Server Locations heading, enter the following information.
   • Environment Type: The environment of the Enterprise Content Management server. Enter the server location information (host name, port, context path, whether it is a secure server, repository name, user ID, and password) for each environment type. These environments are described in the product overview. Modify the IBM Process Server environment.shows you how to change these types. If you do not provide values for these environments, the values from the default environment type are used.
     • Default: If you do not provide values for the following environment types, default values are used.
     • Development: The environment where you develop your services.
     • Test: The environment where you test your services.
     • Staging: The environment where you deploy your services for pre-production testing.

     • Production: The environment where your services are deployed for use by your organization.

   • Hostname: The host name of the Enterprise Content Management server. Specify an IP address or a host name and domain.

     For example:

     myHost.labwide.ibm.com

   • Port: The port number of the Enterprise Content Management server.
   • Context Path: The path to the Content Management Interoperability Services (CMIS) web services application on the server.
   • Secure server: Specify whether you want your service to be secure, that is, to use the Hypertext Transfer Protocol Secure (HTTPS) protocol by selecting this check box. If you select the HTTPS protocol, configure HTTPS security, as described in Access an IBM Case Manager server using the SSL.

   • Repository: The name of your repository.

   • Userid: The user ID to connect to the Enterprise Content Management server.
   • Password: The password of the user ID connecting to the Enterprise Content Management server.

   • Always use this connection information:

     If selected, which is the default, only this user ID and password are used for authentication.

     For example, a human service, which your service is associated with when a Document List or Document Viewer is configured, also has a user context. An administrator uses the Manage Users function to specify human service users. Selecting this check box means this user ID and password overrides any other user information.

4. Click Test Connection to confirm the connection to the server works.
5. Save your work. From the menu, select File > Save All.

   You can change these settings at run time. See Changing Enterprise Content Management server settings.

Integrating with Enterprise Content Management (ECM) systems

Related concepts:
Authentication scenarios
Use the event handler for FileNet Content Manager

Related tasks:
Create an event handler for an Enterprise Content Management system
Building a service that integrates with an Enterprise Content Management system