Siebel Store-and-Forward Messaging Guide for Mobile Web Client > Overview of Siebel Store-and-Forward Messaging >

About Data Flow in Store-and-Forward Messaging for Mobile Web Client

This topic describes how data flows for certain common operations that involve Store-and-Forward messaging, including the following:

• Server to Client Data Flow. Creation, assignment, and transmission of Activity information from the Siebel Server and Enterprise database to the Siebel Mobile Web Client.
• Client to Server Data Flow. Update to Activity information on the Mobile Web Client and transmission to the Siebel Server and the Enterprise database.
• Change in ownership of an Activity record.
• Deletion of a child record of an Activity record.

Store-and-Forward Messaging from Server to Mobile Web Client

The following steps describe what happens when new Activity information originates on the Server and Store-and-Forward transmits it to the Mobile Web Client.

1. A Siebel Web Client user logs in to the Siebel Service application and creates an Activity record.
2. The Dispatch Board lets an authorized user such as a Service Manager assign the Activity record to an appropriate Mobile Web Client user and to schedule the activity for an appropriate time frame. The Dispatch Board - Generic workflow and the SAF - Activity workflow are used in this step.

   NOTE:  If the Activity record includes an attachment, Store-and-Forward Messaging does not send the attachment to the Mobile Web Client. Instead, the attachment is queued for delivery during Siebel Remote synchronization.

3. The RTSDispatcher component retrieves information from the transaction log and creates Store-and-Forward work items that identify which Mobile Web Clients will receive Store-and-Forward messages.
4. The RTSExtractor component extracts the needed data from the database and creates the appropriate Store-and-Forward messages.
5. The RTSSender component sends Store-and-Forward Messages to the designated Mobile Web Clients by means of IBM MQe, and then deletes the associated work items.
6. IBM MQe transmits the message in HTTP format to the assigned Mobile Web Client user.
7. The Store-and-Forward message travels over local intranet and internet channels, as needed, including any of the following network configurations that are needed to deliver the message:
   • Wired networks
   • A Wi-Fi hotspot within range of the Mobile Web Client machine (the machine must have Wi-Fi capability)
   • Cellular phone networks within range of the Mobile Web Client machine (the machine must be equipped with a cellular phone modem and a cellular phone service plan)
8. On the Mobile Web Client, IBM MQe receives the Store-and-Forward Message and passes it to the RTSClient process, autosync.exe.

   The RTSClient process is automatically started as part of the process of starting a Siebel application and connecting to the local database. The process continues running even if the user exits from the Siebel application.

9. The RTSClient process performs the following actions:
   1. It displays an incoming message alert icon (a red arrow pointing down at an envelope) in the notification area of the Mobile Web Client's screen.
   2. It applies the database change that is contained in the message to the local database.
   3. It displays an outgoing message alert icon (a red arrow pointing up from an envelope) in the notification area, indicating that it is sending the Siebel Server an acknowledgement of the message just received.
10. The Mobile Web Client user clicks the incoming message alert icon in the notification area of the screen to display the Incoming Message List, and the message data is available in the local database.

Store-and-Forward Messaging from Mobile Web Client to Server

The following steps describe how Store-and-Forward Messaging operates when a Mobile Web Client user changes any record in the local database.

1. The Mobile Web Client user creates or updates a record. For example, the user might add information about an activity that is in progress, or record the activity's successful completion, or create a new Contact record that is not yet related to any activity.
2. The RTSClient component constructs a message to send to the Siebel Server. The RTSClient component extracts the relevant data from the local database and formats it into a message that is compatible with IBM MQe. The RTSClient component displays an outgoing message alert icon (a red arrow pointing up from an envelope) in the notification area of the Mobile Web Client's screen.

   NOTE:  Handling of any file attachment depends on the size of the attachment. If the file attachment is smaller than the maximum attachment size set by the administrator, then the attachment is included in the message to be sent to the Siebel Server using Store-and-Forward Messaging. If the file attachment exceeds the maximum attachment size, then the RTSClient component queues the attachment for delivery using Siebel Remote synchronization.

3. IBM MQe transmits the message in HTTP format to the Siebel Server.
4. The Store-and-Forward message travels over network channels, as needed, including any of the following network configurations that are needed to deliver the message:
   • Wired networks
   • A Wi-Fi hotspot within range of the Mobile Web Client machine (the machine must have Wi-Fi capability)
   • Cellular phone networks within range of the Mobile Web Client machine (the machine must be equipped with a cellular phone modem and a cellular phone service plan)
5. On the application server, the SMQ Receiver component receives the update message from MQe and passes to it to the RTSQApplier component.
6. The RTSQApplier component applies the update to the Siebel Enterprise Database.

Change in Ownership of an Activity Record

If an Activity record in the Enterprise database is changed to add a Mobile Web Client as the Activity's owner, that change triggers the use of Store-and-Forward Messaging to deliver information about that activity to that Mobile Web Client.

If an activity record in the Enterprise database is changed to end a Mobile Web Client's ownership of that activity, that change triggers the use of Store-and-Forward Messaging to delete the record from that Mobile Web Client's local database. That Mobile Web Client receives no further updates about that Activity record.

Deletion of a Child Record of an Activity Record

If a child record of the Activity business component is deleted from the Enterprise database, Store-and-Forward Messaging does not transmit the delete operation to any Mobile Web Clients, unless your implementation includes a workflow that is specifically constructed to monitor the child business component and propagate such deletions to Mobile Web Clients. However, normal synchronization using Siebel Remote does propagate the deletion. For example, deletion of an invoice associated with an activity would reach the appropriate Mobile Web Clients only by means of Siebel Remote synchronization.