Quantcast
Channel: Indrayan's SOA Blog
Viewing all articles
Browse latest Browse all 62

Enqueue Msg In Tibco EMS Queue From BPEL

$
0
0

Objectve:

To create a BPEL Process which will enqueue messages in a Tibco EMS Queue.

Setting of Queue Connection Factory:

Path of JMS Adapter:

$ORACLE_HOME\j2ee\home\connectors\JmsAdapter

Class Required to access Tibco EMS:

tibjms.jar

Path where external jar needs to be kept to access Tibco Queue:

$ORACLE_HOME\j2ee\home\connectors\JmsAdapter\JmsAdapter

Connect Factory configured in :

$ORACLE_HOME\j2ee\home\connectors\JmsAdapter\JmsAdapter\META-INF\oc4j-ra.xml

By default Connection Factories are pre-configured in this file for most of Industry standard Queue/Topic providers(Tibco,MQ,Webspehere,JBOSS etc). One only need to configure the credential and Provider URL(hostname/port) to use them.

In our case the Connection Factory JNDI name for TIBCO Queue is :

eis/tibjms/Queue.

Error Message in case jar not included:

The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141

ERRJMS_CONN_FAC_NOT_FOUND.

Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor QueueConnectionFactory neither through JNDI nor instantiate it as a Java class [Caused by:

Missing class: com.tibco.tibjms.naming.TibjmsInitialContextFactory

Dependent class: com.sun.naming.internal.VersionHelper12

Loader: jre.bootstrap:1.5.0_06

Code-Source: unknown

Configuration: jre bootstrap

This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.


Creation of BPEL Process:

Below given is sample BPEL process which uses JMS adapter to enqueue messages in Tibco EMS queue(Queue name:Sample).

Below given are the steps to configure JMS Adapter service.






Viewing all articles
Browse latest Browse all 62

Trending Articles