Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport > Enabling Authentication and Authorization for the EAI JMS Transport >

Configuring Against TIBCO Enterprise Message Service

For the TIBCO Enterprise Message Service (EMS) client, no separate security context is needed for each operation. Once a connection is established, with the proper credential, all requests sent through the same connection use the same connection security context. This means that switching the security context requires switching connections.

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 TIBCO EMS

1. ConnectionUsername and ConnectionPassword are set to proper credentials for executing the JMS operations specified by the JMS business service method.

   For example, in the Send method, both ConnectionUsername and ConnectionPassword are set to the credentials that are authorized to send messages to SendQueue.

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

2. Set the following input properties to empty:
   • SendUsername
   • SendPassword
   • ReceiveUsername
   • ReceivePassword
   • TopicUsername
   • TopicPassword
3. 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 lookup JNDI objects.

   However, the connection to the EMS server, and the ability to lookup JNDI objects, does not occur if anonymous access is enabled by TIBCO EMS. For more information, see the TIBCO EMS documentation.

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