Scenarios and Model Information

UML Diagrams

Description Comment
Publish RequestThis Object Sequence Diagram explains the activities that follow a request to "Publish Files" on a Topic configured for Connections to the Post Office using SOAP Protocol. This covers the activities in the first portion of the Demos where data moves from your PC to the Post Office. In order to move files, 2 things must occur. There must be a connection established between the 2 Hosts that must share data. And then, according to its specific Connect Protocol ( API ), there must be issued to the Connection, commands like Call.

In the Diagram, a DataChannel class corresponds to a Protocol implementation under which SOAP Call occurs on a SOAP Connection. Once the data arrives at the Post Office, Subscriber activities commence. see below.
Process Subscriptions TriggerThis Object Sequence Diagram explains the Post Office activities on the Back-End that follow the upload depicted in the above diagram. Some of the model is the same because the Post Office is doing many of the same things, getting connections, issuing commands, and moving data. However, there are some important differences. Data Translation and mapping may occur depending on the Schema requirments of each subscriber. Dispatchers and ConnectionPools provide the scalability that may be needed in the event a single Topic has many subscribers.

When data is posted by a Publisher, the PostOffice quickly returns an ACK to the client and then fires a dispatch Trigger on a different thread whose responsibility is to Distribute Uploaded files to Subscribers. ForEach Subscriber, there is a connection retreived from a Pool. And then, according to specific Connect Protocol ( API ) that was configured when the Subscriber registered an interest in the Topic, a command like put, get, upload, copy, send issued to the Connection. Following data moving commands, Connections are returned to the Pool. If needed, there may also be a Translation Step utilizing standard Java XML transform API's (XSLT) for DataMapping Requirements.

B2BPO has an Object Model employing a number of interfaces and various Contexts. Decoupled design like this allows the flexibility required to handle similar behavior across a Set of Connection API's including FTP, SOAP, SSH, HTTP, and XSL.