← InstallationConfiguration of the Refresh Process →

deprecated topic Preparations

The following steps need to be executed only once when connecting an SAP system to Redwood System Copy module.

JDBC Process Servers

JDBC process servers are only mandatory if your SAP database & Operating system combination requires it. (See See Supported SAP Databases & Operating System Combinations )

You will need a JDBC driver for your database; see the JDBC Drivers topic for more information.

The JDBC process server wizard supports DB2 versions 10.5 to 11.1, Oracle versions 11.2 to 18.3, PostgreSQL versions 9.3 to 11.1, as well as MS SQL Server versions 2012 to 2017.

If your application server does not have the needed JDBC drivers or the wizard does not support your database, refer to the Creating JDBC Process Servers Manually topic for the exact procedure for creating JDBC process servers.

Source SAP System

Configuration of the Source System is optional. If your refresh do not require any automated tasks on the Source System, this part of the configuration can be skipped. All Source System parameters can be configured manually.

The source SAP system needs to be connected to Redwood System Copy module via the following process servers:

  • SAP process server connected to the source SAP system via the RFC protocol (mandatory)
  • OS process server connected to the Redwood System Copy module platform agent running on the central instance host of the SAP system (mandatory)
  • JDBC process server connected to the source database via JDBC OR OS process server connected to the Redwood System Copy module platform agent running on the database host of the SAP system (See Supported SAP Databases & Operating System Combinations)

All process servers need to be served by the same Redwood System Copy module queue.

Follow these steps to create a connection to an SAP system:

  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, . The name should be the actual SID of the SAP instance.
  4. On the XBP tab, fill in Client Number , Username, Password, and check Default Client. Note that the user you specify here should be a technical user, not a dialog user, and should have all RFC authorizations as specified in the RFC authorizations topic.
  5. Choose Save & Close to save the changes and close the edit window.

Please refer to the Connecting to SAP Systems topic to learn more about connecting to SAP systems.

note

Make sure that application server load balancing is not enabled and Process Handling is set to Disabled – neither is needed for system copy.

SAP Process Server

The SAP process server and queue are automatically created when an SAP system is defined in Redwood Server Environment > SAP .

Follow these steps configure the <SID>_ProcessServer:

  1. Navigate to Environment > Process Servers and choose Edit from the context-menu of the <SID>_ProcessServer. Ensure the checkbox Start On Startup is checked.
  2. On the Services tab, add the service ScriptService and MailService.
  3. Choose Save and Close , the process server can now be started.

OS Process Server on the Central Instance

Choose New Process server from the context-menu of Environment > Process Servers, select the OS family (Unix/Linux or Windows) and follow the instructions of the process server wizard.

Redwood recommends calling this process server <SID>_CI_ProcessServer.

This process server needs to be configured to provide the resource SCP_SAP.

If the database resides on the same host as SAP, also assign SCP_DB.

The platform agent needs to be able to switch the user to become SAP administrator (i.e. <SID>adm).

OS Process Server on the Database Host (optional)

Install a platform agent on the DB host of the source SAP system and create a process server for it. Choose New Process server from the context-menu of Environment > Process Servers , select the OS family (Unix/Linux or Windows) and follow the instructions of the process server wizard.

Please refer to the Using the Wizard to Create Process Servers topic for the exact procedure.

Redwood recommends calling this process server <SID>_DB_ProcessServer.

Add the resource SAP_DB to this process server:

  • SCP_DB

The platform agent needs to be able to switch the user to become database administrator (i.e. ora<SID> for Oracle).

JDBC Process Server

Create a JDBC process server that connects to the Source database.

Add the resource SAP_DB to this process server:

  • SCP_DB

Choose New Process server from the context-menu of Environment > Process Servers , select JDBC and follow the instructions of the process server wizard. The wizard supports DB2 10.5 to 11.1, Oracle 11.2 to 18.3, PostgreSQL 9.3 to 11.1, as well as MS SQL Server 2012 to 2017.

Please refer to the Creating JDBC Process Servers Using the Wizard topic for the exact procedure.

Redwood recommends calling this process server <SID>_JDBC_ProcessServer.

Example

Source SAP System PRC

  • SAP process server PRC_ProcessServer

  • RedwoodScript process definition / ScriptService

  • PRC_Queue as queue

  • Process server with a platform agent on the central instance PRC_CI_ProcessServer

  • SCP_SAP resource

  • PRC_Queue as queue

  • Process server with a platform agent on the database host PRC_DB_ProcessServer

  • SCP_DB resource

  • PRC_Queue as queue

Target SAP System

The target SAP system needs to be connected to Redwood System Copy module via the following process servers:

  • SAP process server connected to the target SAP system via the RFC protocol (mandatory)
  • OS process server connected to the Redwood System Copy module platform agent running on the central instance host of the SAP system (mandatory)
  • JDBC process server connected to the source database via JDBC OR OS process server connected to the Redwood System Copy module platform agent running on the database host of the SAP system (See Supported SAP Databases & Operating System Combinations)

See Prerequisites for supported database types. If native is not supported, JDBC must be configured!

SAP Process Server

Please follow the same procedure as described above for the configuration of the SAP process server for the source SAP system, this time connecting to the target SAP system.

Define all clients that need to be considered during the system refresh in the XBP tab. The user here should be a technical user, ie. not a dialog user, and should have all RFC authorizations as specified in the RFC authorizations topic as well as the following:

  • B_ALE_LSYS to allow changing all logical systems
  • S_BTCH_NAM to allow setting the step user on batch jobs
  • S_RFC needs to allow calls to all function modules from the /REDWOOD/ namespace, i.e. the field RFC_NAME needs an additional pattern /REDWOOD/*
  • S_USER_GRP to allow managing users, eg. locking/unlocking
  • S_SDCC and S_SDCC_ADD with read authorizations on development activities and all authorizations on execution activities

The user also needs to be able to call the following transactions:

  • STMS_QA, if the QA list needs to be preserved and the transports need to be reimported back into the source system
  • SMOHQUEUE, if the daemon for the replication & realignment queues should be automatically started after the refresh

Both transactions are called as BDC input, so the RFC user does not need to be of type dialog.

After the SCP application is loaded and initialized, new documents appear in the tool which list the minimal set of authorizations for the RFC user.

Next add the service ScriptService and MailService to the process server.

OS Process Server on the Central Instance

Please follow the same procedure as described above for the configuration of the OS process server for the source SAP system. Choose New Process server from the context-menu of Environment > Process Servers , select the OS family (Unix/Linux or Windows) and follow the instructions of the process server wizard.

Redwood recommends calling this process server <SID>_CI_ProcessServer.

This process server needs to be configured to provide the resource SCP_SAP.

If the database resides on the same host as SAP, also assign SCP_DB.

The platform agent needs to be able to switch the user to become SAP administrator (i.e. <SID>adm).

OS Process Server on the Database Host (optional)

Please follow the same procedure as described above for the configuration of the OS process server for the source SAP system. Choose New Process server from the context-menu of Environment > Process Servers , select the OS family (Unix/Linux or Windows) and follow the instructions of the process server wizard.

Redwood recommends calling this process server <SID>_DB_ProcessServer.

This process server needs to be configured to provide the resource SCP_DB.

The platform agent needs to be able to switch the user to become database administrator (i.e. ora<SID> for Oracle).

If the database is on the same box as the central instance, then this process server is not needed and the resource SCP_DB needs to be added to the OS process server for the central instance. The platform agent on the OS process server for the central instance should also be able to switch the user to become database administrator (i.e. ora<SID>)

Queue

All these process servers need to be served by the same queue <SID>_Queue.

JDBC Process Server

Create a JDBC process server that connects to the Target database. Choose New Process server from the context-menu of Environment > Process Servers , select JDBC and follow the instructions of the process server wizard.

Please refer to the Creating JDBC Process Servers topic for the exact procedure.

Redwood recommends calling this process server <SID>_DB_ProcessServer.

Add the resource SAP_DB to this process server:

  • SCP_DB

Example

Target SAP System QRC

  • SAP process server QRC_ProcessServer
  • RedwoodScript process definition / ScriptService
  • QRC_Queue as queue
  • Process server with a platform agent on the central instance QRC_CI_ProcessServer
  • SCP_SAP resource
  • QRC_Queue as queue
  • Process server with a platform agent on the database host QRC_DB_ProcessServer
  • SCP_DB resource
  • QRC_Queue as queue

See Also

System Copy

sscpTopic

← InstallationConfiguration of the Refresh Process →