Creating RFC Destinations in the ABAP and Java Environments

Use
You need to create the following RFC destinations with both transaction SM59 (ABAP) and the Visual Administrator (Java): AI_RUNTIME_JCOSERVER Points from the Integration Server to the mapping runtime. The program ID corresponds to the entry under JCo RFC provider for the J2EE Engine (used for the mapping runtime, value mapping, and the exchange profile). 1. AI_DIRECTORY_JCOSERVER Points from the Integration Server to the Integration Builder. The program ID corresponds to the entry under JCo RFC provider for the J2EE Engine (used to refresh the runtime cache). 1. LCRSAPRFC The RFC destination LCRSAPRFC is required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile. 1. SAPSLDAPI The RFC destination SAPSLDAPI is required for the connection to the SLD. It is used by the ABAP API. Depending on your client settings, it may be necessary to log on to your Integration Server host as SAP system user with the authorization to maintain customizing tables and to release transport orders. User SAP* or DDIC does not have these authorizations. This task covers the template steps 14 to 17.

Maintain the RFC Connections (ABAP)

Perform the following steps:
...

Log on to your Integration Server host. Call transaction SM59. Choose Create. Enter at least the following: RFC destination: AI_RUNTIME_JCOSERVER 1. Connection type: T 1. Description: <your description> Choose ENTER. Choose the Technical settings tab and do the following: Select Registered Server Program. In the Program ID field, enter: AI_RUNTIME_<SID> <SID> is the SAP system ID of your Integration Server host. Use uppercase letters only. Enter Gateway host and Gateway service of your Integration Server host.

To find out the required parameters:

...

On the Integration Server host, call transaction SMGW. Choose Goto Parameters Display (see entries for gateway hostname and gateway service). Choose the Special Options tab and select the Unicode flag in the Character Width in Target System box. Save your settings. Repeat steps 3 to 8 for the remaining destinations: 1. AI_DIRECTORY_JCOSERVER Program ID: AI_DIRECTORY_<SID>, where <SID>is the SAP system ID of your Integration Server host. 1. LCRSAPRFC Program ID: LCRSAPRFC_<SID>, where <SID> is the SAP system ID of your Integration Server host. 1. SAPSLDAPI Program ID: SAPSLDAPI_<SID>, where <SID> is the SAP system ID of your Integration Server host. Leave transaction SM59 open for later tests.

Configure the Destinations (Java)

Perform the following steps:
...

On your Integration Server host, start the J2EE Engine Visual Administrator. Choose Cluster Server Services JCo RFC Provider. In the RFC destination section, enter exactly the same program ID and gateway options for AI_RUNTIME_JCOSERVER that you used in the step Maintain the RFC Connections (ABAP) above. Additionally, set the number of processes to 10. In the Repository section, do the following: Enter the parameters for the Integration Server host: Application Server, System Number, Client, and Language. For User and Password maintain the login parameters for the user SAPJSF. Select the Unicode flag. Choose Set. Repeat steps 3 to 5 for the remaining destinations: 2. AI_DIRECTORY_JCOSERVER Corresponding values from transaction SM59 Number of processes: 10 3. LCRSAPRFC Corresponding values from transaction SM59 Number of processes: 3 4. SAPSLDAPI Corresponding values from transaction SM59 Number of processes: 10

Test the RFC Destinations

After you have maintained all RFC destinations in both the ABAP and Java environments, you can check all the connections above as follows:
...

Call transaction SM59 again. Open your RFC destination. Choose Test Connection. No errors should be displayed.