- Note:
- The reader should be familiar with IBM(R) WebSphere(R) Business
Integration Express system components, the UCCnet(R) message set, the
UCCnet Document Type Definition (DTD), and the UCCnet XML Schema Definition
(XSD), and have access to UCCnet documentation and UCCnet eRoom digital
workplaces.
The UCCnet DTD and XSD define standards for the item information exchanged
between UCCnet trading partners and for the requirements of the iSoft
Peer-to-Peer Agent, which enable the exchange of data in the form of XML
messages. Depending upon the XML definition type (DTD or XSD), the
WebSphere Business Integration Express system does the following:
- If the DTD XML definition type is used, it transforms UCCnet XML messages
into UCCnetDTD_envelope business objects, which are then passed through the
UCCnetDTD_envelope_to_UCCnetGBO_envelope map.
- If the XSD XML definition type is used, it transforms UCCnet XML messages
into UCCnetXSD_envelope business objects, which are then passed through the
UCCnetXSD_envelope_to_UCCnetGBO_envelope map.
These maps insert default values for the XMLDeclaration and DocType
attributes, so these values are in place when the resulting UCCnetGBO_envelope
business object is processed by collaboration objects.
The UCCnetGBO_envelope business object is based on the UCCnet XSD and is
typically used to exchange data between the runtime connector portions of
specific adapters and collaboration objects. The attributes of the
business object cover the business information types that are published
between trading partners in the UCCnet environment.
- Note:
- The term "connector" used throughout this document refers to the
runtime portion of an adapter. References to specific connectors are
related to specific adapters, as follows:
- "iSoftConnector" refers specifically to the runtime component of an
Adapter for iSoft.
- "JTextISoftConnector" refers specifically to the runtime component of an
adapter based on the Adapter for JText.
If you are exchanging messages with UCCnet through an AS2/EDIINT interface
protocol, use an iSoftConnector. If you are exchanging messages through
the UCCnet Command Line Utility (CLU) or testing your installation, use a
JTextISoftConnector.
The UCCnetGBO_envelope business object is a hierarchical business
object. The following table shows its structure.
Table 1. Attributes for UCCnetGBO_envelope business object
Name
| Type
| Key
| Cardinality
|
TPIRouteInfo
| N/A
|
|
|
XMLDeclaration
| String
|
|
|
DocType
| String
|
|
|
ROOT
| UCCnetXSD_ROOT_envelope
| x
| 1
|
The UCCnetGBO_envelope business object includes attributes based on the
following child business object:
- UCCnetXSD_ROOT_envelope
- This child business object is a hierarchical business object. It
contains child business objects for the message header and for the body of the
message. The child business object representing the body of the message
contains additional child business objects that represent different types of
information used for items in UCCnet. UCCnetXSD_envelope and its nested
child business object definitions contain exactly the same attributes,
sequence, and structure that are specified in the UCCnet XSD. See
UCCnet documentation for more information on the attributes required by
UCCnet.
The UCCnetGBO_envelope business object supports the following verbs:
- Request Processing (sending to the destination application): Create
- Event Notification (receiving from the source application): Create
To examine a listing of the attributes of the UCCnetGBO_envelope business
object, use the System Manager or Business Object Designer.
For more information on related business objects, see the following:
