R3 Connection Objects

SAP Agents require login data to connect to the various SAP areas. To be able to create SAP Jobs and execute them on the SAP Client without leaving the Automation Engine, developers and object designers must assign them Connection (CONN) objects. They provide the connection data to the SAP application server and the SAP Login parameters (SAP Client, user and password). This allows the Agent to login into the SAP system at startup. As an administrator user, 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 CPIC user. All other Connection objects are optional. Afterward, you assign the Connection objects to the SAP Agent.

Depending on the SAP area you want to connect to, you must define either a Remote Function Call or an Internet connection type:

Remote Function Call

Select this type to connect to SAP ABAP Basis.

Connection Section

In Connection Parameter 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.
Login Parameter
- 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.

Interfaces Section

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.
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.
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.
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.

Advanced Settings Section

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).
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).

Internet

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

Specify the Internet Connection Parameter:

Connection URL

URL to Java Scheduler, see Executing Jobs in Java Stack (JXBP)

http://Server name:Port/scheduler~runtime~gate~web/JXBPWebService

URL to Process Integration, see Best Practices: Monitoring SAP PI Communication Channels.

http://Server name:Port

URL to System Landscape Directory, see Registering to System Landscape Directory (SLD)

http://Server name:Port/sld/ds

The port is generally 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.

The HTTPS communications protocol is not supported for CONN objects
Users

Name of the user
Password

Password of the user
Alternative Login

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