170 Implementing EDI Solutions
4. The TPI connector initiates mapping from the generic ItemBasic business object to the
application-specific UCCnet_envelope business object, builds a UCCnet ItemAdd XML
document from the UCCnet_envelope business object, and sends the ItemAdd document
to the TPI Server.
5. The TPI Server uses the trading partner profile for UCCnet, creates the digest, encrypts,
and transmits the ItemAdd document to UCCnet.
6. The Message Disposition Notification (MDN) is generated by UCCnet and returned to the
TPI Server.
7. The UCCnet_requestWorklist collaboration uses the JTextRWL sample connector to poll a
worklist directory on the InterChange Server for an XML message containing a response
Item_Add notification from UCCnet.
8. When the JTextRWL sample connector finds an XML file in its input folder for events, it
transforms and maps the message to a generic UCCnetGBO_envelope business object,
and delivers the business object to the UCCnet_requestWorklist collaboration.
9. The UCCnet_requestWorklist collaboration delivers the business object to the TPI
connector. The TPI connector initiates mapping from the generic UCCnetGBO_envelope
sample business object to the application-specific UCCnet_envelope business object,
builds an XML document from the UCCnet_envelope business object, and sends the XML
document to the TPI Server. The TPI Server uses the trading partner profile for UCCnet,
creates the digest, encrypts, and transmits the XML document to UCCnet.
10.UCCnet generates an MDN and returns this worklist response message to the TPI Server.
The TPI connector transforms the message into a UCCnet_envelope business object,
maps it to a UCCnetGBO_envelope sample business object, which it then sends to the
UCCnet_processWorklist collaboration.
11.The UCCnet_processWorklist collaboration processes the generic
UCCnetGBO_envelope sample business object. It identifies the business object as
representing an ITEM_ADD notification response. It is dispatched to the specific
ITEM_ADD_CHANGE sub-collaboration.
12.This collaboration then sends a UCCnetGBO_envelope sample business object for
ItemPublicationAdd to the TPI connector. The TPI connector builds the UCCnet XML
document from the UCCnet_envelope business object and delivers this ItemPublication
document to the TPI Server.
13.The TPI Server uses the trading partner profile for UCCnet, creates the digest, encrypts,
and transmits the document to UCCnet.
14.The MDN is generated by UCCnet and returned to the TPI Server.
15.The UCCnet_requestWorklist collaboration sends another request for notifications.
4.3 Installation of Item Sync collaboration
The UCCnet Item Sync Collaboration represents synchronization activities between a
supplier and UCCnet. The architectural components involved are the supply-side trading
partner legacy systems, the InterChange Server (ICS), various specific connectors (which
communicate between legacy systems and the ICS), and the Trading Partner Interchange
Server (TPI), which provides Internet access to the UCCnet system. These components are
shown in Figure 4-2 on page 171.

Get Implementing EDI Solutions now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.