Receiver JMS Adapter Content Conversion issue

[Former Member]

Scenario :

R/3 -->XI -->MQ(XML2Plain)

Hi

We are using Receiver JMS Adapter to send the Message from XI to MQ.

The XML has to be converted to plain file. And Content conversion is

being done.

With the new development, the message type defined consist of 8 fields

with fixed length. The XML message goes successfully from XI to MQ

without any content conversion. But once simple content conversion is

being done for Receiver JMS adapter, even though the message is

received but it’s empty (without any data records). The adapter

monitoring everything seems fine and it gives the status that message

converted to binary and the message is delivered to MQ. Though on

checking the messages there is no data records.

Below is my content conversion configuration done in Module tab. Kindly

revert back what can be the problem as have done exactly the same way

as described in Content Conversion How to Guide for receiver JMS.

localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean XML2Plain

localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin

localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService Local Enterprise Bean exit

XML2Plain Transform.Class com.sap.aii.messaging.adapter.Conversion

XML2Plain TransformContentType text/plain;charset=utf-8

XML2Plain xml.addHeaderLine 0

XML2Plain xml.addHeaderLine SimpleXML2Plain

XML2Plain xml.fieldFixedLengths 8,10,10,20,40,40,8,8

XML2Plain xml.fixedLengthTooShortHandling Cut

regards.

santosh.

[Former Member · Accepted solution]

Hi,

check localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin

this is not CallJMSService.

And also check the receiver Structure, if it is falt structure its ok, else

see the below link if it has the complex structure , how to handle..

See the below links

/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

content conversion

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bf...

Regards

Chilla..

[Former Member · Accepted solution]

Hi Sreeram & Chandrasekhar,

I have checked the things according to both of your suggestions.

But, still its the same case.

Only the blank file is getting created without any data records at MQ side.

Monitor in R/3 & XI still shows success status.

regards.

santosh.

[Former Member · Accepted solution]

can you give me our target message side Messagetype strucuture.

[Former Member · Accepted solution]

Hi,

What is sender .. is it Idoc?

What is the target structure is it flat strcture or complex structure as i asked before.it is the important issue.

Regards

Chilla

[Former Member · Accepted solution]

This is the receiving structure.

we want to do the content conversion for below xml file.

<?xml version="1.0" encoding="UTF-8"?>

<ns1:Employee_MT xmlns:ns1="http://pdk/Digiper/hrtl_SapHrToDigiper">

<post_omrade>asdf</post_omrade>

<post_kontor>23847</post_kontor>

<Cost_center>28347</Cost_center>

<CPR_number>34322</CPR_number>

<First_Name>kjshf</First_Name>

<Last_name>023</Last_name>

<End_Date>239</End_Date>

<Personal_number>32984</Personal_number>

</ns1:Employee_MT>

Message was edited by:

santosh koraddi

[Former Member · Accepted solution]

Target sturture seems to ok . what is the occurance of each field i.e cardinality of the message type

[Former Member · Accepted solution]

Santosh,

make that our elements are one level below Employee_MT

<?xml version="1.0" encoding="UTF-8"?>

<ns1:Employee_MT xmlns:ns1="http://pdk/Digiper/hrtl_SapHrToDigiper">

<post_omrade>asdf</post_omrade>

<post_kontor>23847</post_kontor>

<Cost_center>28347</Cost_center>

<CPR_number>34322</CPR_number>

<First_Name>kjshf</First_Name>

<Last_name>023</Last_name>

<End_Date>239</End_Date>

<Personal_number>32984</Personal_number>

</ns1:Employee_MT>

[Former Member · Accepted solution]

Cardinality of message type is 1:1.

[Former Member · Accepted solution]

santosh

make sure that your all elements are one level below Employee_MT or under Employee_MT but not at same level

[Former Member · Accepted solution]

Hi Sreeram,

Yeah , they are 1 level below Employee_MT.

we have written the issue to sap as well.

lets c ...wat they come up with ....

if u have any other suggestion please let me know.....

cheers.

santosh.

[Former Member · Accepted solution]

HI, Actually this comes in Sender side.

See the above given JMS Content conversion, even though it is not user one root element .

But it it better to change into the following way

Empoyee_MT -- occurences -- 0..unbound --( bcz you would have multiple rows)

field1

field2

field 3

....

I hope you got it..

Are you sending the IDoc , sure you are sending the proper data.. check

Regards

Chilla

[Former Member · Accepted solution]

Hi chandrasekhar,

as of now we have 1:1 occurences.....

But, even we are thinking of changing occurences from 1:Unbounded & group similar messages into single message.

lets c if it works...

My scenario is

R/3(proxy) >XI(XML2Plain)>MQ(flat file)

cheers,

santosh.

[Former Member · Accepted solution]

Santosh,

can you type some wrong entries configuration of modules. it should throw error.

[Former Member · Accepted solution]

yeah ...will try that...

Now, i am changing the whole config from 1:1 to 1:Unbounded..

as it is part of interface as well.

let c if this works after config change....

thanks

santosh.

[Former Member · Accepted solution]

delete ur adapter create it from first in adapter moudles dont copy paste all modules names and values type the values and press enter once u complete that line . no spaces.

[Former Member · Accepted solution]

Hi Sreeram,

Problem got solved.

Actually, i declared the Data Type wrongly.

Thanks for all ur help.

cheers.

santosh.

[Former Member · Accepted solution]

cool it works.

[Former Member]

Santosh,

can you check once again is their any blank space at end in these parameters. if you blank space you will have some problems. these parameters does not work.