Skip to Content

CTS+ configuration SAP PO on NW 7.5

CTS+ Configuration:


1     Purpose


  1. The purpose of this document is to describe the general configuration steps required to implement CTS+ for moving transports in PO landscape from Development to
    Quality and Production (DPO -> QPO -> PPO).

2    Preparation


2.1 Prerequisites


Before starting the implementation of CTS+, the following pre-requisites should be check for successful configuration.

To configure CTS+ on SAP Solution Manager for PO landscape, running SAP NetWeaver PO Systems must be accessible and host/port information are available including adequate permissions for the following parts:

  1. You must have administrative access to:

  • SAP NetWeaver Administrator (NWA)
  • Access to DMR/PMR client 000
  • Access to DMR/PMR client 501
  • Service user in DMR/PMR client 501
  • Service user in PO systems

3 CTS+ Configuration:

  1. User Creation (In SOLMAN DMR/PMR client 501)

3.1 User Creation (In SOLMAN PMR client 501)


3.1.1 Create service user CTS_PO in Solution manager PMR client 501

Assign the following roles

Standard role- SAP_CTS_PLUS

Custom role – Z_CTS_PLUS_ADDITIONAL (This need to be created)

Role: Z_CTS_PLUS_ADDITIONAL

Authorization Objects:

                1. S_ICF

       2. S_RFC

       3. S_CTS_ADMI

       4. S_DATASET

       5. S_TRANSPRT

Authorization Values:

Authorization Check for ICF Access (object: S_ICF):

• • • ICF_FIELD: DEST, PROXY, SERVICE

ICF_VALUE: * (Type * in the FROM column or Click Full Authorization)

Authorization Check for RFC Access (object: S_RFC):

• • • ACTIVITY: 16

RFC_NAME: CTS_WBO_DIS, EPSF, RFC1, SDIFRUNTIME, STPA, SYST, SYSU

In the other blogs SYSU is not mentioned. There can be an error- RFC_NO_AUTHORITY

for CTSSRVUSER, as it tries calling a function module SYSTEM_RESET_RFC_SERVER

(can be seen in ST22 dumps). To prevent this add SYSU function Group

RFC_TYPE: FUGR

Administration Functions in the Change and Transport System (object: S_CTS_ADMI):

• • • CTS_ADMFCT: EPS1, EPS2

Authorization for file access (object: S_DATASET):

• • • ACTVT: 06, 33, 34, A6, A7

FILENAME: *

PROGRAM: CL_CTS_ASSIST_BROWSER=========CP, SAPLEPSF,

SAPLSCTS_EXE_FILE, SAPLSCTS_RELEASE, SAPLSLOG, SAPLSTFI, SAPLSTPA,

SAPLSTPP, SAPLSTRF, SAPLTMSM, SAPLTMS

Transport Organizer (object: S_TRANSPRT):

• • • ACTVT: 01, 02, 03, 05, 06, 23, 43, 50, 60, 65, 75, 78, 90 (80 should not be selected)

TTYPE: CUST, DTRA, PIEC, TRAN

3.2    . Create Technical User NWDI_CTSADM in QPO and PPO environment


This user will be logging in the PO Quality/Prod and transport objects to target

Assign the following roles to the user NWDI_CTSADM

SAP_XI_CMS_SERV_USER

SAP_XI_DEVELOPER_J2EE

SAP_XI_CONFIGURATOR_J2EE

  1. QPO - http://sappoqa03:50000/nwa àConfiguration à Identity Management
  2. PPO - http://sapprdpo:50000/nwa àConfiguration à Identity Management

QPO : Identity management

Create user

NWDI_CTSADM

Assign the below roles


PRO



3.3     Create test user in PMR 501 userid same as  PO system and assign below role

Z_CTS_PLUS_ADDITIONAL


This user is used for testing the CTC+ authorizations for end users.


3.4     TMS Configuration


3.4.1  Configuring Transport domain controller for Non-ABAP System

     a. Log on to SOLMAN PMR system in client 000 and start Transaction STMS

 

      Create SAP System ---> Create ---> Non-ABAP System from the menu.

     Create Non-ABAP system as source system DPO do not select deployment service tab.

PPO

Target host sapprdpo

Create Non-ABAP system as target  system  QPO  and  PPO

Additional parameters

DPO

TRANSDIR – solman trans directory

COMMUNICATION_SYSTEM – PMR solman

NON_ABAP_WBO_CLIENT – solman customer client

DEPLOY_DATA_SHARE – solman trans directory\data

DEPLOY_XI_URL – DPO server hostname and java port.

PPO

TRANSDIR – solman trans directory

COMMUNICATION_SYSTEM – PMR (solman system)

NON_ABAP_WBO_CLIENT – solman customer client

DEPLOY_DATA_SHARE – solman trans directory\data

DEPLOY_XI_URL – QPO server hostname and java port

PPO


TRANSDIR – solman trans directory

COMMUNICATION_SYSTEM – PMR (solman system)

NON_ABAP_WBO_CLIENT – solman customer client

DEPLOY_DATA_SHARE – solman trans directory\data

DEPLOY_XI_URL – PPO server hostname and java port.

3.4.2  Configure Transport Route in PMR 501.

     Go to STMS - Transport Routes and Create Transport Layer




Drag the systems and create route DPO---> QPO --> PPO


3.5 RFC Destination to SOLMAN PMR in DPO System

3.5.1 Create destination from NWA and user will be CTS_PO created earlier

              http://sappodev:50100/nwa --> configuration --> Destinations

Desinations

Create

PMR Solman hostname

PMR Solman system number

Gateway host : solman host

Gateway service : sapgwxx

CTS_PO

Ping Destination


3.6 Activating the Web Service for Transport Organizer Web UI


    Check and Activate CTS_BROWSER and CTS_ORGANISER from t-code SICF


Already active

Already active


3.7 Configure the CTS Deploy Web Service


    Logon to PMR and configure CTS Webdeploy Service RFC Destination CTSDEPLOY already there and not required just verify.

     CTSDEPLOY destination available in PMR create one in DMR

Solman host and smicm port

3.8 Configure Logical Port for Web Service

Verify if logical port is configured or not.

  1. Log on to client 000 of SOLMAN PMR. Go to tcode -> LPCONFIG, ignore the warning and proceed

     b. Provide Information as below and click on create

  1. Proxy Class: CO_TFLDEPLOY_PROXY_VI_DOCUMENT
  2. Logical Port: CTSDEPLOY
  3. Description: CTS Deploy Service
  4. Default Port: Checked

DMR


3.9 Configure CTS parameters for PI Dev system


     Logon on to DPO NWA and configure the below Parameters


     Go to Service tab and filter on *XPI* and select XPI Service: All Config Service


com.sap.aii.ibrep.core.cts.enableCITransport

     com.sap.aii.ibrep.core.cts.enableTransportWizard

   Add the below parameters

     com.sap.aii.ibdir.core.cts.enableClTransport = true

     com.sap.aii.ibdir.core.cts.enableRequestSelection = true

     com.sap.aii.ibdir.core.cts.enableTransportWizard = true

4. Test:

   Open ESR/ID and check for Export Design Objects

    Transport an object use option Transport using CTS for exporting Design objects to do a sanity check.

    Create user CTS_PO as copy from developer account

    Open ESR

     http://sappodev:50100/dir

    Right click and Export

    Export using CTS

    Continue

     Continue

     Finish

     Close

     Open CTS Transport organizer

     Edit Assign CTS Project ID and release

     Open STMS QPO and PPO Queue in DMR and import the transport DSOK90004

     Imported successfully in QPO and PPO

     The Local Software Component Versions named test in available in QPO

Result

Now transports in PO system can be moved from Development to Quality and Production using CTS+.