Bookshelf Home | Contents | Index | PDF |
Transports and Interfaces: Siebel eBusiness Application Integration Volume III > EAI MQSeries Transports > About Siebel EAI MQSeries Transports > About the EAI MQSeries AMI TransportWhen using the EAI MQSeries AMI Transport, you need to install and configure:
CAUTION: IBM recommends not using the MQSeries AMI for new projects. For new projects use the WebSphere JMS in place of the MQSeries AMI. See the IBM documentation on using the WebSphere JMS. For more information on how to perform these tasks, contact your IBM sales representative. Configuring the EAI MQSeries AMI TransportIf you are using the MQSeries Application Messaging Interface (AMI), you specify the queues, queue managers, and other parameters in the AMI Administration Tool, when you define your AMI service points and AMI policies. NOTE: Service points define where the message needs to be sent. Policies define how the messages need to be handled. It is very important to understand what a policy is and how to set different policy elements. For more information on AMI policies, consult your IBM documentation. EAI MQSeries AMI Transport ParametersAfter defining the AMI policy and AMI service points, you must set certain enterprise parameters in the Siebel client, as shown in Table 7. NOTE: Do not set the Receive attribute for the AMI policy as Convert if you have set the CharacterSetConversion parameter from the data handling subsystem to True. Also, do not set this attribute if receiving well-formed, self-describing documents such as XML. Using the ReceiveDispatchSend Method with AMIWhen using the ReceiveDispatchSend method of the EAI MQSeries AMI Transport, you must make sure that there is a rule in your MQSeries configuration to check the request message to be put onto the MQSeries queue to contain values for the ReplyToQueue and ReplyToQueueManager parameters. |
Transports and Interfaces: Siebel eBusiness Application Integration Volume III |