Scribd
Upload
433 views14 pages

CTS+ Configuration For SAP PI Single Stack (AEX/PO) : 1. User Creation (In SOLMAN Default Client)

This document provides instructions for configuring SAP Process Integration (PI) for transporting objects between different systems using CTS+. The key steps include: 1. Creating technical and service users in the source and target systems for CTS+ access. 2. Configuring the transport management system (TMS) with the source and target PI systems as non-ABAP systems and defining transport routes between them. 3. Setting up RFC destinations in the source system to connect to the CTS+ organizer in TMS. 4. Activating the CTS+ web services and configuring the deploy web service in TMS. 5. Configuring logical ports and Java system properties in the

Uploaded by

ramesh bandari bandari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
433 views14 pages

CTS+ Configuration For SAP PI Single Stack (AEX/PO) : 1. User Creation (In SOLMAN Default Client)

This document provides instructions for configuring SAP Process Integration (PI) for transporting objects between different systems using CTS+. The key steps include: 1. Creating technical and service users in the source and target systems for CTS+ access. 2. Configuring the transport management system (TMS) with the source and target PI systems as non-ABAP systems and defining transport routes between them. 3. Setting up RFC destinations in the source system to connect to the CTS+ organizer in TMS. 4. Activating the CTS+ web services and configuring the deploy web service in TMS. 5. Configuring logical ports and Java system properties in the

Uploaded by

ramesh bandari bandari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 14

CTS+ Configuration for SAP PI Single Stack (AEX/PO) 

1. User Creation (In SOLMAN Default client)


1.1 Create service user CTSSRVUSER in Solution manager default client (001 in my case)

    This user will be used to export the objects from DEV to import queues of target in SOLMAN.

    a. Go to Tcode – SU01 -> type the username -> click create

b. Give the details of user and set the password. Go to roles and assign following roles to it

Standard role- SAP_CTS_PLUS


Custom role – Z_CTS_PLUS_ADDITIONAL (This need to be created)
2.1. Create Technical User NWDI_CTSADM in PI QAS and PRD environment
              This user will be logging in the PO Quality/Prod [TARGET] and transport objects
to target
                  a. Login to Netweaver Administrator (NWA-> http://<host> :< port>/nwa) ->
Configuration-> Identity Management

Assign the following roles to the user and save.

                        SAP_XI_CMS_SERV_USER

                        SAP_XI_DEVELOPER_J2EE

                        SAP_XI_CONFIGURATOR_J2EE

For transporting SLD objects also have a separate user with SLD role or assign to same user. I have
created SLD_CTSADM user in Quality system for SLD transports.
1. TMS Configuration
          1.1 Configuring Transport domain controller for Non-ABAP System

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

b. Navigate to Overview->Systems. Choose SAP System —> Create—> Non-ABAP System from
the menu.
c. Creating Non-ABAP system as source system (PI DEV)

d. Creating Non-ABAP system as target system (PI QA and PRD Systems)

 Under Target System Settings, select the Activate Deployment Service flag.


 Select the required deployment methods, Select XI/PI and SLD
 Enter the host of your target system (Here PI QA System) in the field Target Host in the
format <FQDN> and the two-character system number in the System No. field.
 In the Field System, enter your PI QA SID and Description of System.
 Under communication System area, in Name filed, enter Solman SID
e. In the pop-up enter the NWDI_CTSADM [Remember Part1 we created this user which will hit
target PI system].
Another pop-up for SLD user, provide any user with access to PI QA/PRD[target] SLD.
            

                   

                   

1.2 Configure Transport Route and Switch to change mode in client 000.

               a. Go to Tcode STMS-> choose Transport Routes


              

                   
b. Switch to Change mode-> Click Edit-> Transport Layer -> Create

                    
 c. Now Drag and Drop the PI Dev and PI QaS system to the Editor area

d. Click on Add Transport Route -> and create arrow from PI Dev to PI QaS and Save.

2. RFC Destination to SOLMAN in SAP PO Dev System


          Now this destination will allow objects from DEV system to reach CTS+ organizer when you
export them, via user CTSSRVUSER
               a. Log in to NWA-> Configuration -> Infrastructure -> Destinations
b. Click on Create

c. Destination Type: RFC and Destination name: sap.com/com.sap.tc.di.CTSserver and then


Click Next
d. Give log on data of SOLMAN default client; give service user which you created before.

e. Click Finish and Ping Destination


3. Activating the Web Service for Transport Organizer Web UI
              a. Go to Tcode SICF -> and click Execute, you will see following screen

 b. We need to activate CTS_BROWSER and CTS_ORGANISER service. Type CTS_BROWSER in


the Service Name
c. Right click on CTS_BROWSER and Activate Service. Same way Activate CTS_ORGANISER. 

4. Configure the CTS Deploy Web Service


          a. Logon to Solution Manager and go to tcode -> SM59

          b. Click on create RFC connection , Type G ,

i. RFC Destination – CTSDEPLOY


ii. Target Host – SOLMAN host
iii. Service no. – 5<sys. No.>00

                  [There are some discussion on service no. to be 8000 or 50000, as SMICM has 8000.
Well, it works with both but Recommended is 50000 ]

c. In the log on and security give a user id with J2EE_ADMIN role

          d. In Special option set the time out to 3600000 or -1. Save and do a Connection Test. You
must get 200 OK reply.
5. Configure Logical Port for Web Service
          a. Log on to client 000 of SOLMAN. Go to tcode -> LPCONFIG, ignore the warning and
proceed
          b. Provide Information as below and click on create

i. Proxy Class :CO_TFLDEPLOY_PROXY_VI_DOCUMENT
ii. Logical Port :CTSDEPLOY
iii. Description :CTS Deploy Service
iv. Default Port :Checked

c. Under Call Parameters tab provide Information as below


               

It may already exist. In that case just choose from value list. Else create it and save
under a transport request and activate

6. Configure CTS parameters for PI Dev system


     a. Open URL  http://<HOST>:PORT/dir/start/index.jsp for PI DEV and click on Administration

               
b. Click on Property Configuration under Repository tab and click Property Configuration link in
the center. 

[You can also reach here by logging in NWA->Configuration->Infrastructure-> Java System


Properties]

 c. Go to Service tab and filter on *XPI* and select XPI Service: All Config Service
d. Filter on *cts* under Properties tab

i. The highlighted parameters have default value false.


ii. Select them, click on Modify and set the value to True. Then Save

Properties to enable CTS+ for Integration directory


f. The above properties are to enable CTS+ transport wizard in ESR. To enable it for Integration
Directory and NWDS iFlows the properties are not available by default. Thus we need to add the
following properties

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

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

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

     
                        Once this is done you can see CTS+ transport wizard in Intergration directory as well as nwds. To see
how to transport in nwds using cts+ I have provided link at the bottom.

7. Configure CTS parameters for PI Dev system


Open ESR/ID and check for Export Design Objects

              

                        
               Transport an object to do a sanity check. The configuration is complete.

You might also like