Why and when to perform this task
Before starting a WebSphere Business Integration Adapter (WBIA) session, you must first ensure that the WebSphere MQ JMS Provider is configured correctly. You do not have to add any new information to enable WBIA support. Install and configure the Websphere MQ JMS Provider in the usual manner as documented in article, Installing WebSphere MQ as the JMS Provider.To install and configure WBIA session support, complete the following steps:
Steps for this task
Security > JAAS Configuration > J2C Authentication Data > New
Then enter an alias name, userid, and password. Select an existing Component-managed Authentication Alias if you want the WBIA management function to use the userid and password specified in the alias when using this WebSphere MQ Queue Connection Factory.Update the remaining fields in the WebSphere MQ Queue Connection Factory in the same manner as for general JMS support.
You must create two new MQ Queue destinations, one for the WBIA AdminIn Queue and another for the WBIA AdminOut Queue. These two queues must be unique for each WBIA resource. These queues process the adminstrative commands that flow between WebSphere Application Server and the WebSphere Business Integration Adapter.
Do not confuse the AdminIn and AdminOut queues when you create the destinations. The WBIA resource represents the remote WBIA connector process so the names you specify must reflect the WBIA adapter. The AdminIn queue is the queue on which WebSphere Application Server places outgoing adminstrative messages that are read by the WBIA adapter. The AdminOut queue is the queue on which WebSphere Application Server listens for responses to the administrative messages.
Update the remaining fields in the WebSphere MQ Queue destinations in the same manner as for general JMS support.
After you click Apply or OK, WebSphere Application Server creates a new WBIA resource.