JMS sender content conversion problem

[former_member348698]

Hello,

My scenario : JMS sender(MQ) --> SAP PI --> SAP ECC.

Problem: Data is sent via Websphere MQ series(JMS provider) in flat file(text format).

The CCSID at MQueue is 1208.

Format: MQSTR

Type: Datagram

I could see the data received by MQueue

We are receiving invalid data in the form "@@@", "@@??????".

<JobNumber>@@???</JobNumber>

  <UserID>??????@</UserID>

    I am using JMS Message transformationBean to convert the data. Below is my confirmation:

    Character Set ID(CCSID) for non-ASCIINames: 1208.

    Processing Sequence for conversion:

    SAP XI JMS Adapter/ConvertJMSMessageToBinary    convert_JMS2Bin

    SAP XI JMS Adapter/ConvertBinaryToXMBMessage    convert_Bin2XI

    AF_Modules/MessageTransformBean                          Plain2XML

    CallSapAdapter                                                          call_AF_MS

    Module Configuration:

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

    Transform.ContentType        text/xml;charset=utf-8

    xml.conversionType            SimplePlain2XML

    xml.documentName           

    xml.documentNamespace

    xml.fieldFixedLengths

    xml.fieldNames

    xml.lastFieldsOptional

    xml.processFieldNames    from Configuration

    xml.structureTitle

      Is there anything missing in the configuration due to which data is not translated properly. I am not getting any error in the processing of message,but data coming is invalid. Let me know if you need further details to understand the problem.

    Thanks,

    Shikha

[Former Member]

Hello,

I have the same scenario...
Do you have a solution now?
I get the Error-message: Context is not allowed in prolog.

The message I get is in textformat:

SA010.....    ....        

and I have the same processing conversion  as you have mentioned.

Thanks

Manfred

[former_member348698]

Yes. The issue was resolved.

The issue was in the MQueue codepage. Check with your MQTeam and see if they have proper codepage. The PI settings were correct and worked once MQueue team corrected it on their end.

(The CCSID at MQueue was 1208, they changed it to 37 as it worked).

Thanks

Shikha

[former_member348698]

       Any Clue . Is this issue being faced by anyone. Please help!!

    Thanks

    Shikha