Defining R3 Connection Objects

{"URL":["/*.*/awa/pa_view_CONN_R3"],"heroDescriptionIdentifier":"ice_connection_r3","customCards":[{"id":"ice_r3conn_remotefunction","title":"Defining R3 Remote Function Call Connections","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_Connection_R3.htm","languages":["en-us"]},{"id":"ice_internet_r3conn","title":"Defining R3 Internet Connections","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_Connection_R3.htm","languages":["en-us"]},{"id":"ice_working_with_objects","title":"Working with Objects","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_WorkingWithOverview.htm","languages":["en-us"]},{"id":"ice_AWIs_CommonFunctions","title":"Common Functions","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/_Common/CommonFunctions/CF_OverviewOfChapter.htm","languages":["en-us"]},{"id":"ice_UnderstandingPA","title":"Understanding the Process Assembly Perspective","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/ProcessAssembly.htm","languages":["en-us"]},{"id":"ice_Overview_AWI","title":"Understanding the User Interface","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/_Common/GettingStarted/GS_OverviewAWI.htm","languages":["en-us"]}]}

Connection objects contain the parameters that make the communication between Automic Automation and external systems possible. As an administrator, you create the Connection objects that developers and object designers use to configure executable objects.

R3 Connection objects contain the connection data to the SAP application server and the SAP Login parameters (SAP Client, user and password). You create a Connection object per SAP area you want to connect to. At least one Connection object for the SAP basis is required in which you specify the SAP system user. All other Connection objects are optional.

You can then assign the R3 Connection object to the SAP Agent. If you do so, all SAP objects are executed using this Agent, see Configuring the Agent Properties. Alternatively, you can assign the R3 Connection object to your SAP Job object template. You can also leave both options empty so that developers and object designers actively assign the R3 Connection object when defining SAP Jobs, see Defining the SAP Connection

If you specify a Connection object at Agent level, it is used by default in all SAP Jobs to which this Agent is assigned. However, if you specify a Connection object at Job level in the SAP Job definition, the Job configuration has priority over the Agent configuration and the Connection object assigned to the Job is used. The table below indicates what happens depending on where the Connection object is assigned:

Connection object assigned to Agent Connection object assigned to Job Result
YES NO The Connection object assigned to the Agent is used by default.
YES YES The Connection object assigned to the Job is used.
NO YES The Connection object assigned to the Job is used.
NO NO The Job fails because it cannot connect to the target system.

Depending on the SAP area you want to connect to, you must define either a Remote function Call (to connect to SAP ABAP Basis) or an Internet connection type (to connect to SAP NetWeaver Application Server Java, Process Integration and System Landscape Directory).

Defining R3 Connections of Type "Remote Function Call"

Select this Connection Type to connect to SAP ABAP Basis.

  1. In the Connection section define the following:

    1. In Connection Parameter: RFC Connection Type, define whether the connection should be established to a specific application server or via a balanced or group selection. The options are:

      Custom Application Server

      • Application Server: The host name of the application server.

      • Instance Number: The number of the SAP system, such as 00.

      • System ID: The system ID of the SAP system, such as T40.

      • SAProuter String: The name of the SAP router.

      Group/Server Selection

      • System ID: ID of the SAP system, such as T40.

      • Message Server: The host name of the message server.

      • SAProuter String: The host name of the SAP router.

      • Group/Server: The name of the login group.

    2. In Login Parameter, define the relevant parameters:

      • SAP Client Number: The number of the SAP client.

      • SAP User: The name of the SAP user.

      • Password: The password of the SAP user.

      • Language: SAP-specific short name for the login language. For more information, see SAP Language Settings.

  2. In the Interfaces section, define the relevant parameters:

    1. Background Processing - Job Scheduling (BC-XBP)

      • Use Automation Engine Interface

        Activate this option if the SAP Agent should use the default interface plus the AE interface.

      • Combine Job Steps

        This option can be used to combine the script elements R3_ACTIVATE_REPORT, R3_ACTIVATE_EXT_PROGRAM and R3_ACTIVATE_EXT_COMMAND in SAP in one job if they are used in immediate succession.

      • Interface Version

        The interface version of the XBP interface.

        Selecting Default here means that the SAP Agent queries the SAP system about the interface version in use.

        For more information about the XBP interface, see the SAP documentation on the SAP Help Portal http://help.sap.com.

      • Audit Level

        XMI log monitoring level.

      • Block Size for Spool Lists

        The SAP spool is transferred block by block.
        Tip: Use the default value because it will also be applied if this field does not include a value or if value 0 has been specified.

      • Confirm Event History

        When you select this checkbox, the status of the events is used instead of timestamps. Events that have been read are then confirmed so that the system only has to process events that are not confirmed yet.

    2. Business Warehouse - Job Scheduling (BW-SCH)

      • Parallel Execution: Allow parallel execution of the same chain

        If you activate this checkbox the system allows a process chain to run multiple times in parallel.

        The parallel execution of a process chain can result in a Dialog service process in the BW Application Server being constantly occupied.

      • Extended InfoPackage Monitoring

        Status monitoring type of the InfoPackage. The options are:

        • No extended monitoring

          No modification, the current status monitoring continues

        • Monitoring until MAXRUNTIME

          It the technical status Red occurs, status monitoring continues until the point in time specified in the MAXRUNTIME= parameter of the BW_ACTIVATE_INFOPACKAGE script element or until the status changes.

        • Repeating status check

          It the technical status Red occurs, status monitoring continues n times. If the status changes, monitoring continues. If the status does not change, the job ends or aborts depending on the specification made in the ERROR= parameter.

      • Repeating Data Request Checks

        This parameter can be used to define how often BAPI_ISREQUEST_GETSTATUS should be called if it returns an error message.

        Default value: "0"

        This is a workaround for an SAP error. More details are available in the SAP note 672353.

      • Ipak Change Method

        This option causes various technical calls of BAPI_IPAK_CHANGE.

        • "0" - No modification, present procedure continues.

        • "1" - BAPI_IPAK_CHANGE is called without using the SELECTIONS parameter.

        • "2" - BAPI_IPAK_CHANGE is called with the SELECTIONS parameter being empty.

        • "3" - BAPI_IPAK_CHANGE is no longer called. AE expects that the start type "Immediately" has been specified in the Job object.

        • "4" - BAPI_IPAK_CHANGE is called using the following parameters:

          • INFOPACKAGE: The technical name of the InfoPackage (mandatory).

          • SCHEDULING_PARAMS: Previously read with BAPI_IPAK_GETDETAILS, STARTTYP=I

          • INFO_CUBES: Only if BAPI_IPAK_GETDETAILS also supplies Info Cubes.

          • RETURN: The export parameters, return information.

    3. SAP NetWeaver AS - External Interface for Alert Management (BC-XAL)

      • Interface Version

        The version of the XAL interface.

        Default means that the SAP Agent queries the SAP system about the interface version in use.

      • System Log: Enable system log on failure

        Activate this option if the SLOG report should be generated and displayed in the Reports window. It contains current SAP system log messages if an SAP job has been canceled.

        For more information, see Special Reports for SAP Jobs.

        • Monitor Set

          The name of the monitor set. For example SAP CCMS Monitor Templates.

        • Monitor

          The name of the monitor. For example Syslog.

        • MTS Name

          The short name of the monitor. For example, Background.

    4. Scheduling Jobs with an External Scheduler (SMSE)

      Activate the SMSE Interface checkbox to display the required SAP and Automation Engine login data input fields.

      • AE Client - Automation Engine client to which you want to connect.

      • AE User - Login name of the Automation Engine user.

      • AE Department - Department as specified in the user login data.

      • Password - Password as specified in the user login data.

      • RFC Gateway Host - The host name of the SAP gateway.

      • RFC Gateway Service - The service of the SAP gateway.

      • RFC Program ID - The program ID.

      • RFC Destination - The name of the RFC destination.

  3. In the Advanced Settings section, define the following:

    1. Connection Settings

      • Alternative Login

        The Login object from which the login data (client, user, password) is retrieved.

      • Max. Concurrent Connections

        The agent dynamically administers the connections to the SAP system. If one connection is busy, another one opens automatically.

        This parameter determines the maximum number of simultaneous RFC connections that the SAP can open per login combination (SAP client, SAP user, SAP login language).
        Default value: unlimited

        Tip: Specify an unlimited setting; the default is no value being specified. Instead, match the agent's resource setting (to be configured in the UC_HOSTCHAR_DEFAULT - Host Characteristics variable (key: WORKLOAD_MAX_JOB) with the number of SAP batch processes. The advantage is that jobs do not become active on the agent side if the resource limit has been reached.

        Note: To use an unlimited number of RFC connections, you need to configure this in SAP (see SAP note 314530).

    2. Secure Network Connection /(SNC)

      Activate the Enable SNC checkbox to enable the SNC mode:

      • Path to SNC Service Library

        The name of the local SNC library.

      • Level of Security

        The SNC service quality.

      • SNC Partner Name

        The name of the SNC partner system.

      • Own SNC Name

        The own SNC name (optional).

      • Enable SSO

        Activate the checkbox for the SSO connection.

Defining R3 Connections of Type "Internet"

r3 connection object,sap connection,sap agent

Select this type to connect to SAP NetWeaver Application Server Java, Process Integration and System Landscape Directory.

Define the relevant Internet Connection Parameter:

  1. In Connection URL you can specify the following:

    Notes:

    • Usually, the port is 50000. For SAP, the port is 50000 plus 100 times the instance number. For example, if the instance is 00 the port number is 50000. AS Java Ports from the SAP documentation contains more details.

    • Connection object support only HTTP communication protocol, not HTTPS.

  2. In Users enter the name of the user.

  3. In Password enter the password of the user

  4. In Alternative Login select the Login (LOGIN) object from which the login data (user, password, etc.) is retrieved.

See also: