NWDI CTS+ integration

[Former Member]

Hello,

we have a NWDI (NW1) 7.0 SP15, three (DH2,QH2,PH2) abap systems nw7.0 with SP14 and three (DP2, QP2, PP2) java systems 7.0 with sp14. With the docu "best practices for implementing cts" we have set up CTS with close coupling between NWDI and CTS. If we create an development and transport the development through the track to prod, we can't see at which point the java development should go to the cts.

All systems dh2, dp2, qp2, qh2, pp2, ph2 have been created on the domain controller dh2.

System DP2 contains the following values.

CTS_SYSTEM_TYPE = JAVA

DEPLOY_URL = http://hostname:50218

NON_ABAP_SYSTEM = 1

NON_ABAP_WBO_CLIENT = 200

WBO_FILE_TRANSFER = STREAM

WBO_GET_REQ_STRATEGY = SMART

WBO_REL_REQ_STRATEGY = AUTO

In NWDI (NW1) we have activated "Connected to CTS" for all tracks.

CTS Upload SYSTEM = DP2

Also we have create with the viusal administrator on NWDI (NW1) the rfc

with the following values.

sap.com/com.sap.tc.di.CTSserver

System = hostname

System number = 00

System ID = DH2

Gateway-Host = hostname

Gateway-Service = sapgw00

Logon Data

Client 200

Username j2ee_adm_dp2

I can open the transport web organiser and create non-abap-transports, but I can only attached files from the filesystem level. I can't find files from the NWDI.

Regards,

Alexander

[Jordan_Stanchev · Accepted solution]

Hello,

Prerequisites for a leading Change and Transport System (CTS) system are that the CTS leading system is configured as the TMS domain controller where the non-ABAP systems with their transport route configuration are maintained centrally.

Configure the AS Java System - For the integration of CTS in NWDI, the following configuration has to be done:

1. Create a new RFC destination for the NWDI server. It must be named sap.com/com.sap.tc.di.CTSserver. See Maintaining RFC Destinations in the SAP documentaiton help.

2. Configure the CMS track. You must mark the track as Connected to CTS and specify the exact CTS upload system to connect the track to. The TMS non-ABAP source system for that transport route is the SID of the runtime system that is connected as NWDI Development System.

To do that, open the CMS Web UI and under the Landscape Configurator, choose Track Data. Enable the Connected to CTS checkbox and configure the CTS system to connect to.

Performing the Transport - Export

3. Go to the NWDI Transport Studio and transport the changes through the NWDI track. For more information, see Transports with the NWDI: Transport Studio.

4. bold The CTS integration takes place within the Assembly step.bold For more information, see Creating a Software Component Archive (Assembly).

5. During assembly, the SCA file is attached to the TMS transport request.

6. If no automatic release is configured for that TMS source system, release the transport request in the Transport Organizer Web UI (which is opened using the Follow CTS Request button).

Performing the Transport - Import

1. The transport request is waiting for import in the import queue of the target system.

2. The import is done in TMS. For more information, see Importing Transport Requests with Non-ABAP Objects in SAP CTS help.

Does this help in your case?

Regards, Jordan

Edited by: Jordan Stanchev on Aug 8, 2008 8:37 AM

[Former Member]

Hello Jordon,

thanks for your reply. In the meantime we have solved our problem. CTS+ is running with close coupling integration.

Regards,

Alexander Türk