Bookshelf v8.0: Overview of Store-and-Forward Messaging for Mobile Web Client Architecture

The architecture of Store-and-Forward Messaging for Mobile Web Client consists of Siebel Server elements, Siebel Mobile Web Client elements, and IBM MQe queueing software, in the context of a Siebel Business Application deployment that includes Siebel Remote.

Table 4 specifies the kinds of data synchronization that are handled by Store-and-Forward Messaging, and the kinds of data synchronization that are handled by Siebel Remote.

Table 4. Synchronization Types Handled by Store-and-Forward Messaging and Siebel Remote
Direction of Synchronization	Handled by Store-and-Forward Messaging for Mobile Web Client	Handled by Siebel Remote
Mobile Web Client to Server	All local database transactions. File attachments smaller than the maximum attachment size set by the administrator. For more information about this parameter, see Configuring Maximum Attachment Size.	File attachments larger than the maximum attachment size set by the administrator. For more information about this parameter, see Configuring Maximum Attachment Size.
Server to Mobile Web Client	New Activities assigned by means of the Dispatch Board to a Mobile Web Client that has Store-and-Forward. Any enterprise database transactions that update existing Activities that have already been sent to the Mobile Web Client using Store-and-Forward Messaging.	All enterprise database transactions that Siebel Remote normally routes to the Mobile Web Client. Any transactions that were previously sent by means of Store-and-Forward Messaging are provided for redundancy, but duplication of records is prevented automatically. All file attachments, regardless of size.

Figure 2 shows the components that are used to transmit and receive messages using Store-and-Forward Messaging. Figure 3 shows the mixture of Siebel Remote components and Store-and-Forward components that are used to transmit all file attachments from the server and receive them on the client, and to transmit large file attachments from the client and receive them on the server.

Store-and-Forward architectural elements are described in the following paragraphs. For information about Siebel Remote elements, see Siebel Remote and Replication Manager Administration Guide.

RTSDispatcher

This server component retrieves transactions from the transaction log and creates Store-and-Forward work items that identify which clients should receive Store-and-Forward messages.

RTSExtractor

This server component extracts the needed data from the database and creates the appropriate Store-and-Forward messages.

RTSSender

This server component sends Store-and-Forward Messages to the designated clients by means of IBM MQe, and then deletes the associated work item.

IBM MQe

IBM WebSphere MQ Everyplace (MQe) provides a secure transport layer for transmitting Store-and-Forward messages over wired and wireless networks. For more information about MQe, see About IBM WebSphere MQe.

RTSQApplier

This server component retrieves messages from the SMQ Receiver server component and applies the updates that are contained in the messages to the server database.

SMQ Receiver

This server component receives Store-and-Forward messages that Mobile Web Clients send by means of the transport service. SMQReceiver invokes the RTSQApplier component and passes the message to that component.

RTSClient

This architectural element is a background process on the Mobile Web Client. It performs the following functions: