Creating physical SAP application server transports

Before you can synchronize an external logical resource for an SAP application server, you must first create a physical connection from your HCL DevOps Test Integrations and APIs (Test Integrations and APIs) project to the SAP application server.

Procedure

  1. Open the Physical View of the Architecture School perspective of Test Integrations and APIs.
  2. On the toolbar of the Physical View, click SAP > SAP Application Server.

    The SAP Application Server window is displayed.

  3. Optional: In the Name field, enter a name for the connection to the SAP application server.
  4. Click Settings, if necessary, to configure the basic settings of the connection.

    The available configuration options are described in the following table:

    Table 1. SAP Application Server window: Config tab, Settings tab

    Host

    The hostname or IP address of the SAP application server.

    System Number

    The system number for the application server (for example, 00).

    User/Password

    The user name and password of the SAP client account to use for connecting to the server.

    Client Number

    The number that is assigned to the SAP client to which this user belongs (for example, 190).

    Java™ Stack (PI 7.31 or later)
    Select this check box if you want to publish or subscribe to IDocs for SAP Process Integration (PI) 7.31 or later systems. Only participate mode subscription is supported.
    Note: This check box is available only in Test Integrations and APIs 8.6.0 or later. Selecting this check box makes the IDoc Monitor Function field on the Advanced tab unavailable.

    Transaction Program Name

    Selecting the Java Stack (PI 7.31 or later) check box enables this field. A transaction program name is required for connecting to SAP PI 7.31 or later systems.

    The transaction program name is usually chosen by an administrator during the installation and configuration of an SAP system. For example, a transaction program name might be XI_IDOC_DEFAULT_JX3.

    Note: If you are unsure about the transaction program name that you must enter, you should consult the administrator of the SAP system that you are using.
    Note: This field is available only in Test Integrations and APIs 8.6.0 or later.
  5. Click Advanced to configure the advanced settings of the connection.

    The available configuration options are described in the following table:

    Table 2. SAP Application Server window: Config tab, Advanced tab

    Language

    Specifies the language that is used to connect to the server. The language can influence the list of available business application programing interfaces (BAPIs) that are retrieved when you refresh the business objects from the SAP business object repository (BOR).

    Server Program ID

    The ID of the remote function call (RFC) server program, registered with the SAP gateway, that is listening for incoming RFC call requests.

    Server Gateway Host

    The hostname of the SAP application server gateway.

    Server Gateway Service

    The service name of the SAP gateway.

    Unicode

    Enable this option if you are connecting to a Unicode SAP system, that is, the server is set up using the jco.server.unicode=1 property.
    Metadata Connection ID
    Note: This field is displayed only in versions of Test Integrations and APIs earlier than 8.6.0.

    Enter the Internal ID of the SAP transport in your Test Integrations and APIs project that will act as a metadata source. This can be found by opening the transport in Physical View and clicking the Documentation tab.
    Metadata Connection
    Note: This list is displayed only in Test Integrations and APIs 8.6.0 or later.

    Select the metadata source from a list of available SAP transports in your Test Integrations and APIs project.

    IDoc Monitor Function

    The qualified name of the IDoc Monitor function.

    Default value: ZRGT_GREENHAT_IDOC_SEND

    Note: If you are using Test Integrations and APIs 8.6.0 or later, selecting the Java Stack (PI 7.31 or later) check box on the Settings tab makes this field unavailable.
    Note: If you want to record or subscribe in watch mode to IDocs, you will need to install the IDoc Monitor RFC. Installation instructions are available in <installation directory>\tools\SAP.
  6. Click Test Transport to verify that the connection works.
  7. Click OK.

Results

The new physical connection is added to your Test Integrations and APIs project.