Implementing WebSphere Business Integration Express for Item Synchronization

44 Implementing WebSphere BI Express for Item Synchronization

6. UCCnet sends a response to the supplier in the form of a message containing

the CIC information from the retailer.

5.3 Technical process overview

Now we can outline each of the stages of the processing for adding a new item to

UCCnet. Each stage is referred to as a workflow in this instance.

5.3.1 ItemAdd workflow (add a new item to UCCnet)

The following steps occur in the ItemAdd workflow:

1. An event occurs in the supplier ERP system that provides the item data to the

connector. (In this example, we use the JDBC Connector that polls for new

item events.)

2. The JDBC Connector converts the input from the supplier into an

application-specific business object.

3. The JDBC Connector passes the application-specific business object to the

InterChange Server.

4. The mapping services of the InterChange Server are called and mapping is

performed to transform the application-specific business object into a generic

ItemBasic business object (with a Create verb).

5. The UCCnet_ItemSync collaboration object accepts the object on its From

port and checks that required fields contain information. (This check verifies

that item data exists for fields required by UCCnet.)

6. If all required fields are complete, the collaboration object continues

processing it. If all required fields are not complete, the collaboration object

aborts processing and sends an email to a configured address (in our

scenario, a Port connector).

7. The UCCnet_ItemSync collaboration object adds an entry for the new item to

the PROCESSED_GTIN table, setting the value for the withdrawn field for this

entry to N.

8. The UCCnet_ItemSync collaboration object adds an entry to the audit_log

table to identify the ItemAdd transaction processed.

9. The UCCnet_ItemSync collaboration object delivers the ItemBasic business

object to the ItemCommandRouter collaboration object.

10.The ItemCommandRouter collaboration object receives the business object

and determines that it represents an item to be added to UCCnet. Then, it

passes the business object to the TO_RCIR port.

Chapter 5. Business case and scenario 45

11.The ItemBasic business object is converted into an application-specific

business object by the

CwItemBasic_to_UCCnetXSD_envelope_

registerCommand_itemAddChange

map.

12.Once the conversion is complete, the business object is passed to UCCnet

through the AS2 channel connector (in our scenario, the iSoft P2P Agent

Connector).

13.The connector sends the business object to the Data Handler for XML, which

produces the ItemAdd XML message in UCCnet format.

14.The connector then passes the message to the AS2 channel server (in our

scenario, the iSoft P2P Agent Express).

15.The AS2 channel server creates the digest. Then, it encrypts and then

transmits the ItemAdd message to UCCnet.

16.An RCIR_ADD_Response notification is generated by UCCnet to indicate a

successful ItemAdd. This notification is returned to the AS2 channel server.

17.The AS2 channel server delivers the notification to the AS2 channel

connector.

18.The AS2 channel connector sends the notification to the Data Handler for

XML, which converts it into a UCCnetXSD_envelope business object. The

business object contains the entire UCCnet notification, including each

individual data instance and the commands related to it.

19.The business object is passed to the InterChange Server.

20.The mapping services are invoked. The application-specific business object

is converted to a UCCnetGBO_envelope business object by passing through

the UCCnetXSD_envelope_to_UCCnetGBO_envelope map.

21.The generic business object is passed to a UCCnet_processWorklist

collaboration object.

22.The UCCnet_processWorklist collaboration object receives the business

object on its From port, identifies it as an RCIR_ADD_RESPONSE

notification, and dispatches it to its RCIR_ADD_RESPONSE subdiagram.

5.3.2 CatalogueItemNotification_Add workflow

As a result of the ItemAdd workflow, UCCnet has been updated with the new

item information. Now, the supplier's demand-side trading partners must be

made aware that the item is available. This on-going process is referred to as the

CatalogueItemNotification_Add workflow.

The RCIR_ADD_RESPONSE subdiagram does the following: