Configuring the CTS Deploy Web Service

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. To check the logical port, proceed as follows:

   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. To set up the system change option for client 000, proceed as follows:

   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

   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.

Creating a User for the HTTP Connection

In general, the user that is used for the HTTP connection must exist on the AS Java where the Deploy Web service is running and it must have a valid password.

If you use dynamic file transfer as file transfer method, the user must have additional authorizations as described under Defining a Method for the File Transfer to the Target System.

If you use SAP NetWeaver Development Infrastructure (NWDI) in connection with CM Services you need a user with special authorizations for the HTTP connection. You must create this user before creating the HTTP connection. Proceed as follows:

1. Create a user of type System in the SAP NetWeaver Application Server Java of your transport system. The user can be called CTSD_RFC, for example.

2. Assign the role SAP_CTSDEPLOY to the user. 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.

For more information on creating users in the User Management Engine (UME), see the SAP NetWeaver Application Server Java documentation under Managing Users, Groups, and Roles.

For more information on the actions available for the CM Services, see the CM Services documentation under Authorizations for Change Management 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 connection 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 the system where the CTS Deploy Web service runs and under Service Number enter the port of this system ( 5<SAPSystem Number>00).

      If you use a dual stack system as CTS system, enter the host name of the current system. If you use separated AS ABAP and AS Java stacks, enter the host name of the AS Java that is used for CTS.

      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 as described above.

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

When using NWDI in connection with CM Services: Configuring and Monitoring the Logical Port CTSDEPLOY_DI

You only have to execute this step if you need another CTS Deploy Web Service.

1. To check that the logical port CTSDEPLOY_DI exists and is active, proceed as described under Checking the Logical Port CTSDEPLOY.

2. You can use the CTSCONFIG connection as the HTTP connection for the logical port CTSDEPLOY_DI. For more information on this HTTP connection, see Configuring the CTS Config Web Service.

3. When creating systems in the Transport Management System, the system enters the value CTSDEPLOY as the name of the Deploy Web service by default. Therefore, change the value of the DEPLOY_WEB_SERVICE parameters to CTSDEPLOY_DI in the TMS configuration manually.

   For further information, see Changing Standard Settings for Target Systems.