Skip to Content
0
Aug 07, 2007 at 06:25 AM

"SOAP:Fault" in scenario with ABAP proxy client

102 Views

Hello,

I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.

XI:

The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).

CRM:

The proxy generation is ok.

SLDCHECK is ok.

All RFC destinations are ok.

APPINT_200_620 for CRM was installed and configured well (I think so, but...).

When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):

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

- http://sap.com/exchange/MessageFormat">

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = EST</Trace>

<Trace level="1" type="T">client = 300</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = BABKIN_RA</Trace>

<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>

<Trace level="1" type="T">PLNAME = SENDER</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>

<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

- <!-- ************************************

-->

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>

<Trace level="1" type="T">system-ID = EST</Trace>

<Trace level="1" type="T">client = 300</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = BABKIN_RA</Trace>

<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>

<Trace level="1" type="T">----


</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">

<Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">

<Trace level="1" type="T">URL for integration server read from global configuration</Trace>

<Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />

- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">

HTTP-client: error response= http://schemas.xmlsoap.org/soap/envelope/"> SOAP:Client Error" target="_blank"> http://schemas.xmlsoap.org/soap/envelope/"> SOAP:Client Error during conversion of XI message http://sap.com/xi/XI/Message/30 xmlns:SAP=" http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"> XIServer INBOUND_SECURE_LEVEL DC4424A659314CF18F500002A541D0E7 HTTP Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP'

</Trace>

<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>

<Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>

<Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

...

</SAP:TraceHeader>

I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.

Does anybody know where to find a solution?

Regards,

Roman