Chapter 9. Configuration for integration of back-end system 189
9.7 Validation using the Test Connector
We now need to validate that the data can be received by the JDBC connector
and successfully passed into the ItemSync collaboration. We have already
shown that the data will be passed from the ItemBasic business object to the
OUTBOX of the iSoft connector. However, we need to validate that the mapping
from ASBO to GBO can also be successfully passed into this process.
1. Start the iSoft connector.
2. Start a Test connector.
3. From the Test connector select File
Create/Select profile.
4. Create a profile for the JDBC connector as shown in Figure 9-25.
Figure 9-25 New profile
5. Connect to the ICS using this profile. See Figure 9-26 on page 190.
190 Implementing WebSphere BI Express for Item Synchronization
Figure 9-26 Connect to server
6. From the drop-down box, select the SUPPLIER_ITEM_CATALOG business
object.
7. Load (or manually create) the SUPPLIER_ITEM_CATALOG business object
that was used for the map test.
8. Give the business object a name (Test in our example below). See
Figure 9-27 on page 191.
Chapter 9. Configuration for integration of back-end system 191
Figure 9-27 ASBO ready to send
9. Select synchronous mode and send the business object.
10.When prompted for the collaboration, we select the
UCCnet_ItemSyncObject collaboration from the drop-down list. See
Figure 9-28.
Figure 9-28 Select collaboration
11.The business object is sent to the ICS for processing and the
ItemCommandRouterObject will eventually send the UCCnet envelope
message to the OUTBOX queue for the iSoft connector as before.
12.Check the contents of the queue for a message that contains the data that we
have sent in our business object. As before, use RFHUTIL to check that the
message looks similar to Figure 9-29 on page 192.
192 Implementing WebSphere BI Express for Item Synchronization
Figure 9-29 UCCnet message on outbox queue
13.Start the Web system monitor application, if it is not already running.
14.Select the Collaboration Overview and check that the Total Flows counter
on the ItemCommandRouterObject has been incremented.
Note: If you do not have a message on the queue, check the log and trace file
for each of the connectors and also the InterChange Server. (When we turned
on the LogAtInterchangeEnd property on for the connectors, it resulted in a
great deal of useful trace information in the ICS log).

Get Implementing WebSphere Business Integration Express for Item Synchronization now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.