Siebel Store-and-Forward Messaging Guide for Mobile Web Client > Installation and Configuration of Siebel Store-and-Forward Messaging > Troubleshooting Store-and-Forward Messaging Setup and Configuration >

Siebel Store-and-Forward Messaging Client-Side Troubleshooting Checklist

Use the following checklist to diagnose problems that originate with Store-and-Forward Messaging clients.

1. Verify that the following parameters are in the [SMQ] section of the autosync.cfg file for the Mobile Web Client. This file is located in the bin subdirectory of the directory where the Mobile Web Client software is installed. Table 6 lists the default values.

   Table 6. Parameter Values in the Mobile Web Client's autosync.cfg File

   Parameter	Default Value
   MQeServerAddr	[hostname] or IP address of the computer hosting the queue manager
   MQeServerCmd	/smq/ServerQM
   MQeServerPort	8082
   MQeServerQMgr	ServerQM
   MQeServerQueue	InboundRTSQ
   QueuingSoftware	MQe. IBM MQe is the only queueing software supported in the current version of Store-and-Forward Messaging.
   SMQCompression	The type of compression used for Store-and-Forward Messaging for Mobile Web Client. The only value currently supported is GZIP.
   SMQConnectOnSend	Controls whether Message Transport software automatically attempts to connect to the server when a message is placed in the client's outbound queue. Default value is FALSE.
   SMQConnectOnStart	Controls whether Message Transport software automatically attempts to connect to the server when a new client session is started. Default value is FALSE.
   SMQEncryption,	The type of encryption used for Store-and-Forward Messaging for Mobile Web Client. The only value currently supported is RC4.
   SMQLogMessages	When TRUE, copies of messages are logged as XML files. Default value is TRUE.
   SMQPollingInterval	Specifies how often the Message Transport software polls for new messages. Default value is 30 seconds.

   If any of the parameter values do not match the server configuration, then modify the autosync.cfg file and reinstall the Siebel Mobile Web Client with the correct parameters.

   NOTE:  The value of the MQeServerPort parameter must be set to match the port number of the Web server where you deploy the MQe Queue Manager servlet. For example, the default port number for a Tomcat Web server is 8080.

2. Examine the Siebel application log file on the Mobile Web Client to find more information for troubleshooting.

   For information on working with the application log file, see Siebel Remote and Replication Manager Administration Guide.

   You can also look for log files with names similar to rtsthrd_7824_5828.log, but with different numerals. Names in this format indicate a log file for the RTSClient.