cancel
Showing results for 
Search instead for 
Did you mean: 

prerequisites to configuration for ABAP Proxy -???

Former Member
0 Kudos
310

My scenario is file->XI->R/3(abap server proxy).

Xi and R/3 are 2 seperate business systems

-Abap server proxy created on R/3 business system. R/3 client 550

-Xi client 400.

-SLD is common for both XI and R/3

<b>My question is in reference to the below message thread:</b>

<b>1.I understand all the below configuartaion has to be done on R/3 business system, tell me am I correct</b>

<b>2. are these configuartion needed for <u>client proxy as well as server proxy</u> also?</b>

-


The prerequisites to configuration for ABAP Proxy include: (landscape dependent)

1. The business systems should be based on SAP Web AS 6.20 and SAP Web AS 6.20 kernel patch level above 1253

2. You have installed the XI Add-On in each of these business systems as described in the Installation Guide SAP Exchange Infrastructure 3.0

3. The business systems and your central Integration Server are maintained in the System Landscape Directory (SLD).

Configuration required on the Business System:

1. Create HTTP connection in the business system.

Configuration Details:

Technical Setting:

1. Following Inputs are required for technical setting

1 Connection Type: H

2 Target Host: System name

3 Service Number: HTTP Port name

4 Path Prefix: /sap/XI/engine/?type=entry

Logon Security

On the Logon/Security tab page, enter the following logon data:

1 User: XIAPPLUSER (for example); this user should represent the sending business system (see also the SAP XI Security Guide under Service Users for Message Exchange).

2 Password: the password you have specified for this user

3 Client: SAP XI Integration server

4 Language: Language required

2. Configuration Business system as local Integration Engine.

1. Goto Transaction SXMB_ADM

2. Choose Edit --> Change Global Configuration Data.

3. Select Role of Business System: Application system

4. Corresponding Integration server: dest://<HTTPDESTINATION>. Here <HTTPDESTINATION> SAPISU_XID created in step 1. Dest://SAPISU_XID.

5. Under Specific Configuration Data you can specify additional configuration data

1.Select the relevant category under Specific Configuration Data.

2.Choose Change Specific Configuration Data.

For ABAP Proxies, Add the following configuration:

1.Category RUNTIME

2.Parameters: IS_URL

3.Current Value: dest://SAPISU_XID

Configuration of the Integration Engine

3. Connection between Business System and System Landscape Directory

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

1.Execute transaction SM59 in the business system.

2.Choose Create.

3.Enter at least the following:

1.RFC Destination: LCRSAPRFC

2.Connection Type: T

3.Description: <your description>

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

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.

RFC Destination

2. Maintaining the SAP J2EE Connection Parameters for LCRSAPRFC and SAPSLDAPI in SAP J2EE engine

1. Goto J2EE Engine

2. Choose Cluster --> Server --> Services. JCo RFC provider

3. Under RFC destination specify the following:

Program ID: LCRSAPRFC

Gateway Host: <Integration Server host>

Gateway Service: <Integration Server gateway service>

Number of process: 3

4. Under Repository specify the following:

Application Server: <Integration Server host>

5. Choose Set.

3. Maintain SLD access details in Transaction SLDAPICUST

1. You can reuse this program ID for all Business systems

2. If there is HTTP error during connection, first run transaction SLDCHECK in the Business system. Also check that HTTP connection is working fine.

3. In XI Adapter use HTTP connection rather then giving R/3 input details as this is easier to transport and maintenance

4. One receiver adapter can be used for all Interfaces connecting to a Business system.

<b>Thanks for your reply in adavnce.</b>

KK

Accepted Solutions (0)

Answers (3)

Answers (3)

moorthy
Active Contributor
0 Kudos

Hi,

Refer this Configuration guide-

https://websmp102.sap-ag.de/~sapidb/011000358700001697502004E.PDF

Page no 12, 24 etc check these

Also check this blog

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

>>>For question no1.. Yes, your R/3 system should act as a application system. And you need to configure Http destination from R/3 system to XI system

Regards,

Moorthy

Former Member
0 Kudos

Hi KK,

Please check this too..

/people/siva.maranani/blog/2005/04/03/abap-server-proxies

cheers,

Prashanth

Former Member
0 Kudos

KK, why not you can publish your scenario in a Blog please, looks very interesting. Thanks.

Shabarish_Nair
Active Contributor
0 Kudos

2. are these configuartion needed for client proxy as well as server proxy also?

>>>>

the configuration is one time thing and your R3 will act as a server or client according to the data being sent or received.

In R3 a point to be noted is that in SXMB_ADM -> Intg. Engine Confg. -> Role of Business System sud be as a Application System.

Ref: /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

Message was edited by: Shabarish Vijayakumar

Former Member
0 Kudos

Could you reply for my 1st questions also.

Thanks

KK