JMS adpater

Dear Expertise,
I have some doubts in JMS Adpater.
1. IS JMS adapter in XI is JMS client?
2. If JMS adaper CC is in sender mode, will XI pull the data(queues) from JMS server or JMS server will send the data to XI.
For IDOC to JMS scenario, what are the steps need to be done in repository framework.
My question is how to send that IDOC data to JMS server. For this, is any message mapping and interface determination required, as I want to send the same IDOC data to JMS server queue.
Advaced Thanks,
Gujjeti

Praveen,
To work on JMS adapter first you need to install the drivers. Check this document on how to install the drivers:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ffd890-0201-0010-708f-d5dad2dfcf3a
Once when you do this it is just like your normal scenario. Check this weblog for some help on how to configure your receiver JMS adapter:
/people/kan.th/blog/2007/02/05/exploring-jms-and-sap-xi-jms-adaper
Also check this for some info. on JMS adapter:
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
---Satish

Similar Messages

  • JMS Adpater Error

    Hi all
    I configure the JMS receiver Adpater of webSphereMQ
    but i got the error as followed:
    <b>Receiver channel. Details: MQJMS2005: failed to create MQQueueManager for '172.31.235.100:QM_Test'</b>
    I have a doubt:
    The XI and MQ are in the same server, should i configure the network of MQ such
    as the domain MQM or something else
    and i have searched this issue in this forum, but there is no solution
    I am eager for your reply
    And Thanks in advance

    Hi Leo,
    have u seen these..
    configuration of JMS  adapter Using WebSphereMQ
    SAP XI and JMS for WebSphere MQ
    connection with the JMS provider
    cheers,
    Prashanth
    P.S Please mark helpful answers

  • Reciever JMS Adpater Error

    Hi Experts,
    I am getting following error in Reciever JMS adapter:
    I am using transport protocol is Acces JMS provider with JNDI
    Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=http://168.89.59.82:7005/, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: CC_eRespond_ServiceTicketson node: 8273250 having object id: d72754188a053d43b6aa0dd420346941: javax.naming.CommunicationException
    at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:66)
    Can anyone please tell me what is the cause of this error.
    Kind Regards,
    Praveen.

    Hi Experts,
    We are sending messages from XI to Weblogic server with the help of JMS Adapter. The Queue is available in Weblogic server.
    Our configuration of JMS receiver Adapter is
    JNDI Lookup Name of Queue Connection Factory----
    ConnectionFactory
    JNDI Lookup Name of JMS Queue----
    queue/IntegrationQueue
    Name of JNDi Initial Context Factory: -
    weblogic.jndi.WLInitialContextFactory
    JNDI Server Address:----
    weblogic server ip
    JNDI Logon User: -
    user
    JNDI Password: -
    password
    Could you please help us.
    The Error message as follows
    Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=http://IP:port/, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: CC_eRespond_ServiceTicketson node: 8273250 having object id: d72754188a053d43b6aa0dd420346941: java.lang.NoClassDefFoundError
    at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:66)
    Regards
    Praveen

  • Special Char disappear after the JMS Adpater

    Hi all,
    I have a problem and nees help because I don't know the solution.
    We send a flat Idoc via a JMS Adapter from XI to a Websphere Queue.
    The flat Idocs have special chars like "ø", "ö", "ä"...
    Unforunately in the message on the queue (after the JMS adapter) we miss this chars and one char behind the special char. They are away.
    In XI I can see that the char are there.
    So I think the that JMS adapter removes this files.
    Can you help me please? What do I need to change in the JMS adapter?
    Thanks and regards
    Manuela

    sounds like an encoding problem. Seems there is a way to change the encoding at the JMS receiver side.
    Have a look at this thread : Re: Change encoding from utf-8 to iso-8859-1 in JMS receiver!

  • JMS adpater issue in XI to MQ

    Hi,
    I am trying to connect XI 3.0 with MQ 5.3. I have done all the mappings in Int. rep. and configurations in the Int. directory. I am using an Outbound JMS adapter to pick up the file from MQ. The details like channel name etc. are given correctly. The integration isn't happening in spite of all these and the MQ driver installation. I would like help on some areas.
    - I am not able to see any log file on what went wrong. I tried sxi_monitor but there were no messages. I tried the Runtime workbench but that isn't listing the JMS adapter. SAP says that it will be listed only after it starts working.
    - The file exists in 'text' format in MQ. So I am not using any conversion in Module in the Outbound JMS adapter.
    - Is there anything else to watch out for in the Int. directory configurations?
    - Does MQ have to reside in XI ? Right now it's in a separate server
    regards,
    Madhavan

    Hi Madhavan,
    A valid 'JMS adapter channel' as sender, and any Sender Agreement refering to this channel, should make the JMS adapter in green.
    In Adapter Monitor, if the status of 'JMS' is:
    1. Not visible in list: Then reimport SCV: 'Basis components' in IR.
    2. GREY: Then no JMS channel is defined or activated. Its a cache problem. Refresh the Directory cache, and check again in monitor.
    3. RED: The list of channels is displayed, and the error message is given. Accordingly you could fix it.
    4. GREEN: No problems. But if it hasn't processed any messages, it shows as - "Sender Channel. (No Details available)". To verify if the channel is really working, try to change the MQ Server name / Queue name to cause an error - and Adapter monitor shows RED for JMS. This indicates that earlier connection was successfully established.
    What is the status in your case?
    See if this information helps to fix yourself..
    regards,
    Pops V

  • BPEL JMS Adpater to publish message to B2B Internal Delivery Channel

    We are planning to use the JMS adapter in BPEL to publish message to B2B Internal Delivery channels. But during the JMS Adapter configuration it doesnt list the B2B Internal queues (IP_OUT_QUEUE and IP_IN_QUEUE) in the list of queues. However for AQ Adapter in BPEL, during the AQ Adapter configuration its lists the queues(IP_OUT_QUEUE and IP_IN_QUEUE) in the list of the queues. We used the same database connection and user for both the adapters. The B2B queues are in the B2B repository.
    Can we use the JMS Adapter in BPEL to publish message to B2B internal delivery channel and if so is there any other configuration we need to do?

    You can use the default AQ to pub/sub messages in/out of the IP_IN and IP_OUT Qs.
    However, if you still need to use JMS, then make the B2B listen to this JMS Q and then use the JMS adapter.
    Using the default AQ should be robust and simple. But, again we have seen several customers implementing in thrid party JMS providers as per their business scenarios.
    Regards
    Anirudh Pucha

  • JMS Adpater Question

    I am trying to implement the JMSAdapter in the two way mode.
    I have configured the queues and have configured the JMS Adapter appropriately.
    I do see the response being generated but the correlation doesn't seem to work.
    Error Message:
    Fault ID     rejected:60006
    Fault Time     Apr 13, 2012 4:44:31 AM
    Non Recoverable System Fault :
    Cannot complete callback since unable to retrieve SourceURI/Wire from Correlation store. Either Instance Tracking is diabled or no corresponding Request succeeded prior to this callback
    The payload details for this rejected message can be retrieved
    Any idea what's missing??
    I do see the response message on the queue.

    Got it to work....had missed setting the Correlation ID in my JMS application :) my bad ..:)

  • JMS connection from SAP PI to Oracle AQ via JNDI...

    Hi,
    I am currently working on a project that requires connections between PI and Oracle AQ. It was advised that we shoule use PI JMS adpater with JNDI driver. However, it seems that not many people have tried this approach.
    Has anyone had similar solutions in production ? How repliable it is ?
    Your help is very much appreciated
    Tim

    Hi Tim,
    We implemented a similar scenario and now itu2019s still working.
    You have to configure a JNDI connection, but not directly with the Oracle AQ. The Oracle AQ are just queues, and you need a JMS provider in order to establish the connection with these queues. The solution we implemented was:
    1. Configure one OC4J server as JMS provider for the Oracle AQ queues.
    2. Configure JMS communication channels in SAP PI to establish the connection with the OC4J server.
    Maybe you can use a different and newer JMS provider, as BEA Weblogic or SAP WAS (I donu2019t know if itu2019s possible).
    We implement the scenario in SAP PI 7.0, and with this version we had a problem: When the communication between JMS adapter and the queues was broken (the DDBB fell down for example), the channel failed, itu2019s normal. But when the DDBB was already running the channel stayed in an error state, and we had to restart the channel manually. The response of SAP to this issue was that the channel behavior was correct because the connection failed.
    But this problem occurred rarely, maybe once a month. The solution is very reliable, we exchange a lot of message with this solution, and support messages of any size with an excellent performance.
    Best Regards,
    Roberto

  • Error while using webmethod JMS provider with JNDI

    Hi,
    I am using webmethod JMS provider (not SAP JMS) with JNDI to connect to webmethod with XI. Central J2EE adapter engine is used and the comm chaneel is configured in with appropriate Provider JNDI Server address, initial context factory, Name of queue connection factory etc. 
    While activated the adapter short log shows: Adapter has not provided any status information about this channel"
    In the detailed log following error message is displayed: "Obtained connection factory: null#"
    #1.5 #001A4BAC31000052000001520000152200045090BF28DACA#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
    #1.5 #001A4BAC31000052000001530000152200045090BF28DB65#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Looking up connection factory under name NAIP_XIQueueConnectionFactory#
    #1.5 #001A4BAC31000052000001540000152200045090BF28E42E#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Obtained connection factory: null#
    #1.5 #001A4BAC31000052000001550000152200045090BF28E4B3#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
    #1.5 #001A4BAC31000052000001560000152200045090BF28E528#1214482519516#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
    #1.5 #001A4BAC31000052000001570000152200045090BF28E5A9#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Info##Java###Sucessfully executed CF invocations for connection factory object: for profile: #2#<null>#ConnectionProfile of channel: CC_RCV_JMS_SAPJNDIon node: 3010950 having object id: e4413a5265a436459e271d5e0dd4859b#
    #1.5 #001A4BAC31000052000001580000152200045090BF28E64E#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
    #1.5 #001A4BAC31000052000001590000152200045090BF28E6CA#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
    #1.5 #001A4BAC310000520000015A0000152200045090BF28E741#1214482519517#com.sap.aii.adapter.jms.core.common.StringUtils##com.sap.aii.adapter.jms.core.common.StringUtils.isBlank(String str)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
    #1.5 #001A4BAC310000520000015B0000152200045090BF28E7C3#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Creating connection...#
    #1.5 #001A4BAC310000520000015C0000152200045090BF28EB51#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning##Java###Catching #1#java.lang.NullPointerException
    at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection(ConnectorImpl.java:198)
    at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:166)
    at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:186)
    at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:151)
    at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:235)
    at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:154)
    at com.sap.aii.adapter.jms.core.channel.AdapterImpl.doAddUpdateChannel(AdapterImpl.java:404)
    at com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(AdapterImpl.java:376)
    at com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl$1.run(ChannelLifecycleCallbackImpl.java:51)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    #1.5 #001A4BAC310000520000015D0000152200045090BF28EC6A#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Error##Plain###[[ChannelName:CC_RCV_JMS_SAPJNDI,ChannelId: e4413a5265a436459e271d5e0dd4859b]] Error adding/updating channel.#
    #1.5 #001A4BAC310000520000015E0000152200045090BF28ECF8#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
    #1.5 #001A4BAC310000520000015F0000152200045090BF28ED76#1214482519519#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl##com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded().run()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
    #1.5 #001A4BAC3100005F000000660000152200045090BF65478A#1214482523474#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded(Channel channel)#AAAAAAAAA#108##n/a##002ee500437911dd99cf001a4bac3100#SAPEngine_Application_Thread[impl:3]_29##0#0#Path##Plain###Exiting method#
    Please let me know anyone has come accross the problem or has idea how to solve it. Thanks.

    Hi,
    Ask ur basis admin to restart JMS adpater From Vis administrator and try again to activate the comm channel.
    Hope this will solve ur problem and once again check connection fatcory and Queue name provided by Webmethod admin.
    Regards,
    Srini

  • Error in  JMS Adapter  for MQ series

    We have configured a JMS Adpater to connect to  MQ Serries queue manager running on our local server. The XI Server is a remote server where JMS adapter is deployed.
    Upon deployment we see following string in JMS adapter log -
    Sender channel. Details: com.ibm.mq.jms.MQQueueConnectionFactory
    And the status of Adpater is RED.
    The Adpater is configured in sender mode.
    We have created a local queue in Queme Manger and a Server Connectio  channel which is being used in adpater configuration.
    Please suggest what could be the missing link here.
    Appreciate if you can provide us link s to any docuemtn which details the steps to configure an MQ JMS adapter.
    Thanks,
    Garima

    Hi Garima,
    Please check the following:
    1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
    2. Check the existence of your JMS drivers.
    3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
    https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
    There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
    Any of the above solutions should help you solve the problem.
    Regards,
    Abhy

  • PI 7.1 JMS adapter - Inputs required.

    Hello Folks,
    There is a requirement to put the below message on the JMS queue.
    EDI_DC40  2000000000001046284700 0312  PEXR2002                                                    PAYEXT                                     PAYEXTSAPSD0    LS  SD0_200                                                                                ZMIDDLE   B   0006000000                                                                                20100924174721                                                                                20091215094549      EOSE2IDKU1                       200000000000104628400000100000001PEXEXTENDED PAYMENT ORDER             2000000665                         ORG001EOS
    However the message that XI is putting on JMS queue is:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_JMS_EFTPAYMENTS xmlns:ns0="urn:pi:eftpayments:mq"><MessagePayload>EDI_DC40  2000000000001046284700 0312  PEXR2002                                                    PAYEXT                                     PAYEXTSAPSD0    LS  SD0_200                                                                                ZMIDDLE   B   0006000000                                                                                20100924174721                                                                                20091215094549      EOSE2IDKU1                       200000000000104628400000100000001PEXEXTENDED PAYMENT ORDER             2000000665                         ORG001EOS                 ............................... </MessagePayload>
    How can i get rid of the XML tagging in the start and end on the JMS adapter?
    Thanks!!
    Harpreet

    >
    Harpreet Daphu wrote:
    > Hello Folks,
    >
    > There is a requirement to put the below message on the JMS queue.
    >
    > EDI_DC40  2000000000001046284700 0312  PEXR2002                                                    PAYEXT                                     PAYEXTSAPSD0    LS  SD0_200                                                                                ZMIDDLE   B   0006000000                                                                                20100924174721                                                                                20091215094549      EOSE2IDKU1                       200000000000104628400000100000001PEXEXTENDED PAYMENT ORDER             2000000665                         ORG001EOS
    >
    > However the message that XI is putting on JMS queue is:
    >
    > <?xml version="1.0" encoding="UTF-8"?>
    > <ns0:MT_JMS_EFTPAYMENTS xmlns:ns0="urn:pi:eftpayments:mq"><MessagePayload>EDI_DC40  2000000000001046284700 0312  PEXR2002                                                    PAYEXT                                     PAYEXTSAPSD0    LS  SD0_200                                                                                ZMIDDLE   B   0006000000                                                                                20100924174721                                                                                20091215094549      EOSE2IDKU1                       200000000000104628400000100000001PEXEXTENDED PAYMENT ORDER             2000000665                         ORG001EOS                 ............................... </MessagePayload>
    >
    > How can i get rid of the XML tagging in the start and end on the JMS adapter?
    >
    > Thanks!!
    > Harpreet
    either use content conversion modules in your JMS adpater as mentioned in the earlier post or write a simple java map to extract the required payload from the XML and post that payload to the adapter

  • How to set password in JMS adapter

    Hi All,
    I have put a JMS adpater partner link into a BPEL process, and everything seems to work fine, except that it wants to authenticate to the App Server using oc4jadmin/welcome1 and I used a different password.
    Can anyone tell me where to set the password it uses?
    I have tried putting it in the JMS Adpater's wsdl file under the jca:address section as mcf.Password, and as properties on the adapter partner link itself. Neither of these seem to work.
    Thanks for your help,
    Mark Nelson

    Mark,
    When you say "authenticating to the app server" you mean the adapter authenticating to the JMS Provider (running in the app server), correct?
    If so, the username/password are in oc4j-ra.xml, more precisely:
    %J2EE_HOME%\application-deployments\default\JmsAdapter
    (you might have to change "default").
    Look for your adapter connector-factory. It should have:
            <config-property name="username" value="oc4jadmin"/>
         <config-property name="password" value="welcome1"/>I understand that this sounds like the previous recommendation but this really should be it. Might be confusing as they are various instances of oc4j-ra.xml.
    Let us know how this works.

  • Weblogic Connection with Oracle JMS AQ errors

    Hi All,
    I am a newbie with SOA 11g and I am trying to do a simple test case for a use case of connecting Oracle AQ JMS with Weblogic and using it in my SOA 11g process. I am trying to publish something to my queue that I created but I am getting this error in the weblogic / soa log files pasted below :
    The steps I followed exactly are this :
    1) Created a Database Queue called DemoInqueue using the following scripts :
    exec dbms_aqadm.create_queue_table ( queue_table=> 'DemoInQueue', queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers=> FALSE, compatible=> '8.1');
    COMMIT;
    exec dbms_aqadm.create_queue(queue_name=> 'DemoInQueue', queue_table=> 'DemoInQueue');
    COMMIT;
    exec dbms_aqadm.start_queue('DemoInQueue');
    COMMIT;
    2) Created a Data Source in weblogic server : Called it using the JNDI name : jdbc/oracle/jms Driver Class Name : oracle.jdbc.xa.client.OracleXADataSource (I tested the connection it works fine)
    3) Created a JMS Module (JMSTestModule) and then Created a New Summary of Resource for it ( AQServer) and chose option Foregin Server.
    Under General Tab, I gave "oracle.jms.AQjmsInitialContextFactory" as the JNDI Initial Context Factory and Under JNDI Properties I put in "datasource=jdbc/oracle/jms" as I created the above datasource.
    Under Connection Factores I created a new "ForeignConnectionFactory-0". Under Configuration I gave Local JNDI name as "jms/DemoCF" and remote JNDI Name as "XAQueueConnectionFactory" (I have also tried with
    QAConnectionFactory but no difference )
    Under Destinations I created a new "ForeignDestination-0" with local JNDI name as "jms/DemoInQ" and Remote JNDI Name as "Queues/DemoInQueue" (Because my Queue name is that)....
    4) I restarted the Weblogic Server then went to SOA suite and tried a very simple process Hello world added a JMS adpater....Inside the adpater I selected OEMS (Advanced Queueing), App server my weblogic server,
    operation as ProduceMessage and when I hit Browse I was able to see my AQServer ForeignDestination-0 Queue. I selected it and under destination name it populated "jms/DemoInQ" but under JNDI name it also
    populated "eis/aqjms/Queue" I left that as is and deployed my process and tried invoking it. It failed with the error message below.....I also tried modifying the JNDI name to something else...in Jdev..but the results
    are the same....
    Are these steps correct ? Am I missing something here.?
    I followed all the blogs and forums in this site and I think I did all the steps...but if anyone can help me I would really appreciate it...
    Here is the error stack below :
    <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437281> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    ####<Dec 1, 2010 2:07:17 PM EST> <Warning> <Connector> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437296> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    SOA LOG.....
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.adapter> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <JCABinding=> [default/HelloWorldComposite!1.0*soa_25f514de-3db3-4bed-9144-44d83dacbe10.Publishmessage]:Produce_Message One-way operation Produce_Message() failed>
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.bpel.engine.ws> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <<WSInvocationManager::invoke> got FabricInvocationException
    oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
    Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue.
    JCA Binding Component is unable to create an outbound JCA (CCI) connection.
    HelloWorldComposite:Publishmessage [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.

    Thanks for passing along the link.
    The part about Oracle's documentation not mentioning the JmsAdapter configuration was a real sticking point for me - I was having the same problem as the original poster until I updated that deployment as the link outlined.
    Also, towards the end of that link the author mentions running in to problems getting their composite to successfully bind to the queue definitions that were created in WebLogic.
    I attempted post my solution to this on the original site, but I'm not sure if it got through - so I'll add the details of what worked for me here:
    Connection Factory:
    Local JNDI: aqjms/JMSTest_Connection_Factory
    Remote JNDI: XAQueueConnectionFactory
    Destination:
    Local JNDI: aqjms/JMSTest_Queue
    Remote JNDI: Queues/JMSTest_Queue
    Outbound Connection Pool:
    Name: eis/aqjms/JMSTest_Queue
    Connection Factory: aqjms/JMSTest_Connection_Factory
    JDeveloper Composite:
    Destination Name: aqjms/JMSTest_Queue
    JNDI Name: eis/aqjms/JMSTest_Queue
    Cheers,
    - Nathan

  • JMS file to idoc

    Hi,
    where in I will get the file is read using JMS adapter,here I have a problem with the content of the flat file as shown below
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <MessageHeader>
    <RecipientId>SAP.TEST</RecipientId>
    <RecipientSapSystemId>xxxxx</RecipientSapSystemId>
    <RecipientIdQualifier> Application</RecipientIdQualifier>
    <SenderId>aaaaa</SenderId>
    <SenderIdQualifier>yyyyyyy</SenderIdQualifier>
    <ApplicationId>zzzzzz</ApplicationId>
    <ApplicationIdQualifier> Application</ApplicationIdQualifier>
    <DateSpecifier>iii</DateSpecifier>
    <DateFormatSpecifier>YYYYMMDD</DateFormatSpecifier>
    <Date>20110208</Date>
    <TimeFormatSpecifier>HHMMSS</TimeFormatSpecifier>
    <Time>154126</Time><AuthorizationId>sunny</AuthorizationId>
    <MessageKeyData>???</MessageKeyData>
    </MessageHeader>
    TID00702751               
    TTE007027512011-02-08-15.41.00.000000K210164   450003280000032700001173490003906
    TO100011734                                                   AJL               
    TO200004004700000000326007600000720800005057000
    Thanks in advance
    Edited by: SWATHIP on Feb 24, 2011 7:03 AM

    I think, your mmeta data file i.e. message type is in complete as it has only header so JMS adpater is not able to convert the entir message into XML.
    /Adi

  • Restrict SOA JMS Adapter dequeue frequency

    Hi,
    we are reading messages from third party JMS queues in the BPEL Process using JMS Adapter in the Composite. Sometimes because of more load on the JMS queue ie around 40 records per second we are facing load issues. BPEL is able to read close to 40 records per second from the queue and calls the Oracle Agile 9.3.2 Web services but the Agile web services are not able to handle such heavy load.
    We want to throttle the JMS Adapter and limit the number of messages we dequeue.
    What properties in JMS Adapter need to configured to control the dequeue rate.
    Here is .jca file of the JMS adpater
    <adapter-config name="ReadFAQueue" adapter="Jms Adapter" wsdlLocation="ReadFAQueue.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
    <connection-factory location="eis/jms/C3FAQueueCF" UIJmsProvider="THIRDPARTY" adapterRef=""/>
    <endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
    <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
    <property name="DestinationName" value="zzqmsbw1.queue.bw.fa"/>
    <property name="UseMessageListener" value="false"/>
    <property name="PayloadType" value="TextMessage"/>
    </activation-spec>
    </endpoint-activation>
    </adapter-config>
    Regards,
    Sudhakar.M

    Hi All,
    Finally I got Answer from SR.
    Here is the link which explain frequency set..http://sudhakarsoa.blogspot.com/2011/03/how-to-set-delay-between-jmsaq-quque.html

Maybe you are looking for

  • I deleted my SYNC Key and now realilze I want it. How do I reinstall it. The Sync Key under options does not work

    I deleted the Sync Key, I thought it was just a refresh button and was not working. I have now read more about it, and want ot reinstall it, but when I go from tools>options.Sync, I get: Incorrect account name or password: Update, reset or unlink I h

  • BCF by Profit center

    In the Matrix Consolidation ( Using Company Code/profit Center), can we do the balance carryforward by profit center. Means in the year end balalnce carryforard has to be clearly executed only using profit center and balances has to be carry forward

  • Create Photoshop stil with alpha channel?

    I'm using dvMatte Pro3 to strip out the green screen. I'd like to be able to generate a Photoshop CS4 file with the alpha channel, so that I could composite the background in Photoshop, but I haven't been able to get that to work. Is there a way to d

  • Organizer view

    I know it's probably something basic, but how do i get my Mediasource to open up in Organizer view, rather than Player view please ?

  • I have lost the short cut to DBA studio?

    Does anyone know how to replace it. (I mean it should be obvious shouldn't it!!!) If anyone could post the target file including any launch text I would be very gratefull :) Ta.