JMS adapter not registered

We are integrating Weblogic JMS with SAP using JMS adapter in XI and in communication Channel we are getting message as "JMS_SENDER - n/a - No adapter registered for this channel " , How to register the JMS adapter ??

Sorry,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ffd890-0201-0010-708f-d5dad2dfcf3a
or try it other:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a05b2347-01e7-2910-ceac-c45577e574e0
Edited by: Carlos Ivan Prieto Rubio on Dec 17, 2007 5:17 PM

Similar Messages

JMS Adapter not appearing in Adapter Monitor, How to Fix ?

JMS Adapter not appearing in Adapter Monitor screen when choosing "Only Installed and Started Adapters" option. What need to do to install and start the JMS adapter.
Thanks in advance

Hi,
Only JMS adapter is not seen in the adapter monitor or other adapters are not listed in the same.
Have you checked whether the JMS drivers are installed on XI or not?
First would be to deploy drivers for JMS scenarios - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
Thnx
Chirag

Jms adapter not polling messages from jms topic

Hi
We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
<adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
    <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
      
      <property name="PayloadType" value="TextMessage"/>
      
      <property name="UseMessageListener" value="true"/>
      <property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
    </activation-spec>
</endpoint-activation>
</adapter-config>
If we remove Durable subscriber and message selector properties,its able to poll messages.
Any pointer will help
thanks in advance
Baji

After changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
<property name="UseMessageListener" value="false"/>
But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
<property name="DurableSubscriber" value="XYZ"/>
If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
Thanks
Baji

JMS Adapter not picking file in PI7.0

Hello,
I am working jms to jms scenario on PI7.0 Service Pack13. file is not able to pick up sendar JMS Channel. I am using WebSphereMQ Transport Protocol. JMS drivers are installed. ports and protocals are correct.
I checked all parameters of JMS Adapter. no mistake in parameters. What is the problem. Please suggest as soon as possible.
Thanks
venkat

Hi San ,
Please checke the status of JMS communication channel. In Runtime work bench , U will get the adapter monitoring there if any activity happens it shows the event details .
I hope picking the file is initial event so you can get some idea with those event log for Communication channel .
Cheers,
Reddy

JMS adapter not picking the file

Hello,
I am working jms to jms scenario on PI7.0 Service Pack13. file is not able to pick up sendar JMS Channel. I am using WebSphereMQ Transport Protocol. JMS drivers are installed.
I checked all parameters of JMS Adapter. no mistake in parameters. What is the problem. Please suggest as soon as possible.
Thanks

Hi,
Whether the Driver file has been mentioned in Provider XML file and check the messages are in the right sender Queue.
Check the Port and Protocol are right one.
Regards
Agasthuri Doss

Sender JMS Adapter - NOT Working

Hello Everybody - We are on SP13, also installed JMS Driver files on the system. We are running, Central Adapter Engine.
We configured the Sender JMS Adapter for WBI MQ->XI->SAP scenario. We need to JMS Adapter to be configured to connect to WBI from XI. Everything looks great in configuration but in the Adpater Monitoring, JMS Adapter is with Error Status and Message says "Sender channel. Details: (No detail information set.)".
Does anybody has any idea about this error ?
I checked SAP Help link as well on this. Based on this link http://help.sap.com/saphelp_nw04/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm. Do we need to configure this JMS Adapter somewhere on teh server as well ? If yes, then where ? Pls respond if you have any clue about it.
Thanks in anticipation...

Hello Stefan - Thanks for response.
Here are the Parameters.......
Adapter Type: JMS
Sender Type Clicked
Transport protocol:WebSphereMQ (non-JMS)
Message protocol:JMS 1.x
Adapter Engine:Integration Server
Queue ConnectionFactory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class:com.ibm.mq.jms.MQQueue
IP Address or Server Name:10.9.48.154
Server Port:1414
Queue Manager Name:WBIDEV
Channel Name:WBI.XI.SVRCONN
JMS Queue:XI_REQUEST
Transport/Network Protocol:TCP/IP
JMS-Compliant:JMS-Compliant
Transactional JMS Session:Check box Set
JMS Queue User:XIUSER
JMS Queue Password:********
Set XI message ID(MessageID) to:GUID(recommended value)
Set XI cenversation ID(conversationID) to:No value
Mapping of Message:Message Payload=JMS Payload
Quality of Service:Exactly Once
Time Period for duplicate check for EO(IO)(secs):86400
Wait After Message Error(msecs):1000
Wait before Reconnect(msecs):1000
Status:Active
The Error Message I see in the Adapter Monitor is "Sender Channel. Details: (No detail information set.)
Pls advice If I am missing anything ?
Thanks....
Amrish.

Restrict message volume through JMS adapter (not individual message size)

Hi, does anyone know of a way to restrict the flow of messages through a JMS adapter? For example, If I wanted to only allow up to 1000 messages to be sent in an hour to a particular system. The rest should just be queued in the Adapter Engine until the next hour begins in order to smooth out the load on the recieving system.
I know this is poor design but there is a system that is getting overwhelmed and cannot be easily changed right away. I'd like a way to control this from the middleware using standard PI (no ccBPM).
Any ideas?
Thanks in advance,
Aaron

Stefan, thank you for the idea, that is a good one.
I'm going to assume there is nothing specific we can do in the SAP JMS adapter to control the flow, and look to a solution in the queueing software like you suggested or the 3rd party application.
-Aaron

JMS Adapter service not visible

Hello All,
I am trying to configure JMS adapter for my scenarios.
I am unable to see SAP XI JMS Adapter service in the Visual Admin.
Also when activate the communication channel. In the RWB it gives error "No adapter registered for the channel"
What could be the issue?
Thanks

Hi Prabhu,
Is it newly installed server,.??? if yes may be installation not done properly i guess...refresh the cache,is problem persist contact basis team.
Regards,
Raj

Can't receive headers from JMS Adapter - "Variable is not initialized"???

I'm using JDeveloper Studio 10.1.3.4.0.4270 to try to build a BPEL process that is initiated by a JMS Adapter. I want this process to access the headers of the incoming message. Despite what Adapter Technical Note #005 says, JDeveloper says I can't do it! Despite the fact that the Receive activity is set up to store the header to a variable, JDeveloper says the variable is not initialized when I try to access it. (At least this is consistent with BPEL Process Manager's behavior -- the runtime also says it's not initialized.) In the following simple code, it looks initialized to me. What am I missing? Thanks.
<?xml version = "1.0" encoding = "UTF-8" ?>

<process name="BPELHello3" targetNamespace="http://xmlns.oracle.com/BPELHello3"
         xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
         xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
         xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
         xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/jms/ToHello3/"
         xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
         xmlns:xsd="http://www.w3.org/2001/XMLSchema"
         xmlns:ns2="http://xmlns.oracle.com/pcbpel/adapter/jms/"
         xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
         xmlns:client="http://xmlns.oracle.com/BPELHello3"
         xmlns:ora="http://schemas.oracle.com/xpath/extension"
         xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">

<partnerLinks>
    <partnerLink myRole="Consume_Message_role" name="ToHello3"
                 partnerLinkType="ns1:Consume_Message_plt"/>
</partnerLinks>

<variables>
    <variable name="inputVariable"
              messageType="ns1:BPELHello2ProcessResponse_msg"/>
    <variable name="header" messageType="ns2:InboundHeader_msg"/>
</variables>

<sequence name="main">
    <receive name="Receive_1" partnerLink="ToHello3"
             portType="ns1:Consume_Message_ptt" operation="Consume_Message"
             variable="inputVariable" createInstance="yes"
             bpelx:headerVariable="header"/>
    <assign name="Assign_1">
      <copy>
        <from variable="header" part="inboundHeader"
              query="/ns2:JMSInboundHeadersAndProperties/ns2:JMSInboundProperties"/>
        <to variable="header" part="inboundHeader"
            query="/ns2:JMSInboundHeadersAndProperties/ns2:JMSInboundProperties"/>
      </copy>
    </assign>
    <bpelx:exec name="Java_Embedding_1" language="java" version="1.3">
      <![CDATA[/*Write your java code below e.g.
     System.out.println("Hello, World");
System.out.println("Hello, Whatever");]]>
    </bpelx:exec>
</sequence>
</process>

Hi,
Your code looks correct to me. However, you should name your durable subscriber: topicSession.createDurableSubscriber(topic, "myDurableSubscriber");
Then it should be possible to use your JMS provider administration API to check that your durable subscriber is registered with your topic. Once the durable subscriber is registered it will start receiving message.
To double check that your code is correct, you should test your code with another provide.
Hope this helps
Arnaud
www.arjuna.com

JMS adapter: JNDI not able to connect to TIBCO server.

Hi All,
We are facing a strange problem here related to JMS adapter. We are trying to connect to TIBCO using JMS adapter.
We have 3 different Business Services, all the three using JMS channels. All the JMS channels are connecting to the same server on same port 7222. We have every thing same in all the JMS channels except the Que Name and the queue/log on user.
All the channels under 1 particular services are working fine while under the other two are giving below error:
===========================================
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection factoryQueueConnectionFactory, for profile: ConnectionProfile of channel: <Interface name> on node: <server node> having object id:<Object ID>: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to any server at: tcp://<host1>:7222, tcp://<host2>:7222<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:135)<br>
=============================================
Below are the basic JMS configuration:
1. QueueConnectionFactory
2. com.tibco.tibjms.naming.TibjmsInitialContextFactory
We are on PI 7.0 and working with both Sender and Receiver JMS adapters.
Looking for your help.
Regards,
Rahul

HI,
Please reply me for this question, or to the other one JNDI not able to connect . Both aer one and the other are same.
--Khaleel

JMS adapter does not recover from error

Hello everyone,
We are noticing some strange behavior with the JMS adapter, and would like your help. We have messages coming into XI from WebSphere MQ. We have configured a Sender Comm channel (MQ_SENDER) with the appropriate JMS adapter, with a specified queue name (TEST.Q) . We have installed the appropriate MQ-JMS libraries for v6.0.
Here's the problem scenario... initially the application sending the messages to the specified queue was putting an incorrectly formatted MQRFH2 structure in the message. Predictably, this caused our comm channel to fail, and it shows up on the adapter monitor in the failed state with the message "MQJMS1050: The MQRFH2 header has an incorrect format Code: MQJMS1050". This in itself is not a problem, we realized that the application was sending a malformed message. The problem occurs when we fixed the sending application to completely strip out the MQRFH2 header altogether. When the new message is sent, the comm channel seems "stuck" on the previous error, and does not even pick up the new message from the queue. The adapter monitor continues to show the same error for the comm channel. Now when we modified the comm channel to read from a DIFFERENT queue (TEST2.Q) , the comm channel got out of the error state and is able to successfully process new messages coming into that queue. However, when we revert the comm channel back to the original queue (TEST.Q) it reverts back to the original MQJMS1050 error, and does not pick up new messages on the queue.
Any assistance would be greatly appreciated...

Hi,
1) Try to refresh the metadata
2) Check the Queue status
3) Once again check the Queue name. try to make the Sender JMS adapter inactive .save it..again make it active and save it and activate the object.
4) Refresh the Cache :
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

Sender JMS Adapter does not work

Hi all,
We have created a sender JMS adapter with transport protocol "Access JMS Provider with JNDI". The adapter connects to destination successfully, so the connection parameters are right. However, we do not receive any message when the sender sends them.
What parameters should we set to be able to retrieve messages from the queue?
Thanks in advance,
Samantha.

Hi,
Into Communication Channel Monitoring, we get the following errors:
1. Error occurred while processing message: null. Detailed error (if any): java.lang.NullPointerException: at java.text.MessageFormat.applyPattern(MessageFormat.java:414) ...
2. Added dynamic header: DCJMSMessageSelector to XI message null which corresponds to JMS message selector: mentioned in the channel configuration
3. XI message ID corresponding to the JMS message with ID: ID:1109F6E3DF541328-00000000053E as stripped of the "ID:" marker and now has the value: null
4. XI message ID corresponding to JMS message with ID: ID:1109F6E3DF541328-00000000053E will be created with the value of JMSCorrelationID which has the value: null
Where is the problem?
Thanks again,
Samantha.

Sender JMS Adapter error: The JMS provider gave the error message as Not permitted, and the error code is null

I am trying to connect tibcoems with PI using a Sender jms adapter.After successfully installing the drivers , the sender adapter goes into error.
"The JMS Provider gave the error message as Not permitted, and the error code is null"
The Transport protocol is 'Access JMS Provider with JNDI' and i have been given the required parameters from the tibco guys.
Your input are highly appreciated.
Shyam

Hi AQmit,
Thanks for the reply.
Please find the screenshots of what i am trying to do.
Also, Can u direct me how to check the right logs?

Special Characters not showing correctly in XI from JMS Adapter.

Hi All,
Scenario: IBM Websphere MQ->XI->CRM (RFC Adapter)
We have a flat file being picked up by JMS adapter and content conversion is done. The scenario works fine except when specific swedish alphabets appear in the flat file. When i checked in XI, these characters appear as rubbish characters.
I understand that we need to use CCSID and put the value 00819 in the CCSID of Destination field for the Comm Channel. However i still did not have any luck after changing this field. Do i need to flush my queues and restart MQ?
Does anyone have any idea what i am missing?
Message was edited by:
lookman

Hi Lookman,
We need to make sure that the conversion to UFT-8 is done correctly, I see that as a potential cause. So first, stop the communication channel in XI, send a test file and download it from the Queue manger where XI is supposed to read the message from (using a tool like RFHUtil).
Then use a code page detector tool (http://cpdetector.sourceforge.net/) to make sure that the data is indeed in UTF-8.
By the way, the destination code page field in a Sender communication channel has no effect(http://help.sap.com/saphelp_nw04s/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm).
cheers
danus

SOA 10g JMS adapter does not pick up large messages in Oracle AQ

I am using SOA 10g 10.1.3.4 MLR #9. When I enqueue a large JMS message ( of type SYS.AQ$_JMS_TEXT_MESSAGE ) into the AQ from SOA 11g it goes into the TEXT_LOB portion of the USER_DATA column in AQ. In addition to this GROUPID and GROUPSEQ do not seem to get set. When that happens, my JMS adapterfrom SOA 10g does not seem to dequeue the message. But if I enqueue the same message using sql and set the GROUPID and GROUPSEQ my JMS adapter from 10g picks up the clob message.
How do we make the 10g adapter always pick up the large message in TEXT_LOB? I don't have this problem when the message is small because it goes into TEXT_VC field instead of TEXT_LOB field.

We are having this problem and have not figured it out yet. We need help. An oracle SR is opened but no progress from Oracle yet. I need to get some traction on this so anyone's help is appreciated. Our suspicion is that the AQ client in the wls 10.3.1 is incorrectly choosing to put the xml payload in TEXT_LOB even though the character size is less than 4000.
Here is a summary of our observations....
Today we did some testing with our old 6.3.1 OSM environment and our new 7.0.2 environment. We tested each against our QA1 environment and then our QA2 environment. Scenrio 1 is our problem. Scenario 2,3,and 4 all behave similar to each other. Why does Scenario 1 behave differently. It is causing AIA a problem when it dequeues the message.
Scenario 1:
We pointed our 7.0.2 OSM/Weblogic 10.3.1/Out of the Box AQ (which is part of our QA1 environment) to send messages to the AIA AQ table in our QA1 environment. The AIA database uses ALT32UTF8 character set. We don't know what character set the 7.0.2 OSM/Weblogic/AQ uses. Wehn we sent messages to the AIA QA1 table we saw that everything under TEXT_LEN 1000 went to TEXT_VC, Over 1000 went to TEXT_LOB. This is causes AIA to throw an exception if the message is over 1000 when it dequeus the message, because it thinks it shoudl look in the TEXT_VC which is null for AIA.
Scenario 2:
We pointed our 7.0.2 OSM/Weblogic 10.3.1/Out of the box AQ (which is part of our QA1 environment) to send messages to the AIA AQ table in our QA2 enviornment. The AIA database uses UTF8 character set. We don't know what character set the 7.0.2 OSM/Weblogic/AQ uses. When we sent messages to the AIA QA2 AQ table we saw that everything under TEXT_LEN 4000 went to TEXT_VC. Over 4000 went to TEXT_LOB. This is fine for us.
Scenario 3:
We pointed our 6.3.1 OSM/Weblogic 9.2.1/Custom AQ Solution (which is part of our QA2 environment) to send messages to the AIA AQ table in our QA2 environment. The AIA database uses UTF8 character set. We don't know what character set the 6.3.1 OSM/Weblogic/AQ uses. When we sent messages to the AIA QA2 AQ table we saw that everything under TEXT_LEN 4000 went to TEXT_VC. Over 4000 went to TEXT_LOB. This is fine for us.
Scenario 4:
We pointed our 6.3.1 OSM/Weblogic 9.2.1/Custom AQ Solution (which is part of our DEVINT1 environment) to send messages to the AIA AQ table in our QA1 enviornment. The AIA database uses ALT32UTF8 character set. We don't know what character set the 6.3.1 OSM/Weblogic/AQ uses. When we sent messages to the AIA QA1 AQ table we saw that everything under TEXT_LEN 4000 went to TEXT_VC. Over 4000 went to TEXT_LOB. This is fine for us.

JMS adapter not registered

Similar Messages

Maybe you are looking for