Skip to Content

Prerequisites

Note: Install new SAP Kernel for PI 7.3 system and make sure you have new version of tp.exe and R3trans.exe

Procedure in SAP PI Development system

1.       Create service user CTSSRVUSER (Note: user is created in to PI working client; Example Client 100)

/wp-content/uploads/2012/07/image001_120398.png
1.1.    Create SAP role “Z_CTS_PLUS_ADDITIONAL”

/wp-content/uploads/2012/07/image003_120399.png

1.2.    Assign USER ROLES “SAP_CTS_PLUS” And “Z_CTS_PLUS_ADDITIONAL”

/wp-content/uploads/2012/07/image005_120400.png

2.       Create RFC Destination for PI  Java to PI ABAP Connectivity

2.1.    Login to http://<PI_Host>:5XX00/nwa

/wp-content/uploads/2012/07/image007_120404.png

2.2.    Navigate to Configuration >> Infrastructure >> Destinations

/wp-content/uploads/2012/07/image009_120405.png

2.3.    Click Create

/wp-content/uploads/2012/07/image011_120406.png

2.4.    Provide information as below
Hosting System: Local J2EE System <SID>
Destination Name: sap.com/com.sap.tc.di.CTSserver
Destination Type: RFC

/wp-content/uploads/2012/07/image013_120407.png

2.5.    Provide information for SAP PI system and continue
Load Balancing: No

Local System Connection: Checked

System ID: <SID> (Your system id)

Gateway Host: localhost

Gateway Service: sapgwXX (Your system instance number)

SNC: Active or Inactive

/wp-content/uploads/2012/07/image014_120408.png

2.6.    Provide user detail you created under step 1

/wp-content/uploads/2012/07/image015_120409.png
2.7.    Press Finish
Pooled Connection Mode : Uncheck

/wp-content/uploads/2012/07/image016_120410.png

2.8.    Test RFC

/wp-content/uploads/2012/07/image017_120411.png

Result should be

/wp-content/uploads/2012/07/image019_120412.png

3.       Maintain Exchange Profile
Note: Before you start with the maintenance, you might want to export the current version of your exchange profile.

3.1.    Open Exchange profile through http://<PI_Host>:5XX00/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp

/wp-content/uploads/2012/07/image020_120413.png

3.2.    Create new parameter

/wp-content/uploads/2012/07/image022_120414.png

3.3.    To enable the CTS integration out of the Transport Wizard in the Integration Directory create boolean parameter com.sap.aii.ibdir.core.cts.enableTransportWizard and set value to true

/wp-content/uploads/2012/07/image023_120415.png

3.4.    To enable the CTS integration for the Changelist transport in the Integration Directory create boolean parameter com.sap.aii.ibdir.core.cts.enableClTransport and set value to true.

/wp-content/uploads/2012/07/image024_120416.png

3.5.    Open IntegrationBuilder.Repository

/wp-content/uploads/2012/07/image025_120417.png

3.6.    To enable the CTS integration for the Transport Wizard in the Enterprise Service Repository create boolean parameter com.sap.aii.ibrep.core.cts.enableTransportWizard and set value to true.

/wp-content/uploads/2012/07/image026_120418.png

3.7.    To enable the CTS integration for the Changelist transport in the Enterprise Service Repository create boolean parameter com.sap.aii.ibrep.core.cts.enableClTransport and set value to true

/wp-content/uploads/2012/07/image027_120419.png

4.       TMS configuration for JAVA systems in PI ABAP

4.1.    Login to SAP PI client 000 with user DDIC

/wp-content/uploads/2012/07/image028_120420.png

4.2.    Run TCode STMS

/wp-content/uploads/2012/07/image029_120421.png

4.3.    Open System Overview

/wp-content/uploads/2012/07/image030_120422.png

4.4.    Select Your SAP development system from list and create Java Stack Configuration (Navigation :SAP System >> Create >> Java Stack Configuration)

/wp-content/uploads/2012/07/image031_120423.png

4.5.    Select  Activate Transport Organizer under Source System Settings
Provide your SAP PI Development system SID  and PI integration client number and Save

/wp-content/uploads/2012/07/image032_120424.png
(In our cace PD1 is development system)

4.6.    This will create following entry in transport tool for SAP PI development system

/wp-content/uploads/2012/07/image033_120425.png

/wp-content/uploads/2012/07/image034_120426.png

4.6.1 Navigation to varify
Highlight development system and from menu select Sap System and Change

/wp-content/uploads/2012/07/image035_120427.png
4.6.2 Open transport tool TAB

/wp-content/uploads/2012/07/image036_120428.png
Note: Other parameter depends on your SAP transport stratagy

5.       Activating the Web Service for Transport Organizer Web UI (Should do in all CTS+ systems)

5.1.    Login to SAP PI development system

5.2.    Run TCode SICF

/wp-content/uploads/2012/07/image037_120429.png

5.3.    Search for *CTS*

/wp-content/uploads/2012/07/image038_120430.png

5.4.    Activate both services “CTS_BROWSER” And “CTS_OBJECTLIST_BROWSER”

/wp-content/uploads/2012/07/image039_120431.png
Select Yes

/wp-content/uploads/2012/07/image040_120432.png

5.5.    Test Service

6.       Target Systems Configuration (Quality Assurance, Pre Production, Production)
Example is for Quality Assurance system (QAS)

6.1.    Create “CTSDEPLOY” RFC connection in PI QAS  system

6.1.1.  Login to PI QAS ABAP system

6.1.2. Run TCode SM59

/wp-content/uploads/2012/07/image041_120433.png

6.1.3.  Create RFC

/wp-content/uploads/2012/07/image042_120434.png

6.1.4. Provide PI localhost information

/wp-content/uploads/2012/07/image043_120435.png

6.1.5. Provide user as J2EE_ADMIN

/wp-content/uploads/2012/07/image044_120436.png

6.1.6. Specify Timeout as 3600000 and Save

/wp-content/uploads/2012/07/image046_120437.jpg

7.       Configure the Logical Port for the Web Service

Note: This has to be configured in client 000 PI QAS system Make sure your client is open for “Automatic  recording of changes”. Once port created change it back to “No changes allowed”.

/wp-content/uploads/2012/07/image047_120438.png

7.1.    Login to ABAP PI client 000 QAS system

7.2.    Run Tcode LPCONFIG

/wp-content/uploads/2012/07/image048_120439.png

7.3.    Continue on warning

/wp-content/uploads/2012/07/image049_120440.png

7.4.    Provide information as below and press Create
Proxy Class :CO_TFLDEPLOY_PROXY_VI_DOCUMENT
Logical Port :CTSDEPLOY
Description :CTS Deploy Service
Default Port: Checked

/wp-content/uploads/2012/07/image050_120441.png

7.5.    Under call Parameter TAB
HTTP Destination  : CTSDEPLOY
Path Suffix :  /DeployProxy/default?style=document
Message ID : Checked
State Management : Checked

/wp-content/uploads/2012/07/image051_120442.png

7.6.    Activate Port

/wp-content/uploads/2012/07/image053_120443.png

7.7.    Check Status of port after saving changes

/wp-content/uploads/2012/07/image054_120444.png

8.       Create CTS User NWDI_CTSADM for Deployment in Target system (QAS, Pre Prod, Prod)

8.1.    User information

/wp-content/uploads/2012/07/image056_120445.png

8.2.    User roles are as below

SAP_BC_WEBSERVICE_PI_CFG_SRV

SAP_SLD_CONFIGURATOR

SAP_SLD_DEVELOPER

SAP_XI_BPE_CONFIGURATOR_ABAP

SAP_XI_CMS_SERV_USER

SAP_XI_CMS_SERV_USER

SAP_XI_CONFIGURATOR

SAP_XI_CONFIGURATOR_ABAP

SAP_XI_CONFIGURATOR_J2EE

SAP_XI_DEMOAPP_EXECUTE

SAP_XI_DEVELOPER

SAP_XI_DEVELOPER_ABAP

SAP_XI_DEVELOPER_J2EE

SAP_XI_EXCHANGE_PROF_READ

9.       TMS configuration for Target system (QAS, pre prod and prod)

9.1.    Login to SAP PI DEV ABAP system in client 000 with user DDIC

9.2.    Open TMS and go to system overview

9.3.    Select Your SAP PI Quality assurance system from list and create Java Stack Configuration (Navigation :SAP System >> Create >> Java Stack Configuration)

/wp-content/uploads/2012/07/image058_120446.png

9.4.    Under Target system setting Activate Deployment Service
Method : XI
Target Host : SAP PI QAS system host name
System Number : PI QAS Instance number

/wp-content/uploads/2012/07/image059_120447.png
As soon as you save it will ask for NWDI_CTSADM user and password

9.5.    Provide NWDI_CTSADM user password

/wp-content/uploads/2012/07/image060_120448.png

9.6.    This will create following entry in transport tool for SAP PI QAS system

/wp-content/uploads/2012/07/image061_120449.png

/wp-content/uploads/2012/07/image062_120450.png

/wp-content/uploads/2012/07/image063_120451.png

If you want to include SLD in to transport then create parameters as below

/wp-content/uploads/2012/07/image064_120452.png

Note: Host name is PI QAS SLD URL

Provide SLD user in configuration in PI QAS system

/wp-content/uploads/2012/07/image065_120453.png

9.7.    Configuration is DONE

Errors :

Note 1497388 – CTS+ deploy test: Incorrect return code 8

Note 1428106 – Null Reference Error in the CTS+ Browser

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Sanjay Sahita

    Hi,

    Thanks for the nice steps.

    What if I have JAVA Only PI 7.3 based on AEX and I am planning to use Solman as Domain controller.

    In that case; What from above steps would change in terms of configuration ?

    – Sanjay

    (0) 
    1. Yogesh Patel Post author

      Hello Sanjay,

      If you want to follow this doc you can. I don’t see much difference. But keep in mind that you are trying to connect from other system for CTS+ so tweak accordingly..

      Cheers and best of luck.

      Yogesh

      (0) 

Comments are closed.