SOA Suite 11g - dynamic JNDI destination JMS adapter

Question

hi there soa suite users,
im currently using oracle soa suite 11g,
my use case having a bpel process processing something
and then route the result to several queue.
like this:
jms/adminduk/queue/mks1
jms/adminduk/queue/pdg1,
etc...
so the destination name can be build dynamically in the bpel,
and i stored in a string variable "destName".
(im using WLS 10.3 jms)
now i need to invoke a jms adapter service with produce operation,
but the queue destination needs to be using the variable "destName".
i already tried using assigning to property "jca.jms.JMSDestinationName"
in the invoke activity.
<invoke ...>
<bpelx:inputProperty name="jca.jms.JMSDestinationName"
variable="destName"/>
</invoke>
but it seems not working, and im getting this error:
Caused by: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation
'SendSinkBioWniFromDaerahResponse' failed du
e to: ERRJMS_ERR_CR_QUEUE_PROD.
ERRJMS_ERR_CR_QUEUE_PROD.
Unable to create Queue producer due to JMSException.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>[JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer
requested. The linked
exception may contain more information about the reason for failure.</detail>
,code=<code>null</code>
this is a basic use case of jms interoperability,
anyone have answers to this ??
thank you :)

Answer 1

Hi,
If someone is looking to dynamically set the JMSqueue name here is the solution.
in the Invoke activity set "jca.jms.JMSDestinationName"
value to "JMSHeaderVariable"
set the type to "input"
in the JMSHeaderVariable set the queue name dynamically.
and in the JMSadapter give any valid queue name, still the message will be routed to the queue which you have set in the invoke adapter.