Quantcast
Channel: SCN : All Content - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 7030

File-to-RFC scenario in PI 7.1

$
0
0

I am doing a set up for the File-to-RFc scenario.  Testing works fine in Message mapping and Test configuration.

The file is picked from sender side and also able to view the data in SXMB_MONI.

 

I am getting the following error in C.C monitoring of receiver:

Receiver channel 'CC_FILE2RFC1_RECEIVER' for party '', service 'DEC' (internal name 'RfcClient[CC_FILE2RFC1_RECEIVER]')

Client data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=110, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=****, jco.client.sysnr=02, jco.client.ashost=*****}

Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=110, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=****, jco.client.sysnr=02, jco.client.ashost=****}

Current pool size: 0, maximum pool size : 1

 

And the following error in SXMB_MONI:

 

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--  Request Message Mapping

  -->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

  <SAP:Category>Application</SAP:Category>

  <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>

  <SAP:P1>com/sap/xi/tf/_MM_TH_FILE1_</SAP:P1>

  <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException:</SAP:P2>

bold  <SAP:P3>Content is not allowed in prolog.</SAP:P3> bold

  <SAP:P4 />

  <SAP:AdditionalText />

  <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_TH_FILE1_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Content is not allowed in prolog.</SAP:Stack>

  <SAP:Retry>M</SAP:Retry>

  </SAP:Error>

 

Could anyone help me at the earliest


Viewing all articles
Browse latest Browse all 7030

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>