Bug 779723 (SOA-2085)

Summary:	jBPM JCA inflow needs to support JMSProviderAdapter
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Kevin Conner <kevin.conner>
Component:	JBossESB	Assignee:	Kevin Conner <kevin.conner>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0.0 GA	CC:	dlesage
Target Milestone:	---
Target Release:	5.0.2
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2085
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-12 18:06:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kevin Conner 2010-05-14 10:48:30 UTC

Date of First Response: 2010-05-31 01:57:17
project_key: SOA

Comment 1 Kevin Conner 2010-05-14 10:48:47 UTC

Link: Added: This issue depends JBESB-3317

Comment 2 Kevin Conner 2010-05-14 11:05:25 UTC

Code has been changed in ESB codebase but still need a docs update.

The adapter can be initialised in JNDI by including something similar to the following MBean within jbpm-service.xml.

   <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=RemoteProviderLoader">
      <attribute name="ProviderName">RemoteProviderAdapter</attribute>
      <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
      <attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>
      <attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
      <attribute name="Properties">
         java.naming.provider.url=192.168.1.1:1099
      </attribute>
   </mbean>

This can then be referred to from within jbpm.cfg.xml and the inflow activation spec, for example the message configuration could be as follows (scheduler is similar)

    <service name="message">
      <factory>
        <bean class="org.jboss.soa.esb.services.jbpm.integration.msg.JmsMessageServiceFactory">
          <field name="providerAdapterJNDI"><string value="RemoteProviderAdapter"/></field>
        </bean>
     </factory>
    </service>

Comment 3 Dana Mison 2010-05-31 05:57:17 UTC

More information need for release notes:

JMSProviderAdapter is now supported by jBPM JCA inflow.

Needed: What is the usecase that this enables ?

Comment 4 Kevin Conner 2010-06-08 13:17:44 UTC

This allows the jBPM JCA inflow to be refer to JMS providers which are located in a JNDI context other than the current one, i.e. hosted on a remote system.

Comment 5 Dana Mison 2010-06-11 06:33:08 UTC

Added to the SOA 5.0.2 release notes as resolved:

JMSProviderAdapter is now supported by jBPM JCA inflow.  This allows the jBPM JCA inflow to be referred to by JMS providers which are located in a different JNDI context to the current one, such as on a different server.

Comment 6 David Le Sage 2010-06-16 00:58:45 UTC

Hello Kevin,

Has this been added to the community docs yet?  Please let me know and I will then add it to the product docs.

Thanks,

David

Comment 7 Kevin Conner 2010-07-08 11:00:20 UTC

The platform documents differ from the project documentation in this area.  The project Administration Guide will be modified to include the text as included within JBESB-3363.

Comment 8 David Le Sage 2010-07-09 00:12:27 UTC

This information has now been added to the product Administration Guide.  The Release Note has also been amended to point to it.

Comment 9 Len DiMaggio 2010-07-12 18:06:16 UTC

Verified int he SOA-P product docs here:

http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html-single/ESB_Administration_Guide/index.html#remote_providers