← Connecting to Redwood Finance Automation from SAP AS ABAPIntegrating into Solution Manager →

finance-related topic Connecting to Redwood Server from SAP AS ABAP

SAP Business Automation Enabler (BAE) connectors are RFC servers and allow ABAP stacks to connect to Redwood Server and interact with the scheduler. Redwood Server interfaces with the SAP Applications API, which allows you to schedule processes in Redwood Server, for example from SAPGui. At the time of this writing, the following SAP components have been optimized for SAP BAE connectors (SAP Applications API):

note

More SAP components are currently being optimized to make use of SAP BAE.

note

You need an ABAP stack of NetWeaver 7.00 SPS 16 or later to connect to SAP Business Automation Enabler.

You start the SAP Inbound Connector which, when started, will start an RFC server in Redwood Server. It will also create an RFC connection in the SAP instance you specified to Redwood Server. The SAP user must be Enabled.

Security

ABAP users are mapped to Redwood Server users and need the SAP_BC_BATCH_ADMIN_REDWOOD role in the SAP R3 subsystem and Business Automation User for the SAP System in Redwood Server.

SAP Solution Manager Setup

Please see SAP Note 1729766 - Solution Manager Setup for information on setting the Solution Manager connection.

SAP Gateway Hardening

Newer SAP releases have hardened SAP gateway configurations that prevent external programs from connecting to the central Redwood Server, by default. If the gw/acl_mode gateway parameter is set to 1, you must register Redwood Server as an external program in gw/reg_info. See SAP Note 1843782 and Defining the reginfo File ] for more information.

Example

In the following example, the gw/acl_mode is set to 1, so gw/reg_info points to a file with the contents below; in SM59 the name of your RFC connection is CPSECCMLS, 10.0.0.5 is the IP of the SAProuter client and 10.1.2.9 is the IP of the central Redwood Server.

TP=CPSECCMLS HOST=10.0.0.5,10.1.2.9

Security

By default, users can log in from all clients. You create BAE-only logins by granting these the scheduler-bae-only-user role which prevents users from accessing Redwood Server from other interfaces. Users with this role will not be allowed to log into the Redwood Server web interface, for example. Deactivated users can log in via the SAP Inbound (SAP BAE) interface, by default; you create the /configuration/sap/bae/DenyDisabledUsersregistry entry to deny deactivated users access.

User Mapping

By default, the SAP usernames are mapped to users with the same name in Redwood Server.

To map SAP users to specific Redwood Server users, you create a table named BAE_User_Mapping_Configuration_Definition; the table needs a VALUE column (case-sensitive).

The key is in the format <SAPUSERNAME>@<Partition>.<SAP Inbound Name>, the VALUE is the name of the Redwood Server user.

Example:

keyVALUE
JDOE@example.PR1jsmith
EMUSTERMANN@example.BW1jsmith
CBERTHIER@example.IS1jsmith

Prerequisites

  • XBP 3.0 is required in the SAP instance

a free slot is required in the ProcessServerService.SAP.BAEConnector.limit license key

Procedure

Enabling the RFC server in Redwood Server

  1. Navigate to "Environment > SAP Inbound".
  2. Choose _New _ from the context-menu.
  3. On the SAPBASE Connector, fill in the Name, RFC Connect String, and Time Zone fields.
  4. Choose the Check connection button, if the connection fails, check the RFC connect string.
  5. On the On the SAP BAE Configuration tab, choose Add.
  6. Fill the Client Number, the username, and Password fields.
  7. Choose Check Connection Settings, if the connection fails check the client/username/password combination.
  8. Choose Save & Close.
  9. Choose Start from the context-menu of the SAP BAE Connector.

Testing the RFC Destination to Redwood Server

  1. Open transaction SM59.
  2. Expand TCP/IP connections`.
  3. Choose the entry: CPS-nnnnnn@<Redwood Server>:<hostname>:<port>.
  4. Choose Display and, once the details of the RFC connection are displayed, choose Connection Test.

Example

Enabling the RFC server in Redwood Server and creating a connection to it from the PR1 SAP instance

  1. Navigate to "Environment > SAP Inbound".
  2. Choose _New _ from the context-menu.
  3. On the SAPBASE Connector tab, fill PR1 into the Name, ASHOST=pr1.example.com SYSNR=15 TRACE=0 into the RFC Connect String, and Paris into Time Zone fields.
  4. On the SAP BAE Configuration tab, choose Add.
  5. Fill 200 into the Client Number, jdoe into the username, and mybestkePtseCret into the Password field.
  6. Choose Save & Close.
  7. Choose Start from the context-menu of the SAP BAE Connector named PR1.

Checking the RFC connection

  1. Open transaction SM59.
  2. Expand TCP/IP connections.
  3. Choose the entry: CRONACLE-438320@REDWOODPLATFORM:PR3.EXAMPLE.COM:10180.
  4. Choose Display and, once the details of the RFC connection are displayed, choose Connection Test.

See Also

financeTopic

RFC server BAE Destination

← Connecting to Redwood Finance Automation from SAP AS ABAPIntegrating into Solution Manager →