Siebel Store-and-Forward Messaging Guide for Mobile Web Client > Installation and Configuration of Siebel Store-and-Forward Messaging > Deploying IBM MQe Queue Managers >

Optional Step: Creating Additional SMQ Subsystems


You can use additional SMQ subsystems in Siebel implementations that have more users than a single IBM MQe queue manager can support. Each IBM MQe queue manager must communicate with an SMQ subsystem that is dedicated to that queue manager. Each Mobile Web Client is configured to communicate with a specific SMQ Subsystem (and its associated queue manager).

NOTE:  Regardless of how many SMQ subsystems you create, you only need one Siebel Mobile Web Client record to be listed in Administration > Store-and-Forward > Message List > Store-and-Forward Applications.

To create additional SMQ subsystems

  • From the server manager, execute the following command:

    create named subsystem SmqRTSReceiverSubsys1 for subsystem SMQRcvSubsys with
    SmqQueueType=MQe,SmqQueueName=InboundRTSQ,SmqQueueManagerName=ServerQM,
    SmqServletPathName=/smqServerQM,SmqServerMachineName=sdch70a012,
    SmqServerPortNumber=8080,SmqTransportServiceName="SMQ Transport Service",
    SmqTransportMethodName="WaitForMessage",SmqCompression="GZIP",SmqEncryption="RC4",
    SmqProcessComponentName="RTSApplier",SmqProcessMethodName="RunRTSApplier",
    SmqProcessServiceName="RTS Message Apply Service"

    NOTE:  The value for SmqServerPortNumber should match the port for the Web server where you deploy the MQe Queue Manager servlet. The value of 8080 that is shown in this topic is the default port for a Tomcat Web server.

To start SMQReceiver for this new subsystem, you would use the following server manager command:

start task for comp SMQReceiver1 with ReceiveConnectionSubsystem=SmqRTSReceiverSubsys1,
ReceiverDataHandlingSubsystem=SmqRTSDispatchSubsys,
ReceiverMethodName=ReceiveDispatch

Siebel Store-and-Forward Messaging Guide for Mobile Web Client Copyright © 2006, Oracle. All rights reserved.