The party_trickle_load job processes continuous updates
(insert and update interactions) that are made to the on-premises
MDM data and propagates the updates to the Cloudant® cache. The job must run continuously
for updates to propagate to Cloudant.
Use this procedure to configure the party_trickle_load job for your
environment. This task requires access to IBM® InfoSphere® DataStage® and QualityStage® Designer client.
Before you begin
You must complete the
Enabling MDM Broadcast Notification task
before running this job.
You must also verify that you have the
following
IBM WebSphere® Application Server JAR
files available.
- /usr/IBM/WebSphere/AppServer8.5/runtimes/com.ibm.ws.ejb.thinclient_8.5.0.jar
- /usr/IBM/WebSphere/AppServer8.5/runtimes/com.ibm.ws.messagingClient.jar
- /usr/IBM/WebSphere/AppServer8.5/runtimes/com.ibm.ws.sib.client.thin.jms_8.5.0.jar
This task assumes that you have already completed an initial
bulk data load from MDM to the Cloudant cache.
About this task
InfoSphere MDM has
a predefined JMS Queue. The MDM and Cloudant integration
sample uses MDM Change Broadcast Queue (com/ibm/mdm/messaging/ChangeBroadcastQueue).
Procedure
- Open the Designer client and import the party_trickle_load.dsx file
from the opt/mdm_integration/com.ibm.mdm.integration.cloudant/datastagejobs directory.
- Open the party_trickle_load job.
- Select .
- On the party_trickle_load - Job Run Options dialog,
provide values for the following job parameters.
| Property |
Description |
|---|
| user |
Enter your Cloudant account
ID. |
| pwd |
Enter your Cloudant password. |
| MDM userid |
Enter the ID used to connect to the MDM operational server. |
| MDM password |
Enter the password to connect to the MDM operational server. |
| Cloudant DB userid |
Enter the ID to access the Cloudant database. |
| Cloudant DB |
Enter the name of the Cloudant database
on which the JSON documents are stored. |
| DB2® MDM DB |
Enter the name of the MDM database from which to retrieve
entity data. |
| DB2 userid |
Enter the ID to access the MDM database. |
| DB2 password |
Enter the password to access the MDM database. |
| MDM Host/Port |
Enter the name and port for the MDM operational server in hostname:port format. |
| Initial Context Factory |
Use com.ibm.websphere.naming.WsnInitialContextFactory |
| Provider URL |
Use corbaloc::localhost:9810 |
| Connection Factory |
Use com/ibm/mdm/messaging/ResponseQueueConnectionFactory (or
whatever the JNDI name is for the queue connection factory). |
| Destination |
Use com/ibm/mdm/messaging/ChangeBroadcastQueue (or
whatever the JNDI name is for your queue). |
| SSL Config URL |
Use file:WebSphere_install_home/profiles/Node01/properties/ssl.client/props |
| JMS Classpath |
Enter the following: tmp/build;/usr/IBM/WebSphere/AppServer8.5/runtimes/com.ibm.ws.ejb.thinclient_8.5.0.jar;/usr/IBM/WebSphere/AppServer8.5/runtimes/com.ibm.ws.messagingClient.jar;/usr/IBM/WebSphere/AppServer8.5/runtimes/com.ibm.ws.sib.client.thin.jms_8.5.0.jar;/tmp/xercesImpl.jar
where tmp/build is
the root installation directory of the MDMListener.class (not
counting the package path) and where usr/IBM/WebSphere/AppServer8.5 is
the install location for IBM WebSphere Application Server 8.5.
|
- Click Run.