Senders are transport specific. WBI-C ships with senders for FTP/S, JMS, File, SMTP, and HTTP/S transports. To add a new capability to the WBI-C system, such as adding a WAP transport, users can write their own senders, using an API provided with the 4.2.2 release. These new senders can be associated with transports using the Community Console and integrated into the processing flow in the normal way. This section describes the process of developing a new sender. It covers:
The nature of processing flow on the sender side of WBI-C is in part dictated by the needs of the particular situation and transport, but there are basic tasks that must always be done. This section describes those tasks in a high level, general way.
Sender development is based on two major parts: the sender itself, represented in the API by the SenderInterface interface and the Sender Framework, a Connect-supplied class that is responsible for managing the sender. The sender is responsible for actually sending the message to the destination, and for creating and initially populating the SenderResult object. In the case of a synchronous request, the sender also writes the response document to a file, and places a reference to the File object in the SenderResult object. The Framework is responsible for taking care of pre- and post-processing of documents and for instantiating and utilizing the sender.