on 03-21-2013 2:08 PM
Hi Experts,
In our current Project, we have configured SOAP to File scenario where third party will send the message through webservice to PI using soap adapter.
We have used file as a receiver where the message through webservice using soap is written to file , the transport protocol being NFS.
The issue is when we test the webservice using SOAP UI, the message is received in PI Moni where as the same is not to be seen in the specified directory al11. However if we try after 10- 12 minutes, if we try to send the message again, the message is sometimes can be seen in al11 directory and other times, the message doesnot appear in the specified file directory.
Please let the if I need to do any setting in the recievr file adapter to resolve this error.
Also let me know if you need any more details.
Thanks in advance.
Regards,
Amarnath
Hi All,
the issue is now resolved.
The issue was out of the 3 clustered used 1 cluster's mountpoint was ecc(new one) and the others for the old one.
So basis checked this and now we are able to see all the files in the directory
Regards,
Amarnath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Aramnath,
You need to note down the message id apprearing in SXMB_MONI & search the same message on adapter engine. In case if the file is not created check the status of the message if this is failed or to be delivered state.
May be you file is too big to write ont the target folder & take time to write. Or could have the same name & it must be getting owerwritten each time you run or can be empty file & you must have setting in receiver adapter as "do not write empty file".
Check for all the possiblilies & drill down the issue, kindly post the status of themessage when the file is not written to the NFS.
Regards,
Ashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello All,
@Mark...In RWB(RWB -> Message Monitoring (Adapter Engine)), the final status is DLVD.
May what could be the issue in FCC.
we are using only this parameter under FCC
filecontent.fieldSeparator | 'nl' |
.
@Manish, Yes, it is old file being overwritten. There is no error as such , only , at times essage reaches the directory and at times don't...
@Ashish.... checked after changing the setting to "do not write empty file". still same error.
Please let me know if I need to do anything else.
Regards,
Amarnath
Hi Ashish,
This is not a disc space issue as the message can be seen in the directory if we try to send the new message after a gap of 10 15 minutes.However old messages sent cannot be seen in the directory before 10 15 minutes.
Also checked with the option of timestamp, issue remains same.
Regards,
Amarnath
Hi Amarnath,
Please check the uniqueness of filename. It might be the old file is overwritten.
Also, if there is any error kindly paste the log here.
-Manish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
It could be a problem with FCC, what does RWB -> Message Monitoring (Adapter Engine) say?
Regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.