Definitions and terminology

Definitions of terminology used in the guide.

Definitions of connector and adapter

The term connector used throughout refers to the runtime portion of an IBM® WebSphere® Business Integration Adapter. References to specific connectors are related to specific adapters, as follows:
Term Usage
iSoftConnector The runtime portion of an IBM WebSphere Business Integration Adapter for iSoft.
TPIConnector The runtime portion of an IBM WebSphere Business Integration Adapter for Trading Partner Interchange.
JMSConnector The runtime portion of an IBM WebSphere Business Integration Adapter for Java™[tm ] Message Service (JMS).
JTextConnector The runtime portion of an IBM WebSphere Business Integration Adapter for JText.
JTextISoftConnector The runtime portion of an adapter based on the IBM WebSphere Business Integration Adapter for JText.
JTextTPIConnector The runtime portion of an adapter based on the IBM WebSphere Business Integration Adapter for JText.
JTextJMSConnector The runtime portion of an adapter based on the IBM WebSphere Business Integration Adapter for JText.
WebSphereMQWorkflowConnector The runtime portion of an IBM WebSphere Business Integration Adapter for WebSphere MQ Workflow.

The way you connect to UCCnet determines the connector that you use to communicate with it.

If you exchange messages with UCCnet using an AS2/EDIINT interface protocol, you can use a TPIConnector, an ISoftConnector, or you can use WebSphere Business Integration Connect in conjunction with a JMSConnector.

Use the TPI connector if you communicate with UCCnet through Trading Partner Interchange servers.

Use the ISoftConnector if you communicate with UCCnet through an iSoft Peer-to-Peer Agent.

Use the JMS connector if you communicate with UCCnet through WebSphere Business Integration Connect.

If you exchange messages through the UCCnet Command Line Utility (CLU) or are testing your installation, you can use either a JTextTPIConnector, a JTextISoftConnector, or a JTextJMSConnector.

Because the actual connector you use is dependent on your set up, this documentation uses "AS2 channel connector" as a general term for any of the TPIConnector, iSoftConnector, JMSConnector, JTextTPIConnector, JTextISoftConnector, and JTextJMSConnector.

Schema and DTD terminology

The information in the following sections outlines how the Product Information Management for Retailers solution handles publication information notifications (in systems supporting the UCCnet DTD) or Catalogue Item Notifications (in systems supporting the UCCnet XSD). Because the collaboration templates within the Product Information Management for Retailers solution are schema-based, in DTD-based systems, the solution maps incoming DTD-based publication information notifications into XSD-based Catalogue Item Notifications during processing, and converts outgoing XSD-based Catalogue Item Confirmation commands into DTD-based Authorization commands at the end of solution processing. For simplicity, the solution will be discussed throughout using schema terminology only.

Definitions of NULL and BLANK

The terms NULL and BLANK are defined as true responses when the attributes are tested using the business object methods isNull() and isBlank(), respectively. The method isNull() returns true when a value has never been set in an attribute. The method isBlank() returns true when the attribute contains a zero-length string. An attribute containing a space character is not considered BLANK by the isBlank() method.

Parent topic: Solution Development Guide