Establish a Connection via a Direct Connection to the Application Server

This task is performed by an Administrator.

Before performing this task, gather information about the target system instance, such as the application server name, system number and log in credentials.

The connection allows for the set up and configuration of the target system instances for Integrate and dspCompose™.

A connection can also be established through a Message Server. Refer to Establish a Connection via a Message Server or more information.

Refer to Establish a Connection to a Target System Overview for general information.

NOTE: The steps below are used when establishing an SAP connection. Information about connection types to other target systems is available on the Data Source Registry page’s Vertical View.

To establish a connection that directly connects to the Application Server:

  1. Select Configuration > Data Source Registry in the Navigation pane.

  2. Click Add.

    View the field descriptions for the Data Source Registry page.

    NOTE: Though they are not marked as required on the page, the following fields are required when adding an SAP Application Server data source.

  3. Enter the data source name in NAME field.

  4. Select SAP Application Server (%) from the APPLICATION DATA SOURCE TYPE list box.

  5. Click Save; the Vertical View displays.

  6. Enter a value in the SAP System ID field.

    NOTE: The SAP System ID is a three-character alpha-numeric identifier for the SAP system.

  7. Enter the name of the SAP server in the SAP APPLICATION SERVER field.

  8. Enter the SAP system number in the SAP SYSTEM NUMBER field.

    NOTE: The System Number is a two character integer that identifies the SAP instance. It is used as a parameter in the SAP GUI Logon client for the SAP connection. The SAP System Number displays in SAP on the SAP GUI Change Item screen.

  9. Enter a value in the SAPMAX POOL SIZEfield, if needed.

    NOTE: Max Pool Size is a value to specify how many RFC connections are left open for the current user, even if the connections are not being used actively. A pooled RFC connection is allocated much faster than a new connection. Therefore, increasing the pool size minimizes the time needed to get a new connection.
    However, if a connection is pooled, it is not available for other users. Typically, ABAP backend systems define an upper limit for the number of RFC connections. If this number has been fully allocated by pooled connections, then new users requesting a new connection may not succeed because the maximum number of connections allowed by the ABAP system has already been allocated.
    Typically, the maximum pool size is kept very low and may even be set to 0. If there are substantially fewer concurrent users than the number of concurrent RFC connections to an ABAP system, then increase the pool size to improve performance.
    The recommended setting for Max Pool Size is 10 in highly parallel environments.

  10. Click Save.

Continue with Add Default User Credentials to a Connection or Add User Credentials to a Connection for a Specific User.