on 04-28-2014 12:07 PM
Hi Expetrs,
I have a scenario, where there is a FTP sender adapter with adpater specific message attributes on for file name and folder. Then on Integration Engine, the message is sent to two receivers and the messages go back to Adapter engine. On receiver communicate via FTP including secure connection, one NFS... But what I see is that the file name is different for NFS and FTP receiver. NFS file name is shrinked, and FTP contains the source value...
The point is that when I'm checking message header on adapter engine for NFS receiver I see that the file name is shrinked from
DBDC-PROD_GMA_28042014060034679_AFB120.SNL18169D11398664841838226S
to
DBDC-PROD_GMA_28042014060034679_AFB120.SNL1816
For FTP it is ok.
On Integration engine both messages contains still correct file name, so I believe the file name is shrinked on AE...
Do you know why?
Best regards,
Milan
Hi Milan,
The file name length depends of the Operating System, check which is the maximum length for your O.S
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Iñaki,
You mean the receiver business system OS? How does the adapter engine knows the receiver OS?...
I really see in AE in message header for two messages two different file names, even the source is just one message with one file name... I think this is really some kind of issue in PI.
Thanks for answer,
Milan
Hi Milan,
I misunderstood your problem i thought that you was checking in the endpoints and not in the adapter engine monitoring. If you are using dynamic configuration for the file name, have you tried to print a trace in message mapping in order to assure that the filename has all the characters in the message mapping level for the NFS case?
Regards.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.