Bug 777883 (SOA-411)

Summary:	Document solution for JBESB-1460
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Martin Vecera <mvecera>
Component:	Documentation	Assignee:	Joshua Wulf <jwulf>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 CR3	CC:	lcarlon
Target Milestone:	---
Target Release:	4.2 GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-411
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-15 05:35:28 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Martin Vecera 2008-02-11 13:58:36 UTC

Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Complexity: Low
Date of First Response: 2008-02-15 00:30:27
project_key: SOA

Document the solution for JBESB-1460 - see http://jira.jboss.com/jira/browse/JBESB-1460#action_12398819

This MBean definition should be included in ha-jndi.xml for instance on the node where the queue is really deployed.

Comment 1 Martin Vecera 2008-02-11 13:58:56 UTC

Link: Added: This issue is related to JBESB-1460

Comment 2 Mark Little 2008-02-13 15:05:43 UTC

Affects: Removed: [Documentation (Ref Guide, User Guide, etc.)] Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]

Comment 3 Joshua Wulf 2008-02-15 05:30:27 UTC

5.4. Using jms-jca-provider with queues on other nodes

 To enable a jms-jca-provider to talk to queues on other nodes you will need to use a provider adapter.

You will need to define an MBean representing the provider adapter:

<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
        name="jboss.esb:service=JMSProviderLoader,name=RemoteJMSProvider,server=remote">
    <attribute name="ProviderName">remoteProvider</attribute>
    <attribute name="ProviderAdapterClass">
        org.jboss.jms.jndi.JNDIProviderAdapter
    </attribute>
    <!-- The queue connection factory -->
    <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
    <!-- The topic factory -->
    <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
    <!-- Connect to JNDI on the host "remote" port 1099 -->
    <attribute name="Properties">
      java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
      java.naming.factory.url.pkgs=org.jnp.interfaces
      java.naming.provider.url=remote:1099
    </attribute>
</mbean>

This MBean should be defined in ha-jndi.xml on the node where the queue is really deployed

Then, in the definition of the jms-jca-provider you need to add a providerAdapterJNDI attribute, e.g:

providerAdapterJNDI="java:/remoteProvider"

The JCA adapter will use the provider adapter from JNDI to create the JNDI context.

Further Information: http://jira.jboss.com/jira/browse/JBESB-1460