Siebel Store-and-Forward Messaging Guide for Handheld > Administration of Siebel Store-and-Forward Messaging > Process of Administering Applications with Siebel Store-and-Forward Messaging >

Moving PDA Users to a Different MQe Queue Manager and Inbound Queue

A high-volume Siebel Handheld Store-and-Forward Messaging environment can have multiple MQe queue managers and multiple MQe generic inbound queues. At installation, each PDA is assigned to a specific queue manager and generic inbound queue. To bypass a problem such as a server outage, PDA users can be moved from the original queue manager and inbound queue to another queue manager and inbound queue.

This topic sets forth a way to switch PDA users to a secondary server, if multiple MQe servers are present and the primary server fails. This topic describes how to move a handheld device from one MQe queue manager and inbound queue to another, where the following circumstances apply:

• There is one primary MQe server, with a backup server to which you can move users if the primary server fails.
• You have access to the registry editor, either from a Siebel application or from CE Tools, which can run on a desktop computer and access the PDA device registry through ActiveSync.
• The SMQ server has been configured, and Workflow Manager and HandHeldSync are running.

If your company network is set up in a different configuration, then you can vary the steps of this procedure accordingly.

To move a user to a different MQe queue manager and inbound queue

1. Launch the registry editor and access the PDA device registry.
2. In the PDA device registry, change the values of the fields in the following table.

   Field	Comments	Example Original Value	Example New Value
   MQeServerAddr	MQe server	Server1	Server2
   MQeServerQMgr	MQe queue manager	ServerQM1	ServerQM2
   MQeServerQueue	Inbound queue	InboundQ1	InboundQ2

   Change only the fields that are required.

   NOTE:  It is not necessary to reregister the PDA, because the device has been registered before and the user is already in the mobile user list.

3. Send an SMQ message to the server and verify, on the server side, that a queue named InboundQ.Client Queue Manager Name is created, for example:

   InboundQ.ServerQM2

   The workflow retrieves the message from the queue, processes the message, and creates the outbound queue.

When you change the server, the client continues to push messages to and pull messages from the server that is specified in the device registry.