Show TOC

Procedure documentationConfiguring the CTS Deploy Web Service Locate this document in the navigation structure

 

To be able to use the CTS Deploy Web service, you must configure the HTTP connection CTSDEPLOY. A prerequisite for the HTTP connection is that the logical port CTSDEPLOY exists on the SAP NetWeaver Application Server ABAP of your transport system and the CTS Deploy Web service exists on the SAP NetWeaver Application Server Java of your transport system. As of enhancement package 1 for SAP NetWeaver 7.0, the logical port CTSDEPLOY is delivered completely configured. The CTS Deploy Web service has been part of SAP NetWeaver 7.0 AS Java since Support Package Stack 12.

Procedure

The following steps describe how to configure the CTS Deploy Web service, using a dual-stack system as transport system.

Checking the Logical Port CTSDEPLOY

Check that the logical port CTSDEPLOY exists in client 000 and is active.

You are in the SAP NetWeaver Application Server ABAP of your transport system in client 000.

  1. Check the logical port

    1. Call transaction LPCONFIG. Ignore the message that the transaction is obsolete.

    2. In the Proxy Class field enter the value CO_TFLDEPLOY_PROXY_VI_DOCUMENT and in the Logical Port field enter the value CTSDEPLOY.

    3. Choose Display.

    4. If the logical port does not exist, create it in client 000. For this you first have to set the system change option of the client 000 to Modifiable (see step 2 below).

      After creating it, select tab page Call Parameter and in the HTTP Destination field enter the value CTSDEPLOY and in the Path Suffix field enter the value DeployProxy/default?style=document.

    5. If the logical port exists, check that the path suffix has the value shown above and that it is active.

    6. You must activate the logical port if it is not already activated. For this you first have to set the system change option of the client 000 to Modifiable (see step 2 below).

    7. To activate the logical port, choose Display<->Change. Select Activate.

  2. Set up the system change option for client 000

    1. Call transaction SE03 in a new mode.

    2. Choose   Administration   Set System Change Option   and choose Execute.

    3. Choose Client Setting.

      The Display "Clients" View: Overview screen is displayed.

    4. Select the Client 000.

    5. Choose Display -> Change.

    6. Confirm the message that the table is cross-client with Continue.

    7. Choose Detail.

      The Change "Clients" View: Detail screen is displayed.

    8. Select Automatic Recording of Changes.

    9. Save your entries.

    Caution Caution

    You must only open the system change option temporarily for client 000. Make sure that you reset the system change option for client 000 to its initial value after you have made the settings for the logical port.

    End of the caution.
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 the user before creating the HTTP connection.

Note Note

For all other applications the following applies: For the HTTP connection you only need a user that exists on the system where the Deploy Web service is running and which has a valid password. The user does not need to have any special authorizations.

End of the note.

You are in the SAP NetWeaver Application Server Java of your transport system.

  1. Create a user of type System with the name CTSD_RFC.

  2. Assign the role SAP_CTS_DEPLOY to the user CTSD_RFC. This role is created automatically when deploying the CM Services and gets all necessary actions to be able to access the CM Services of ABAP. Alternatively, you can assign the role to a group and the users of this group.

More information on creating users in the User Management Engine: Managing Users, Groups, and Roles

More information about actions available for CM Services: Authorizations in CM Services

Configuring the HTTP Connection

You are in the SAP NetWeaver Application Server ABAP of your communication system in the client that you use for transports.

  1. Call transaction SM59.

  2. Create a new HTTP connection called CTSDEPLOY by choosing Create.

  3. Choose conntection type HTTP Connection to External Server, and enter a description for the HTTP connection.

  4. Choose the Technical Settings tab page.

    1. Enter the name of the host of your CTS system and under Service Number enter the port of your system where the CTS Deploy Web service runs (5<SAPSystem Number>00). Ensure that no path prefix is entered and confirm your entries with Enter.

    2. If you encounter warnings about invalid query strings or missing documentation, ignore them by choosing Enter.

    3. Save your entries.

  5. Choose the Logon and Security tab page.

    1. Select Basic Authentication as the logon procedure.

    2. 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.

    3. Save your entries.

  6. To test the new HTTP connection, choose Connection Test.

  7. Choose Continue to confirm.

    If you have created the new HTTP connection successfully, the status text in the test results is set to OK.

Setting a Timeout for the Deployment

Timeouts can occur when very large objects are deployed. Always set the timeout to be longer than the longest expected deployment time.

You are in SAP NetWeaver Application Server ABAP in your CTS system.

  1. Call transaction SM59.

  2. Choose   HTTP Connections to External Server   CTSDEPLOY  .

  3. Select the Special Options tab page.

    The ICM Default Timeout option is selected as the default under Timeout.

    Caution Caution

    Select a timeout that is higher than the longest expected deployment. If in doubt, select No Timeout to avoid the connection timing out during a deployment.

    End of the caution.
When using NWDI in connection with CM Services: Configuring and Monitoring the 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.

Note Note

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).

End of the note.

Since you have to use the deploy Web service for NWDI development on the CM Services Server, you need an additional logical port CTSDEPLOY_DI and a related HTTP connection.

  1. Create an additional logical port CTSDEPLOY_DI on the CTS System. Proceed as described in Checking Logical Port CTSDEPLOY. In step 4 use CTSCONFIG as the HTTP connection.

  2. Assign the role SAP_CTS_DEPLOY to the user that is used for the HTTP connection CTSCONFIG.

    For more information on this HTTP connection, see Configuring the CTS Config Web Service.

  3. Execute the steps described under Setting Timeout for Deployment for the HTTP connection CTSCONFIG.

Note Note

When creating systems in the Transport Management System, the system enters the value CTSDEPLOY as the name of the Deploy Web service by default. Change the value of the DEPLOY_WEB_SERVICE parameter manually to CTSDEPLOY_DI in the TMS configuration. For further information, see Changing Standard Settings for Target Systems.

End of the note.