Connecting to SAP Systems

SAP System definitions describe the characteristics of a single SAP System. It is possible to create more than one SAP System definition to connect to more than one SAP System. The SAP System definition is used to:

• Schedule/monitor SAP jobs via XBP and BW-SCH interfaces.
• Synchronize monitoring and alerting data with the SAP System via XAL and XMW interfaces.
• Synchronize CCMS events, requires XBP 3.0.

Prerequisites

• The JCo libraries must be available. For more information, see Installing the JCO Libraries.
• A user with sufficient privileges.
• The SAP R/3 connect string to the SAP System.
• Client/username and password of the RFC user for the desired interfaces.
• The SAP System must have a default client configured.
• A license for the SAP Job Server.

• An available shared Partition if the license key System.sharedPartitions is set to a numeric value.

Configuration

The configuration for each SAP System is managed through the Configure > Admin > Manage Connections > SAP Systems view. No standard SAP Systems are provided with RunMyJobs.

For each SAP System, you can configure the following:

• General settings such as name and RFC connect string.
• One or more client connections for the XBP interface.
• Zero or more job control rules.
• Multiple Event Synchronization rules (requires XBP 3.0).

For most interfaces, a username, password, and client number are required.

Note: If you do not set an XBP account, RunMyJobs will not be able to connect to the ABAP stack of the SAP instance.

Connect String

The connect string lets you specify a subset of the settings you can specify in other SAP client tools.

• ASHOST: The application server host to connect to.
• GROUP (optional): The name of the SAP server group. This is a group of application servers in a load balancing connection. The default value is PUBLIC.
• GWHOST (optional): The gateway host to use for the connection.
• MSHOST: The message server host of the SAP instance.
• MSSERV (optional): The port of the message server. This is required if the /etc/services file is not correctly configured for the R3NAME service name.
• R3NAME: The SID of the SAP instance.
• SYSNR: The system number of the SAP instance (usually the last two numbers of the port).
• TRACE: Lets you trace the RFC session. This should be left on 0 unless Redwood Support Services request you to change this value.
• TYPE (optional): The type of SAP system to connect to. Only R3 is supported.
• SNC: SNC requires you to set up the SAP Connector as well as the SAP System for SNC connections. For more information, see Secure Connections with SNC.
  • SNC_MODE: Activates SNC for the connection. Required for SNC. Example: SNC_MODE=1
  • SNC_PARTNERNAME: Specifies the DN or Kerberos name of the user. Required for SNC. Example: SNC_PARTNERNAME="p:CN=SERVERS,OU=SAPR3,DC=EXAMPLE,DC=COM"
  • SNC_SSO: Enables SSO (default). Example: SNC_SSO=1
  • SNC_QOP: Specifies how secure the connection is. 1=Auth only, 3=Integrity, 3=Privacy, 8=Default, 9=Maximum. Example: SNC_QOP=3
  • SNC_MYNAME: Specifies the DN or Kerberos name of the PSE to use. Example: SNC_MYNAME="p:CN=connector,OU=SNC,DC=EXAMPLE,DC=COM"
  • SNC_LIB: Specifies the location of the sapcrypto library. Example: SNC_LIB="C:/redwood/sapcrypto.dll"

Note: RunMyJobs will discard usernames and passwords.

You need several entries in your LOCAL /etc/services on the RunMyJobs host for the remote SAP system when specifying MSHOST connection strings with R3NAME=SAPSID. Alternatively, you can specify the port in MSSERV.

sapms<SAPSID> 36<instance ID>/tcp
sapms<SAPSID> 36<instance ID>/udp
sapdp<instance ID> 32<instance ID>/tcp
sapdp<instance ID> 32<instance ID>/udp
sapgw<instance ID> 33<instance ID>/tcp
sapgw<instance ID> 33<instance ID>/udp

The following two combinations are frequently used:

• Connection to a message server:

  MSHOST=<MS host> R3NAME=<SAPSID> GROUP=<group> [[MSSERV=36<instance_number>]

• Connection to a central or dialogue instance:

  ASHOST=<CI/DI-hostname> SYSNR=<Sys-Number> TRACE=0

Tip: For better performance, connect to the Message Server of the SAP instance, ideally specifying the port for MSSERV (36<instance_ID>) and the SAP SID in R3NAME.

When you create an SAP System definition, a Job Server and Queue of the same name are automatically created with the required services, along with a Queue Provider that links the Queue to the Job Server. When you delete an SAP System, the Job Server and Queue are automatically removed.

The Job Server and Queue share the same Folder when you create the SAP System. If you edit the SAP System later, you may want to change the Folder on the Queue and scheduler manually, because this allows you to easily export the SAP System via the Folder.

Note: When you edit an SAP System, the required services are added automatically to the Job Server, so there is no need to change services on a Job Server.

Note: The SAP configuration is read-only when the SAP Job Server starts up or is running. Any changes in settings require a restart of the corresponding Job Server.

Note: You can set a maximum number of RFC connections. For more information, see SAP Tuning.

Security

The privileges available in the Security tab are as follows.

Procedure

To create a connection for starting jobs from RunMyJobs only, without job interception, event handling, or Monitor synchronization:

1. Choose Configure > Admin > Manage Connections > SAP Systems in the Navigation bar.
2. Choose New SAP System from the context menu.
3. On the SAP System tab, enter a Name, Connect String, and a Time zone,.
4. On the XBP tab, fill in Client Number, Username, Password, and check Default Client.
5. Click Save & Close.

Notes

• To start ABAP programs from Redwood Server in an SAP System, use the Run Wizard.

• To trigger batch input sessions in an SAP System, see Controlling Batch Input Sessions.

• To monitor or intercept (take control) of jobs in an SAP System, see Intercepting SAP Jobs.

• To map Redwood Server events to events in an SAP System, see Interacting with SAP Events.

• To map specific job log entries to return codes, see Parsing Log Files to set Status of SAP Jobs.

• To import one or more CCMS monitors from an SAP System, see Integrating SAP Monitors.

• To send Redwood Server monitoring data to CCMS, see Sending Monitoring Data to SAP Systems.

• To control communication channels in an SAP System, see Controlling Communication Channels with Redwood Server via PI/XI.

• To monitor Redwood Server availability from the CEN, see Monitoring Redwood Server Availability.

• Note:

  When you create or edit an SAP System definition, you have to restart the corresponding Job Server.

• For every SAP System, at least one default client must exist.

• Every SAP System created in Redwood Server requires the settings mentioned in Connection Details for Connecting to the ABAP Stack, even if you only want to synchronize monitors.

Values

For information on the necessary fields of the tabs that you need to fill-in in order to be able to connect to the ABAP stack of an SAP instance, see Connection Details for Connecting to the ABAP Stack.

Example

Assume you need to create a connection to an SAP System running SAP BW 6.40. You have the following information:

• The SAP R/3 connect string (to a message server) is: MSHOST=169.254.10.12 R3NAME=PR1 GROUP=SPACE
• The Client is 200, username is example and password is example
• XBP version supported is XBP 2.0 (INITXBP2 has run).
• The default client of the SAP System is client 200.

To accomplish this:

1. Navigate to Configure > Admin > Manage Connections > SAP Systems.
2. Click New.
3. Enter the information below.
4. Navigate to Configure > Control > Job Servers.
5. From the context menu of the Job Server that belongs to the newly created SAP System connection, choose Start.