Chapter 2. Insurance industry call center scenario 107
7. Select WebSphere as the Application Server from the pull-down list. This
displays the default properties of JNDI. Check the port number that the
java.naming.provider.url property is set to use (2810 in Figure 2-40), and
ensure that it is the same as the iiceServer’s name server port recorded
during the deployment process.
Figure 2-40 JNDIInfo Editor 2/2
108 WebSphere Information Integrator Content Edition: Planning, Configuration, and Monitoring Guide
8. In our case, this was 2811 and the port number is modified accordingly as
shown in Figure 2-41. Click OK to save the changes and update your default
application server settings. Then click Lookup to test the communication with
the application server.
Figure 2-41 Update JNDIInfo Editor
9. A successful lookup will display as shown in Figure 2-42. Click OK to close
Figure 2-42 Naming lookup succeeded message
Chapter 2. Insurance industry call center scenario 109
10.To test the connection to the Documentum repository, right-click
DocumentumConnector. Select Test Connection.
Figure 2-43 Test Connection
Note: The RMI Proxy Connector must be running on the connectors-only
110 WebSphere Information Integrator Content Edition: Planning, Configuration, and Monitoring Guide
11.Provide logon information to the Documentum repository as shown in
Figure 2-44, and click OK to test the connection.
Figure 2-44 Logon information
A successful connection will display as shown in Figure 2-45.
Figure 2-45 Connection succeeded message
This completes the successful configuration of the Documentum connector using
the RMI Proxy Connector server on the Windows platform.
After the various connectors have been configured using the administration tool,
you can export these configurations to an XML file for import into other
WebSphere Information Integrator Content Edition servers.
The following sections describe the process of exporting the configurations of
DB2 Content Manager connector, FileNet IS connector, and Documentum
connector. It also describes importing one of these XML files into another
WebSphere Information Integrator Content Edition server.