Skip to end of metadata
Go to start of metadata

Business Scenario :

Version : EP7.3

The functions of the Change and Transport System (CTS) is to enable the transport of non-ABAP objects.Non-ABAP objects can be attached to transport request. In the portal use case deployment takes place using the Deploy Controller. The transport routes have to be defined in the transport (CTS) system . Using CTS + , it is possible to transport SAP Portal objects, Change lists , KM Documents, Configurations , NWDI developments from CMS /CM services with automatic transport request.

Prerequisites :

1. Need SAP NW AS JAVA and AS ABAP . AS ABAP system can act as CTS+ Domain controller and manages transport requests.

2. To be able to perform the configuration steps below, you require full administration privileges both for the CTS+ system and for the portal .

Procedure :

1. Configure the Transport :

            1.1   Configuring the CTS Deploy Web Service :

                         Check whether the logical port CTSDEPLOY exists in CTS (ABAP client) system and is active.from transaction *lpconfig.*In the Proxy Class field enter the value CO_TFLDEPLOY_PROXY_VI_DOCUMENT and in the Logical Port field enter the value CTSDEPLOY, Choose Display.

                      

If it don't exist , create similar to below. Generally it exists by default.


                       

           1.2        When using NWDI with CM Services: Creating Users for the HTTP Connection:

                                  If you use SAP NetWeaver Development Infrastructure (NWDI) in connection with CM Services, then you need a user with special authorizations for the HTTP connection.Create a user of type System with the name CTSD_RFC in Development Portal where Deploy Web service is running. Assign the role SAP_CTS_DEPLOY to the user CTSD_RFC. This role is created automatically when deploying CM Services and contains all the necessary actions for the CTS Deploy Web Service. Alternatively, you can assign the role to a group and the users of this group.

           1.3  Configure Http Connection:

                                        Login SAP NetWeaver Application Server ABAP (CTS) of your transport system in the client that you use for transports. Call Transaction SM59.Create a new HTTP connection called CTSDEPLOY. Choose connection type HTTP Connection to External Server, and enter a description for the HTTP connection.Choose Technical settings tab and give Target Host value as hostname of portal ( Ex: Dvelopment Portal host name) . In the Service no , enter port number of the portal.


Choose the Logon and Security tab page. Select Basic Authentication as the logon procedure. Enter a user and password that is recognized on the system where the Deploy Web service is running or, if using the NWDI with CM Services, enter the user CTSD_RFC just created. Save your entries.

To test the new HTTP connection, choose Connection Test. Choose Continue to confirm. If you have created the new HTTP connection successfully, the status text in the test results is set to OK.

1.4  Only when using NWDI in connection with CM Services: Check and configure logical port CTSDEPLOY_DI :

You must only execute this step if all of the following prerequisites apply:

You want to use the same CTS system for both Java transport with CM Services and for transports of other SAP applications (for example, Portal, PI). The CM Services run on a different AS Java to the CTS system. If the existing port displays CTSDEPLOY on the server that is used as CM Services Server, then you must ensure that the user of the HTTP connection CTSDEPLOY is assigned the role SAP_CTS_DEPLOY (see When Using NWDI with CM Services: Create User for HTTP Connection).

 Used same CTSDEPLOY in this scenario for CM Services as well.

1.5 Configuring the CTS Config Web Service :

You only need the CTS Config Web service when you use the SAP Net Weaver Development Infrastructure (NWDI) in connection with CM Services.Create a user of type System with the name CTSC_RFC in Development Portal where Deploy Web service is running. Assign the role SAP_CTS_DI_CONFIGURATOR to the user CTSC_RFC. This role is created automatically when deploying CM Services

To be able to use the CTS Config Web service, you must configure the HTTP connection CTSCONFIG. A prerequisite for the HTTP connection is that the logical port CTSCONFIG exists on the SAP Net Weaver Application Server ABAP of your transport system and the CTS Config Web service exists on the SAP Net Weaver Application Server Java of your transport system.

Login SAP NetWeaver Application Server ABAP (CTS) of your transport system in the client that you use for transports. Call Transaction SM59.

Create a new HTTP connection called CTSCONFIG. Choose connection type HTTP Connection to External Server, and enter a description for the HTTP connection.Choose Technical settings tab and give Target Host value as hostname of portal ( Ex: Dvelopment Portal host name) . In the Service no , enter port number of the portal.

Choose the Logon and Security tab page. Select Basic Authentication as the logon procedure. Enter the user CTSC_RFC created for the HTTP connection and the password.Save your entries.

To test the new HTTP connection, choose Connection Test. Choose Continue to confirm. If you have created the new HTTP connection successfully, the status text in the test results is set to OK.

2.       Configuring the Transport Organizer Web UI :

Call SICF transaction in CTS system and activate Webdynpro ABAP application CTS_BROWSER and CTS_OBJECTLIST_BROWSER.

3.      Configuring the Destination Service on your Development Portal:

Open Netweaver administrator of development portal and navigate to Configuration -> Security -> Destinations and create RFC Destination "sap.com/com.sap.tc.di.CTSserver".Under Connection and Transport Settings, enter the connection data of your CTS server. Under Logon Data, select the Current User (Assertion Ticket) option as authentication for the connection to your CTS server. We recommend that you use Single Sign-On (SSO). If you cannot use SSO, select the Configured Useroption and enter your preferred language, a client, and an appropriate user and password.

4.  User Authorizations to use CTS in portal environment and NWDI.

Users who need to use CTS plus should have SAP_CTS_PLUS role in CTS system.

5.  Configuring the Transport Landscape:

Create the systems of your portal landscape as non-ABAP systems in TMS. Use their SID to provide a clear understanding of the transport routes to the portal administrators who are using the Transport Organizer Web UI from within the portal.

You are in your TMS domain controller.Create Non-ABAP system ( Portal).

       1.      Call transaction STMS -> Choose System Overview ->  Choose SAP System -> Create -> Non-ABAP System ,  Create the non-ABAP system with a system ID and a description.  Select the CTS system as the communication system. Make the following settings, depending on whether your system is a source system or a target system (or both):

Under Source System Settings, select the Activate Transport Organizer flag and enter the client where you want to use Transport Organizer , Under Target System Settings, select the Activate Deployment Service flag. Select your preferred deployment methods and fill out the rest of the fields accordingly. Enter a system user and password for your preferred deployment methods.

     Save your settings and confirm that you want to distribute the TMS configuration.

Create Transport routes as per transport landscape.Now CTS plus is ready to accept portal requests automatically.

  • No labels