Project

General

Profile

Image Support #3687

Image Support #3666: JBOSS EAP 7.2.0 : TIBCO queues configuration using existing jms .rar

JBOSS EAP 7.2.9 : Java application uses JMS messaging unable to connect to TIBCO ems queues

Added by Shweta about 2 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Normal
Due date:
% Done:

0%

Operating System:
Linux
JRE:
Not Applicable
Instance Type:
Not Applicable
Your Marketplace Account ID:
2872-5568-4589
Marketplace:
Amazon Web Services
Customer State:
Sydney
Customer Country:
New South Wales

Description

Hi Team,

We have java application running on JBOSS eap 7.2.9. We want out application to connect with tibco ems queues (JMS queues). Please assist to make this happen. Can you please provide any documents stating the steps required for configuration.

Please find below the current configuration in the standalone-full.xml related jms queues.Please verify and let us know if we are missing any configurations.

1. Configuration of resource adapter : urn:jboss:domain:resource-adapters:5.0
<subsystem xmlns="urn:jboss:domain:resource-adapters:5.0">
<resource-adapters>
<resource-adapter id="jms-ra.rar">
<archive>
jms-ra.rar
</archive>
<transaction-support>XATransaction</transaction-support>
<connection-definitions>
<connection-definition class-name="org.jboss.resource.adapter.jms.JmsConnectionFactory" jndi-name="java:/RemoteJMSProvider" pool-name="RemoteJmsXA">
<config-property name="ConnectionFactory">
n109978_IPAM2_QCF
</config-property>
<config-property name="UserName"> **
</config-property>
<config-property name="DefaultJMSConnectionFactory">
java:jboss/DefaultJMSConnectionFactory
</config-property>
<config-property name="SessionDefaultType">
javax.jms.Queue
</config-property>
<config-property name="JndiParameters">
java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory;java.naming.provider.url=tcp://<hostname>:<port>;java.naming.security.principal=
****;java.naming.security.credentials=******
</config-property>
<config-property name="Password"> **
</config-property>
<security>
<application/>
</security>
</connection-definition>
</connection-definitions>
</resource-adapter>
</resource-adapters>

2.
<subsystem xmlns="urn:jboss:domain:naming:2.0">
<bindings>
<lookup name="java:/RemoteJMSProvider/Telstra.IPAM.SearchSubnet.Request" lookup="java:/RemoteJMSProvider/java:/RemoteJMSProvider/Telstra.IPAM.SearchSubnet.Request"/>
</bindings>
<remote-naming/>
</subsystem>

3. Configure the default message-driven bean pool in the ejb3 subsystem to use the resource adapter.

&lt;mdb&gt;
&lt;resource-adapter-ref resource-adapter-name="jms-ra.rar"/&gt;
&lt;bean-instance-pool-ref pool-name="mdb-strict-max-pool"/&gt;
&lt;/mdb&gt;

Thanks,
Shweta Hegade,IPAM2

#1

Updated by Mariusz about 2 months ago

  • Status changed from New to In Progress
  • Assignee set to Mariusz
#2

Updated by Mariusz about 2 months ago

  • Status changed from In Progress to Feedback
  • Assignee changed from Mariusz to Shweta

Hi,

Just to clarify - is this issue related to the one you updated recently? #3666

Thanks,
Mariusz Chwalek

#3

Updated by Mariusz about 2 months ago

  • Status changed from Feedback to In Progress
  • Assignee changed from Shweta to Red Hat Support
  • Parent task set to #3666
#4

Updated by Shweta about 2 months ago

Hi Mariusz,

The current ticket can be closed as we are working on this issue under ticket Image Support #3689.

Thanks for your assistance.

Regards,
Shweta Hegade,IPAM2.

#5

Updated by Mariusz about 2 months ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF