Transports and Interfaces: Siebel eBusiness Application Integration Volume III > EAI MQSeries Transports > About Siebel EAI MQSeries Transports >

About the EAI MQSeries AMI Transport


When using the EAI MQSeries AMI Transport, you need to install and configure:

  • MQSeries Server
  • MQSeries Client if necessary
  • MQSeries Application Messaging Interface
  • MQSeries Application Messaging Interface Administration Tool (available only on Windows NT and Windows 2000)

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 Transport

If 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 Parameters

After defining the AMI policy and AMI service points, you must set certain enterprise parameters in the Siebel client, as shown in Table 7.

Table 7.  EAI MQSeries AMI Transport Specific Parameters
Argument
Display Name
Description

MqPolicyName

Policy Name

Defaults to the AMT.SYSTEM.SYNCPOINT.POLICY provided by IBM, if you do not specify an AMI Policy. This parameter is optional. The name of the policy you define in the AMI Administration Tool. The AMI policy defines properties such as Connection Type and Mode, Message Type, Send and Receive parameters, and many others. The policy is stored in the AMI Repository, which is an XML document. You can have multiple policies and multiple repositories. Refer to the IBM MQSeries Application Messaging Interface (AMI) documentation for more details.

MqReceiverServiceName

Receiver Service Name

The name of the service point you define as a receiver in the AMI Administration Tool. Service points specify queue names, queue manager names, model queue names, and several other parameters. You must create a service point that specifies the queue and queue manager that receives messages. The Receiver Service and the Sender Service may specify the same queue and queue manager.

MqRepositoryName

Repository Name

Optional. Fully qualified name of the directory containing AMI repository files. If unspecified, the business service looks for the repository files in the default location determined by the MQSeries AMI installation.

MqSenderServiceName

Sender Service Name

The name of the service point you define as a sender in the AMI Administration Tool. Service points specify queue names, queue manager names, model queue names, and several other parameters. You must create a service point that specifies the queue and queue manager that sends messages. The Receiver Service and the Sender Service may specify the same queue and queue manager.

MqTrace

Trace

Default is False. Turns on tracing for AMI.

MqTraceLocation

Trace Location

Name of the directory for output of AMI tracing.

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 AMI

When 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