1. Transports and Interfaces: Siebel Enterprise Application Integration
  2. Configuring Against IBM WebSphere MQ

Configuring Against IBM WebSphere MQ

For the IBM WebSphere MQ client, no separate security context is needed for each operation. Once a connection is established, all requests sent through the same connection use the same connection context.

Note: The IBM WebSphere MQ server does not perform authentication by default. By default, passwords are not validated. Setup authentication for IBM WebSphere MQ is a task for the IBM WebSphere MQ administrator, not the Siebel application administrator.

For the ReceiveDispatchSend method, the implication is that the receive credentials must be the same as the send credentials. Receive and send must be executed on the same session or connection to remain a single transaction.

To configure the EAI JMS Transport business service against IBM WebSphere MQ

  1. Set the ConnectionUsername and ConnectionPassword to the proper credentials to execute the JMS operations specified by the JMS business service method. For example, in the Send method, both ConnectionUsername and ConnectionPassword must be set to the credentials that are authorized to send messages to SendQueue.

    Note: ConnectionUsername and ConnectionPassword are recommended for supported Microsoft Windows operating systems.

  2. In the ReceiveDispatchSend method, set the ConnectionUsername and ConnectionPassword to the credentials that can both send to SendQueue and receive from ReceiveQueue.

  3. Make sure the jndi.properties file contains the java.naming.security.principal and java.naming.security.credentials properties that are used to connect to the EMS server and to look up JNDI objects.

    Note: These JNDI credentials are set separately from ConnectionUsername and ConnectionPassword.

For more information about configuring the EAI JMS Transport business service against IBM WebSphere MQ, see 828113.1 (Article ID) on My Oracle Support.