Creating Destinations on the Java Server

Use

There are three kinds of destinations on the Java Server:

JCo RFC providers
RFC destinations
HTTP destinations

Procedure

1. Create JCo RFC Providers

Create the following JCo RFC providers on the Java Server using the SAP NetWeaver Administrator. Each JCo RFC provider points from the ABAP Server to the Java Server.

JCo RFC Provider	Description
AI_RUNTIME_JCOSERVER	Points from the Integration Server to the mapping runtime. The program ID corresponds to the entry configured for the destination on AS Java (used for the mapping runtime, value mapping, and the exchange profile). See Destinations for Technical Communication
AI_VALIDATION_JCOSERVER	Points from the Integration Server to the XML validation service. The program ID corresponds to the entry configured for the destination on AS Java (used for XML validation). See Destinations for Technical Communication
LCRSAPRFC	Required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile. See Destinations for Technical Communication
SAPSLDAPI	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 release transport orders.

Perform the following steps:

On your Integration Server host, start the SAP NetWeaver Administrator.
Choose Configuration Infrastructure JCo RFC Provider.
Choose Create and 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 server count to 10 and choose Next .
In the Repository Configuration section, do the following and choose Next :
1. Deselect the Use RFC Destination flag.
2. Enter the parameters for the Integration Server host: Application Server Host , System Number , Client , and Language .
3. For User and Password maintain the login parameters for the user SAPJSF.
Do not select anything in the Security Settings and Additional Options sections and choose Next .
Choose Finish .
Repeat steps 3 to 6 for the remaining destinations:
- AI_VALIDATION_JCOSERVER
  
  Server Count 10
- LCRSAPRFC
  
  Server Count 3
- SAPSLDAPI
  
  Server Count 3

2. Create RFC Destinations

Create the following RFC Destinations on the Java Server using the SAP NetWeaver Administrator. Each RFC Destination points from the ABAP Server to the Java Server.

RFC Destination	Description
BusinessProcessEngine_RFC	Points to the integration server where the business process engine ABAP is running.
XI_EXCHANGE_PROFILE	Points to the integration server (AS ABAP) where the exchange profile is stored.
XI_IDOC_DEFAULT_DESTINATION	Destination, where the IDOC metadata is stored.

To create BusinessProcessEngine_RFC , proceed as follows:
1. In SAP NetWeaver Administrator, choose Configuration Infrastructure Destinations
2. Choose Create to create an RFC destination.
3. Specify BusinessProcessEngine_RFC as the destination name, and RFC as the type.
  
  Apply the default values except for the following:
  - In the Connection section, set Load Balancing to No .
  - In the Authentication section, specify the user PIRWBUSER .
To create XI_EXCHANGE_PROFILE , see Exchange Profile Parameters
To create XI_IDOC_DEFAULT_DESTINATION , proceed corresponding to XI_EXCHANGE_PROFILE. In the Authentication section, specify the user PIISUSER . In case you do not want to use the default settings during the initial setup, you can configure the IDoc Metadata. To test your configuration, finally choose Ping Destination .