The connector's internal business objects are used as transitional data wrappers, as data is pulled off the network (in event mode) and as it is being fed to the network (in service call request mode).
In event mode, the connector functions as a TCP server, listening on a socket for requests from remote applications to establish a channel to transmit data. The connection management subcomponent establishes the connection and manages the incoming data stream from the network, including load balancing and setting up parallel processes to handle multiple requests. As the data flows in, it is passed off to the message processing component where it is held in a BIA_ContentBO, the basic data wrapper.
Figure 2. BIA_ContentBO in the Business Object Designer
The pertinent attributes of the BIA_ContentBO are as follows:
BO Level Attributes | Description |
---|---|
Content | Stores application or protocol data |
The content object is contained in a BIA_InputMessage business object. The input message object may initially include complete and incomplete messages from the remote application. The connector separates complete and incomplete messages, queuing the incomplete messages until they are complete, and sending completed messages, wrapped in their BIA_InputMessage objects, to the PIMO framework where some forms of pre-processing may be done before they are passed on to the data handler for final processing.
Figure 3. BIA_InputMessage in the Business Object Designer
The pertinent attributes of the BIA_InputMessage object are as
follows:
BO Level Attributes | Description |
---|---|
CharSet | Encoding applied to the incoming bytes |
Content | Stores content coming in the socket as BIA_ContentBOs. It is of N cardinality because attribute length is limited compared to length of incoming message |
In service call request mode, the WBI business objects that represent messages to be transmitted to the remote application are sent from the integration broker. These objects are translated into the appropriate message form by the data handler. The connector wraps this message data in a BIA_ContentBO which is contained in a BIA_ApplicationMessage object. The message data may be subject to PIMO post-processing, after which the connector, acting as a TCP client, sends the message data back out over the TCP/IP network to a target specified in the connector configuration file.
Figure 4. BIA_ApplicationMessage in the Business Object Designer
The pertinent attributes of the BIA_ApplicationMessage object are as
follows:
BO Level Attributes | Description |
---|---|
Charset | Encoding applied on incoming bytes |
Content | Stores content coming in from the data handler as BIA_ContentBOs. It is of N cardinality because attribute length is limited compared to length of incoming message |
There are two other general internal business objects used by the connector: the BIA_ResponseMessage object, which contains any acknowledgement message--wrapped in a content object--from the remote application as a result of a service call request; and BIA_FinalMessage object, which contains information for the connection management subcomponent itself. The definition files for all internal business objects and meta objects are stored as XML schema files (.xsd) in the following directories: ProductDir\connectors\TCPIP\Samples for Windows and ProductDir/connectors/TCPIP/Samples for UNIX. They can be viewed either using the Business Object Designer or an XML-capable browser.