Configuring an SAP System for Process Automation
To configure the central Redwood Server, you first need to have an account with Administrative privileges.
When you connect to Redwood Server to monitor, intercept and submit jobs as well as other tasks, Redwood Server connects to the different SAP Systems with an RFC user to perform the requested tasks. So each SAP System that is to be managed by Redwood Server must have a user defined with sufficient authorizations. Depending on the required functionality, different SAP authorizations need to be granted to the RFC user. See the Reference section Required Authorizations of the Remote System User and the Assigning SAP Authorizations to the RFC User procedure for more information.
note
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.
Prerequisites
SAP process servers require at least one of the following keys
- ProcessServerService.External.limit - the total number of external process servers (Platform agents, distinct web service endpoints, and SAP connectors)
- ProcessServerService.SAP.limit - the total number of SAP process servers
note
Both license keys must be honored if present; their presence depends on your contract. The most restrictive applies.
Connecting to Older SAP Systems
When you connect to SAP NetWeaver Systems version 6.40 or lower, Redwood recommends you install transport files to enable advanced features not available in XBP version 2 or earlier.
Different interfaces are used to interact with the various SAP Systems in your landscape. XBP is one of them, to take full advantage of your SAP System, it is advised to enable XBP 2.0 or 3.0 available as of SAP Basis 4.6B (XBP 2.0) with the latest Support Package from SAP.
Upgrading Older SAP Systems
When you upgrade SAP systems that do not differentiate between uppercase and lower case passwords, like SAP NetWeaver version 6.40 or lower, your users can potentially get locked. This is due to the SAP connector detecting if passwords are case-sensitive or not. The SAP connector will create SAP_UppercaseRfcPassword to true if the passwords are case-insensitive. When you upgrade and do not set the process server parameter to false or you do and do not apply the new password policy to all passwords of users the SAP connector uses, users might get locked.