|Bookshelf Home | Contents | Index | PDF|
Siebel Store-and-Forward Messaging Guide for Mobile Web Client > Installation and Configuration of Siebel Store-and-Forward Messaging > Process of Installing and Configuring Mobile Web Client Applications >
Each Mobile Web Client must be registered for Siebel Remote communication with a particular server—either the HQ (headquarters) server, or a Regional Node. At the same time as you register a Mobile Web Client to communicate with a particular server, you can also specify the SMQReceiver subsystem that the Mobile Web Client will use for Store-and-Forward Messaging.
Briefly, this task is performed by creating a Mobile Web Client record in the Siebel Remote Administration screen's Mobile Web Client view. While specifying other values needed for Siebel Remote operations, you can enable Store-and-Forward Messaging for the Mobile Web Client by entering the SMQReceiver subsystem name (such as SmqRTSReceiveSubsystem) in the SAF Queue Subsystem field.
For detailed instructions on how to complete this task, see Siebel Remote and Replication Manager Administration Guide. For more information about queue subsystems, see Enabling the SMQReceiver, and Optional Step: Creating Additional SMQ Subsystems.
NOTE: This task must be performed before you extract the local database for the Mobile Web Client. Any time you change whether a Mobile Web Client uses Store-and-Forward Messaging, that client must be re-extracted in order to make the client and server use the same encryption key. Each subsystem and queue manager has its own encryption key, which the Mobile Web Client obtains during local database initialization. When a Mobile Web Client and a server have non-matching encryption keys, incoming messages from either machine will be incomprehensible to the other.
|Siebel Store-and-Forward Messaging Guide for Mobile Web Client||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|