You must create the required connector between IBM® Content Integrator
and the Content Platform Engine object store in which the metadata for the
federated documents is to be stored.
Before you begin
Before you create the
FileNet® P8 connector, ensure that you
created and updated the necessary connectors between
IBM Content Integrator and
the external repositories that contain the original documents.
In highly
available environments, you must install and update IBM Content Integrator
connectors on every node.
Procedure
Create the Content Platform Engine to IBM Content Integrator connector. The connector name must match the object store name. Deploy the connector as a stand-alone
remote method invocation (RMI) proxy connector. The connector cannot be deployed as a web
application archive.
If you use the IBM
WebSphere® Application Client for WebSphere Application Server on your development client
workstation, you must have the same JRE on the WebSphere
Application Server and on the server on which the RMI proxy server is running. For configuration
instructions, see Setting Up a Thick Client Development Environment.
See the
IBM Content Integrator documentation for instructions about creating a
Content Platform Engine to
IBM Content Integrator connector. Use
the procedure that is appropriate to your application server. When you test the connector, you are
prompted for valid object store credentials.
Important: For high
availability environments, use the following URLs to point to the
Content Platform Engine Cluster:
Table 1. Remote server URL addressesServer |
Remote URL |
WebSphere Application
Server
|
Remote Server
URL: iiop://node1 name:node1 port,
node2 name:node2 port/FileNet/Engine
Remote Server Upload
URL: iiop://node1 name:node1 port,
node2 name:node2 port/FileNet/Engine
Remote Server Download
URL: iiop://node1 name:node1 port,
node2 name:node2 port/FileNet/Engine
This configuration requires the WebSphere cluster name in addition
to the node names as part of the URL. The default bootstrap port (for example, 9810) is different
from the non-default (for example, 2809) on a non-cluster configuration (that is, a stand-alone
WebSphere installation).
|
Oracle WebLogic Server
|
Remote Server
URL: t3://node1_name:node1_port,
node2_name:node2_port/FileNet/Engine
Remote Server Upload
URL: t3://node1_name:node1_port,
node2_name:node2_port/FileNet/Engine
Remote Server Download
URL: t3://node1_name:node1_port,
node2_name:node2_port/FileNet/Engine
|
JBoss Application Server
|
Remote Server
URL: jnp://node1_name:node1_port,
node2_name:node2_port/FileNet/Engine
Remote Server Upload
URL: jnp://node1_name:node1_port,
node2_name:node2_port/FileNet/Engine
Remote Server Download
URL: jnp://node1_name:node1 port,
node2_name:node2_port/FileNet/Engine
|