JMS adapter -Message format pre-requisites

Hi,
I am using a sender JMS adapter in XI to read a message from MQ. Can anyone tell me whether the message should be in any specific format like comma separated (csv) or text-tab delimited. I am wondering on what basis the system will split the message and map it to the source structure.
regards,
Madhavan

Hi Abhisheek,
It doesnt work... i tried adding the ISO 8859 1 in the module and also tried setting the CCSID which is to 819.. for the ISO 8859 1.. bt i doesnt work
i dont understand why its behaving in such a manner but i really feel some silly mistake i am missing out a parameter or something...
I have created a txt file with 2 line only
AAABBBCCC
DDDEEEFFF
And jst trying to pick up this file without any conversion ... kind of a JMS to File senario without any modules.. it still doesnt work..
i dnt think it is recognizing the new line which i have given.. or may be because the conversion modules are stripping out the new line characters
And i have not upgraded my system as well. its XI 7.0 SP 9
RGds
ADitya

Similar Messages

Sender/receiver JMS Adapter XML Format

What is the XML format do we need to pass to Sender/receiver JMS adapter to get it processed. Do we have any specific format like JDBC adapter.
Thanks,
Sam

Hi,
1) The JMS adapter (Java Message Service) enables you to connect messaging systems to the Integration Engine or the PCK
2) Before to use the JMS adapter we must first install the relevant JMS driver.
The required Java libraries are product-specific The provider setting specifications are the same for the receiver and sender adapter
3)We need to configure the JMS adapter in the configuration part of the Integration Builder/PCK
4) The Sender JMS adapter is configured to send JMS messages to the Integration Engine or the PCK.
5)The Receiver JMS adapter is configured to be able to convert XI messages from the Integration Server or the PCK into JMS messages
Please go through this link
1)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm
2)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm - Configuring the Sender JMS Adapter
3)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm -
Configuring the Receiver JMS Adapter
4)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm -
JMS-Provider-Specific Settings
5)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm -
JMS Adapter Modules
6)http://help.sap.com/saphelp_nw04/helpdata/en/45/20d1dec20a0732e10000000a155369/frameset.htm -
Async/Sync and Sync/Async Bridge in the JMS Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
Thanks,
Soumya.

JMS adapter Message

Hi ,
I am getting below message in my JMS adapter.
"Sender Channel. Details: (No detail information set.)"
Status of adaper is green. What is the meaning of above statement?

Hi S R,
What is the error detail in SMQ1,SMQ2?
Did you try to reprocess them from execute luws? try to change the status to recorded if possible.then execute again.
thanks

JMS Adapter Message Selector Problem...

Hi
I have set the following in the invoke before producing the message and dropping on the queue
<invoke name="Invoke_1" partnerLink="adapt"
portType="ns1:Produce_Message_ptt"
operation="Produce_Message"
inputVariable="Invoke_1_Produce_Message_InputVariable"
bpelx:inputHeaderVariable="Sender"/>
On the receive side I have the message selector configured for the adapter as follows:
<jca:operation
ActivationSpec="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec"
DestinationName="dattjndi"
UseMessageListener="false"
MessageSelector="Sender=AdaptationRequest"PayloadType="TextMessage"
OpaqueSchema="false" >
</jca:operation>
Where AdaptationRequest is the value for the Sender variable which will be used to filter the message. But this does not work. the messages are still not consumed. What could be the problem?
Thanks,
Anil

did you check the message selector section on
http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/Message.html
explains all the operators you can use and the correct syntax. Make a note of the case sensitivity.

JDBC Sender Adapter Message format

I am somenone who is new to SAP PI so please help me out in the format of datatype for JDBC SENDER Adapter ?

Hi Rajesh
The source xml structure for JDBC adapter is like below
<resultset>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
</resultset>
Then in the sender JDBC adapter, write the select and update query
SQL statement for query: SELECT * FROM table WHERE processed = 0;
SQL statement for update: UPDATE table SET processed = 1 WHERE processed = 0;
processed is the indicator in the database.
Check this link for details
https://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm

Module in Receiver JMS Adapter

I am using the following Modules in one of receiver JMS adapter. What is the function of each Bean that we are using here ??
Any links in this regard is appreciated
1-AF_Modules/RequestOnewayBean-Local Enterprise Bean-0
2-SAP XI JMS Adapter/ConvertMessageToBinary-Local Enterprise Bean-convert_XI2Bin
3-SAP XI JMS Adapter/SendBinarytoXIJMSService-Local Enterprise Bean-exit
4-AF_Modules/WaitResponseBean-Local Enterprise Bean-1
thanks
kumar

Hi,
The JMS adapter (Java Message Service) enables you to connect messaging systems to the Integration Engine or the PCK.
This link will help you...
JMS adapter
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5393. [original link is broken] [original link is broken] [original link is broken]
http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
ref this weblog by william Li
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
syn-asyn bridge( with out bpm)
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
similary asyn-syn bridge
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
also refer
http://help.sap.com/saphelp_nw04/helpdata/en/45/20d1dec20a0732e10000000a155369/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/how%20to%20use%20the%20content%20conversion%20module%20with%20the%20xi%203%20j2ee%20jms%20adapter
/thread/217893 [original link is broken]
JMS adapter -Message format pre-requisites
/people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure

PI JMS Adapter MQ Message Format

Hi,
I know that if you change the target client in the JMS adapter properties il will change the message format for MQSTR (Websphere MQ Non-JMS) or MQRFH2 (JMS-Compliant).
But is there a way to force the MQ Message format to NONE or an empty string? The MQSTR is causing some unwanted conversion in legacy systems.
PI 7.1 EHP1.
Thanks,
Martin

Hi Martin - I relize you've already answered, but as an fyi, my somewhat related requirement was to have the mqmd.format=MQIMS, instead of the value MQSTR that PI seems to default to.
I was able to achieve this by
(1) setting that Module JMSMessageType=bytes parm like you did, and
(2) set an additional parameter entry (i.e. on your 'Advanced' tab) of
JMS.Message.method.setStringProperty java.lang.String JMS_IBM_Format, java.lang.String MQIMS
(I think you need MQ7 libraries for this).
Keith

Message format to be send to the JMS Adapter

Hi all,
I have a very strange situation. i have a sender JMS channel where i am trying to use the Message Transformation module
I have done the configuration but the problem is that i have made a .dat file
AAABBBCCC
DDDEEEFFF
and i am using the PutMessage fuction to put the messages in the Queue and process it
dont knw y but the newline characters get disapeared. I am not sure why this is happening on investigation i found that we have 2 modules which are used before the conversion for XML
localejbs/SAP XI JMS Adapter/ConvertJMSMessageToBinary
localejbs/SAP XI JMS Adapter/ConvertBinaryToXMBMessage
Is it because of this.. that the channel is behaving like it. please give your inputs as to what can be done
if so will the messages work fine if the messages are directly put into the queue
what special character should i use to get the desired output with new line characters

Hi Abhisheek,
It doesnt work... i tried adding the ISO 8859 1 in the module and also tried setting the CCSID which is to 819.. for the ISO 8859 1.. bt i doesnt work
i dont understand why its behaving in such a manner but i really feel some silly mistake i am missing out a parameter or something...
I have created a txt file with 2 line only
AAABBBCCC
DDDEEEFFF
And jst trying to pick up this file without any conversion ... kind of a JMS to File senario without any modules.. it still doesnt work..
i dnt think it is recognizing the new line which i have given.. or may be because the conversion modules are stripping out the new line characters
And i have not upgraded my system as well. its XI 7.0 SP 9
RGds
ADitya

Message Conversion in JMS adapter

Hello Friends,
I have a scenario where in I will be getting the message from MQ, and the message will look like
SOURCE
<Root><MessageHeader><MessageID><MessageIDSystem>SCV</MessageIDSystem><MessageIDType>FE</MessageIDType><MessageIDIdentifier>CUSTOMER_MASTER</MessageIDIdentifier></MessageID><MessageReleaseNo>0004</MessageReleaseNo><MessageVersionNo>00</MessageVersionNo><MessageOrigApplID>SCV</MessageOrigApplID><MessageDestApplID>BROKER</MessageDestApplID><MessageInterfaceID>IDD088</MessageInterfaceID></MessageHeader><MessageBody><SCVData>53435646453030340130303030303401323030372d31312d31362031393a34303a343401313336333938323401330130010154414730303101574542555345525f52454c4154494f4e0155504441544501323030372d31312d31362031393a34303a343301544147303138013836373134013332353030303039343239013332353030303035323338013332353030303035323339010131014e014e01494e41435449564501350154414730303101504552534f4e01494e414354495641544501323030372d31312d31362031393a34303a343401544147303032013332353030303039343239015941553b56414e4553534101333235013301494e41435449564501323030352d30342d30332031383a34363a3136015343563234324d4947524154494f4e01323030372d31312d31362031393a34303a3433014a43473031370133515955493630554b36355136015041015441473031390131013332353030303039343239015041303030303934323901013101544147303033015941550156414e455353410156590101014601013530372d34333032383838013530372d363736383332380149544350545940435750414e414d412e4e4554013201013530372d343330323839310101544147303031014c494e4b01494e414354495641544501323030372d31312d31362031393a34303a3434015441473030360130303432013332353030303035323338013332353030303039343239015343563234324d4947524154494f4e013530372d34333032383838013530372d343330323839310101323030352d30342d30332031383a34363a313601393939392d31322d33312030303a30303a3030015343563234324d4947524154494f4e01494e41435449564501323030372d31312d31362031393a34303a3433014a43473031370149544350545940435750414e414d412e4e4554013530372d343330323839310154414730313901320133323530303030353233380150413b494e5445524558503b48454144510101320154414730313901310133323530303030353233380150413030303035323338010131015441473031390134013332353030303035323338013832373032313030010134015441473031390131013332353030303039343239015041303030303934323901013101</SCVData></MessageBody></Root>
and the ascii data in this message needs to be converted into XML format.
JMS Adapter is picking this message from MQ and posting it to XI.
Also there is an adapter module develped for this conversion and it is working fine for most of the messages, but it failing for this above message.
Can you please help me out in this issue and how to test that adapter module.
Thanks & Regards,
Kumar

hi kumar,
>>Can you please help me out in this issue and how to test that adapter module.
put brek points in ur adapter module and then run ur scenario and debug. this is how u test ur adapter module.
this will also help u to see why is it running for certain msgs n failin for others. at different steps/points check the value for variables etc while debugging.
Also put some statements to write audit log entries in ur code for module. this will also help in debugging.
[reward if helpful]
regards,
latika.

How to set MQ message header properties using JMS adapter? (10.1.2)

Hello,
I am trying to send MQ messages from a BPEL process. We are using OAS 10.1.2 and JMS MQ adapter. Could you please let me know how to set the message descriptors like message format, type, report and reply to queue properties and queue open options (in jmsAdapterOutboundHeader).
Regards,
Geratayya

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>

How to covert EBCDIC format to ASCII in JMS Adapter??????????

Hi All,
I am developing one JMS to File scenario, in which JMS adapter will pick file which is in EBCDIC format from WebSphere MQ and send it to receiver file system by receiver file adapter. when i am trying this, i am getting file in EBCDIC format in receiver file system, but the file system is expecting data in ASCII format.
Is there any options to encode the EBCDIC format to ASCII in Sender JMS Adapter or Receiver File Adapter.
Thanks,
Madhusudhan.

Hi,
It was Basis / Database / OS staff that configured this aspect of the connection, and I am afraid I do not have any more details.
A Google search gave me the following from IBM Documentation on MQ Series:
<a href="http://publib.boulder.ibm.com/infocenter/wsphelp/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ucli_pqcfm.html">http://publib.boulder.ibm.com/infocenter/wsphelp/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ucli_pqcfm.html</a>
MQSeries queue connection factory settings for application clients
CCSID
The coded character set identifier for use with the WebSphere MQ queue manager.
This coded character set identifier (CCSID) must be one of the CCSIDs supported by WebSphere MQ.
Data type String
For more information about supported CCSIDs, and about converting between message data from one coded character set to another, see the WebSphere MQ System Administration and the WebSphere MQ Application Programming Reference books. These are available from the WebSphere MQ messaging multiplatform and platform-specific books Web pages; for example, at <a href="http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html">http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html</a> , the IBM Publications Center , or from the WebSphere MQ collection kit, SK2T-0730.
hope this may be of some help
Andrew

Wrong format in JMS Adapter

Hi,
we have an interface from R3 to MQSeries using a JMS adapter.
When we put the message in queue MQ the message format is wrong.
The message correct should be:
<?xml version="1.0" encoding="UTF-8" ?>
<requestMsg>
 <dse_operationName>MPB8</dse_operationName>
 <dse_formattedData>
 <kColl id="entryData">
 <field id="Usuario" value="NXCARDP" />
 <field id="PAN" value="45516401393530624" />
 </kColl>
 </dse_formattedData>
 <dse_processParameters>LIST</dse_processParameters>
</requestMsg>
But, the message that MQ receive is:
0000 RFH \00\00\00\02\00\00\00\E4\00\00\01\11\00\00\04\
0000-1 E4MQSTR \00\00\00\00\00\00\04\B8\00\00\00 <mcd><
0000-2 Msd>
0001 jms_text</Msd></mcd> \00\00\00\98<jms><Dst>queue:
0001-1 ///AEA.Q
0002 L.ANSWER.MT.I?CCSID=1252</Dst><Rto>queue:///AEA.QL
0003 .ANSWER.SAP</Rto><Tms>1191940306584</Tms><Cid>SINC
0004 RO</Cid><Dlv>2</Dlv></jms> <?xml version="1.0" en
0005 coding="UTF-8"?>\0A<requestMsg><dse_operationName>
0005-1 MP
0006 B8</dse_operationName><dse_formattedData><kColl id
0007 ="entryData"><field id="Usuario" value="NXCARDP"><
0008 /field><field id="PAN" value="45516401393530624"><
0009 /field></kColl></dse_formattedData><dse_processPar
0010 ameters>LIST</dse_processParameters></requestMsg>.
The MQ is unable to process the message because the properties of JMS adapter are being included in the begining of the message.
We don't know why and how to avoid this.
Thanks for advanced.
Paloma

Hi
Try with this blog it wil solve your problem
XI--WebSphereMQ : Receiver Channel Inactive in MQ
Thanks
sudhir sharma

CPO SAP Adapter pre-requisite Check Error

TEO 2.3.5 SAP adpater Pre-requisite Error
 Trying to setup an SAP ABAP connection. Satisfied the pre-requisite of SAP NCO sapnco30dotnet40P_7-20007348, still get the following error while checking the pre-requisite.
Unable to check for prerequisites:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
This is what I see in the logs-
/StackTrace><ExceptionString>System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.TransportReplyChannelAcceptor+TransportReplyChannel, cannot be used for communication because it has been Aborted.</ExceptionString></Exception></TraceRecord>
||735|2013/03/01 07:33:30.028|2084|PoolThread:57|||WCF: System.ServiceModel Error: 131075 :
||736|2013/03/01 07:33:30.029|2084|PoolThread:57|||WCF: <TraceRecord xmlns="
http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord
" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>Tidal.Automation.Server.exe</AppDomain><Source>System.ServiceModel.Channels.TransportReplyChannelAcceptor+TransportReplyChannel/59871390</Source><Exception><ExceptionType>System.ServiceModel.CommunicationObjectAbortedException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The communication object, System.ServiceModel.Channels.TransportReplyChannelAcceptor+TransportReplyChannel, cannot be used for communication because it has been Aborted.</Message><StackTrace> at System.ServiceModel.Channels.InputQueueChannel`1.EndDequeue(IAsyncResult result, TDisposable&amp; item)
 at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext&amp; requestContext)
 at System.ServiceModel.Dispatcher.ChannelHandler.EndTryReceive(IAsyncResult result, RequestContext&amp; requestContext)
 at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)
 at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
 at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
 at System.Runtime.InputQueue`1.AsyncQueueReader.Set(Item item)
 at System.Runtime.InputQueue`1.Shutdown(Func`1 pendingExceptionGenerator)
 at System.ServiceModel.Channels.CommunicationObject.Abort()
 at System.ServiceModel.Dispatcher.ListenerHandler.AbortChannels()
 at System.ServiceModel.Dispatcher.ListenerHandler.OnAbort()
 at System.ServiceModel.Channels.CommunicationObject.Abort()
 at System.ServiceModel.Dispatcher.ChannelDispatcher.OnAbort()
 at System.ServiceModel.Channels.CommunicationObject.Abort()
 at System.ServiceModel.ServiceHostBase.OnAbort()
 at System.ServiceModel.Channels.CommunicationObject.Abort()
 at Tidal.Automation.Server.WebService.WCFHost.StopServiceHost(Object state)
 at Tidal.Automation.Common.ThreadPool.OuterWaitCallBack(Object state)
 at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
 at System.Threading.ThreadPoolWorkQueue.Dispatch()
 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
</StackTrace><ExceptionString>System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.TransportReplyChannelAcceptor+TransportReplyChannel, cannot be used for communication because it has been Aborted.</ExceptionString></Exception></TraceRecord>
||737|2013/03/01 07:33:30.164|2508|MainEngineThread|||Encountered an exception while attempting to kill adapter SAP Solution Manager Adapter (95151695-aacc-4310-af5f-c38abfcea384). Proceeding.
||738|2013/03/01 07:33:30.164|2508|MainEngineThread|||EXCEPTION (Tidal.Automation.Common.Product.RhapsodyException): An attempt was made to stop the adapter named 95151695-aacc-4310-af5f-c38abfcea384 but it appears to have never been started.
Stack Trace: at Tidal.Automation.Engine.Core.AdapterStarter.KillAdapter(Guid adapterId)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.DisableAdapterStartups()
||739|2013/03/01 07:33:30.165|2508|MainEngineThread|||Encountered an exception while attempting to kill adapter SAP ABAP Adapter (cf6f0f84-a364-4105-b11f-0fef62873b37). Proceeding.
||740|2013/03/01 07:33:30.165|2508|MainEngineThread|||EXCEPTION (Tidal.Automation.Common.Product.RhapsodyException): An attempt was made to stop the adapter named cf6f0f84-a364-4105-b11f-0fef62873b37 but it appears to have never been started.
Stack Trace: at Tidal.Automation.Engine.Core.AdapterStarter.KillAdapter(Guid adapterId)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.DisableAdapterStartups()
||741|2013/03/01 07:33:30.221|2508|MainEngineThread|||Encountered an exception while attempting to kill adapter SAP Solution Manager Adapter (95151695-aacc-4310-af5f-c38abfcea384). Proceeding.
||742|2013/03/01 07:33:30.221|2508|MainEngineThread|||EXCEPTION (Tidal.Automation.Common.Product.RhapsodyException): An attempt was made to stop the adapter named 95151695-aacc-4310-af5f-c38abfcea384 but it appears to have never been started.
Stack Trace: at Tidal.Automation.Engine.Core.AdapterStarter.KillAdapter(Guid adapterId)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.DisableAdapterStartups()
||743|2013/03/01 07:33:30.222|2508|MainEngineThread|||Encountered an exception while attempting to kill adapter SAP ABAP Adapter (cf6f0f84-a364-4105-b11f-0fef62873b37). Proceeding.
||744|2013/03/01 07:33:30.222|2508|MainEngineThread|||EXCEPTION (Tidal.Automation.Common.Product.RhapsodyException): An attempt was made to stop the adapter named cf6f0f84-a364-4105-b11f-0fef62873b37 but it appears to have never been started.
Stack Trace: at Tidal.Automation.Engine.Core.AdapterStarter.KillAdapter(Guid adapterId)
 at Tidal.Automation.Engine.Core.AdapterLifecycleManager.DisableAdapterStartups()

Please open a TAC case. They can not only get you past the missing prerequisite, but also raise the issue on the bad prerequisite detection error which you are seeing so we can get it fixed in the product.

JMS adapter with complex messages

Each of our MQ Series messages contain several transactions. Our standard format is:
<Message>
<RecordSet(1..n)>
HeaderRecord
Item Record(1..n)
</RecordSet>
</Message>
Does anyone have an example for how this would be done in XI 3.0? I have seen how this can be done with the file adapter, but with the JMS adapter do I need to use BPM?
Thanks,
Andrew

Each of our MQ Series messages contain several transactions. Our standard format is:
<Message>
<RecordSet(1..n)>
HeaderRecord
Item Record(1..n)
</RecordSet>
</Message>
Does anyone have an example for how this would be done in XI 3.0? I have seen how this can be done with the file adapter, but with the JMS adapter do I need to use BPM?
Thanks,
Andrew

JMS Message Format

Hi,
I have to set-up a scenario where I have to load messages from a Message Queue system via XI JMS Adapter into R/3. On R/3 side, we are talking about the Invoices IDoc. Now I have to define the XML structure of the message that has to be provided in the message queue of the SonicMQ System. Does anybody have experience with loading XML messages from a message queue system and can tell me how the message structures are defined? Is a XSD or DTD desription enough? Or does a JMS message also contain somehting like Header data like SOAP?
Thanks in advance.
Alex

Hi Alexander,
Or does a JMS message also contain somehting like Header data like SOAP?
The datatype you create for your JMS message will be like any other XMl messsage you craete for a FILE.
If the application posting the message to the JMS queue is not posting an XML message or in a format that you want, you can always do content conbersion in the Sender JMS adapter.
Take a look at this,
http://help.sap.com/saphelp_nw04/helpdata/en/4d/a3bc97ff55c742af7faed661635baf/content.htm
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891">How to use Content Coneversion Module of JMS adapters</a>
Regards,
Bhavesh

JMS adapter -Message format pre-requisites

Similar Messages

Maybe you are looking for