Siebel Store-and-Forward Messaging Guide for Handheld > Overview of Siebel Store-and-Forward Messaging > Overview of Store-and-Forward Messaging for Handheld Architecture >

Store-and-Forward Messaging Server Components

Figure 4 displays the server components for Siebel Store-and-Forward Messaging.

Figure 4. Siebel Store-and-Forward Messaging Server Components

A Siebel Server with Store-and-Forward Messaging enabled can support multiple Siebel Handheld applications. Store-and-Forward Messaging includes the following services and server components.

Store-and-Forward Messaging Message Service (SMQ Message Service)

The Store-and-Forward Messaging Message Service is called SMQ Message Service. SMQ stands for Siebel Messaging and Queuing. The SMQ Message Service consists of the methods listed in Table 4.

Store-and-Forward Messaging Transport Service (SMQ Transport Service)

The Store-and-Forward Messaging Transport Service (SMQ Transport Service) is a bidirectional transport service which interacts with the MQe queuing system. The transport service sends or receives messages to and from the server queues, provides data encryption or decryption, and performs data compression or decompression. Data is encrypted with the RC4 cipher and compressed with a suitable compression algorithm such as GZIP.

The SMQ Receiver

The SMQ Receiver is a server component which polls the server inbound queues by way of the transport service. Server inbound queues consist of two-level queues, the main application queue and individual queues. For each Siebel Handheld application with Store-and-Forward Messaging enabled, there is one main application inbound queue; for each application user, there is one individual inbound queue.

SMQ Receiver dispatches messages from the main application queue into the individual user queues. It starts an inbound workflow task for each user to process the inbound messages in each individual queue. The inbound workflow calls the inbound message handler ProcessUserQueue method, which processes the message based on the message type. For example, if the message is a transaction message, the message is passed to the Handheld Sync Transaction Apply Services.

Outbound Workflows

Siebel Store-and-Forward Messaging comes with the following sample workflows.

• SMQ Outbound Activity to One Recipient. Based on the Action business object. This workflow's main function is to generate a message, format the message, send the message to a server outbound queue, and update the message history table.
• SMQ Outbound Activity \to Primary Owned By. Uses SMQ Outbound Activity to One Recipient as a sub-workflow. This workflow is triggered by the WriteRecordUpdated runtime event in the Action business component. If an activity is assigned to a mobile user, or if an activity owned by a mobile user is updated, the workflow sends a data message to the mobile user with the updated activity and its associated data.
• SMQ Outbound Activity to Team. Uses SMQ Outbound Activity to One Recipient as a sub-workflow. The workflow allows you to send the same activity message to all service technicians on the same team.
• SMQ Process User Queue. Picks up server inbound messages from each individual inbound queue and processes them.
• SMQ PreDelete FS Invoice Record. Saves the information of a to-be-deleted record. When the PreDeleteRecord runtime event fires, it invokes this workflow.
• SMQ Delete FS Invoice Record. Invokes the SMQ Outbound Delete in Action Business Object workflow and passes the information saved by the SMQ PreDelete FS Invoice Record workflow to it. When the DeleteRecord runtime event fires, it invokes this workflow.
• SMQ Outbound Delete in Action Business Object. Generates a TXN Delete message and sends the message. When the SMQ Delete FS Invoice Record workflow runs, it invokes this workflow.

For more information about Store-and-Forward Messaging workflows, see Siebel Store-and-Forward Messaging Sample Workflows. Additionally, you can examine these workflows with Siebel Tools. For more information, see Siebel Business Process Framework: Workflow Guide.