Scribd
Upload
180 views

Proxy

This document outlines the steps to setup proxy communication between SAP ECC and PI/PO systems. The steps include: 1) Creating HTTP destinations in both systems for communication with the integration engine. 2) Configuring the integration engine and SLD access in SAP ECC. 3) Creating SOAP sender and receiver channels in PI/PO for proxy processing between the two systems.

Uploaded by

Uday
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
180 views

Proxy

This document outlines the steps to setup proxy communication between SAP ECC and PI/PO systems. The steps include: 1) Creating HTTP destinations in both systems for communication with the integration engine. 2) Configuring the integration engine and SLD access in SAP ECC. 3) Creating SOAP sender and receiver channels in PI/PO for proxy processing between the two systems.

Uploaded by

Uday
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

setup of proxy communication between sap ecc and pi/po

1.create http destination for advanced adapter engine in sap ABAP back-end
system.HTTP_POD

2.create http destination to enterprise service repository ESR in sap ABAP back end
system.SAP_SPROXY_ESR.

3.setup http rfc destination to sld. SLD_POD.

4.Configure the integration engine administartion using transaction.SXMB_ADM.

5.configure SLDAPICUST.

6.create http destination in pi/po for inbound proxy processing.prerequisites:HTTP


services are active in SICF.

7.create proxy sender and receiver communication channels in pi/po.sender


channel:Soap_sender,Receiver channel:Soap_receiver

step-1: create destination for advanced adapter engine in (SM59).

> the destination of type G (http connection to external server ) is directed to


AAE OF PROCESS INTEGRSTION OR PROCESS ORCHESTRATION.

> we can name the destination http <pi/po system ID> ,let's assume the system ID
of the development server is POD .http destinatioin namewill be HTTP_POD.

CONNECTION TYPE : G(HTTP CONNECTION TO EXTERNAL SERVER)

TARGET HOST =<HOST NAME OF AAE OR AEX>

PORT(service number)=<HTTP PORTNUMBER OF AAE OR AEX HOST SERVER>:DEFAULT-50000

PORT FOR HTTP IS 5<SYSTEM NUMBER>00 & FOR HTTPS IS 5<SYSTEM NUMBER>01.DEFAULT
PORT FOR J2EE IS 50000

>PATH PREFIX = /XISOAPAdapter/MessageServlet?ximessage=true

step 2: Create http destination to ESR.

> THIS RFC DESTINATION IS USED by transaction SPROXY to import esr objects and
generate proxy objects we can name the rfc destination SAP_PROXY_ESR.

parameters used for http connection to esr.

>connection type = G

>target host = <host name of AAE OR AEX>

>port = HTTP port number of aae or aex:default =50000

> path prefix = /rep

step[ 3: setup http rfc destination in SLD.

>create another http rfc destination to sld from SM59.we will reuse this http
destination in step 5 to setup SLD access data in SLDAPICUST Transaction.
step 4: configure the integration engine administration using transaction SXMB_ADM.

>go to SXMB_ ADM. and select the node ~Integration Engine Configuration.
then choose configuration option.

Add new entries to the configurration and define parameters


'IS_URL' ,HTTP_TIMEOUT and 'ENGINE_TYPE'.

DESTINATION NAME AFTER CHARACTERS dest:// IS THE RFC DESTINATION WE CREATED IN STEP
1 :HTTP_POD

step 5 : setup SLD access data via SLDAPICUST.

>go to transaction sldapicust


>And add the SLD HTTP destination name as alias name SAP_CONFIG.
>make sure to select the option ..Access to sld server using HTTP and connect
using HTTP destination.

these are the recommended settings .but we can directly configure the SLD URL
without http destination also.

step 6 : create http destination in NWA.

in this step we will create an http destination to sap back end integration server
from PI/PO NWA.

> go to NWA > CONFIGURATION > INFRASTRUCTURE > DESTINATIONS and create HTTP
destination to Netweaver Integration Engine .

>create a new destination using NEW destination creation wizard.

>usually destination name is defined as <SAP System ID>CLNT<Client Number>_HTTP.

> give the fields of hosting system,destination name ,destination type.

in next tab define the connection and transport details, URL,SYSTEM ID,CLIENT AND
LANGUAGE parameters are mandatory.

> to find the url ,go to transaction SICF(SAP back-end) and choose Execute .service
tree will be displayed in the result .expand the service tree default host and
navigate to default_host > sap > iwbep or default_host > sap > xi > engine.

Next Step is to define the logon data. In this example I will use Basic
Authentication method with Username and Password.

This HTTP destination will be reused in SOAP Receiver Communication Channel in


step 7.

step 7 : for proxy communication select soap channel sender & receiver.transport
protocol as XI 3.0

>>>Check if RFC and HTTP Destinations Are Working Fine.

Using transaction sm59 and Connection Test, check if the RFC Destinations are
functioning as expected. Repeat this step for all RFC destinations we created in
previous steps.

>>Test SLD Status Using Transaction SLDCHECK.

Execute Transaction SLDCHECK to make sure SLD configuration steps were performed
correctly. Choose Allow in the pop-up window.

>>Test SLD Status Using Transaction SLDCHECK.

Execute Transaction SLDCHECK to make sure SLD configuration steps were performed
correctly. Choose Allow in the pop-up window.

Test ESR connectivity using program SPROX_CHECK_IFR_RESPONSE.


Test ESR connectivity using program SPROX_CHECK_IFR_RESPONSE

>>Check Proxy Objects via Transaction SPROXY.


Check if SPROXY shows the Software Components (SWCVs) and Proxy Objects included in
the Namespaces.

>>Test Communication Channels via Runtime Monitor.


Go to Configuration Monitoring Home > Adapter Engine > Communication Channel
Monitor and ping the Sender and Receiver Communication Channels.

You might also like