JMS Adapter Destination Name value

Hi
I am trying to connect to a WLS remote distributed queue using the JMS Adapter but I am struggling to find the correct format for the destination name property as each time it gives various JMSExceptions stating that it cannot find the queue. Below is the .jca properties
<connection-factory location="eis/wls/Queue" UIConnectionName="OSB_Test" UIJmsProvider="WLSJMS" adapterRef=""/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
<activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
<property name="DestinationName" value="jndiEmployeeDQ"/>
<property name="UseMessageListener" value="false"/>
<property name="PayloadType" value="TextMessage"/>
</activation-spec>
</endpoint-activation>
I have also set the factory properties of the outbound connection pool as follows
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory; java.naming.provider.url= t3://<remote-hostname>:<port>;java.naming.security.principal= <username>;java.naming.security.credentials=<password>
Below is the message I am receiving
<01-Feb-2011 11:35:32 o'clock GMT> <Warning> <oracle.soa.adapter> <BEA-000000> <JMSAdapter TestEmployeeQueueA
BINDING.JCA-12135
ERRJMS_ERR_CR_QUEUE_CONS.
ERRJMS_ERR_CR_QUEUE_CONS.
Unable to create Queue consumer due to JMSException.
Please examine the log file to determine the problem.
     at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:620)
     at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
     at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
     at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:913)
     at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
     at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
     at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
     at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
     at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045101]The destination name passed to createTopic or createQueue "jndiEmployeeDQ" is invalid. If the destination name does not contain a "/" character then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character then the string before the "/" must be the name of a JMSServer or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WLS server will be returned.
     at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
     at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
     at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
     at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
     at weblogic.jms.client.WLSessionImpl.createQueue(WLSessionImpl.java:938)
     at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
     at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
     ... 8 more
Has anyone encountered this problem before?
Damien

Could you connect to same destination using any other client (like java). I think issue is either in the queue deployment or in the connection pool configuration at your side. Make sure that queue is available (by connecting to same queue using any other client) and cross check you connection pool configuration.
Let us know the version of products you are using and connecting to.
Regards,
Anuj

Similar Messages

OCEP JMS Adapter implement InboundMessageConverter issue

Hello,
I'm new to OCEP. I have a JMS adapter receiving Weblogic JMS message. JMS Message is a TextMessage, so the default MapMessage can't convert it. I need to write my own converter which implement InboundMessageConvert. Eclipse compiles just fine, but when deploying into a runtime OCEP environment, I get an error saying that my custom converter class does not implement InboundMessageConverter which I did. Did anyone encounter this issue and how to get around it?
I also tried the sample code provided in Developer Guide and it doesn't work. My code bellow is a sample to by pass the deployment issue..
package com.converter;
import com.bea.wlevs.adapters.jms.api.InboundMessageConverter;
import com.bea.wlevs.adapters.jms.api.MessageConverterException;
import javax.jms.JMSException;
import javax.jms.Message;
import java.util.List;
public class MyMessageConverter
implements InboundMessageConverter
public MyMessageConverter(){
super();
public List convert(Message message) throws MessageConverterException, JMSException
return null;
--- error message when deploy to runtime environment ---
<Mar 22, 2010 10:30:57 AM PDT> <Error> <Deployment> <BEA-2045010> <The application context "FilteringEvent" could not be started: org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.IllegalArgumentException: converter-bean com.converter.MyMessageConverter does not implement InboundMessageConverter
org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.IllegalArgumentException: converter-bean com.converter.MyMessageConverter does not implement InboundMessageConverter
at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:136)
at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
I have included the following two lines into the Manifest file, but this action has not fixed the problem:
com.bea.wlevs.adapters.jms;version="11.1.1.4_0",
com.bea.wlevs.adapters.jms.api;version="11.1.1.4_0"
My EPN file is as shown:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:osgi="http://www.springframework.org/schema/osgi"
xmlns:wlevs="http://www.bea.com/ns/wlevs/spring"
xmlns:jdbc="http://www.oracle.com/ns/ocep/jdbc"
xmlns:spatial="http://www.oracle.com/ns/ocep/spatial"
xmlns:application="http://www.bea.com/ns/wlevs/config/application"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.bea.com/ns/wlevs/spring
http://www.bea.com/ns/wlevs/spring/spring-wlevs-v11_1_1_3.xsd
http://www.oracle.com/ns/ocep/jdbc
http://www.oracle.com/ns/ocep/jdbc/ocep-jdbc.xsd
http://www.oracle.com/ns/ocep/spatial
http://www.oracle.com/ns/ocep/spatial/ocep-spatial.xsd
http://www.bea.com/ns/wlevs/config/application
http://www.bea.com/ns/wlevs/config/application/wlevs_application_config.xsd">
     <bean id="myConverter" class="com.bea.wlevs.adapter.example.jmsclient.JMSClient"/>
     <wlevs:adapter id="jmsInbound" provider="jms-inbound">
          <wlevs:instance-property name="converterBean" ref="myConverter"/>
     </wlevs:adapter>
     <application:jms-adapter>
<application:name>jmsInbound</application:name>
<application:jndi-provider-url>t3://localhost:9002</application:jndi-provider-url>
<application:destination-jndi-name>Queue1</application:destination-jndi-name>
<application:user>wlevs</application:user>
<application:password>123456</application:password>
<application:work-manager>JettyWorkManager</application:work-manager>
<application:concurrent-consumers>1</application:concurrent-consumers>
<application:session-transacted>false</application:session-transacted>
</application:jms-adapter>
<wlevs:event-type-repository>
The error showned by Eclipse is:
Multiple annotations found at this line:
     - cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'application:jms-adapter'.
     - schema_reference.4: Failed to read schema document 'http://www.bea.com/ns/wlevs/config/application/
     wlevs_application_config.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the
     document is not <xsd:schema>.
Thanks!
Edited by: 899693 on 15-dic-2011 2:48

SOA Suite 11g - dynamic JNDI destination JMS adapter

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 :)

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.

Passing dynamic jndi destination to jms adapter in SOA Suite

hi i post this thread in SOA Suite category,
but havent got any answer yet,
maybe someone in weblogic jms community here have an answer :)
im interfacing Weblogic JMS 10.3 with SOA Suite 11gR1 BPEL/JMS Adapter,
and i need to pass a dynamic destination jndi to message producing adapter in the orchestration process.
details here:
Re: SOA Suite 11g - dynamic JNDI destination JMS adapter

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.

How to get the incoming file name using JMS adapter and SOAP adapter

Hi Everybody,
   In one of my interface i need to get the file name of incoming flat file using JMS adapter at sender side. and then i am using xslt to convert it to IDOC and then posting to SAP IDOC.
my incoming filname are in this form price<DateTimestamp>.txt. when i do the tranformation this incoming file name should be part of one element in the IDOC which i am posting.
EX:
<IDOC
<REF>price<DateTimestamp>.txt</REF>
</IDOC>
Hope it is clear to everybody. I need your suggestion how i can capture this incoming file name and send it as part of IDOC.
Thanks
raj

If they are passing it in message id or correlation id,
you can access it using
<xsl:variable name="dynamic-conf"
        select="map:get($inputparam, 'DynamicConfiguration')" />
    <xsl:variable name="dynamic-key"
        select="key:create('http://sap.com/xi/XI/System/JMS', 'DCJMSMessageID/ DCJMSCorrelationID')" />
    <xsl:variable name="dynamic-value"
        select="dyn:get($dynamic-conf, $dynamic-key)" />
Check this:
http://help.sap.com/saphelp_nw70/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Thanks,
Beena.

How to ignore Recordset name in XML(Sender JMS Adapter)?

Hi All.
I am using Sender JMS Adapter along with content conversion.
I have put in Parameter:
Plain2XMLService xml.ignoreRecordsetName true
still the Inbound payload in SXI_MONITOR has Node Recordset, which should not be the case.
Please advice, does this ignoreRecordsetName works in JMS adapter, if Yes does it works same way as in File Adapter content conversion?
Thanks in Advance

>
Gowtham Peddi wrote:
> Hi All.
>
> I am using Sender JMS Adapter along with content conversion.
>
> I have put in Parameter:
> Plain2XMLService xml.ignoreRecordsetName true
>
> still the Inbound payload in SXI_MONITOR has Node Recordset, which should not be the case.
>
> Please advice, does this ignoreRecordsetName works in JMS adapter, if Yes does it works same way as in File Adapter content conversion?
>
> Thanks in Advance
can you try
ignoreRecordsetName true instead of xml.ignoreRecordsetName
also try to not give any value for the xml.recordsetName parameter.
I actually doubt if we can ignore the record set name using the module.

Help on Dynamic queue name in JMS Adapter

Hi Experts,
Could you please explain how to configure dynamic queue name in JMS Adapter.
My requirement is i would have to add the date and time to JMS Queue Name in receiver JMS Adapter.
Thanks in Advance
Chilla

hi,
as it's not in Adapter-Specific Message Properties
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
looks like you cannot do it with jms adapter in standard
use proxy or your own adapter instead
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

JDeveloper - ESB / BPEL - JMS Adapter - prefix queue name with db schema

When I use the JMS Adapter in ESB to create a new message queue producer or consume using database (AQ) I'm experiencing a problem when selecting the queue.
I can browse the queue in the database but when I have selected the queue JDeveloper prefix it with the schema name owning the queue.
Example:
java:comp/resource/DocumentQueueResourceProvider/Queues/QUEUES.DOCUMENT_IMPORT_QUEUE
Schema owner is QUEUES and the name of the queue is DOCUMENT_IMPORT_QUEUE.
The problem is when I try to use it its unable to look up the queue and I have to manually remove the prefix from .wsdl file before deploying it - as with setting mcf.IsTransacted='false'.
When the resource provider finds the queue and exposes it in the JNDI three it does it without the prefix.
Question: How do I either:
a) make the schema prefix be removed by JDeveloper
b) make the resource provider prefix the queue name with the schema name.
Anybody?
Best regards
Christian Damsgaard

Try this:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://www.yourcompany.com/msg"
xmlns:tns="http://www.yourcompany.com/msg"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
nxsd:encoding="ASCII" nxsd:stream="chars" nxsd:version="NXSD"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:element name="rootnode" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eof}"/>
</xsd:schema>
This will result in a single node xml.
Edited by: user472896 on Sep 22, 2010 10:29 AM

Unable to select jms destination in the jms adapter configuration

hi,
I am trying to use JMS queues for consuming messages but after creating the JMS queues(destination) in the application server, i am unable to find the destination while configuring the jms adapter in jdeveloper.
any help would be appreciated

i am using soa 10g. are you saying there is an option for starting the jms server in the application sever or do i have to create a seprate jms erver for creating the jms server etc.
it will be really helpful if you can explain the how to create/start jms server,jms queue etc or provide link to any article that is available. also please note that i am using SOA 10g
thanks in advance

Format of "JMS Message Destination Parameter" for JMS Sender Adapter

Hi,
I am trying to use the JMS Sender Communication Channel for several Interfaces by using the "JMS Message Destination Parameter". Currently, the Comm.Channel is reading the message and puts it back on the queue with the following error:
Fehler bei der XI-Eingangsverarbeitung für Message am bzw. um 2007-07-25|09:34:12.057+0200. JMS- und XI-Identifikatoren für die Message sind ID:414d512051535749515441302020202046a4e892201c4d04 bzw. 701ec850-3a81-11dc-8176-00306e2c36a3. Der JMS-Adapter führt einen Rollback der Datenbank und der JMS-Sitzungtransaktionen durch. Wird die Sitzung ausgeführt, geht die Message nicht verloren und wird später erneut durchgeführt. Der Ausnahme-Stack-Trace ist java.lang.RuntimeException: MQJMS0003: Destination not understood or no longer valid: UserCreateRequest
at com.ibm.mq.jms.MQDestination.createDestination(MQDestination.java:790)
at com.ibm.mq.jms.MQSession.createDestination(MQSession.java:1092)
at com.ibm.jms.JMSMessage.getJMSDestination(JMSMessage.java:4127)
What is the format I will have to fill this parameter with in order for XI to understand it? I have tried the following so far which did not work:
1. (as in error message above)
Help much appreciated.
KR,
Colin.

One option in BPEL is to have a mid process receive, but this would require you to handle the Correlation of the message with BPEL process instance.
Please refer the following section in SOA Guide for the same.
Using Correlation Sets and Message Aggregation - 11g Release 1 (11.1.1.7)
Please note the example is with File adapter but the same can be achieved for Any Adapter.

JMS Sender Adapter with constant values

Hello Friends,
My scenario is,
1. I am having 6 Sender JMS CCs with different Queues
2. One Inbound Proxy to post the data into R/3
Sender (JMS) -
> XI -
> R/3 (Inbound Proxy)
Note: There is no Message Mapping used.
Problem: When my sender JMS adapter picks the data from JMS Queue then before sending it to Proxy I want to add some more data (lets say a kind of header info) along with the original data.
Reason: Based on this additional data I will process my data in proxy in 6 different ways.
Regards,
Sarvesh

You can use the DynamicConfigurationBean to set constants to the message header:
http://help.sap.com/saphelp_nw04/helpdata/en/45/da2239feb22e98e10000000a155369/frameset.htm
The configuration would be something like this:
key.0 insert http://sap.com/xi/XI/System/ABC XYZ
value.0 123
Regards
Stefan

HTTP adapter as receiver to POST name-value pairs - How to?

Hi,
Scenario: HTTP Sender <> XI <> HTTP receiver (Sync throughout; no BPM)
In this scenario, a HTTP channel is configured to the target URL to post data.
The message mapping results in a XML. HTTP posts the same XML to the target URL.
However,the target URL expects data Posted as name-value pairs.
eg. eid=45678&zip=11011&ename=Tom%20Lee
How can we configure HTTP adapter channel to post XML data as
name-value pairs (as in standard HTTP Form Post)?
Any pointers?
thanx,
Pops

Hi Udo,
I currently have a solution (simpler than having a BP), but do not expect it to be the right way of doing.
I am using Java Mapping to convert the XML structure into Name-Value pair. So the output of Mapping is a string like how HTTP post is expected. So the interface mapping having multiple mappings - firstly, the original Message mapping, and then the Java mapping to do the conversion. So, with a small extension, the solution is still kept simple.
However, I thought the POST requirement to HTTP URLs would be a common requirement, and expected the HTTP adapter doing this conversion. So, I am still looking for a straight solution (without any custom extensions).
Any one else faced this situation?
Can't this be handled by HTTP Adapter?
-- Pops V

Same file name using JMS adapter on sender side.

Hi Friends,
I got a requirement to capture file name using JMS adapter on the sender side.
Can some one help me in resolving this issue.
Regards,
Jeevan.

Hi ,
You can use Dynamic Configuration in mapping.
Create a UDF with input as file name and copy/paste this code
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
//conf.removeAll();
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
//String filename= conf.get(key);
conf.put(key, fileName);
key= null;
return fileName;
Thanks.

Problem with Send using JMS Adapter with Websphere MQ

Hi,
We have two scenarios using JMS Adapter with MQ:
1. File->PI->MQ
This works fine and drop the file in MQ correctly.
2. MQ->PI->File
This gives an error reading from the queue: (see highlighted in the log below). It correctly connects to the queue name. But it fails with the message "Could not begin a AF transaction".
Our PI version is 7.0 SP 13
Websphere MQ Version 6.0.
Any idea what could be wrong?
Cluster Node Administration Information Availability Times
Cluster Node Details for Channel CC_JMS_MQ_Sender
Short Log
In the Last 4 Hours Server 0 15_92786
_Sucessfully connected to destination 'queue:///MMPP.PLM.FGH41? CCSID=37&targetClient=1'_
Line 1 / 1
Processing Details for Cluster Node Server 0 15_92786
Type
Time Stamp
Message ID
Explanation
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d Error while processing message '2e6206f0-7925-11dd-bc02-0003bae50b4d'; _detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ..._
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d XI message ID corresponding to JMS message with ID 'ID:414d512071736431202020202020202047d9462024028b02' will be created as a new GUID with value '2e6206f0-7925-11dd-bc02-0003bae50b4d'
Amith Dharmasiri

Checked the drivers installed in :
/usr/sap/<SID>/DVEBMGS<SYSNO>
/j2ee/cluster/server0/bin/ext/com.sap
.aii.af.jmsproviderlib
They are available and properly added to aii_af_jmsproviderlib.sda.
The drivers are:
CL3Export.jar
CL3Nonexport.jar
com.ibm.mq.jar
com.ibm.mqjms.jar
connector.jar
dhbcore.jar
rmm.jar
These were installed per OSS note 747601.
Any other suggestions, why retrieving from MQ doesn't work?

JMS Adapter Config issues with Plan.xml

Hi All,
I'm learning how to configure JMS Resources in WLS to use within a JMS adapter in my application. My approach so far has been :
1. Configure Outbound Connection in JMS Adapter : eis/wls/Queue. I used the weblogic.jms.XAConnectionFactory as the Connection Factory.
2. Create Queue within SOAJMSModule : jms/MyQueue and target - soa managed server.
Updated the JMSAdapter.rar deployment and restarted the SOA server as well as the JMS module.
3. Create JMS Adapter within JDeveloper to use jms/MyQueue as the destination and eis/wls/Queue as the JNDI source.
On deployment and running, I see this following error. Apologies it is a bit difficult to trawl through. I did have a look in the Plan.xml and it definitely has an entry for this Adapter and the jndi-name. Any other approach?
Oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(Unknown Source) at com.sun.el.MethodExpressionImpl.invoke(Unknown Source) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:765) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:305) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:185) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:276) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(Unknown Source) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source) at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:260) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:992) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:729) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:569) ... 81 more Caused by: javax.xml.ws.soap.SOAPFaultException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1012) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:803) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:256) ... 84 more
The deployment plan reads as follows :
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>connectors</application-name>
<variable-definition>
<variable>
<name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
<value>eis/wls/Queue</value>
</variable>
<variable>
<name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
<value>weblogic.jms.XAConnectionFactory</value>
</variable>
</variable-definition>
<module-override>
<module-name>JmsAdapter.rar</module-name>
<module-type>rar</module-type>
<module-descriptor external="false">
<root-element>weblogic-connector</root-element>
<uri>META-INF/weblogic-ra.xml</uri>
<variable-assignment>
<name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/jndi-name</xpath>
<origin>planbased</origin>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/connection-properties/properties/property/[name="ConnectionFactoryLocation"]/value</xpath>
</variable-assignment>
</module-descriptor>
<module-descriptor external="false">
<root-element>connector</root-element>
<uri>META-INF/ra.xml</uri>
</module-descriptor>
<module-descriptor external="true">
<root-element>wldf-resource</root-element>
<uri>META-INF/weblogic-diagnostics.xml</uri>
</module-descriptor>
</module-override>
<config-root>E:\oracle\product\middleware\11.1.1\soa_11.1\soa\connectors\plan</config-root>
</deployment-plan>
Thanks
JB
Edited by: 939260 on Jun 20, 2012 5:13 AM

Hi JB,
Please follow the below steps from beginning...
1. Create the JMS Server in the Admin Console, the target server for the same should be the soa server
2. create new JMS Module.
3. Create new Connection factory in resources, give your JNDI names, the target servers should be the admin and the soa.
4. create new queue, give the JNDI names, the target server should be the JMS Server which you have created in the step 1 above.
5. Now go to deployments, slect the JMS adapter, click update, and say redeploy with the location of JMS-plan.xml given below...
6. Now inside the composite while configuring the JMS adapter, select the queue which you have created above.
If you have followed the abpve steps correctly, you should not face any problem.
Hope this helps,
N

JMS Adapter Destination Name value

Similar Messages

Maybe you are looking for