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.

Context Menu

SAP Systems support the following context menu options.

Note: For generally applicable object context menu options, see Object Context Menu.

Configuration

The configuration for each SAP System is managed through the "Environment > SAP" view. No standard SAP Systems are provided with Redwood Server.

For each SAP System, you can configure the following:

• General settings like 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. If you do not set an XBP account, Redwood Server will not be able to connect to the ABAP stack of the SAP instance.

Connect String

The connect string allows you to specify a subset of the settings you can specify in other SAP client tools:

• ASHOST - The application server host to connect to.
• GROUP - (optional) 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, it is usually the last two numbers of the port.
• TRACE - Allows you to trace the RFC session, 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 setup the SAP connector as well as the SAP System for SNC connections. See Secure Connections with SNC for more information.
  • SNC_MODE - Activates SNC for the connection. Example SNC_MODE=1 (required for SNC).
  • SNC_PARTNERNAME - Specifies the DN or Kerberos name of the user. Example SNC_PARTNERNAME="p:CN=SERVERS,OU=SAPR3,DC=EXAMPLE,DC=COM" (required for SNC).
  • 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: Although it would be valid to specify a username and password as well as other settings, Redwood Server will discard them.

You need several entries in your LOCAL /etc/services on the Redwood Server host for the remote SAP system when specifying MSHOST connection strings with R3NAME=SAPSID. Alternatively, you 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, you should connect to the Message Server of the SAP instance; ideally specifying the port for MSSERV (36<instance_ID>) and SAP SID in R3NAME.

When you create an SAP System definition, a Process 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 Process Server. When you delete an SAP System, the Process Server and Queue are automatically removed. The Process Server and Queue will share the same Application when you create the SAP System, if you edit the SAP System later, you should change the Application on the Queue and scheduler manually, this allows you to easily export the SAP System via the Application. Export requires the Import/Export Module which in turn requires the Module.ImportExport license key.

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

The SAP configuration is read-only when the SAP Process Server starts up or is running, any changes in settings require a restart of the corresponding Process Server.

Note: By default, Mozilla Firefox browsers will offer to remember the password in the SAP System editor window. If you fill in two passwords on two tabs (XBP, XAL or XMW) in the SAP System editor, the Mozilla Firefox password manager assumes you want to change a password. You can either choose Cancel or disable Remember password for sites in the Mozilla Firefox Options/Preferences dialog, the latter is not recommended.

You may set a maximum setting for the number of RFC connections, please see the tuning for more information.

Finding SAP Systems

You can search for SAP Systems using filters and the Search SAP Systems box on the SAP Systems tab. This box is known as the IntelliSearch box and located under your username on the top right-hand side of the user interface. Filters allow you to specify a list of objects with static criteria. IntelliSearch allows you to specify complex queries in a simple way using prefixes. Prefixes are used to specify which property you are searching in and have short as well as long syntaxes. For example, if you want to display all SAP Systems with the term import in the comment, you would use the search criteria as follows:

c:import

You can search more than one property, as follows:

c:import n:Bi

Note: No spaces should be entered before or after the colon ( :).

See the Advanced Object Search for more information.

The following table illustrates the available prefixes for SAP Systems:

Deleting SAP Systems

You can only delete an SAP System when no other objects relate to them. For example, if there are processes that have run in the Queue of the SAP System, the SAP System cannot be deleted until all processes that ran in that Queue have been deleted. You can see all processes that relate to the Queue in Related Objects in the lower detail pane and on the show page of the Queue. Besides, You cannot delete an SAP System if the Process Server is still running, please stop the Process Server before you delete the SAP System.

The table in related objects contains three columns:

• Type - the type of object with a link to it
• Related Object - the name of the object with a link to it
• Used As - objects can sometimes be used in different roles

Security

The privileges available in the Security tab are as follows.

For more information, see Security Tab.

Prerequisites

• The JCo libraries must be available, see the Installing the JCO Libraries topic for more information.
• A user with sufficient privileges in the central Redwood Server http://<server>:<port>/redwood.
• The SAP R/3 connect string to the SAP System.
• Client / username and password of the RFC user of the desired interfaces.
• XBP versions supported in the SAP System (XBP 0.1, 1.0, 2.0, 3.0) (for parent child dependencies the report INITXBP2 must be run).
• The SAP System must have a default client configured, please refer to the SAP documentation.
• A license for the additional SAP Process Server.

An available shared Partition if the license keySystem.sharedPartitions is set to a numeric value.

Procedure

To create a connection for starting jobs from Redwood Server only, without job interception, event handling, or Monitor synchronization, perform as follows:

1. Choose "Environment > SAP" 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 to save the changes and close the edit window.

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

To trigger batch input sessions in an SAP System, refer to the following procedure:

Controlling Batch Input Sessions

To monitor or intercept (take control) of jobs in an SAP System, refer to the following procedure:

Intercepting SAP Jobs

To map Redwood Server events to events in an SAP System, refer to the following procedure:

Interacting with SAP Events

To map specific job log entries to return codes, refer to the following procedure:

Parsing Log Files to set Status of SAP Jobs

To import one or more CCMS monitors from an SAP System, refer to the following procedure:

Integrating SAP Monitors

To send Redwood Server monitoring data to CCMS, refer to the following procedure:

Sending Monitoring Data to SAP Systems

To control communication channels in an SAP System, refer to the following procedure:

Controlling Communication Channels with Redwood Server via PI/XI

To monitor Redwood Server availability from the CEN refer to this procedure:

Monitoring Redwood Server Availability

Note: When you create or edit an SAP System definition, you have to restart the corresponding Process 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 the Connection Details for Connecting to the ABAP Stack section of the documentation.

Example

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.

1. Choose "Environment > SAP" in the Navigation bar.
2. Choose the New SAP System button and enter the information below (listed per tab).
3. Choose "Environment > Process Servers".
4. From the context menu of the Process Server that belongs to the newly created SAP System connection, choose Start.

See Also

SAP Systems