PI 7.11 Proxy communication to SAP BW 7.01 failed

[Former Member]

Hello to all,

we have following sync. scenario:

3rd Party >SOAP> SAP PI >ABAP Proxy> SAP BW

Now I send with soap UI request to the Service on PI.

I get an error and could it see in the sxmb_moni on PI:

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

- <!-- Aufruf eines Adapters

-->

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

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>

<SAP:P1>35</SAP:P1>

<SAP:P2>HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Error while sending by HTTP (error code: 35 , error text: HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.)</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

I have found this link:

But it do not resolved my problem.

Could please someone help me?

Thanks and regards

Martin

[Former Member · Accepted solution]

Hi ..

What we can do is Point you to Correct directions.

Please Check following things ...

1. Check SLD BW Object is OK ..

2. RFC and Proxy Base line Config in BI System

2.1 RFC-TYPE 3 to DEV PI Client from BI System

2.2 RFC Destination in BI: PI_INTEGRATIONSERVER

Technical Setting:

1. Following Inputs are required for technical setting

1 Connection Type: H

2 Target Host: PI HOST NAME

3 Service Number: HTTP Port name 8000 - Check with SMICM

4 Path Prefix: /sap/xi/engine/?type=entry - check this.

2.3 Configuration Business system as Application system ( BI system).

1. Goto Transaction SXMB_ADM

2. Goto Integration Engine Configuration -> Choose Edit

3. Select Role of Business System: Application system

4. Corresponding Integration server: dest://PI_INTEGRATIONSERVER (Created in 2.2)

2.4 CLick configuration Compare button in same screen to SLD.

2.5 Create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection.

1.Execute transaction SM59 in the application system.

2.Choose Create.

3.Enter at least the following:

1.RFC Destination: LCRSAPRFC

2.Connection Type: T

3.Description: <your description><in our case LCRSAPRFC>

4.Choose ENTER.

5.Choose the Technical settings tab page and do the following:

6.In the Program ID field under Registered Server Program, enter LCRSAPRFC_<SYSTEM ID>

7.This program ID must correspond to a program ID specified in the RFC engine settings of the SAP J2EE Engine on the Integration Server host.

2.6 Execute transaction SM59 in the business system.

2.Choose Create.

3.Enter at least the following:

1.RFC Destination: SAPSLDAPI

2.Connection Type: T

3.Description: <your description><in our case SAPSLDAPI>

4.Choose ENTER.

5.Choose the Technical settings tab page and do the following:

6.In the Program ID field under Registered Server Program, enter SAPSLDAPI_<SYSTEM ID>

7.This program ID must correspond to a program ID specified in the RFC engine settings of the SAP J2EE Engine on the Integration Server host.

2.7 Maintain SLD access details in Transaction SLDAPICUST

3. TCODE - SICF

All services acticated for XI system.

4. TCODE - SMICM

Check for active Service

HTTP

SMTP

Note1 : Check for all password along with Username and their authorisations.

Note2 : Perform SLDCHECK ON BI System to check all configuratins.

Now USE TCODE - SPROXY - With Developement auth.

[Former Member]

Strange msg indeed ! Is it really sthg related to SSO ? Is SSO involved b/w your systems ? Sometimes, having a look at ICM log files (SMICM transaction) may help if HTTP is handled by the ABAP stack ...

Rgds

Chris