Different Systems, same Configuration in ID, but different Result?!

Question

Hi guys,
i´m working on a Idoc to File Scenario, which works in our development environment (DXI) but fails in our test environment (QXI)
first of all some information about our system landscape.
We are using 3 XI Systems for development (DXI), test (QXI) and production (PXI).
For some reason we don´t have one central SLD, but 3 SLD (one for each XI System)
So the Repository content could be transported via File, the configuration in ID is environment specific (not transported) and have to be maintained manually.
As I sad above the scenario is Idoc to File, more exactly it is 1 Idoc to 2 files.
The result files of one idoc are used to have the "same" file name pattern for example
file 1 = file2_TIMESTAMP.idoc
file 2 = file1_TIMESTAMP.eds
The order of the files is important. file 1 should be created first, file 2 afterwards.
in this pattern TIMESTAMP is the timestamp should be the same for both file, so I use the timestamp of the XI message of the idoc
(=> StreamTransformationConstants.TIME_SENT)
the content of the file differs. While file 2 contains one text line with some control information (static and some payload data), contains the file 1 the idoc xml, but with a
different codepage (ISO-8859-1 instead of UTF-8)
To get the wright content and filename, 2 java mappings are used, that are referenced in interface determination. furthermore the order of the files should be maintained, so that file 1 (idoc xml) should be created first, and file 2 (control information) afterwards
(filename mapping is done via Dynamic configuration)
As I sad at the beginning the whole scenario works fine for development environment, but fails for test.
In test the 2 files are created with the correct filename, but the file content of the file 1 is wrong. It contains the same content then the file 2 (control information)
when i have a look at the apap monitoring sxmb_moni the message content after java mapping is correct for both files.
but in message monitoring (RWB) the file 1 has the same content as file 2, which is incorrect.
Directory content of development and test are the same.
why is the result different?
anybody has an idea.
This error drives me crazy
Kind regards
Jochen

Answer 1

Hi Suddha,
thanks for your help.
obviously something like that must be the reason for that behaviour.
I compared the audit logs of a succesful message (DXI) and a failed message (QXI)
there was only one difference between this to messages.
In the QXI there was a entry like "process the underlying message of mulit-message-ID xxxxxx"
I have searched both the RWB and the integration server for thismsg-ID, but without success.
I forgot one detail.
There is one difference between development environment and test.
In test and production we have two java nodes. In development we only have one single java node.
Could this be of any influence on a scenario like that?
Suddhasatta Guha wrote:
Could this be a problem while retrieving the message from the Receive queue...............the application retrieving the wrong message before delivering it to the File Channel
Since the IDoc message is splitted in the Interface Determination Step - is there any Parent Message ID to this individual messages?
In RWB the messages from the Integration Engine have a reference and a parent msg id, but the adapter engine message don´t.
In this point there is no difference between DXI and QXI.
maybe somebody have another idea how to get more information about this error
Kind regards
Jochen