To create feeds from a DB2® Content Manager repository, you must open a port number on the DB2 server and copy three JAR files from the IBM® DB2 Information Integrator for Content library.
Before you begin
- You need a connection to a server running IBM DB2 Content Manager, Version 8.4.
- The port 50000 on the Content Manager server must be accessible from the MashupHub server
- IBM DB2 Information Integrator for Content, V8.4 is required. The DB2 Information Integrator for Content contains three JAR files that you must copy to the MashupHub server. The DB2 Information Integrator for Content is included in IBM DB2 Content Manager Enterprise Edition. It is not, however, installed with the DB2 Content Manager product. You must install it in addition to DB2 Content Manager. Installation instructions for the DB2 Information Integrator for Content are in the IBM DB2 Content Manager information center topic: Installing and configuring DB2 Information Integrator for Content.
If you are installing the DB2 Information Integrator for Content only to access the three JAR files, you do not need to install the Web Services toolkit or run the configuration wizard.
About this task
Windows systems use backslashes (\) to delimit directories in a directory path. AIX® and Linux® systems use forward slashes (/) as delimiters. This information uses backslashes (\) to delimit directories in paths that apply to all operating systems; depending on the system that you are using, you might have to enter the directory path differently than shown.
To configure the DB2 Content Manager server, you copy three JAR files and the cmbicmenv.ini
file to the MashupHub server. Then you must edit the cmbicmenv.ini
- Copy three JAR files from the DB2 Information Integrator for Content library to the MashupHub server:
- In the DB2 Information Integrator for Content library, locate the following files: cmbsdk81.jar, cmb81.jar, and cmbview81.jar in one of the following locations:
Use the WebSphere® Administration Console to stop MashupHub.
Copy the three JAR files into the MashupHub Content Manager connector directory:
- On Windows®: C:\\Program Files\\IBM\\db2cmv8\\lib
- On Linux or UNIX®: /opt/IBM/db2cmv8/lib
On the Content Manager server, locate the cmbicmenv.ini file in one of the following locations:
Copy the cmbicmenv.ini file to the cm_ini_files directory on the MashupHub server:
- On Windows: C:\\Program Files\\IBM\\db2cmv8\\cmgmt\\connectors
- On UNIX : /opt/IBM/db2cmv8/cmgmt/connectors
Rename the cmbicmenv.ini file to CM-hostname_domainame_suf-icmServerName.ini
Restart MashupHub. You can use the WebSphere Administration Console to restart MashupHub.
Make sure that the default port 50000 is open on the DB2 Content Manager server.
The parts of the renamed file have the following values:
The network name and domain of the DB2 Content Manager server. Replace the periods with underscore characters. For example, for mycompany.workplace.com, type mycompany_workplace_com.icmServerName
The name of the DB2 Content Manager server.
Example of a renamed cmbicmenv.ini
What to do next
To connect to the DB2 Content Manager repository, users will need the following information:
- Username and password for the Content Manager repository.
- The Hostname (network name and domain) of the Content Manager server. This name must match the hostname you entered in the modified cmbicmenv.ini file for the hostname_domainame_suf value. However, when users enter the hostname in the MashupHub interface when they create the feed, they must use the period separators in the hostname. For example, mycompany.workplace.com.
- The Port number (50000).
- The Content Manager server name. This name must match the DB2 Content Manager server you entered in the modified cmbicmenv.ini file for the icmServerName value.
- The database for the Content Manager repository.
- The database schema for the database of the Content Manager repository.
Parent topic: Configuring enterprise Content Manager servers for feeds: imc3