Implementing WebSphere Business Integration Express for Item Synchronization

220 Implementing WebSphere BI Express for Item Synchronization

6. Stop the collaboration objects.

7. Redeploy the two changed collaboration objects.

8. Restart the InterChange Server.

11.4 Test the Catalog Item Confirmation

For the Catalog Item Confirmation, we will not make any changes to the

collaboration for processWorklist. We currently have this with a Port connector as

an end-point. For our testing purposes, this is sufficient.

We use the method from 11.2, “Process the response from UCCnet” on

page 212, but substitute the RCIR_Response file (number 15) with the CIC sent

to ITSO message (number 15). Check the InterChange Server log for any errors.

Also check the audit log. Ensure that there is an entry containing the following:

򐂰 Product ID 00094860443115

򐂰 Transaction type: CCnet_processWorklist_CATALOGUE_ITEM_CONFIRMATION

򐂰 Transaction status: SYNCHRONISED

This concludes the individual unit tests for each of the components. We now

move on to a full end-to-end test with what we have in place.

11.5 End-to-end simulation

We now have all of the configuration in place to run a full end-to-end simulation.

We will run our test without using a test connector (instead using the actual

JDBC connector).

1. Trigger an event from the catalog item application (using a DB2 command) to

start the item synchronization.

2. This sends the new item details to the iSoft connector and onwards through

the AS2 channel to our partner.

3. The response message is received by our AS2 channel.The iSoft connector

passes this message to the process worklist.

4. The process worklist processes the response and creates a CIN (since we

only have a single subscribing retailer) that is sent back through the AS2

channel to UCCnet.

Before we run this test, let’s ensure that we have a clean slate and a controlled,

known environment to work with. We want to make sure that there are no

Chapter 11. Final configuration and test from end-to-end 221

outstanding Work In Progress (WIP) items. Finally, we also want to clear the

audit logs so that we have a clear view of what we are looking at.

1. Shutdown the InterChange Server and all components.

2. In the additional materials, there is a script named CleanDB.bat. This goes

through and deletes any entries from the various Work In Progress tables in

the smb_db database. Run this script from a DB2 command window.

3. Clear the contents of the audit_log table so that we have a clean view to start

with (using a DB2 command window and deleting all rows from the table).

4. Ensure that the following components are running:

– InterChange Server

– JDBC connector

– JTextRWL connector

– iSoft connector

– P2P agents for both ITSO and UCCNET

5. As mentioned earlier, we have a small file to automate the placing of files in

the correct directories. We also have a set of files for this final test (found in

Appendix C, “Additional material” on page 259).

6. Open a command window and navigate to these files.

– Automate.cmd

– DB insert ITEM.txt

– RCIR_ADD_response.ITSO_16.xml

– CIC_SentTo.ITSO_16.xml

7. Using a DB2 command window insert a record into the item catalog using the

text contained in the DB insert ITEM.txt file, as shown in:

Figure 11-9 Insert record into item catalog

insert into smbadmin.item_catalog (productid, unitof_wgt, description,

descriptionshort, upceancode) values('00094860443116', '1', 'Really cool thing

that we make to sell', 'COOLITEM1', '00094860443116')

8. Once you have seen the RCIR_ADD be transmitted across the AS2 channel

to the ‘UCCNET’ receiver and the MDN be received back again, enter

Important: Be judicious in the use of a script such as this one. It should never

be used in anything other than a development environment and only in a

controlled fashion!