Re-using JMS Receiver Channel

Hi,
I have scenarios with SAP -> PI -> 2 Different External Parties.
External Parties use JMS.
There are some flows which are common for both the parties, like sending Acknowledgement from SAP to JMS.
Now can I just configure one common Receiver Communication Channel and Send message (Acknowledgement) to any of the two Parties? So I will have two Receiver Agreements using the same Receiver JMS channel.
Like by using some concept can I populate JMS channel parameters like IP Address or Server Name , JMS Queue
Thank you,
Pankaj.

Hi,
You need as many receiver channels as you have JMS queues. When you have 60 JMS queues, then you need 60
channels.
I have only 6 queues; one each for one Party.
When you send all messages to same JMS queues and receiver can identify the message type anyhow, then you need
only one channel for this queue.
Ok.
But even when you have only one JMS queue, you might need seperate channels anyway, for example when you use
FCC for each interface individually.
So basically if the setting is different then I need to have that number of channels. the way messages are sent is the same in all the cases. Even when we are using Dynamic Configuration it is the same for all the messages to be send to the External Party.
Thank you,
Pankaj.

Similar Messages

Error in JMS receiver channel

Hi,
I have a JMS receiver channel which is connected to message queue of TIBCO which is working fine.
But if I use the same channel after a day it goes into error and after restart of the channel it again works fine.
Error: Message process failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to write newJMS Message body for message: 343241-......... Connector Exception: ... session ended..
Thanks,
Aravind

Hello Aravind,
I have made similar experiences while accessing JMS queues.
Maybe the JMS queue was not available for a short time. So the receiver channel could not connect.
Best regards,
André

JMS Receiver channel EOIO

Hi,
In SAP help, for one of the parameters of JMS Receiver channel it is mentioned that:
Delivery Mode of Message Producer :
Specify the quality of service of the message producer. You have the following options:
u2022 Persist JMS Messages in the JMS Provider
u2022 Do Not Persist JMS Messages in the JMS Provider
Does this means EOIO/EO. I have proxy to JMS scenarios & like to send the data to JMS in EOIO.
We are using Transport Protocol " Access JMS Provider with JNDI"
With this I want to achieve, EOIO for Proxy to JMS. Pls let me know if Delivery Mode of Message Producer parameter would help & what should be the value.
Thanks.

Exactly Once messages are handled by default using status information in the J2EE server. All adapter error statuses and program terminations initialized externally are also handled in this mode. i.e.
= persist jms messages in the jms adapter.
Now if you specifically want to have dedicated queue; check manage queues under SXMB_ADM.
See if you can set dedicated queue to your interface so that the messages can be processed in the sequence they have received.
Also, once it is out of PI into target system (queue) the order will be maintained.
Cheers!

Heartbeat possibilty in JMS receiver channel?

Hi,
Does anyone know if it is possible to define a heartbeat interval in JMS receiver channels.
Is there maybe a possibility in the additional JMS paramters fields?
We need this to prevent connections being shut down by firewalls due to long inactivity. Once a JMS receiver channel is inactive due to this there is no automatic activation of the channel possible (I think).
The sending JMS channels pose no problem since XI AF seems to poll these every 5 seconds and thu sthe connection remains alive.
thanks
Tom

Hi Shai,
We are using XI 7.0 with SP 12 and we entered this parameter in advanced settings in JMS receiver adapter called "CONNECTION_TEST_POLL" as true and it does the polling to see if the adapter is active...
Hope this helps.
Regards,
TJ

Error with JMS receiver channel

Hi,
We have a scenario in which Order response will be sent from ECC to WebLogic (JMS system) through PI.
After the restart of JMS, we are facing issues with JMS receiver channel.
Some of the responses are delivered, and for few we have the error as described below.
Also, one of the cluster node of the JMS receiver channel has the below error.
Please anybody throw some light on this.
Error description:
" Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Pending message discovered: dfff2e2b-80f5-94f1-a068-001cc4d99b3e.The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards.. "
Thanks in advance.
Regards
Bhanu Tiruveedula.

Hello Bhanu,
we have been getting this error from long time with JMS channel but no solution except changing the configuration so that it can throw exception and move on.
we have also noticed that this happens for some time and then gets resolved automatically. so it seems to be some data which is not expectable by jms channel.
regards,
Ratna

JMS Receiver channel : No Correlation ID

Hi,
JMS Receiver channel to WebSphere MQ,
I want to put a message on the queue with correlation ID left blank (= no correlation ID), because this causes problems on the receiving side.
Is there a way to achieve this?
I have tried several different settings, but the message appears always with correlation ID.
Kind Regards
Edmond Paulussen

I think you should use the notify response bean on the sender channel
Configuring the Sync/Async Bridge Using the JMS Adapter - Adding Modules to the Module Processor - SAP Library
Sync/Async communication in JMS adapter without BPM (SP19)

JMS receiver channel Error !!

Hi All,
We are facing problem in all JMS receiver communication channels, all rcevr channels are failing with following error,
Error while processing message '498499a3-e65c-0086-e100-80000a05260c';
detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Pending message discovered: 498499a3-e65c-0086-e100-80000a05260c.
The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards. at
com.sap.aii.adapter.jms.core.channel.filter.OutboundDuplicateCheckFilter.filter(OutboundDuplicateCheckFilter.java:153) ...
does anybody know whats the exact error??
is it due to Adpater engine message buffere is full ?
regards
biplab

Biplap,
1) Did you restarted the Java Engine ? If so deactive & active the JMS Adapter,
2)Check any EOIO message got struck in Adapter Engine ( RWB-Communication channel- JMS Adapter )
3) Sxmb_moni - Look for the below message status - 498499a3-e65c-0086-e100-80000a05260c
Cheers
Agasthuri Doss

Writing to 2 different directory using file receiver channel

I have a scenario where i am picking multiple files from one server and writing it on another. While writing the files, i want to write them to different folders using one communication channels based on the filename. is it possible? if yes how?

You have to go for dynamic configuration UDF in the mapping.
Refer to the below document
http://wiki.scn.sap.com/wiki/display/XI/Dynamic+file+name+and+directory+in+Receiver+File+Adapter+-+summary+of+possibilities
Also http://****************/Tips/XI/ASMA/Index.htm
You just need to add filters/fix value lookup and pass it to UDF to determine the target directory
Message was edited by: Hareesh Gampa

How to Send message to MQ without using JMS Receiver Adapter

Hi Frnds,
Actually i am working one File to JMS scenario,I have to send message to MQ,What are the different ways we can send message to MQ without using JMS Adapter.
Regards,
Raj

Hi Ramesh,
Thanks for your replay,could you please eloborate how to integrate that one with XI,and how to use in XI?
regards,
raj

Error in JMS receiver channel - XI - Weblogic

Hi Experts
We are also having the situation that 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
We are getting the error in the adaptor like " com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA:"
Could you please tell me if there are any other JAR files for this as i have already deployer weblogic.jar. If yes, Can you please give me some more details on that.
Thank you very much for your time and help.
Manjunath
Edited by: Manjunath Achar on May 23, 2010 4:12 PM

Hi Manju
There could be some problem while deploying the libraries. please check you have deployed the JAR Files correctly.
You need to include the Weblogic Thick client driver 'weblogic.jar' - with all classes under the package 'javax.jms' removed in your aii_af_jmsproviderlib.sda (releases 3.0/7.0) or com.sap.aii.adapter.lib.sda (releases 7.1).
The below links might be helpful for you,
http://wiki.sdn.sap.com/wiki/display/XI/FAQ+J2EEJMS+Adapter
Note 1090516 - XI JMS Adapter and BEA Weblogic JMS: FAQ
Regards
Ramg

How to replace/Change the JMS MSG ID in MQ using JMS Receiver Adapter

Hi Experts,
I am working on File to JMS Scenario,
My Requirement i need to chnage the JMS Message ID(not XI Msg ID) Value with My custoimer specific Value,
How can i achieve this??
any valuable inputs welcome,
Thanks advance,
Raj

Thanks for your reaply,we can change the value of XI MSG ID using Dynamic Configuration,
Then set the XI MSG ID and then make use of the correlation settings
From the help section:
Correlation Settings
Define the correlation settings.
·        Set JMSCorrelationID To:
¡        XI Message ID (MessageID) (default value)
¡        XI Reference ID (RefToMessageID)
¡        XI Conversation ID (ConversationID)
¡        No Value
But cant we directly make use of the ASMA to configure DCJMSCorrelationID?
Regards,
Abhishek.

Can we archive files using the receiver file channel

Dear all,
I'm looking for a option, where in I want to archive the files being sent to the target system.
Do we have that facility in XI Receiver File communication channel.
Can the same be achieved for JMS Receiver channel.
Kindly give your comments or responses.
Regards,
Younus

Hi,
AFAIK only the sender file adapter has such a functionality.
A workaround would be to send the file to a second receiver (for example a archive directory on your PI server).
Regards
Patrick

Convert UTF-8 to ISO-8859-1 in JMS receiver

Hi Freinds,
We are sending an XML message to the MQ via JMS receiver channel and I need to change the character set from UTF-8 to the ISO-8859-1 while sending it to the MQ queues. Will this be possile?
Please suggest how can I acheive this.
Regards,
Kumar.

Hi Kumar,
Try changing the encoding using XSLT mapping and you can call this mapping as shown in this blog:
/people/michal.krawczyk2/blog/2005/11/01/xi-xml-node-into-a-string-with-graphical-mapping
or try this wiki page:
http://wiki.sdn.sap.com/wiki/display/XI/SOAPMessagesin+XI
Regards
Suraj

Viewing the flat file in JMS Receiver???

How can i see the Flat file generated after content conversion by JMS Receiver channel in a in a ECC->PI->JMS scenario.
I have a JMS Receiver channel connecting to WMS system , how can i see the flat file produced just after the JMS adapter's content conversion. its like
ECC ---> PI----->JMS----> (intermediate client MQ file cannot be viwed here it forwards the file to WMS MQ)------>(MQ)WMS
i need to see the flat file produced just after the JMS channel content conversion..is there some logging option there should be. Please help

Hello,
I don't think there is any standard way to achieve ur req.
But what u can do is, write a custom AM module to either write a file on PI file system (for ur monitoring) or display the text file in ur audit logs.
Send File to Two Different Locations using Adapter Module
Thanks
Amit Srivastava

JMS Receiver Adapter to MQ - additional message property error

Hi,
I'm trying to add addional message properties to a Receiver JMS message for MQ Server queue. Creating the message in the MQ queue only works when I don't try to
add additional message properties. As soon as I try to add additional message properties the XI-Monitor says it's OK but there is no message in the queue.
Our system constellation is a bit odd cause we implemented the JMS/MQ classes of release 5.3 in XI/J2EE.
Our actual used MQ Server is on release 5.1 due to compatibilty reasons of other productive software.
Is there a need to use a MQ server of release 5.3 ?
Has anybody a step by step description for implementing a JMS receiver Adapter for MQ with with additional message property (f.ex. mesType = salesOrder) in the MQ header?
Thanx a lot in advance
Hans

Hi,
You also might want to look at sap note 856346...for this ..
2.6) I am connecting to a JMS provider using JNDI mode. How do I add pass an extra name,value property pair while setting up the JNDI initial context?
Answer: Assuming that your property value is a string, please add the following name, value pair in "JMS Additional properties" table of your channel configuration:
JNDI.InitialContext.property.X=java.lang.String propertyName, java.lang.String propertyValue
where X is a number, the LHS part needs to be put in the name column and the RHS part in the value column of the table respectively.
This note covers frequently asked questions that arise during the installation, configuration or administration of the XI JMS Adapter from the Adapter Framework (AF).
Other terms
JMS - Java Message Service
AF - Adapter Framework
AE - Adapter Engine
SP - Service Pack
Reason and Prerequisites
This note clarifies the frequently asked questions on the XI/PI JMS adapter for released 3.0, 7.0 and 7.1 in the form of an FAQ. References to external information is provided at the end.
Solution
1. Documentation
1.1) Where do I find the JMS adapter documentation?
Answer: In the SAP online help. Go to http://help.sap.com and select SAP Netweaver-> SAP Netweaver 7.1 or SAP NetWeaver 7.0 (2004s) or SAP Netweaver 2004. This opens up SAP Library topic page for that release.
For releases 3.0 and 7.0:
Select SAP Netweaver Library -> SAP Netweaver by Key capability-> Process Integration by Key Capability -> SAP Netweaver Exchange Infrastructure -> Runtime -> Connectivity -> Adapters -> JMS Adapter.
For releases 7.1:
Select SAP Netweaver Process Integration 7.1 -> SAP Netweaver Process Integration Library -> Function Oriented View > Advanced Adapter Engine.
In the topic page click on the JMS Adapter link.
Alternatively, you may simply enter the search string "JMS adapter" and navigate to the documentation page directly from the relevant search results. This is much faster.
1.2) Which JMS providers are supported?
Answer: The JMS Adapter supports JMS 1.02b and 1.1. JMS providers that also claim to be compatible with JMS 1.02b or 1.1 can be accessed using the JMS Adapter.
Furthermore, SAP makes no assertions as to whether a particular JMS provider is tested or can be recommended, because SAP has not set up a certification or testing process.
2. Functions and architecture
2.1) Does the JMS Adapter support JMS topics (publish&subscribe)?
Answer: No. Currently the JMS Adapter works with JMS queues because 100% Exactly Once (In Order) service quality can only be guaranteed with JMS queues. However, this capability might be planned for introduction at a future release. (no planned time estimate)
2.2) I have JMS message properties that are of significant. How do I get this data into XI? How do I get this data out of XI?
Answer:
A feature generically referred to as XI adapter-specific message properties was introduced in the adapter framework. This allowed additional adapter information to be attached to a XI message which can be used the routing, mapping and BPE. The message properties of different adapters are differentiated by namespaces.
If you are on XI 3.0 support pack 18 onwards, the JMS adapter allows you to copy JMS message properties into these XI adapter specific message properties (at the sender JMS channel), and to copy the values of XI adapter specific message properties back into JMS message properties (at the receiver JMS channel).
The JMS adapter currently supports upto 10 JMS message properties to be copied into the XI message properties with the name DCJMSMessageProperty0 to DCJMSMessageProperty9. The configuration details of how to achieve this are explained in the sub-topic pages of the JMS adapter documentation. (See sub topics: "Configuring the Sender JMS adapter", "Configuring the Receiver JMS adapter")
JMS Message properties can have values belonging to types: boolean, byte, short, int, long, float, double, and String (defined in the specification). These are all normalized to strings when converted to the their respective XI message properties at the sender JMS channel.
However, in the receiver JMS channel configuration, you can enter specific JMS message property types, such that these normalized XI message properties may be coerced back into their original types (or any compatible JMS message property type) when translating a XI message into a JMS message.
Transfer of custom JMS Message properties from/to XI adapters-specific message attributes is only supported for JMS compliant messages, i.e. this feature will not work for Websphere MQ in legacy mode.
Deprecated Information on this feature
Between support pack 14 to support pack 18, the JMS adapter allowed the allowed you append only up to two JMS string properties to the XI message in the sender channel, which could then be analyzed in XI routing, mapping and BPE. In the JMS receiver channel, the XI adapter-specific message attributes could be read, and up to two JMS string properties could be set. The names of the (now deprecated) XI message properties were DCJMSStringProperty1 and DCJMSStringProperty2.
Regards
Ravi Raman

Re-using JMS Receiver Channel

Similar Messages

Maybe you are looking for