Set JMSType in JMS Receiver

Hello.
I have to send a JMS Message to MQ Series and can not set the JMSType (is a JMS Header property). Any know about this ? Thanks.

Hey
This needs to be set in UDF in message mapping and use the technical name DCJMSType.check the below two links
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
set it the way attributes are assigned in the below blog
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
Thanx
Aamir

Similar Messages

Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper

Hello
Has anyone managed to set the DCJMSCorreleationID dynamic attribute in a JMS RECEIVER using Seeburger AttribMapper module?
Here is how I configured the JMS_RECEIVER:
In the module tab, I added a new module:
Module Name     Module Type     Module Key
localejbs/Seeburger/AttribMapper     Local Enterprise Bean     map
And I added the following parameter:
Module Key     Parameter Name                                                       Parameter Value
map                     http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
When I process a message, I can see in the adapter engine Audit log the following lines:
SEEBURGER/AttribMapper: Setting dynamic property http://sap.com/xi/XI/System/JMS - DCJMSCorreleationID = TEST
SEEBURGER/AttribMapper: Finished succesfully, 1 properties set or deleted
However looking at the Message Content/SOAP Document, I can see no dynamicConfiguration (it should be the case according to Seeburger documentation).
If I check the message properties on the JMS queue, I can see the correlation ID is not set to TEST.
Any idea?
Thanks in advance!
Greg

Are you using the AttribMapper in the Sender or in the Receiver Channel ? Please be aware that you will not be able to see the change of attribmapper in the message content in receiver channels (they are not updated/persisted there).

Issue with JMS Receiver Comm. Channel using Seeburger AttribMapper

Hello,
I'm using a JMS_RECEIVER Comm. Channel on which the Seeburger AttribMapper is configured (I need to use the DCJMSCorreleationID dynamic attribute).
In the module tab, I added a new module:
Module Name Module Type Module Key
localejbs/Seeburger/AttribMapper Local Enterprise Bean map
And I added the following parameter:
Module Key Parameter Name Parameter Value
map http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
When processing a message, I get the following error on the Communication Channel Monitoring:
Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of AttribMapper.
Does anyone has an idea on how to fix this problem?
Thanks for your help!
Benoit

HI,
Refer the discussion of
Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper
Dynamic subject in AS2 receiver
Thanks
Swarup

JMS Receiver - set DCJMSMessageProperty value dynamically from message

Hi,
I have a JMS Receiver where I want to set a DCJMSMessageProperty value to a value from the message contents
For example:
Scenario 1:
Message content field <EANCode>123456</EANCode>
DCJMSMessageProperty6 should be set to 123456 in this instance
Scenario 2:
Message content field <EANCode>99999</EANCode>
DCJMSMessageProperty6 should be set to 99999 in this instance
I know how to set this property to a fixed value using the module DynamicConfigurationBean but do not know how to make this value to use message content.

Hi,
As stated earlier, I need to set DCJMSMessageProperty on the communication channel to a value held in the content not a fixed value.
I will use a UDF to do this now as there are only certain dynamic values you can use using the DynamicConfigurationBean such as message ID, interface name etc. I want to use something in the content so a UDF should be able to do this.
Cheers
Colin.

JMS Receiver Adapter Catching MQ Exceptions

Hi Experts,
We are running into an issue with our JMS receiver adapter failing PI. We are trying to send transactions via the adapter to a MQ Series' queue but it is failing after no transactions have been sent after a period of 3 hours or more. The only way we can flush the queue is to change the setting on the adapter to Bypass, restart the adapter and then resend the message. Once we do this, everything runs fine throughout the day. It seems to be the amount of time between transactions be processed on the queue.   For instance, last night the last transaction processed successfully was at 7:36pm EST. Then around 11:40pm EST we tried sending another and this is when we caught an exception from MQ once again. We have tried everthing that we know of u2013 we thought it might have been a background job running on PI that causes the issue but last night proved that it wasnu2019t the issue since it occurred before midnight. I feel that the issue is between our JMS connection and your MQ. Below is the message log of the transaction:
What course of action should we take next in diagnosing the issue?
Audit Log for Message: 1c728f10-2044-0441-0a04-604e2cf00000
Time Stamp     Status     Description
2009-05-21 22:40:48     Success     Message successfully received by messaging system. Profile: XI URL: http://bus0157:52000/MessagingSystem/receive/AFW/XI Credential (User): PIPISUSER
2009-05-21 22:40:48     Success     Using connection JMS_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2009-05-21 22:40:48     Success     Message successfully put into the queue.
2009-05-21 22:40:48     Success     The message was successfully retrieved from the receive queue.
2009-05-21 22:40:48     Success     The message status set to DLNG.
2009-05-21 22:40:48     Success     Delivering to channel: JMS_IDOC_SPK_RCV
2009-05-21 22:40:48     Success     MP: Entering module processor
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService
2009-05-21 22:46:48     Error     MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP
Time Stamp     Status     Description
2009-05-21 22:46:48     Error     Exception caught by adapter framework: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP?targetClient=1 JMSReplyTo:      null JMSRe
2009-05-21 22:46:48     Error     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: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP.

Ok, would you mind taking a look at my forum question titled "Multiple Message Types into one Websphere Message Queue", it may be an easy one for you since you are already doing this!
Best regards,
Aaron
[Multiple Message Types into one Websphere Message Queue|Multiple Message Types into one Websphere Message Queue]

JMS receiver adapter Error

Hi Experts,
Any idea about this error. We are getting following in JMS receiver adapter in PI 7.1.
Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connector for ConnectionProfile of channel: JMS_Receiver_THQPRD2_Slow_Replyon node: 284760550 having object id: cf2f6eb7d6c93902b64b27bfcaad0ba5 encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>' in sending to destination queue:///QR.EAIPRD.THQPRD2.REPLY.SLOW?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID:ID:414d5120504c535748353533202020204e6324ae23eb5b2d JMSDestination: null JMSReplyTo: null JMSRedelivered: false XPLOR PIPXSDI2030 45219q00282YSDI2030PROCESS_MQSERIES PLSWH553 Another 12,761 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>'.
Thanks,
Hari

Hello,
The error indicates a JMS driver issue.
Another customer resolved this issue by updating their MQ and the MQ drivers version (in their case to 6.0.2.8.)
You could try contacting IBM for advice on a similar upgrade.
#1086303 XI JMS Adapter and IBM Websphere MQ: FAQ
12)What is the recommended version of MQ drivers for the PI JMS
Adapter - IBM MQ connectivity ?
Kind regards,
Sarah

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

JMS receiver Adapter - Weblogic

Hi,
Could you please help us.
We are sending messages from XI to Weblogic server with the help of JMS Adapter. The Queue is available in Weblogic we are able to ping the Weblogic server from XI Server. The port is right one.
Our configuration of JMS receiver Adapter is
JNDI Lookup Name of Queue Connection Factory: javax.jms.QueueConnectionFactory
JNDI Lookup Name of JMS Queue:com.nyc.OmsQueue
Name of JNDi Initial Context Factory: weblogic.jndi.WLInitialContextFactory
JNDI Server Address:http://nyc-d01:7001
JNDI Logon User: (Emty)
JNDI Password: (Emty)
There is no User Name and Password
Could you please help us. this is very urgent.
The Error message as follows
Error during channel initialization; exception trace: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class java.lang.Object; nested exception is:
java.io.OptionalDataException]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:83) ...
Regards
Ramidi

Hi,
>>Error during channel initialization; exception trace: java.lang.ClassCastException
at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:419)
at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:369)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
The error u posted is from Weblogic server side, not from XI side.
The problem is that the channel created in weblogic server is not opened. For this you have specific setting while creating channels and queues in weblogic server.
Contact the concerned weblogic server guys in ur team to help you in this issue.
I faced the same error while configuring JMS receiver adapter.
Ravi.

JMS receiver adapter configuration error

Hi All,
I am facing an issue with JMS receiver adapter. My Configuration parameters for receiver adapter are as follows.
1.Transport protocol:WebspherMQ (MQSeries) JMS provied
2.Message porotocol:JMS 1.x
3.Adapter Enigen: Integration Server
4.QueueConnecation Factory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
5.Queue Java Class:com.ibm.mq.jms.MQQueue
6.IP Address or server name:<Host Name>
7.Server port:1414
8.Queue Mannager Name:TestQM
9.channal name:Recv_Channel
10.JMS queue:SAP_PI
11.Transport/netwrok protocol:TCP/IP
12.JMS compliant:WebSpherMQ(non jms)
13.Delivery mode of message Producer:Persist JMS Messages in the JMS provider
14.Mapping of message:Message Payload=JMS Payload
In adapter monitor, the adapter status shows below error.
<b>Receiver channel. Details: (No detail information set.)</b>
I have already installed the external drivers for JMS adapter. Can someone help me if I am missing some parameter in the above configuration.
Thanks in advance
Regards,
Ashish

Hi,
I am getting the below error in Audit Log.
Error - Exception caught by adapter framework: The JMSSender returned no JMSTextMessage to use. Must abort send process.
Error - Delivery of the message to the application using connection AFW failed, due to: The JMSSender returned no JMSTextMessage to use. Must abort send process..
Can someone please help me in resolving this issue...
Thanks in advance.
Regards,
Ashish

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

Sync/Async communication with JMS Receiver

Hi all,
I am working on one Sync/Async model without BPM. Sender is RFC which is expecting some response, but we know receiver jms doesnt support response message directly. For this i used modules provided by SAP.
While developing interface i used below objects.
One Outbound Synchronous interface--> for Sender RFC channel
Inbound Synchronous Interface----->for Receiver JMS Channel
outbound asynchronous interface--->for Sender JMS channel
one request mapping and one response mapping
Operational mapping between outbound Synchronous to inbound synchronous.
ID Objects:
2 sender agreements: one with sender jms channel
one with sender rfc channel
1 receiver agreement: with jms receiver channel
1 receiver determination
1 interface determination
In receiver jms and sender jms channels i used modules as specified in the document http://help.sap.com/saphelp_nw04/helpdata/EN/45/20d2b4c20a0732e10000000a155369/content.htm
But my interface is not working end to end successfully.
Please confirm below points
1)do i need to have other external application put response message to response queue or will the MQ automatically generates the response message and put into response queue
2)In receiver jms channel is it ok if i will put response queue(Q2) name in the field JMS ReplyTo Queue Name or do i need to put in the form queue://<ReplyToQMgr>/<ReplyToQ>
3). what is the format of data type for asynchronous outbound interface which i used for sender agreement of jms sender channel.
4). Do i need to do any other special settings at MQ settings in MQ server.
Note: i am using PI7.1 and i selected the option JMS-compliant for target client in jms channels.
Thanks,
Madhu
Edited by: Madhusudana Reddy on Nov 4, 2009 9:38 AM

1)do i need to have other external application put response message to response queue or will the MQ automatically generates the response message and put into response queue
The following information is available in SAP note-
Message correlation implies correlating a response message with a request message. With respect to the JMS adapter, this means that you sent have sent a message through a JMS receiver channel to some JMS queue (say queueA) , some external application processes this message and puts the response onto another JMS queue(say queueB) which is then picked up by a JMS sender channel. You need to relate this response message with the original request message.
In the simple case, for all JMS compliant providers this can be done in a straightforward manner:
a) In the JMS receiver channel configuration, set the JMSCorrelationID to the XIMessageID. (or some other XI header which is applicable)
b) Ensure that your external application does not change the value of the JMSCorrelation
c) In the JMS sender channel configuration, set the XIConversationID to the JMSCorrelationID
d) The XIConversationID header of the response XI message now contains the XIMessageID of the request XI message.
For some providers such as Websphere MQ in legacy/native mode this is not so straightforward.
Do i need to do any other special settings at MQ settings in MQ server.
If your using Websphere MQ, refer que#4 in sap note :1086303
Edited by: nagarjuna _s on Nov 4, 2009 11:02 AM

Dynamic Queue names at JMS receiver

HI All,
            I have a scenario where sender is an RFC and receiver is via JMS and also get a reply back . JMS is asynchonous but as suggested in other threads it is possible to capture the response by setting some Adapter specific parameters.
            But my problem is the queue name for the response is not constant and it varies from request to request for the response. I have no clue how to achieve this , I tried searching some threads but couldn't come to a conclusion.
            Possibility of dynamic MQ queue selection in one receiver JMS channel
            help on Dynamic queue name in JMS Adapter
Has anyone come across such a situation ? Please suggest.
Also In one of threads it was suggested to use Java Proxy? Please suggest a way forward in this approach too
Regards,
Mohan.

> please refer the link what you provided in section 2.8 mentioned JMS Receiver communication channel will give response back,but i never tried.
Yest because this document is applicabe for a scenario where request msg will come form sender JMS to XI and then Response will be sent back again to JMS by using receiver JMS adapter. So senario is JMS request --- R3 (via XI) --- R3 response to JMS.
But here case is different. e.g. RFC --> PI --> JMS and reply will get back from JMS to RFC. So definetly in this case response will come from sender JMS and not from receiver JMS.
Read sec 2.8 throughly, you will come to know how to set the queue names dynamically for RECEIVER JMS Adapter.
Regards,
Sarvesh

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

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!

JMS Type in JMS Receiver

Experts
I need to send JMS Type to the JMS Receiver.
The following UDF was used.
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS","DCJMSType");
String a="341";
conf.put(keyHeader1,a);
return "";
Selected ASMA in the Receiver channel. Anything else needs to be done ?
Thanks and regards,
J Augastine

Abhishek
Modified the UDF.
Also
In the JMS Receiver channel did the following
- Checked the box for 'Use Adapter Specific Message Attributes'
- Checked the box for 'Fail if Adapter Specific Message Attributes missing'
- Checked the box for 'Specify Additional JMS Message Properties'
- Defined property in the table and set the Java type
DCJMSMessageProperty0 String
Under the Module tab,
- Added the module AF_Modules/DynamicConfigurationBean in position 1 with module key HEADER
- Added module configuration as follows:
Module key HEADER
Parameter name key.0
Parameter value write http://sap.com/xi/XI/System/JMS DCJMSMessageProperty0
Module key HEADER
Parameter name value.0
Parameter value JMS DCJMSMessageProperty0
What change needs to be done ???

Set JMSType in JMS Receiver

Similar Messages

Maybe you are looking for