Configure tibco jms bus in Websphere for Maximo application

Configure Tibco as JMS provider:

Create JMS provider:

1. In Websphere, create a new Tibco provider tibjmsbus
2. Classpath field: Copy the tibco jar files from TIBCO server to the machine where Websphere is installed.
3. External initial context factory: com.tibco.tibjms.naming.TibjmsInitialContextFactory
4. External provider URL: tibjmsnaming://HOST:PORT (e.g. tibjmsnaming://localhost:7222) – refer the real time in the below screen shot.
5. Under Additional properties, click on custom properties:

            java.naming.security.principal – a name of a the user used to connect to Tibco

            java.naming.security.credentials – a password of the user used to connect to Tibco

Create connection factory

Within Tibco JMS provider create a new queue connection factory specifying the following:

• Name:   QueueConnectionFactory (default queue connection factory in Tibco) . We can modify as per our wish.
• JNDI name – local name to be used on WebSphere server (e.g. QueueConnectionFactory)
• External JNDI name – external JNDI name on Tibco server from a container-managed authentication alias drop-down select the newly created in the previous step tibcoUser alias. (e.g. jms/tibcoQCF).  

Create authentication alias
Create a new authentication alias (eg: tibcoUser) providing a user name and password to be used while connecting to a connection factory.

Create queue

Within Tibco JMS provider create a new queue providing the following:

• Name:

MY_QUEUE, by default. You can give any name. TibocInbound or TibcoOutbound – sample names.

• JNDI name – local name to be used on WebSphere server. This name will be referred in Maximo External system application.

External JNDI name – external JNDI name on Tibco server. It should be obtained from Middleware tibco team. 


Maximo:

TIBCO Buses can be configured as End point or Queue. 

 


Reference: http://www.mjonik.pl/blog/2011/03/tibco-as-a-jms-provider-within-websphere/