Integrating Redwood Server Promotion into SAP CTS+

You integrate Redwood Server into your CTS+ (BC-CTS) landscape by downloading the CTS+ tools from Configuration > Software, installing the shell scripts into the <sapmnt>/<SAPSID>/global/CtsScripts directory (do not overwrite existing SAP shell scripts) and importing the CTS+ Export Pusher process definition via the CAR file into Redwood Server. You now configure CTS+ for use with Redwood Server. Note that <sapmnt> defaults to /sapmnt on UNIX and <drive>:/sapmnt on Windows (example: D:\\sapmnt)).

You use the CTS+ Export Pusher process definition without modifying it; if you need to modify it, you duplicate it and modify the copy. Your modifications will be lost if you inadvertently re-import the CAR file. See Pusher Process Definition for SAP CTS+ Integration for more information on the parameters.

Change and Transport System Plus

The Change and Transport System Plus (CTS+) is an extension of the Change and Transport System (CTS). It allows for non-ABAP objects to be collected and transported to other destination systems. The Redwood Server promotion module integrates into your CTS landscape and allows you to control promoting Redwood Server objects from within CTS.

Configuring Redwood Server to Adhere to your Transport Strategy

You configure the behavior of Redwood Server with regards to the CTS transport strategy by setting parameters on the CTS+ Export Pusher process or process definition. You duplicate the process definition when you want change the default values of parameters; see Pusher Process Definition for SAP CTS+ Integration for more information on the parameters. By default, when you promote an object via your Transport Domain Controller the submit wizard is displayed where you can override defaults; you set all mandatory parameters and the Default Queue on the process definition to suppress the submit wizard.

CTS supports the following transport strategies for requests ( WBO_GET_REQ_STRATEGY); for each strategy the recommended parameter values on the CTS+ Pusher process are as follows:

• Tagged - Requires a pre-selected request; if you use this strategy, you set the Request number parameter to either the request number or default, if the request in question is the user's default, in the CTS+ Export Pusher process.
• Smart - The system either uses the pre-selected request or, if there is none, automatically creates a transport request and selects it. If you use this strategy, you do not fill the Request number parameter in the CTS+ Export Pusher process; a new request will always be created.
• Create - The system automatically creates a transport request and selects it as the standard request, ignoring any pre-selected request. If you use this strategy, you do not fill the Request number parameter in the CTS+ Export Pusher process; a new request will always be created.

CTS supports the following transport strategies for releasing requests ( WBO_REL_REQ_STRATEGY); for each strategy, the recommended parameter values on the CTS+ Pusher process are as follows:

• Auto - The system automatically releases the transport request as soon as an object is added to the request. This is the default behavior of Redwood Server; it will release the request in question automatically.
• Manual - You must release the transport request manually or set the value of the parameter to Auto. If you use this strategy, set the Release request parameter of the CTS+ Export Pusher process to No.

Contents of the CTS+ CAR file

Object Type	Name
Process Definition	CTSPlus_Export_Pusher

CTSPlus_Export_Pusher

Export Pusher for CTS+ Remote Systems.

Parameters

Tab	Name	Description	Documentation	Default Expression	Values
Parameters	SAP_SYSTEMS	SAP System
Parameters	CLIENT	Client
Parameters	TARGET_SID	SID of the transport source system
Parameters	REQUEST	Request number			<request_number>, default
Parameters	DESCRIPTION	Description for the new request
Parameters	RELEASE_REQUEST	Release request		Yes	Yes, No
Parameters	CTS_URL	CTS URL
Parameters	CTS_MESSAGE	Message
Parameters	REQUEST_URL	Request URL
Parameters	Address	Address	The address associated with the source process server check, or the address of the Remote System.
Parameters	Data	Data	Data associated with the current process or process server check, or location of the CAR file.
Parameters	Message	Message	The message associated with the source process server check.
Parameters	SourceObject	Source Object	Name of the source that initiated this process.
Parameters	SourceObjectType	Source Object Type	Object type of the source that initiated this process.
Parameters	SourceObjectUniqueId	Source Object UniqueId	UniqueId of the source that initiated this process.
Parameters	exportRuleSetBusinessKey	Export Rule Set Business Key	BusinessKey of the export rule set that contains all the objects that must be included in the generated CAR file.
Parameters	remoteSystemBusinessKey	Remote System Business Key	BusinessKey of the remote system that this promote should go to. The same information is available in the Source* parameters, but this is for backwards compatibility.
Parameters	sendToRemoteSystem	Send to Remote System	Should only the CAR file be generated (false), or must it also be send to the remote system (true).
Parameters	SAP_USER_NAME	Request owner
Parameters	CTS_PROJECT	CTS+ Request Project
Parameters	TMWFLOW	Request Attribute Value
Parameters	promotionComment	Comment for this promotion	Additional information as to why this promote is being done. E.g. an issue number, link to documentation, etc.

Process Flow

1. Download the Redwood Server CTS+ tools.
2. Import the CAR file into Redwood Server.
3. Copy the shell scripts to your SAP system.
4. Create the Application Type SAP_CPS in CTS.
5. Create a Non-ABAP System in CTS.
6. Create a remote system in the Redwood Server Promotion module.
7. Test the setup.

Prerequisites

• Domain Controller: SAP Solution Manager 7.01 SP25 at least, SAP Solution Manager 7.1, SAP NetWeaver 7.3 EHP1, or SAP NetWeaver 7.4.
  • CTS plug-in installed on the CTS system (taken from SL Toolset 1.0 SP09 at least – always use the newest available CTS plug-in), see also SAP Note 1665940 for installing the SAP CTS Plug-In of SL Toolset. Note: Starting with SAP Solution Manager 7.1 SP5, CTS_PLUG is automatically part of your SAP Solution Manager.
• XBP RFC user needs SAP_CTS_PLUS role
• Redwood Server user with sufficient privileges to create and export objects in the source Redwood Server system
• Redwood Server user with sufficient privileges to create objects in the target Redwood Server system (for CTS+)

Procedure

Setup an XBP connection to the Transport Domain Controller

note

Only follow these steps if you do not already have a connection to the Transport Domain Controller.

1. In Redwood Server navigate to "Environment > SAP".
2. Choose New SAP System from the context-menu.
3. On the SAP System tab, enter a Name, the Connect String to your Transport Domain Controller, and a Time zone.
4. On the XBP tab, fill in Client Number, Username, Password, and check Default Client.
5. Choose Save & Close to save the changes and close the edit window.

Download the Redwood Server CTS+ Tools

1. In Redwood Server, navigate to Configuration > Software.
2. Download the Redwood Tools for CTS+ integration.
3. Unpack the contents into a temporary directory.

Import the CAR File into Redwood Server

1. In Redwood Server, navigate to Promotion > Imports, choose Submit Import Process.
2. Choose Browse and navigate to the directory where you previously unpacked the Redwood Tools for CTS+ integration.
3. Select the CTSPlus_Export_Pusher.car file.
4. Choose Submit.

Copy the Shell Scripts and JAR file to your SAP system

1. Open a command prompt on the Transport Domain Controller host.
2. Copy the api-tool.jar file to <sapmnt>/<SAPSID>/global/CtsScripts and ensure the file is executable by the <SAPSID>adm user.
3. Inspect your <sapmnt>/<SAPSID>/global/CtsScripts directory to see if you already have a deploy.sh or deploy.bat file and proceed as follows:
4. If the Transport Domain Controller is on UNIX:
5. If you have a deploy.sh file.
6. Integrate the code between "# === SAP_CPS extension === start" and "# === SAP_CPS extension === stop" from the provided deploy.sh file into your deploy.sh, copy the deploy_SAP_CPS.sh file to the same directory.
7. Ensure the shell scripts are executable by the <SAPSID>adm user.
8. If you do not have a deploy.sh file in <sapmnt>/<SAPSID>/global/CtsScripts.
9. Copy both files into your <sapmnt>/<SAPSID>/global/CtsScripts directory.
10. Ensure the shell scripts are executable by the <SAPSID>adm user.
11. If the Transport Domain Controller is on Windows.
12. If you have a deploy.bat file.
13. Integrate the code between "REM === SAP_CPS extension === start" and "REM === SAP_CPS extension === stop" from the provided deploy.bat file into your deploy.bat, copy the deploy_SAP_CPS.bat file to the same directory.
14. Ensure the shell scripts are executable by the <SAPSID>adm user.
15. If you do not have a deploy.bat file in <sapmnt>/<SAPSID>/global/CtsScripts.
16. Copy both files into your <sapmnt>/<SAPSID>/global/CtsScripts directory.
17. Ensure the shell scripts are executable by the <SAPSID>adm user.

note

If the directory <sapmnt>/<SAPSID>/global/CtsScripts does not exist, you can create it; note that you must know the location of <sapmnt>; The CtsScript directory must be executable by the <SAPSID>adm user of the CTS host system. Restrict access to the CtsScripts folder to users who are performing setup and deployment.

Create the Application Type SAP CPS in CTS

1. In SAPGui connect to the Transport Domain Controller, enter the transaction code STMS.
2. In the Transport Management System, navigate to Overview > Systems (Shift+F6).
3. Choose Extras > Application Types > Configure.
4. Choose Edit > New Entries (F5).
5. Fill in the details from the following table:

Field	Value
Application Identifier	SAP_CPS
Application Description	SAP CPS: Transport of automation objects
Application Support Details	Contact your SAP Basis support team (OSS via component XX_PART-REDWOOD-CPS)

Create a Non-ABAP Target System in CTS

1. In SAPGui connect to the Transport Domain Controller, enter the transaction code STMS.
2. In the Transport Management System, choose Overview > Systems (Shift F6).
3. Choose SAP System > Create > Non-ABAP System.
4. Create the non-ABAP system with an appropriate system ID and a description.
5. Select the Transport Domain Controller as the communication system.
6. Under Target System Settings, select Activate Deployment Service, and select Method Other.
7. Save your settings and confirm that you want to distribute the CTS configuration.
8. In the next dialog, choose Edit > New Entries (F5).
9. Select the SAP_CPS application type.
10. Fill in the following details:

Field	Value
Deploy method	Script-based Deployment
Deploy URI	<cps_host> <cps_port> [-targetpartition <partition>] [<import_rule_set>]
User	<secret_file>
Password

Example:

Field	Value
Deploy method	Script-based Deployment
Deploy URI	pr1.example.com 53000 MSLN_ImportRuleSetProduction
User	secret.conn
Password

note

In the above example, the secret file secret.conn as generated with jsecret is used instead of the user/password combination.

Create a Non-ABAP Source System in CTS

1. In SAPGui connect to the SAP Solution Manager, enter the transaction code STMS.
2. In the Transport Management System, choose Overview > Systems (Shift F6).
3. Choose SAP System > Create > Non-ABAP System.
4. Create the non-ABAP system with an appropriate system ID and a description.
5. Select the SAP Solution Manager as the communication system.
6. Under Source System Settings, select Activate Transport Organizer, and choose appropriate client; the client should be the same as the one specified on the SAP System in Redwood Server. Navigate to _ "Environment > SAP" _, select Edit from the SAP System that is connected to the Transport Domain Controller; the client is specified on the XBP tab.
7. Save your settings and confirm that you want to distribute the TMS configuration.

Create a Destination Type Remote System in the Redwood Server Promotion Module

1. Navigate to Promotion > Remote Systems.
2. Choose New Remote System from the context-menu.
3. Fill in a Name, select a Type of Destination or Both.
4. Enter the URL to your local Redwood Server system into the URL field using the syntax: http[s]://localhost:<port>/<context> such as http://localhost:53000/redwood.
5. Enter valid credentials for the remote server.
6. Select CTSPlus_Export_Pusher in the Pusher Process Definition Field.
7. Choose Save & Close.

Creating Transport Routes

The configuration of your transport routes must be performed and heavily depends on your CTS landscape. See Configuring Transport Routes for more information.

Test the Setup

1. Ensure the process server for the Transport Domain Controller SAP system is running.
2. Navigate to "Definitions > Processes".
3. Create a process definition of type RedwoodScript with the following Source: {} and a name of RS_Test_CTS_Integration.
4. Choose Save & Close.
5. Select the context-menu of process definition RS_Test_CTS_Integration and select Promote > Promote to System.
6. Select the previously created remote system that has the CTSPlus_Export_Pusher pusher process definition set.
7. Fill in the parameters:
8. SAP System - select the transport domain controller SAP System.
9. SID of the transport source system - the SID of the current (source) SAP System.
10. If the user has to use a default transport request as defined in CTS, specify default in the Request number parameter. Alternatively, a request number may be specified. If you leave the field empty, a new request will be generated.
11. The other parameters are optional.
12. Choose Next and specify the queue of the SAP System connected to the transport domain controller.
13. Navigate to "Monitoring > Processes" and locate the CTSPlus_Export_Pusher process.
14. In the lower details pane, inspect the CTS URL parameter; navigate to that URL.
15. You might have to enable the Transport Organizer Web UI for your client, refer to the See Also section below.
16. Locate the transport request, it was generated by the RFC user, and release it if needed (depending on the Redwood Server and CTS transport strategy, see Choosing a Transport Strategy for more information).
17. In SAPGui open the import queue of the target System, transaction code STMS.
18. Select Import Overview (F5), select the target system and inspect the Import Queue (F8).
19. Locate the Import Request, Select Start Import, review the information and correct it if necessary, choose Continue.
20. In the target Redwood Server system, locate the import process in "Monitoring > Processes"; inspect the process definition RS_Test_CTS_Integration in "Definitions > Processes".

See Also

• Pusher Process Definition for SAP CTS+ Integration
• Choosing a Transport Strategy
• Starting the Import of All Requests in an Import Queue
• Resources on CTS+
• Starting Transport Organizer Web UI
• Transport Strategy in the CTS
• Transporting Non-ABAP Objects in Change and Transport System