Performing Configuration Steps for Non-ABAP Transports

The CTS Deploy Web service connects the ABAP transport tools with the deployment tools in the non-ABAP applications. The transport control program tp communicates with the CTS Deploy Web service when deploying the non-ABAP objects.

For more information, see Configuring the CTS Deploy Web Service.

If you use the SAP NetWeaver Development Infrastructure (NWDI) with CM Services, then you must configure the CTS Config Web service. The CTS Config Web service provides the connection between the ABAP transport system and the system where the CM Services run.

For more information, see Configuring the CTS Config Web Service.

By creating a transport landscape in the Transport Management System (TMS), you specify the roles the individual systems play in the software lifecycle. To transport non-ABAP objects in your transport landscape, you require non-ABAP or dual-stack systems:

• Configuring non-ABAP systems

  CTS handles non-ABAP systems as virtual systems, which means they require an ABAP communication system. The transport control program tp runs in this communication system. For source systems, the Transport Organizer is used in this communication system.

  Recommendation Also use the Domain Controller as ABAP communication system.

  For more information, see Defining and Configuring Non-ABAP Systems.

• Configuring Dual-Stack Systems

  Dual-stack systems consist of an SAP NetWeaver Application Server ABAP and an SAP NetWeaver Application Server Java. If you want to perform transports for both application servers, then you first have to include the SAP NetWeaver Application Server ABAP in the transport domain and configure it. Then you can configure the SAP Application Server Java or a dual-stack system.

  Note that for dual-stack systems you must execute configuration steps on all source and target systems. This is different than with non-ABAP systems where the configuration only takes place on the ABAP communication system.

  For more information, see Configuring Dual Stack Systems.

With activity-based SDA transports you can transport the runtime objects that belong to activities using transport requests and deploy them in the target system.

For more information, see Configuring Systems for Activity-Based SDA Transports.

For more information on activity-based SDA transports, refer to Activity-Based SDA Transports under Using CM Services in the Development Infrastructure administration documentation of the SAP NetWeaver Application Server Java.

With Activity Transports you can attach activities directly from the SAP NetWeaver Developer Studio to transport requests and transport them.

For more information, see Configuring Systems for Activity Transports.

For more information on activity transports, refer to Activity Transports under Using CM Services in the Development Infrastructure administration documentation of the SAP NetWeaver Application Server Java.

Non-ABAP systems and dual-stack systems can be the source or target of transports. When you create non-ABAP systems or dual-stack systems as source or target systems in your transport landscape, they are configured automatically with the appropriate standard settings. If you want to adjust these settings to your system landscape, you can modify the relevant parameters accordingly:

• Changing the Standard Settings for Source Systems

  If you want to change the standard settings you used to create your source systems, you must adjust the automatically-generated parameters for your source systems or add new parameters.

  For further information, see Changing the Standard Settings for Source Systems.

• Changing the Standard Settings for Target Systems

  If you want to change the standard settings you used to create your target systems, you must adjust the automatically generated deployment parameters or add new parameters.

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

To be able to manage transport requests with the Transport Organizer Web UI, you first have to activate the service for the Transport Organizer Web UI. If you want to use the object list browser you also have to activate the related service.

For more information, see Activating Services for Transport Organizer Web UI.

For more information on Transport Organizer Web UI, see Managing Transports of Non-ABAP Objects.

For more information on object lists, see Using the Object List.

If you want to attach objects of other non-ABAP or non-SAP applications to transport requests directly with the Transport Organizer, then you can connect these applications with the Change and Transport System by making them known in the domain.

For more information, see Configuring Source Systems for Further Applications.

If you want to transport objects directly from your non-ABAP application, you must connect the application to the transport system. In this way you can closely couple your application with the Change and Transport System. Execute the following configuration steps to be able to influence the export behavior of your application:

1. Configure the connection from your application system to the ABAP communication system.

   To be able to attach objects in the application (for example, SAP HANA, SAP Process Integration, or SAP Enterprise Portal) directly to transport requests, you must set up a remote connection with the ABAP communication system for your source system. This enables your application to communicate with the transport system. This connection can be set up using an export destination on the AS Java, or using the CTS Export Web Service, depending on the application.

   For more information on configuring export destinations, see Configuring Export Destinations. For more information on how to configure the CTS Export Web Service, refer to the guide of the application that uses the CTS Export Web Service.

2. Define the transport strategy.

   You can influence the behavior of the transport system when you create and release transport requests by configuring the strategy parameters. In this way, you provide optimum support for the transport process that you have chosen for closely coupled applications (automatic/manual creation or automatic/manual release of requests).

   For more information, see Choosing a Transport Strategy.

3. Optional: Choose a method for the file transfer from the source system to the CTS Server.

   To add non-ABAP objects to a transport request, you must transfer these objects (files) to the CTS server on which Transport Organizer is located.

   For more information, see Defining a Method for the File Transfer from the Source System.

1. Optional: Specify the method for the file transfer from the CTS Server to the target system.

   For more information, see Defining a Method for the File Transfer to Target System.

2. Optional and only possible if the CTS plug-in is installed in the SAP system: Connect the target systems of further applications with the Change and Transport System.

   If you want to transport objects of other non-ABAP or non-SAP application with Change and Transport System, then you must connect the target systems of these applications with the Change and Transport System.

   For more information, see Configuring Target Systems for Further Applications.