14 Implementing WebSphere BI Express for Item Synchronization
򐂰 GTIN Query
Retrieves the 35 elements defining the GTIN from the GLOBALregistry
򐂰 Other Queries
Organizations
1.7 UCCnet message structure
Now we move on to the structure of the UCCnet messages. All UCCnet
messages are XML (either schema or DTD). For our solution in this redbook, we
have chosen to use schema (XSD)-based messages.
There are three layers in an XML document, as follows:
򐂰 Transport:
How does the message get from A to B?
򐂰 Command:
What function needs to be performed when the message arrives?
򐂰 Document/Data:
What information does the command act upon?
1.7.1 Envelope: transport layer
򐂰 messageHeader (See Example 1-1.)
elements to, from, messageIdentifier, userId, password, representingParty
Example 1-1 messageHeader
<?xml version="1.0" encoding="UTF-8" ?>
- <uccnet:envelope communicationVersion="2.2"
xmlns:uccnet="http://www.uccnet.org/schemas/2.2/uccnet"
xmlns:eanucc="http://www.uc-council.org/smp/schemas/1.3/eanucc"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.uccnet.org/schemas/2.2/uccnet
../../schema/uccnet/2.2/Envelope.xsd">
- <messageHeader>
- <messageIdentifier>
<value>RCIR-MSGID-001</value>
</messageIdentifier>
<userId>RCIRUSER001</userId>
- <representingParty>
<gln>0101010101010</gln>
Chapter 1. UCCnet 15
</representingParty>
</messageHeader>
򐂰 body (See Example 1-2.)
Either a response or a transaction element.
Example 1-2 body
<?xml version="1.0" encoding="UTF-8" ?>
- <uccnet:envelope communicationVersion="2.2"
...
- <messageHeader>
....
</messageHeader>
- <body>
- <transaction>
- <entityIdentification>
<uniqueCreatorIdentification>RCIR-TXID-001</uniqueCreatorIdentification>
- <globalLocationNumber>
<gln>0101010101010</gln>
</globalLocationNumber>
</entityIdentification>
-<command>
....
</command>
</transaction>
</body>
</uccnet:envelope>
1.7.2 Transaction: Command layer
򐂰 entityIdentification
Who created the transaction, including GLN
uniqueCreatorIdentification: acts as a transaction ID
򐂰 command
queryCommand, notifyCommand
See Figure on page 16.
Example 1-3 Transaction
<transaction>
<entityIdentification>
<uniqueCreatorIdentification>99</uniqueCreatorIdentification>
<globalLocationNumber>
16 Implementing WebSphere BI Express for Item Synchronization
<gln>4134456747001</gln>
</globalLocationNumber>
</entityIdentification>
<command>
...
</command>
</transaction>
Command layer: Register command
򐂰 registerHeader
entityIdentification, used to acknowledge the command
registerCommandListEnum (ADD, DELETE, CHANGE...).
򐂰 registerOperand
registerCatalogueItem (for Add, Change, and Correct commands)
or registerCatalogueItemKey (for Delete command)
or registryCatalogueItemQuery (for Query command).
See Example 1-4.
Example 1-4 Register command
- <command>
- <uccnet:registerCommand
xmlns:uccnet="http://www.uccnet.org/schemas/2.2/uccnet">
- <registerCommandHeader type="ADD">
- <entityIdentification>
<uniqueCreatorIdentification>RCIR-ADDID-001</uniqueCreatorIdentification>
- <globalLocationNumber>
<gln>0101010101010</gln>
</globalLocationNumber>
</entityIdentification>
</registerCommandHeader>
- <registerCommandOperand>
+ <eanucc:registryCatalogueItem ...
</registerCommandOperand>
</uccnet:registerCommand>
</command>
Document layer: UCCnetRegistryCatalogueItem
򐂰 informationProviderOfTradeItem
Mandatory element, can be same as item brand owner.
򐂰 brandownerOfTradeItem

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.

Start your free trial