Monday, December 10, 2007

I see an error "Unable to connect to the Integration Builder" while trying to create ABAP Proxies - what can I do?

Have you got the error message "Unable to connect to the Integration Builder, when you are trying to create a ABAP PROXY from a R/3 system?

This blog enumerates the process of Configuration required for ABAP proxy. All the configurations are available in the SAP XI configuration guide and Installation guides. This is an attempt to bring the entire configuration together.

Consider the following system landscape for configuration of the ABAP Proxy:
Two systems exist in the landscape:
System X : SAP XI 3.0 system and
System Y : SAP R/3 on WAS 620

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

HTTP Connection to Connect SAP R/3 to SAP XI

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://. Here 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
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:
Gateway Host:
Gateway Service:
Number of process: 3

4. Under Repository specify the following:
Application Server:
5. Choose Set.

3. Maintain SLD access details in Transaction SLDAPICUST

My Learnings:
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.

No comments:

Blog Archive