sententia
Home    Blog

Tibco JBoss JMS Connection


Attached are the jboss connection jar files that I placed in a directory and provided a path to them in my \tibco\designer\5.8\bin\designer.tra file
 
 
 ## this will be prepended to tibco.class.path.extended tibco.env.CUSTOM_CP_EXT
C:/tibco/adapter/admqs/6.2/hotfix/lib/palettes;C:/tibco/adapter/admqs/6.2/lib/palettes;
C:/tibco/adapter/admqs/6.2/hotfix/lib;C:/tibco/adapter/admqs/6.2/lib;C:/tibco/adapter/adadb/6.3/hotfix/lib;
C:/tibco/adapter/adadb/6.3/lib;C:/tibco/adapter/adadb/6.3/lib/palettes;C:/tibco/bw/5.11/hotfix/lib;
%TRA_HOME%/lib/TIBCOjms.jar;%TPCL_HOME%/lib/mail.jar;%TRA_HOME%/lib/TIBCrypt.jar;
%TPCL_HOME%/lib/httpclient_3.0;%HAWK_HOME%/lib;C:/tibco/bw/5.11/lib;
C:/tibco/bw/5.11/lib/palettes;%TPCL_HOME%/uddi4j/lib/uddi4j.jar;C:/tibco/bw/plugins/lib;C:/tibco/bw/plugins/lib/palettes;
c:/myjboss/lib
 

JNDI Context Factory: org.jboss.naming.remote.client.InitialContextFactory
 
JNDI Context URL: remote://<server>:<port>
Topic Connection Factory:jms/RemoteConnectionFactory
Queue Connection Factory:jms/RemoteConnectionFactory
 
 
JNDI Properties
 Name  Type  Value
 jboss.naming.client.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT string  false 
 jboss.naming.client.remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED string false
 jboss.naming.client.connect.options.org.xnio.Options.SSL_STARTTLS string false

 






Tibco2JBossEms.zip
(5.34 MB)