CTS+ Confguration for Portal Transports

CTS+ Confguration for Portal Transports

Use:

Enhanced Change and Transport System (CTS+)  helps us to transport Java objects and SAP-related non-ABAP applications in the system landscape, alongside ABAP objects. we can also administer non-ABAP systems during a CTS transport domain in SAP NetWeaver Application Server ABAP.

Transportable Objects:

You can use CTS+ to move the subsequent additional objects:

•Java-based and J2EE-based objects:

 Software Component Archives (SCAs)
 Enterprise Application Archives (EARs)
 Software Deployment Archives (SDAs)

•SAP NetWeaver usage type SAP NetWeaver Portal (EP) objects:

 Enterprise Portal Archives (EPAs)
 Enterprise Portal Applications (PARs)
 Knowledge Management objects (KM Content and KM Configurations)

• SAP NetWeaver usage type PI (Process Integration) Non-ABAP objects:

 Integration Builder objects (TPZs)

Objects related to SLD content  (products, software components, technical systems, and business systems)

Configuration – Concept:

The following three components must be configured before you'll use the improved Change and Transport System.

• CTS Deploy Web service (SAP NetWeaver AS Java)

This is a Java Web service liable for communicating with the deployment tools in non-ABAP systems. The transport control program tp communicates with the 

CTS Deploy Web service when deploying the non-ABAP objects.

• CTS Deploy proxy (SAP NetWeaver AS ABAP)

A CTS Deploy proxy is required on the ABAP side to enable the transport control program tp on SAP NetWeaver AS ABAP to communicate with the CTS Deploy Web service on SAP NetWeaver AS Java.

• Transport Organizer Web UI (SAP NetWeaver AS ABAP)

This is an Web Dynpro ABAP application during which you create and edit transport requests for non-ABAP systems.

Configuring the CTS Deploy Web Service:

Use:The CTS Deploy Web service connects the ABAP transport tools to the deployment tools within the non-ABAP applications.

Prerequisites:

This deployment Web service has been a part of SAP NetWeaver 7.0 since Support Package Stack 12.

Information about using the CTS Deploy Web service in another SAP NetWeaver system is out there in SAP Note 1003674.

Checking the CTS Deploy Web Service:

1.  Open the CTS server in SAP NetWeaver Application Server Java,.
2. In your Web browser, enter the following URL:
3. Open Web Service Navigator.

The DeployProxy Web service is within the list of deployment Web services.

Note: Deploy the patch DI CHANGE MGMT SERVER 7.00 as per the SAP Note no: 1076189 if you couldn’t find the service

Configuring the HTTP Connection:

You should be in SAP NetWeaver Application Server ABAP in your CTS system.

1. Call transaction SM59.
2. Create a new HTTP connection called CTSDEPLOY.
3. Choose the Technical Settings tab page.

 a. Enter the name of the target host, the service number (500), and therefore the path prefix /DeployProxy/default?style=document. Confirm by choosing Enter.

 b. If you see any warnings about invalid query strings or missing documentation, ignore them by choosing Enter.

 c. Save your entries.

4. Choose the Logon and Security tab page.

 a. Select Basic Authentication as the logon procedure.

 b. Enter a J2EE user name and password.

 c. Save your entries.

5. to check the new HTTP connection, choose Connection Test.
6. Choose Continue to confirm.

If you've got created the new HTTP connection successfully, the status text within the test results is about to OK.

Setting a Timeout for the Deployment:

Use:Large objects can cause timeouts in deployments. set more time out duration  than the longest expected deployment time.

Procedure:
You should be in SAP NetWeaver Application Server ABAP in your CTS system.

1. Call transaction SM59.
2. select HTTP Connections to External Server ® CTSDEPLOY.
3. Select the Special Options tab page.

The ICM Default Timeout option is chosen because the default under Timeout.

Select a timeout that's above the longest expected deployment. If unsure , select No Timeout to avoid the connection timing out during a deployment.

Configuring the Logical Port for the Web Service:

Use:Logical ports for Web services are Customizing objects.

Prerequisites:

To configure a logical port, you want to enable Customizing changes to be made in client 000. You can cancel these changes once you've got configured the CTS Deploy Web service.

Setting the System Change Option:

You should be in SAP Net Weaver Application Server ABAP in your CTS system.

1. Call transaction SE03.
2. select Administration  -> Set System Change Option and click on Execute.

 The System Change Option screen appears ->
3. Choose Client Setting.

 The Display “Clients” View: Overview screen is displayed.

4. Select the client 001(The client which you're getting to use for CTS+ Transport Requests).

5. Choose Change ® Display.

A panel with the messageCaution: The table is cross-client. appears.

6. Choose Continue to confirm.

7. Make the following changes:

 a. Choose Detail.

 The Display “Clients” View: Detail screen is displayed.

 b. Select Automatic Recording of Changes.

8. Save your entries.


Creating a Logical Port:

You should be in SAP Net Weaver Application Server ABAP in your CTS system.

1. Log on to client 000.

2. User must be aside from DDIC and SAP*.

3. Call transaction LPCONFIG.

 The Display/Create Logical Port screen is displayed.

4. choose the proxy class CO_TFLDEPLOY_PROXY_VI_DOCUMENT from the proxy list.

5. Enter CTSDEPLOY as the logical port.

6. Choose Create.

 The Edit Logical Port screen is displayed.

7. Enter an outline for the logical port and choose the Default Port checkbox.

8. Under General Settings, choose the decision Parameters tab page.

9. Select CTSDEPLOY as the HTTP destination.

10. Save your entries.

 A panel is displayed that prompts you to specify a customizing request.

11. Enter your changes in a change request.

12. Activate the CTS Deploy Web service logical port .


Activating the online Service for Transport Organizer Web UI:

Use:To sign up non-ABAP objects to a transport request, you want to activate the online service CTS_BROWSER.


Prerequisites:

• You have authorization for transaction SICF.

• Ensure to activate all ICF services required to run an ABAP Web Dynpro application.


Note: For more information, see SAP Note 517484.

Procedure:

1. Call transaction SICF. This transaction is a cross-client transaction.

2. Enter SERVICE within the Hierarchy Type field and CTS_BROWSER within the Service Name field.

3. Choose Execute

4. Select the online service (CTS_BROWSER) on the Maintain Services screen.

5. Activate the online service by opening the context menu (secondary mouse button) and selecting Activate Service.

A dialog box for activating IFC services is displayed.

6. Choose Yes (with tree icon).


If you would like to check the online service, open the context menu (secondary mouse button) and choose Test Service.


Starting Transport Organizer Web UI:

Use:You must start Transport Organizer Web UI before you'll begin editing and organizing your transport requests.

Prerequisites:

You have set the parameter NON_ABAP_WBO_CLIENT.


Procedure:

1. go online to the SAP system client with the user and password that you simply want to use to start out Transport Organizer.

2. To start Transport Management System (TMS), call transaction STMS.

3. to try to to this, choose Environment -> Transport Organizer Web UI.

 This starts Transport Organizer Web UI for the client to which you're logged on.

4. within the System panel , choose the system ID of the system that you would like to organize your transport request. This is usually the development system.

5. In other way, you'll use below URL to open Transport Organizer Web UI:

http://:/sap/bc/webdynpro/sap/cts_browser?SYSID=


Customizing for Application Types:

Use:The application type is only a display attribute and doesn't determine the deployment method. Application types are utilized in the CTS_BROWSER Web Dynpro to classify attached objects. You can also add your own application types manually within the table CTS_RQ_APPLID.


Procedure:

1. Call transaction SE16.

 The Data Browser: Initial Screen appears.

2. In the Table Name field, enter CTS_RQ_APPLID.

3. Choose Table Contents or Enter.

 The Data Browser: Table CTS_RQ_APPLID: Selection Screen appears.

4. Click on  Execute button leaving the application field empty.

 The Table CTS_RQ_APPLID screen appears.

5. Click on Create button if the application type doesn’t exist.

 The Insert Table CTS_RQ_APPLID screen appears.

6. Enter the name of the application within the Application field.

 When you choose the F4 help within the Application field, the application name you entered appears within the list box.

7. Enter an outline of your application type within the Description field.

8. Save your entries.


Defining and Configuring Non-ABAP Systems:

Use:When you create a transport landscape in Transport Management System (TMS), you define how you want objects to be transported between systems in the different phases (development, quality assurance, and production) of the software lifecycle.


Prerequisites:

You have configured the CTS Deploy web service.

Creating Non-ABAP Systems:

You are in your TMS domain controller.

1. Call transaction STMS.

2. Choose System Overview.

3. Select SAP System -> Create -> Non-ABAP System.

 The TMS: Configure Non-ABAP System panel is displayed.

4. Create the non-ABAP system with a system ID and an outline .

5. Select the CTS system because the communication system.

6. Make the following settings, depending on whether your system is a source system or a target system (or both):

 o Non-ABAP system as source system

 Under Source System Settings, select the Activate Transport Organizer flag and enter the client where you would like to use Transport Organizer.

 o Non-ABAP system as target system

 Select the Activate Deployment Service flag under Target System Settings, Select the preferred deployment methods filling out the remainder of the fields accordingly.

7. Provide system user and password for your preferred deployment methods.

8. Save your settings and ensure that you simply want to distribute the TMS configuration.

All parameters and their values will automatically be generated bu the system now by default. To display these parameters, select your system within the system overview and choose the Transport Tool tab page.


Configuring Transport Routes:

1. Goto STMS and choose Transport Routes in Overview menu

2. it'll open below window to configure Transport Routes. Change to Edit Mode as below

3. In Menu Option: Configuration -> Standard Configuration -> Select appropriate Configuration option consistent with your landscape requirements.

 Here we have selected Development and Production System.

4. Provide both Development System and Production system SIDs 

5. it'll create Transport Routes in between above two mentioned systems. Save the configuration.

6. In the popup screen click Yes to distribute and Activate the configuration.


Configuring the Destination Service:

Use:You must first use RFC to connect your SAP application system ( before you can attach objects to transport requests directly in the application;such as SAP NetWeaver PI or SAP NetWeaver Portal) to the CTS server. This enables your application to talk with the transport system.


Prerequisites:

• You have change authorization in Visual Administrator.

• you've got a user with the acceptable authorizations in SAP NetWeaver Application Server Java.


Procedure:

1. Open Visual Administrator in SAP Application Server Java.

2. Opt Cluster -> Server -> Services -> Destinations.

3. Create an RFC connection naming it as sap.com/com.sap.tc.di.CTSserver by choosing Create.

4. Under Connection Settings, provide the connection data of the CTS server.

5. Under Logon Data, select the present User (Logon Ticket) option as authentication for the connection to your CTS server. We recommend that you use Single Sign-On (SSO).

If you can't use SSO, select the Configured User option and enter your preferred language, a client, and an appropriate user and password.

Enter the client entered within the parameter NON_ABAP_WBO_CLIENT in TMS.

6. Under Repository Connection and Pool Settings, use the default settings.

7. Save your entries.

If you would like to check the connection, choose Save and Test.


Choosing a Transport Strategy:

Use:You can influence the behavior of the transport system once you create and release transport requests by configuring the strategy parameters. In this manner, we can provide optimum support for your chosen transport process (automatic or manual creation and release of requests).

You only require these parameters for applications that have a close coupling with the CTS system (such as SAP NetWeaver Portal systems and SAP NetWeaver PI systems).

Prerequisites:

You have configured the connection between your application and therefore the CTS server.

Procedure:

1. Call transaction STMS.

2. Choose Overview ® Systems.

3. Select a system.

4. The screen Display TMS Configuration: System appears.

5. Choose the Transport Tool tab page.

6. Switch to change mode.

7. Add the following parameters:


o WBO_GET_REQ_STRATEGY - smart

Once you export an object from an SAP NetWeaver portal system or an SAP NetWeaver PI system, transport request will be automatically created.

The following values are possible:

§ Smart

The system creates a transport request (if not already available) and flags it because the standard request.

§ Tagged

This is configured because the default value within the system. You must have created a transport request already in Transport Organizer Web UI and flagged it because the standard request.


o WBO_REL_REQ_STRATEGY - Manual

Transport request will be automatically released  in an SAP NetWeaver portal system or an SAP NetWeaver PI system.

The following values are possible:

§ Auto

Transport request will be released automatically from the system as soon as an object is added to the request in an SAP NetWeaver portal system or an SAP NetWeaver PI system.

§ Manual

This is configured because the default value within the system. You must release the transport request manually or set the worth of the parameter to Auto.


Create Transport Request using Transport Organizer Web UI

1. Use below URL to access Transport Organizer:

'Protocol'://'server':'Web AS Port'/sap/bc/webdynpro/sap/cts_browser?SYSID='SID of Development System as Configured in TMS'

E.g.: http://pwdf4156.wdf.sap.corp:8002/sap/bc/webdynpro/sap/cts_browser?SYSID=CAI

2. Transport Organizer will look like below. Click on Create Request to create new Request.

3. Mention Short Description and Owner of Request. Project field can be left blank.

4. Click on Attach Object to connect non ABAP Object to move Request.

5. In crop up window, select Client and Browse for the file and click on on OK

o Client: look for the file on your desktop and ensure by choosing OK.

o Server: Search the directory defined within the parameter NON_ABAP_WBO_INBOX for the acceptable source system. In the directory, select the file and confirm by choosing OK.

6. you'll check the attached Non-ABAP Object in Object List Tab as below:

7. Now click on Release to Release the Request to move Queue.

Document References:

1. https://websmp108.sap-ag.de/changecontrol

2.http://help.sap.com/saphelp_nw70/helpdata/EN/45/ec25370fdc3481e10000000a1553f6/frameset.htm