Cluster ID in JMS adapter

Hi All:
What is the Cluster ID in JMS adapter? I chose QoS = EOIO. It is asking me
Queue ID and Cluster ID.
I know Queue ID can be the Queue Name within 16 limit. But what is Cluster ID and what value I need to fill in it??
Thanks
Farooq.

Hi,
you don't need to fill it in:
"If you do not enter the cluster ID, the EOIO channel is activated automatically on a different working node. This configuration ensures node failover by the adapter in a clustered environment."
but you need to read this:
"This specification stops queue-jumping in the JMS queue. The valid cluster ID is located on the J2EE server Administrator under Server."
from:
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Regards,
michal

Similar Messages

How to set property for Cluster Environment for JMS Adapter

Hi All,
I am moving from DEV to Prod environment which is cluster.
Can you Please explain me what property I need to Set for Cluster Environment for JMS Adapter, so that I could avoid race condition for Dequeue/enqueue.
I am using soa suite 10.1..3.4
Thanks in Advance.
Edited by: vikky123 on Jul 12, 2010 7:03 AM

put something like this
<activationAgents>
      <activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="PARNERLINKNAME">
        <property name="clusterGroupId">SOMEUNIQUEVALUE</property>
        <property name="portType">PARTNERLINK_PORTTYPE</property>
      </activationAgent>
    </activationAgents>

Accessing JMS UDD deployed on OSB cluster from a composite JMS adapter deployed on soa cluster

Our environment setup
Single domain with three clusters
osb_cluster.soa_cluster and bam_cluster
osb_cluster: osb_server1 and osb_server2
wlsbJMSServer_auto_1: targetted to osb_server1
wlsbJMSServer_auto_2: targetted to osb_server2
osb_subdeployment1:targetted to wlsbJMSServer_auto_1 and wlsbJMSServer_auto_2 JMS servers
osb_subdeployment1 has JMS UDD queue jms/wlsb/queue
soa_cluster: soa_server1 and soa_server2
There is a BPEL composite deployed to soa_cluster. It has JMS adapter trying to read messages from jms/wlsb/queue
JCA JMSAdapter is deployed to osb,soa clusters and Admin server
ConnectionFactory is targetted to soa and osb clusters (osb_cluster and soa_cluster)
We have bounced soa and osb servers(not admin) after jms changes.
soa log says
JMSAdapter Composite1l JmsDDEndpoint_onFailure: Unable to resolve 'jms.wlsb.queue. Resolved 'jms'
Can we access JMS destinations deployed on one cluster from different cluster?
If yes, how can we do that ? do we need to modify BPEL JCA file to indicate destination is on another cluster?
Thanks,
Praveen

Anybody has faced similar issue?

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?

Sender JMS Adapter with EOIO Quality of Service

Hi,
I have a sender JMS adapter with a quality of service as EOIO. In the SAP help it says that I need to specify the "Processing J2EE Cluster Server (Cluster ID)". Just wondering how I get this value? Does anyone have an example?
Thanks,
Krishneel

Hi,
Please go through the bleow Wiki:
http://wiki.sdn.sap.com/wiki/display/XI/FAQ+J2EEJMS+Adapter
http://help.sap.com/saphelp_nwpi71/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Thanks,
satya

Problem in configuring JMS adapter

Hello,
My purpose is to send xml data from MQSeries to BW using XI. MQSereies is installed in XI server. For thah I am trying to configure JMS adpter for MQSeries in XI. I have successfully deployed the necessary external drivers using SDM. I have configured the sender channel with the following parameters.
Adapter type: JMS
Transport Protocol :WEBsphereMQ(non-JMS)
Message protocol :JMS1.x
Queue connection factory java class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class: com.ibm.mq.jms.MQQueue
IP address: IP address of XI system.
Port: 1414
Queue manager name : MQ-manager-name_XI-system-name
Channel Name : reciever-channel-name_XI-system-name
JMS queue: postcard
Charecter set ID:
Transport/networkprotocol: TCP/IP
JMS-Compliant : WebsphereMQ(non-JMS)
But when I check it in adapter monitor JMS is shown as red.
When I go to Visual Administrator
"cluster->server->services->monitoring->runtime->monitor tree->services->Connector Service" is white instead of green.
Can any one tell what could be the problem.
Regards,
Amith

Hi Vijaya,
In VA there is only option to stop or start JMS XI adapter.
I dont know where to activate JMS adapter in VA. It is already started in VA.
Regards,
Amith

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

Mediator Resequencer,JMS Adapter: queue consumers increase from PS2 to PS4

Hi,
We have an environment using SOA Suite and Mediator Resequencer, it is using a FIFO approach. It has been running fine in SOA Suite version 11.1.1.3.
We are using a JMS Adapter, consuming the messages from the UDD queues as we have a SOA cluster of two managed servers.
Well we are now doing some test for upgrading to PS4 (11.1.15) and we have noticed some differences after the upgrade in terms of # consumers on the UDD queues.
In 11.1.1.3 eache member of the UDD was showing just 1 consumer. Looks like this is the right configuration when using and mediator resequencer FIFO approach, as they say you need to have a single-threaded approach to avoid unpredictible result.
After upgrade that, we have noticed that in 11.1.1.5 each UDD member shows 2 consumers, we have not changed anything, we just follow the upgrade guide to do that. To be honest we are not sure wheter it is a problem or not.
Can anybody advise about that? If it is an issue, How and where can configure it to get back to 1 consumer connected to UDD member?
Thanks a lot!

The Bridge is configured to use the MQ CF and destination directly without the foreign JMS wrapper. Does this make any difference to the bridge's transactional behaviour with MQ?
Even with the foreign jms wrapper, the local jndi name of the MQ CF is still mapped to com.ibm.mq.jms.MQXAQueueConnectionFactory class. So I think there is no wrapper classes are used from foreign JMS perspective. But if a bridge is configured to lookup local jndi, does it add any wrapper classes which handles the XA interactions with MQ in a different way ?
I am trying to see if introducing a foreign server resolves the problem. Not sure if its worth to take this path.
Thanks in advance.
Regards,
Atheek

JMS Adapter Classpath

Folks...
I am having problems with a conflicting Java .class file existing on WebAS and in a WebLogic driver I deployed for use with the JMS adapter. I am looking for a problem solving approach for this issue.
I am able to post a message to WebLogic using a JMS receiver adapter, but the adapter immediately invalidates with a ClassCast exception once the message has been posted. After intensive debugging of the Java code in the driver I have discovered that this due to a conflict with WebAS due to a .class file with the exact same name. Specifically Request.class. WebAS has a Request.class and the WebLogic driver contains a Request.class, hence the ClassCast exception.
What I am hoping is that there is a way to isolate the classpath for the adapter so that I can prioritize the .jar file before the standard SAP .jars. This way the adapter will find the WebLogic Request.class file before the SAP Request.class.
If someone has a different way to approach this problem I am all ears. As usual many thanks for reading this note. -Jonathan

Folks... In case anyone is interested. The full path for the Request and Response objects in WebAS are
\usr\sap\RKK\JC01\j2ee\cluster\server0\apps\sap.com\tc~uddi\servlet_jsp\uddi\root\WEB-INF\classes\com\sap\uddi\interfaces
\usr\sap\RKK\JC01\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.netweaver.bc.uwl\private\classes\com\sap\netweaver\bc\uwl\core\push
They appear to be related to UDDI and UWL. So this afternoon I am going to try and delete them to see if the problem is corrected. If anyone has information on what these class files do then that would be helpful as well. I know that WebAS comes out of the box with services that are not always used by every usage type. It may be that these files are not needed by XI.
Thanks

SOA JMS Adapter JCA Properites Issues

Hi,
we are using JMS adapter in a BPEL process for polling on a JMS queue which has Destinationname= "Queue1".
After deploying the composite we are changing JCA property Destinationname="Queue2" through SOA EM console.
It is working fine as expected,but when we restart the SOA server,then agian the Destinationname is pointing to "Queue1".
This is not expected functionality. Seems like a bug. . We have to change the settings every time the server is bounced.
Any Suggestions on this would be appreciated.
Regards,
Sudhakar.M

Hi Arun,
We have implemented minimumDelayBetweenMessages property in SOA Dev standalone environment.it is working AS excepted.
But when test this in Cluster environment it is not working as expected. then using oracle JCA documents we i found some other properties need to set
<property name="adapter.jms.receive.threads">1</property>
<property name="clusterGroupId">myBpelCluster</property>
<property name="clusterAcrossSubnet">false</property>
can you explain what is each property do,
what is the clusterGroupId value ? can we put any value or name of the SOA cluster.
what is the value we need to set for clusterAcrossSubnet?? how to decide .
Any help would be appreciate.
Regards,
Sudhakar.M

MDB,MDB container or JMS adapter stops processing messages from JMS queue

Hi guys,
we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
Thanks for your help.
Cheers,
Martin
Edited by: east1979 on Jan 13, 2009 8:06 AM

Hi Manoj,
I have a very similar if not identical issue,
Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
15/11/12 09:10:08 JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
TION TO CONTINUE.
15/11/12 09:10:15 Communication Error. See real time job log for details.
Dump available:
https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
Version of DS:14.0.3.273
Any comments?
Thansk and kind Regards,
Kenneth

Having multiple service operations in a single JMS adapter best practice

Hi All,
I am using JDeveloper and SOA Suite 11.1.1.6. I need to read from multiple JMS Topics and transform and enhance the messages through the Mediator and then persist into Database.
My question is
What is the best practice to consume from multiple topics, Should I configure separate JMS adapter for each of the Topic destination
OR
have a single JMS adapter with multiple operations by manually changing the JMS adapter wsdl and jca file?
I find cannot have
Please suggest.
Thanks in advance
Edited by: user5108636 on 15/05/2013 11:36

Hi Vijay,
did you actually test this? When I finish creating a DBAdapter, there is a operation present. Then when I click edit again on the DBAdapter, and I create another select, when I finish only the first operation is gone, and I can only see the one I've created via the last edit.
I dont understand your reply. Can I have two operations, each one with select underneath, in the same adapter?
Edited by: user13604541 on Jan 30, 2012 11:19 AM

Calling Foreign JMS in SOA Suite 11g JMS Adapter

Hi,
Just want to get some guidance in the implementation of Foreign JMS in WebLogic 10.3.
I followed the creation of the Foreign JMS Server using this document:
http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/foreign_servers/CreateForeignServers.html
I am trying to connect to a remote Weblogic 10.3 JMS queue but cannot get pass the JDev wizard stage.
I need to call the foreign JMS via the Fusion 11g JMS Adapter but cannot lookup the destination from the JDev wizard. My composite will produce a message that will end up in the remote queue.
Has anybody got this to work? Is this supported in JMS Adapter? I've read quite a few using MDB to call the Foreign JMS but not JMS Adapter.
Regards,
Robert

Please refer to the following document that shows how to access remote wls jms queues and topics. This is the preferred way when accessing remote wls destinations.
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10231/adptr_jms.htm#BABJACJA
Thanks
Aman

Invoking Jms Adapter from BPEL with enque stoped

Hi guys, I have an issue.
In my BPEL flowI have an invoke activity which has a jms adapter as a partner link.
The thing is that if you stop the enque in the DB, your flow in BPEL continues like nothing happened. It just passes the payload to the jms adapter. From it's point of view is asynchronous , but I want to make sure that the payload is in the queue before I continue the flow.
Any ideas?

Hi Oracler,
I don't understand what you mean by XML schema inline? Where do you define that in a JMS adapter ? Can you be more specfic when you say Try including both the elements(TEXT_LOB , TEXT_VC ) in the schema? I don't have those elements in my schema at all. I have tried the opaque option I still get the same Translator NULL error.
Please anyone help....

Sending Msg From HTTP client to XI through JMS Adapter using WebSphereMQ

Hello
I am trying to send some msg from Http client
I configured JMS adapter as receiver
Transport Protocol :WEBsphereMQ JMS provider
Message protocol :JMS1.x
I have given the Ip address of my machine where I installed WEB Sphere MQ
Server Port :1416
Transport Protocol :WebSphere MQ
JMS compliant: JMS-compliant
In SXMB_MONI
Http client sends message without any error.
But while tracing I got message
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
Can anybody tell me the solution..
Thnaks

Hi,
I have not directly faced this but i may suggest ,
1. What do you see in sxmb_moni, do you have a queue problem?
2. see this File-to-File Scenario Stopped Working the reply from Shravan and the last message.
<i>The XBTO que was the problem. I deleted all LUWs in it and now new transactions are working again</i>
3. You may also use this /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Anirban.

Cluster ID in JMS adapter

Similar Messages

Maybe you are looking for