On the following pages, you can find some information what has to be configuredif you would like to use the Change and Transport System (CTS) of AS ABAP totransport your components developed with SAP NetWeaver DevelopmentInfrastructure (NWDI) e.g. from your development to your test and productiveruntime systems.

1

Here you see the situation of ABAP transport landscapes and Java landscapeswith NWDI before CTS provided the option to transport Java componentsdeveloped by the help of NWDI. Two separate tools and transport landscapes hadto be used – one for the Java parts (CMS) and one for the ABAP parts (TMS).

2

Since SAP NetWeaver 7.0 SP14 a tight integration for NWDI into CTS is possible.During the assembly step, the assembled SCA file will be automatically attachedto a TMS transport request if the respective track is configured to be used withCTS.If you are using Dual Stack systems, changes to ABAP and Java objects can betransported together with TMS – in one single tool, in one transport request.

3

To be able to use CTS for Java, some configuration steps are required. You canfind the details on the SAP Help Portal. On the CTS system, you have to configurethe Deploy Web Service and activate the Transport Organizer Web UI. In addition,you have to create representations of your runtime systems and connect them bythe help of transport landscapes. This is done in transaction STMS. On the NWDI,you have to configure a destination which establishes the connection to the CTSsystem. In addition, you have to configure the tracks which you would like to usewith CTS. The following slides show some details.

4

Starting with SAP NetWeaver 7.0 including enhancement package 1, you have tomaintain the destination in the NetWeaver Administrator on the NWDI system. Youcan only maintain one destination. This means that you use your NWDI with oneCTS system. The destination has to be namedsap.com/com.sap.tc.di.CTSserver.

5

In releases prior to SAP NetWeaver 7.0 including enhancement package 1, youhave to maintain the destination in the Visual Administrator on the NWDI system.You can only maintain one destination. This means that you use your NWDI withone CTS system. The destination has to be namedsap.com/com.sap.tc.di.CTSserver.

6

If you use CMS with CTS, the connection to CTS is done in the assembly step. InTMS, you have to create a landscape consisting of the representations of yourruntime systems and transport routes between them. The example above shows athree system landscape consisting of a development, a test and a productivesystem. When you assemble an SCA, you can attach it to a transport request forEPD in our example.

7

If you would like to use a certain track with CTS, you have to configure this in thetrack data. Enable the option ‘Connect to CTS’ and name your runtime systemwhich is used for development (=the first system in your transport landscape inTMS) as ‘CTS Upload System’ (if no cons runtime system is used).

8

9

These screenshots show how the integration of CTS in CMS looks like. In the topright corner of the transport studio, the user can find a link to the TransportOrganizer Web UI. He can use it e.g. to check the available transport requests,create a new one or check the import status of already released transportrequests. When the user clicks on Assemble Component(s)… a new windowopens up to set the Assembly Options. On this screen, the user can decide aboutthe transport request to be used. A link to the Transport Organizer Web UI isprovided as well. In addition, the user can add some documentation to thetransport request via the input field Note.

10

Now – let‘s have a short look at the development process within a track. Adeveloper imports the development configuration of the stage „Development“ intohis Developer Studio. Here he starts development and every change is recordedwithin DTR activities. With the CheckIn, he decides to store it in the DTRworkspace to make it visible for all other developers working in that track. With theActivate step he starts the central build process on CBS to see if his coding workstogether with the active changes of all other project team members. With asuccessful activation the buildspace is updated with the new archives and thedeployment to the Development System is triggered. Here the developer can testif his application is running. After that first integration test, he can release hischanges. With the release he hands-over to the administrator. The Change list isnow waiting for import into the Consolidation system. The developer can nowperform the import. With the import the DTR workspace and CBS buildspace ofthe Consolidation Development Configuration are updated and if everythingworked fine, the deployment is triggered to the Consolidation system. After thatthe Software Component can be assembled – a SCA file is created. Now the SCAfile can be imported (deployed) to a Test and after a successful testing phase thechanges can be approved and imported to the Production System.

11

Test and Production in a CTS-integrated scenario are configured as TMS non-ABAP systems. That means there is no runtime system configured for TEST andPRODUCTION within the CMS track.

12

Starting with SAP NetWeaver 7.0 including enhancement package 1 it is possibleto configure a Single System Track, where the Consolidation system is deleted.

13

A Single System Track can be configured in the CMS Landscape Configuration –Track Data. Note: there is no way back - once you changed a track to be a SingleSystem Track. After you checked the checkbox „Development System only“, thedevelopment configuration, workspaces and buildspace for the Consolidationsystem are deleted. The tab „Consolidation“ is no longer available in the TransportStudio of CMS for this track.

14

Compared to the development process before, the import to the consolidationsystem is of course not needed anymore in a Single System Track. Therefore theintegration to CTS takes place earlier and the CMS administrator just assemblesand attaches the SCA file.Note: In a single system track the assembled SCA will contain the sources of thedev/active workspace and the archives of the development system buildspace.In NWDS the developer still needs to ‚Release‘ his changes. This is especiallyrequired if you use repair connections (between several tracks if the single systemtrack is the source track).

15

16

17

18