Defining JCo Destinations (SAP Library)

Defining JCo Destinations

Use

iViews in the Enterprise Portal that require data from systems that are based on SAP Basis technology access these via remote function calls (RFC). These are invoked using the SAP Java Connector (JCo). You need to define a JCo destination for each SAP component system that you wish to connect to via RFC, for example when you use the role migration tool.

This information is stored in an XML file in the PCD.

You can define more than one JCo destination for a SAP System, for example, if you want to define two destinations that each use a different Single Sign-On variant.

Prerequisites

The Java iView Runtime is installed.

You are familiar with XML and XML schemas.

Procedure

You can find a sample JCo destinations XML file and the XML schema for the file on the Java iView Runtime at the following path:

<Servlet_engine>\web-inf\plug-ins\portal\system\xml

The JCo destinations file is jcoDestinations.xml.

The XML schema is jcoDestinations.xsd

Copy the sample file to a local directory and modify it to suit your needs.

The name attribute is a descriptive identifier only. You can use any name. This name must be specified in the property SystemIdentifier of an iView that uses this JCo destination. For example, if you define a JCo destination called Fred (see example below), you must include the following line in the property file of any iView that uses this JCo destination:

SystemIdentifier.value=Fred

The list of possible attributes that you can define for each destination is listed at List of Attributes for JCo Destinations.

The minimum set of attributes that you should maintain for each system is:

MSHOST (message server)

R3NAME (R/3 name)

CLIENT (client)

Note that in order to create an RFC connection to an SAP System, the Java Connector requires the port number of the message server. Normally this information is stored in a system file (‘SERVICES’) on the client machine, which is distributed by network administration. If you enter the system name in the attribute R3NAME, then you must ensure that the entries for the systems are available in the SERVICES file. If these entries are not available, then you should enter the port number of the message server directly in R3NAME. However this is only recommended if the SERVICES file is not updated automatically, as you would have to change the JCo destinations file each time there is a change to the port number.

When you have finished modifying the file, upload it to the Portal Content Directory (PCD) as described in Uploading System Landscape Descriptions into PCD.

You can also test your entries in the file as described in Testing Your JCo Destinations.

Result

To ensure that the new entries in jcoDestinations.xml are published on the Portal Server, you must restart the Java Servlet Engine (JRun).

Example

The following is an example of a JCo destinations file.

<?xml version="1.0" encoding="UTF-8"?>

<wpl:Destinations xmlns:wpl="www.sapportals.com/portal/landscape" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xsi:schemaLocation="wpl_jco_destionations_v10.xsd">

<wpl:Destination name="SAP_R3_Cross">

<wpl:SYSTEM>SAP_R3_Cross</wpl:SYSTEM>

<wpl:LOGONMETHOD>SAPLOGONTICKET</wpl:LOGONMETHOD>

<wpl:TYPE>3</wpl:TYPE>

<wpl:MSHOST>host1.company.com<</wpl:MSHOST>

<wpl:GROUP>PUBLIC</wpl:GROUP>

<wpl:LANG>EN</wpl:LANG>

<wpl:R3NAME>ABC</wpl:R3NAME>

<wpl:CLIENT>123</wpl:CLIENT>

</wpl:Destination>

<wpl:Destination name="SAP_R3_Cross_DE">

<wpl:SYSTEM>SAP_R3_Cross</wpl:SYSTEM>

<wpl:LOGONMETHOD>SAPLOGONTICKET</wpl:LOGONMETHOD>

<wpl:TYPE>3</wpl:TYPE>

<wpl:MSHOST>host2.company.com</wpl:MSHOST>

<wpl:GROUP>PUBLIC</wpl:GROUP>

<wpl:LANG>DE</wpl:LANG>

<wpl:R3NAME>DEF</wpl:R3NAME>

<wpl:CLIENT>456</wpl:CLIENT>

</wpl:Destination>

<wpl:Destination name="SAP_CRM">

<wpl:SYSTEM>SAP_CRM</wpl:SYSTEM>

<wpl:LOGONMETHOD>SAPLOGONTICKET</wpl:LOGONMETHOD>

<wpl:TYPE>3</wpl:TYPE>

<wpl:MSHOST>host3.company.com</wpl:MSHOST>

<wpl:GROUP>PUBLIC</wpl:GROUP>

<wpl:LANG>EN</wpl:LANG>

<wpl:R3NAME>XYZ</wpl:R3NAME>

<wpl:CLIENT>100</wpl:CLIENT>

</wpl:Destination>

<wpl:Destination name="SAP_BW">

<wpl:SYSTEM>SAP_BW</wpl:SYSTEM>

<wpl:LOGONMETHOD>SAPLOGONTICKET</wpl:LOGONMETHOD>

<wpl:TYPE>3</wpl:TYPE>

<wpl:MSHOST>host4.company.com</wpl:MSHOST>

<wpl:GROUP>PUBLIC</wpl:GROUP>

<wpl:LANG>EN</wpl:LANG>

<wpl:R3NAME>NOP</wpl:R3NAME>

<wpl:CLIENT>200</wpl:CLIENT>

</wpl:Destination>

</wpl:Destinations>