Hi Experts i am working on JMS to file with Dynamic Configuration

[vijaya11]

Hi Experts i am working on JMS to file with Dynamic Configuration(ICO) in SAP PI 7.1.

but at the target path i am getting the text file insted of XML

[vijaya11]

I am using the receiver file adapter with Append mode,could you please help on this

[vijaya11]

Thank you so much Steffi

[vijaya11]

I have tried and now placing xml file sinto AL11 path but its writing the half of the file only

Regards,

Vijaya

[vijaya11]

Hi Experts,

Could you please suggest any help.

Trying to placing the file without append mode but still getting the text file in AL11 path.

Regards,

Vijaya

[vijaya11]

Hi Manoj,

For this"Don't try to append XML file as the file which is getting appended will have multiple XML headers which will cause XML to be invalid"

The first file its self we got the text file in AL11 path.

The first scenario we are using the JMS to file for placing the files in Al11 path.

The 2nd approach is File to Proxy : The file adapter pick the files form AL11 path and send to Ecc via proxy, here we are using peace of XSLT code for removing the XML headers from the appended files.

Could please suggest your inputs

[manoj_khavatkopp]

Vijaya,

Well your approach looks promising . Yes collecting messages in PI is not good idea and using append mode is the good one . But as you said you are getting Text File instead of XML file . Don't try to append XML file as the file which is getting appended will have multiple XML headers which will cause XML to be invalid .

Not sure how it is the creating XML file as there is not much details mentioned check the source file format is it XML if yes then if there is no FCC/Module used then . But my suggestion try to convert XML to text and place it in Al11 and keep appending . The you can ask ABAP developer to read this text file periodically . ECC can convert the text file to XML as per your requirement.

Br,

Manoj

[vijaya11]

This is the requirment Manoj

Current scenario:

• 1.MQ(message broker) sends individual messages to PI

• 2.PI reads messages one by one from the queue(MQ)

• 3.PI pushes each message to ECC

• 4.ECC receives each message, stores the message and process(postings) the message.

Bottleneck: storing each and every message costs lot of insert/read/delete/update operations on database level, this is actually delaying the processing of a message especially when high volumes are delivered.

Proposed scenario:

• 1.MQ(message broker) sends individual messages to PI (same as current scenario)

• 2.PI reads messages one by one from the queue(MQ) (same as current scenario)

• 3.Can PI club 4 to 5 messages into one message and then send as a single message to ECC ? meaning 4 to 5 messages are in one payload. This reduces the bottleneck of insert/read/delete/update to 4 to 5 times.

• 4.ECC receives single message and then process clubbed messages(4 to 5) - ABAP consultant can easily do this.

[vijaya11]

Hi Manoj,

Thank so much for your reply.

We are not converting the xml file to text file, we are receiving the messages from JMS queue and doing the transformation.

With the the receiver file adapter we are try to append the files.But in the AL11 path we are getting the text file instead of XML file.

Our requirement is MQ sending the 1000 messages to PI..we need to club the 500 message into one message and send it to ECC

So we don't want go with the BPM we are trying with JMS-poll interval and File adapter with append mode

could please provide your suggestions

[manoj_khavatkopp]

Vijaya,

You need to apply FCC or MTB module to convert XML to Text file . Try searching you ll find a lot of threads/blogs.

Br,

Manoj