Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport > Enabling Authentication and Authorization for the EAI JMS Transport > Configuring Against IBM WebSphere MQFor 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 will use the same connection context. NOTE: The MQ server does not perform authentication by default. By default, passwords are not validated. Setup authentication for MQ is a task for the 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
For more information on configuring the EAI JMS Transport business service against IBM WebSphere MQ, see Article ID 828113.1 on My Oracle Support. |
![]() |
![]() ![]() |
Transports and Interfaces: Siebel Enterprise Application Integration | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |