Configuration Details on Interacting with SAP Events
The following configuration data needs to be used to interact with SAP events via the XBP 3.0 interface.
XBP event control rules control which events are raised in Redwood Server when an event is raised in SAP.
Setting up connection information
| Tab | Field | Description |
|---|---|---|
| SAP System | Name | The name for the SAP System. This name is also used to create the corresponding SAP process server and queue. For instance, if the name of the SAP System definition is TST, then the created process server gets the name TST_ProcessServer and the queue is named TST_Queue. |
| SAP System | Connect String | RFC connection definition used to connect to the SAP System via SAP Java Connector (JCo). |
| SAP System | Job Handling Enabled | Is job handling enabled for this SAP System, if enabled the intercepted and monitored jobs are shown in the processes monitor. |
| SAP System | Default Time Zone | This field is used for detecting the time zone of the SAP instance. The default time zone for processes is the time zone of the original request time. |
| SAP System | Application | The name of the application used to group this object. |
| SAP System | Description | The description of the SAP System. |
| Documentation | Documentation | A comment about the SAP System. |
Time zone data
The time zone of the SAP system is detected via the offset. If the current offset matches the current offset of the time zone specified in Default Time Zone, then Redwood Server uses that time zone when interpreting dates from SAP instances (used for Remote Start Time, for example). If the two do not match, Redwood Server uses the current offset of the SAP instance as the time zone, like GMT+,<offset>.
Setting up client/username combinations
At least one is required, one client/username combination must be configured as the default.
| Tab | Field | Description |
|---|---|---|
| XBP | Client number | SAP client number as a three digit number. |
| XBP | Username | The RFC user name. This user needs certain authorizations in the SAP System, as described below in the Reference section under Required Authorizations of the Remote System User. Of course it is possible to use here the same user as for XAL and XMW. In this case the user needs all authorizations required by these interfaces. |
| XBP | Password | Password of the RFC user. |
| XBP | Audit level | The XBP audit level (the audit log is visible via SAP transaction RZ15) of the interface, and is an integer with the value range of 0-3, with higher numbers denoting more verbose audit level; only to be used when Redwood Support instructs you to do so. |
| XBP | SAP language | The language that the SAP process server uses to connect to the SAP System. This is also the default step language for ABAP jobs, if the corresponding parameter in the process definition is left empty. |
| XBP | Description | the description to use for this rule. If the description is not set, the rules are named <Client number>/<Username>. |
| XBP | Default client | Specify if this client is the default client. The default client is used by the SAP process server for the standard connection to the SAP System to start/monitor/intercept process definition. Please make sure that only one client is marked as default. If the default client check box is selected in multiple XBP interfaces, the one with the lowest client number is used by default when required. Yet to avoid confusion it is better to ensure that only one client is designated as default client. |
| XBP | Max. RFC connections | Specifies how many RFC connections the SAP process server opens for this client. If omitted, the number of connections are not limited. The SAP process server uses internally a connection pool, so the open connections are reused, and also closed if they are idle for a certain amount of time. |
| XBP | Interface version | The version of the XBP interface that the SAP process server should use. If this field is left empty, the highest available interface version is used. |
note
You can force the use of a specific XBP release, if it is available in the SAP system, by specifying the SynchronizationMode registry entry. This is especially handy on older NetWeaver 7.0 systems, which do not correctly report the available XBP version.
Mapping Redwood Server Events to SAP Events
| Tab | Field | Description |
|---|---|---|
| XBP Event Control Rules | SAP Event ID | The SAP Event ID |
| XBP Event Control Rules | SAP Event Parameter | The parameter of the SAP event |
| XBP Event Control Rules | Event to Raise | The event to raise in Redwood Server |
| XBP Event Control Rules | Description | The description of the rule. If this is not set the description is <SAP Event ID>/<SAP Event Parameter>/<Event to Raise> |