How To Setup CM Services - SAP · 6.3 Configuring NWDI ... The integration with CTS+ is possible...

SAP NetWeaverHow-To Guide

How To... Setup CM Services

Applicable Releases:

SAP enhancement package 1 Support Package 6 for SAP NetWeaver® 7.0

IT Practice / Topic Area:Unified Lifecycle Management

IT Scenario / Capability:Software Lifecycle Management

Version 1.1

May 2013

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The information containedherein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,i5/OS, POWER, POWER5, OpenPower and PowerPC aretrademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Readerare either trademarks or registered trademarks of AdobeSystems Incorporated in the United States and/or othercountries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registeredtrademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAPNetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world.All other product and service names mentioned are thetrademarks of their respective companies. Data containedin this document serves informational purposes only.National product specifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAPGroup products and services are those that are set forth inthe express warranty statements accompanying suchproducts and services, if any. Nothing herein should beconstrued as constituting an additional warranty.

These materials are provided “as is” without a warranty ofany kind, either express or implied, including but notlimited to, the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind includingwithout limitation direct, special, indirect, or consequentialdamages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links or other items containedwithin these materials. SAP has no control over theinformation that you may access through the use of hotlinks contained in these materials and does not endorseyour use of third party web pages nor provide any warrantywhatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplifythe product implementation. While specific productfeatures and procedures typically are explained in apractical business context, it is not implied that thosefeatures and procedures are the only approach in solving aspecific business problem using SAP NetWeaver. Shouldyou wish to receive additional information, clarification orsupport, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)included in this documentation are only examples and arenot intended to be used in a productive systemenvironment. The Code is only intended better explain andvisualize the syntax and phrasing rules of certain coding.SAP does not warrant the correctness and completeness ofthe Code given herein, and SAP shall not be liable forerrors or damages caused by the usage of the Code, exceptif such damages were caused by SAP intentionally orgrossly negligent.

Disclaimer

Some components of this product are based on Java™. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is onlyto be used by SAP’s Support Services and may not bemodified or altered in any way.

Document HistoryDocument Version Description

1.00 First official release of this guide

1.10 Updated Recommendations

Typographic ConventionsType Style Description

Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, graphictitles, and table titles

Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.

Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

IconsIcon Description

Caution

Note or Important

Example

Recommendation or Tip

Table of Contents

1. Scenario ...........................................................................................................................1

2. System Requirements .....................................................................................................2

3. Background Information .................................................................................................3

4. Introduction .....................................................................................................................44.1 Landscape Options ...................................................................................................54.2 Source Transport ......................................................................................................64.3 Deployable Transport (SCA Transport) .....................................................................8

5. Recommendations & Restrictions ................................................................................ 10

6. Initial Setup and Configuration of CM Services ........................................................... 126.1 Assumptions ........................................................................................................... 126.2 Configuring SLD ..................................................................................................... 136.3 Configuring NWDI ................................................................................................... 136.4 Mapping Roles in UME ........................................................................................... 196.5 Configuring Connections ......................................................................................... 21

6.5.1 Configurations on the CM Services Server .................................................. 216.5.2 Configuring the CTS+ System ..................................................................... 24

7. System Landscape Configuration ................................................................................ 327.1 Creating a Non-ABAP System with Development Configuration .............................. 337.2 Configuring the Development Configuration ............................................................ 377.3 Required Software Component Archives ................................................................. 39

7.3.1 Initial Configuration of an Upload System .................................................... 397.3.2 Transport and Import Required Software Component Archives ................... 42

7.4 Landscape Configuration ........................................................................................ 487.4.1 Landscape Configuration for Source Transport ........................................... 487.4.2 Landscape Configuration for Deployable Transport ..................................... 52

8. Development and Export Process ................................................................................ 548.1 Development Process ............................................................................................. 548.2 Activity Transport .................................................................................................... 668.3 SCA Export and Transport ...................................................................................... 68

9. Troubleshooting ............................................................................................................ 739.1 CTS Transporter Exception ..................................................................................... 73

9.1.1 CANNOT_GET_DOMAIN ........................................................................... 739.1.2 FILE_NOT_PERSISTABLE ........................................................................ 74

9.2 CTS Packager Exception “Access Denied” .............................................................. 75

10. Appendix ........................................................................................................................ 7610.1 Extending the Landscape ........................................................................................ 7610.2 Configure Users and Groups manually on CM Services server ................................ 77

11. Abbreviations ................................................................................................................ 79

How To…Setup CM Services

April 2013 1

1. ScenarioStarting with enhancement package 1 for SAP NetWeaver 7.0, SAP provides the first version of theCM Services (Change Management Services).CMS provides the functionality to perform two different tasks. The first task is the systemadministration part where you setup a track in order to create a transport landscape for your runtimesystems and the second task is the configuration of so called development configurations for yourdevelopment cycle and the export of deployable units (SCA files – Software Component Archives).The integration with CTS+ is possible during the assembly step where the sca file is attached to aCTS+ transport request. But in that case – a track configuration is still needed.With the introduction of CTS+ and CM Services a clear separation of both tasks is provided. The firsttask is covered by CTS+, where you define your non-ABAP runtime systems and your transport route.The remaining second part – development configurations and export - is now handled by the new CMServices. Therefore a CMS track is not needed on the Java side. With the close integration of CMServices with the mechanism of the enhanced Change and Transport System (CTS+) you canmanage your development configurations together with your transport landscape via the CTS+system.

Note Of course it is still possible to use NWDI with CMS with or without CTS+ integration.

With the CM Services two scenarios are possible. You can transport sources (Activity Transport orSCA transport) or you can transport deployables (SCAs). For the transport of sources, you can decideon which granularity level you want to transport. The transport of source changes on a small granularlevel which is called Activity Transport is a new functionality provided with the CM Services.The transport of activities is triggered directly from within the SAP NetWeaver Developer Studio via theTransport View in the Development Configuration Perspective of the NWDS. When releasing anactivity the sources are exported and attached to a transport request in CTS+. The file format of theattached activity package is called *.dip (Development Infrastructure Package). Transporting sourcesthrough the system landscape requires a development configuration (with DTR workspaces and CBSbuildspace) for each target system that is part of the transport route in your landscape. The import isstarted from the import queue of your target system on the CTS+ system. Compared to the transportof deployable units the import process for sources triggers a rebuild within each CBS buildspace. TheSDAs that are affected by the changed sources will be re-built and deployed to the target runtimesystem. This process is in most cases much quicker than transporting the whole software component(SCA) if there are just small changes on an upper level. But if your change is done in a very basic DCthat is used by many other DCs, a re-build for all the dependent DCs will be done as well. In that case,the transport of activities might not speed up the process.

CAUTIONKeep in mind that as a consequence of the Source Transport, sources are available inthe corresponding DTR workspaces for all systems of your landscape – even for theproductive system. Therefore you should set ACLs in these workspaces to prevent anaccidentally source change by your developers. For more details take a look at the SAPlibraryhttp://help.sap.com/saphelp_nw70ehp1/helpdata/en/c9/d94388f62c8f478eadd4d1902d7101/frameset.htm.

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c9/d94388f62c8f478eadd4d1902d7101/frameset.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c9/d94388f62c8f478eadd4d1902d7101/frameset.htm


April 2013 2

A combination of both options – transporting Activities and SCAs on a source level might make sense.Take a look at chapters ‘Landscape Options’ and ‘Recommendations & Restrictions’ to learn more.Read these chapters carefully and decide for which option you would like to go before you configureyour landscape.

The second scenario offered by the CM Services is the transport of deployables (SCA and SDA forexperts). The developer activates his activities and an administrator/project lead manages the exportof the corresponding software components by the use of a new DI Export UI. During the export the scafile is attached to a CTS+ transport request. Imports are again done via TMS in the CTS+ system. Tosetup such a scenario, a development configuration is needed only for your development system. Allother non-ABAP runtime systems in your landscape are pure deployable targets.

The main purpose of this guide is to explain how to setup CM Services and make your systemlandscape ready for the use of CM Services. The required configuration steps to enable the CMServices are described step-by-step. The two landscape scenarios or options (Source Transport andDeployable Transport) are explained for a simple transport landscape and the development process isshown in a simple example. We assume that you have a basic knowledge about CTS+ and NWDI.

2. System Requirements

In order to be able to use CM Services you need the following systems:Enhanced Change and Transport System (CTS+) on enhancement package 1 for SAPNetWeaver 7.0 or higher

o SAP NetWeaver Application Server ABAP (AS ABAP) which acts as Domain Controller Communication System

o SAP NetWeaver Application Server Java (AS Java)

SAP NetWeaver Development Infrastructure (NWDI) on enhancement package 1 for SAPNetWeaver 7.0 or higher with the components

o DTR (Design Time Repository) (Usage Type DI)o CBS (Component Build Service) (Usage Type DI)

NoteIt is possible but not recommended to use the components DTR and CBS of NWDI on arelease lower than enhancement package 1 for SAP NetWeaver 7.0. For more detailsand restrictions see SAP Note 1361909.

The NWDI component CMS is still part of the usage type DI installation (NWDI) but notneeded or used in case your development and transport process is based on CMServices. Nevertheless you can use CMS and CM Services in parallel.

SAP NetWeaver Developer Studio (NWDS) on enhancement package 1 for SAPNetWeaver Composition Environment 7.1 or on enhancement package 1 for SAP NetWeaver7.0 or higher.


April 2013 3

CAUTIONIf you plan to develop Web Dynpro for Java, make sure that the Runtime Systems andthe NWDS are on the same release and SP level.

System Landscape Directory (SLD): no special requirements but make sure your SLDcontent is always up to date

Runtime Systems: no special requirements

CAUTIONIf you plan to develop Web Dynpro for Java, make sure that the Runtime Systems andthe NWDS are on the same release and SP level.

The CM Services are part of every AS Java installation as of enhancement package 1 for SAPNetWeaver 7.0. The recommendation is to setup CM Services on the NWDI system.

CAUTIONFollowing the recommendation requires that your NWDI is on enhancement package 1for SAP NetWeaver 7.0 at least. Using an NWDI on a previous release is not possible.

Please see the chapter ‘Introduction’ and ’Recommendations & Restrictions’ for more details on that.

NotePlease always check the central CM Services SAP Note 1361909.

3. Background InformationDocumentation about CTS+ in the SAP Library at:http://help.sap.com/saphelp_nw70ehp1/helpdata/en/bb/6fab6036a146baa58e42fac032ab7b/frameset.htmDocumentation about CM Services in the SAP Library at:http://help.sap.com/saphelp_nw70ehp1/helpdata/en/84/1fabea09f048c69b48d8e08de38c95/frameset.htmBest Practice Guide for Implementing CTS+ (does not include CM Services):https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10456aac-44f7-2a10-1fbe-8b7bcd7bcd58

SAP Notes:Central CM Services Note: 1361909Central note on CTS+: 1003674CMS / CM Services – What to use in which scenario: 1775838

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/bb/6fab6036a146baa58e42fac032ab7b/frameset.htm


http://help.sap.com/saphelp_nw70ehp1/helpdata/en/84/1fabea09f048c69b48d8e08de38c95/frameset.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/84/1fabea09f048c69b48d8e08de38c95/frameset.htm

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10456aac-44f7-2a10-1fbe-8b7bcd7bcd58


https://service.sap.com/sap/support/notes/1361909




April 2013 4

4. IntroductionMainly two systems are relevant for configuring the CM Services. You need a system, where NWDI(DTR and CBS) is installed and one that can be used for hosting the transport landscape (CTS+system). An SLD is required as well to register the Development Configurations and to create e.g.Products and Software Components.The following figure shows an overview of the available components on your systems if both NWDIand CTS+-System are on enhancement package 1 for SAP NetWeaver 7.0.

Figure 1: Components on NWDI and CTS+ System

Before starting configuring the CM Services, you should think about the systems that you have andhow you could use them. One option for the CTS+-System would be to use the SAP SolutionManager. Take a look in the Best Practice Guide for Implementing CTS+ to read more about possiblesystem landscapes and options for setting up CTS+ in general.

CAUTIONKeep in mind that the CTS system has to be on enhancement package 1 for SAPNetWeaver 7.0 as a basis release. If you are using SAP Solution Manager for CTS+,make sure that your SAP Solution Manager is using this basis release at least. The SPnaming of SAP Solution Manager is different from its SAP NetWeaver Support Packagelevel.

Starting with enhancement package 1 for SAP NetWeaver 7.0, SAP provides CM Services as part ofeach AS Java. So CM Services and some other components (e.g. SLD, Deploy WS) are available onboth systems (NWDI and CTS+). It is up to you and depends on the scenario on which server youwant to use CM Services and the Deploy Web Service. Please take a look at the chapter ‘



April 2013 5

Recommendations & Restrictions’ before you start.

CAUTIONFor the usage of CM Services (e.g. Activity Transport and/or SCA Transport) you have touse the CM Services on the same system as the Deploy Web Service - in that use caseyou can’t separate these two components. For more Information on the Deploy WebService, take a look athttp://help.sap.com/saphelp_nw70ehp1/helpdata/en/2b/326d6274134cea8b217f24889d19c1/frameset.htm .

NoteIf you are already using CTS+ for other scenarios e.g. for transporting Portal objects, youmight already have configured a Deploy Web Service. This does not influence yourdecision on where to run the CM Services. The configuration for the Deploy Web Servicein SM59 can be copied to point to another AS Java – details are described later on(chapter ‘Checking and Creating Logical Port’ and ‘Checking and Creating RFCConnections’).

The NWDI consists of three components: Design Time Repository (DTR), Component Build Service(CBS) and Change Management Service (CMS). Please use CM Services (on enhancement package1 for SAP NetWeaver 7.0) only in case you see advantages in the newly provided features. Then youdon’t need CMS anymore. Otherwise you can still use CMS with its track configuration.In case you have existing tracks and want to use the new features of CM Services for newdevelopment landscapes, you can use CMS and CM Services in parallel. In both cases DTR isneeded to store the sources and CBS will build the components and store the archives. The migrationfrom CMS to CM Services is described in the guide ‘How to switch from CMS to CM Services’.This guide will explain step-by-step how to setup CM Services initially, how to setup a systemlandscape for transport and with development configurations and how to work with the newly providedfeatures by CM Services.The configuration steps how to setup CM Services initially are explained in chapter ‘Initial Setup andConfiguration of CM Services’.In case the CM Services are already enabled in your system landscape, you need to decide whichkind of landscape option (see chapter ‘Landscape Options’) you want to enable. Depending on thescenario, the system landscape configuration described in chapter ‘System Landscape Configuration’looks different.Chapter ‘Development and Export Process’ focuses on the development and export process andexplains how to work with development configurations in the NWDS, how to bundle an activity forbeing transported via CTS+ and how to export a software component archive (SCA) to be attached toa CTS+ transport request with the new Export UI.

4.1Landscape OptionsThis guide is based on a landscape example with three runtime systems: a Development (DEV), aTest (TEST) and a Production (PROD) System.There are basically two options how you could transport your Java based development objects usingCM Services:

1. Source Transport (Granularity Options: Activity or SCA)2. Deployable Transport (SCAs)

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2b/326d6274134cea8b217f24889d19c1/frameset.htm


http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40941f5c-087a-2d10-95b3-8be402af3358


April 2013 6

The question that you have to ask yourself is ‘What do I like to transport?’

Dependent on the transport scenario, the configuration of your system landscape looks different. Themain difference is, for Source Transport a development configuration is needed for your source(development) system and each target system in your transport route. For a pure DeployableTransport a development configuration is needed just for the Source/Development System.

NoteIn case you enable your landscape for transport option 1 you have the possibility totransport on a small granularity level – the so called Activity Transport. Or you cantransport the complete software component (SCA) as well. In case your landscape isenabled for option 2 only, a transport on the level of small source code changes (ActivityTransport) is not possible. Usually you transport the complete SCA. It is recommendednot to use the SDA Export except you really know what you do. This option is only madefor experts. You have to make sure that all dependent SDAs that were changed are partof the same transport request or were already transported.

CAUTIONIn case you decide to use the Source Transport, you have to setup each target systemwith a development configuration. It is not possible to have e.g. the DEV system with adevelopment configuration, the TEST without and the PROD again with a developmentconfiguration. A so called mixed scenario concerning development configurations is notpossible and not supported!

Let’s look at the two options in more detail.

4.2Source TransportWe assume the system landscape with DEV, TEST and PROD is setup and configured with adevelopment configuration for each system in the transport route. That means your landscape isconfigured and ready for source transport. The steps how to do so are explained in chapter ‘SystemLandscape Configuration’.For such a landscape you have now the possibility to transport your source changes based onActivities or based on a complete Software Component (SCA).First we’ll have a look at the Activity Transport. The following figure shows an overview on how theprocess of transporting Activities works. Consider this as a logical view on the components involved inthe process.


April 2013 7

Figure 2: Process for Activity Transport – logical view

As a developer the first thing you have to do is to import the Development Configuration into yourNetWeaver Developer Studio and to synchronize the sources if you would like to change an existingapplication.The first two steps (checkin and activate) after having finished your development in the NWDS remainthe same – it doesn’t make any difference if you are using CM Services or CMS. Checking in anactivity and activating it are unchanged. During the activation process the changes will be deployed tothe DEV system. This hasn’t changed compared to the CMS behavior. Only when releasing anActivity, you will find a new dialog. A transport request from CTS+ will be provided or you can create anew one by the help of the Transport Organizer Web UI (a Web Dynpro ABAP application that runs onthe CTS system). The DIP-file containing the changed source files is attached to the transport requestby then. With this, the developer has finished his work in the Developer Studio. As a next step, thetransport request has to be released. This could be done either by the help of the Transport OrganizerWeb UI or in an automated way.

NoteBoth, the behavior of the CTS+ System when asking for a request and what happensafter having attached something depend on the transport strategy that you haveconfigured. It is possible to let the system create requests and to make it release themautomatically. Take a look at the parameters for details:http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htm

Now, the transport request is ready for import in the next system – the TEST system in our example.You can start the import via transaction STMS in TMS of the CTS+ system. If you do so, a rebuild ofthe changed DCs and the dependent ones will be done for the TEST system and the respective CBSbuildspace is updated. The sources will become part of the respective workspaces for the TESTDevelopment Configuration in DTR. After that, your new or changed application will become available

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htm


April 2013 8

via deployment on the TEST system and is ready for import into PROD. Here the same process isbeing triggered during import for the PROD system.In case you decide to use the SCA based transport (with sources), you will use the new DI Export UI.The process is explained in the next chapter or in much more detail in chapter SCA Export andTransport.

NotePlease keep in mind, that the usage of the DI Export UI is exactly the same for the SCAtransport with or without sources. The sources of an SCA file will be assembled in bothcases. But it depends on the landscape configuration what will happen during the importprocess. In a source transport enabled landscape, the DI CM Services will trigger theDTR workspace update, CBS rebuild and deployment to the target system. In alandscape that is configured for deployable transport only, the sca file will be deployed tothe target system via the Deploy WS directly.

4.3Deployable Transport (SCA Transport)Instead of the Activity Transport (with or without an SCA based transport from time to time), it ispossible to configure your landscape for a pure deployable transport by the help of the CM Services.In this case, you transport an SCA – which means: a deployable – through your landscape. ADevelopment Configuration is only required for the development (DEV) system. All other systems inyour transport route are pure deploy targets where you’d like to import your application. For thesesystems you only have to make sure that there is the Java Deploy URL configured for the deployment.The process for this is shown in the following figure:

Figure 3: Process for SCA Transport – logical view

NoteFrom the developer point of view, nothing has changed. You have to import theDevelopment Configuration and synchronize the sources at first. After that, you can startdeveloping. Checking in and activating the changes is done as described before. You


April 2013 9

can release the activity, but in case your changes will be transported via SCA export, youdon’t need to do it explicitly. That means the export process will take all activatedactivities that are related to the SCA export. For activities that are listed as ‘Waiting’ inthe transport view of the Developer Studio, the export process triggers the automaticrelease.

To export and attach the SCA to a transport request a new UI is used - the DI Export Web UI. You cancall this UI from the Development Configuration UI (see chapter ‘SCA Export and Transport’ for moredetails). As a first step, you have to choose the system from where you would like to export an SCA –this is usually your source/development system. After that, you can choose one SCA from those thatare to be developed in this system. The Export UI will guide you through the process of adding theSCA to a transport request. For this process, the same is valid as it was for the Activity Transport: aTransport Request can be taken automatically from the CTS+ system or you can create one by thehelp of the Transport Organizer Web UI. Also after having added the SCA to the request, the requestcan be released automatically or manually – this depends on the transport strategy that youconfigured.As mentioned before, the activities related to the SCA export that are listed as ‘Waiting’ in thetransport view of the NWDS are released automatically after the export was done.


April 2013 10

5. Recommendations & RestrictionsThis chapter covers some recommendations and restrictions but in general you should check the CMServices central Note 1361909 and 1775838 (CMS / CM Services – What to use in which scenario).Enhancement Package 1 for SAP NetWeaver 7.0 delivers the first version of the CM Services. Checkwhether the CM Services offer benefits for you and if yes, use them. If not, you can continue usingCMS.There are some restrictions for the usage of CM Services in enhancement package 1 for SAPNetWeaver 7.0 that you should take into consideration:

CM Services require a NWDS on enhancement package 1 for SAP NetWeaver 7.0 orenhancement package 1 for SAP NetWeaver Composition Environment 7.1 for releasing theactivity to CTS+. If you develop Web Dynpro for a runtime system which is not yet onenhancement package 1 for SAP NetWeaver, you have to use one NWDS on the release thatfits to your runtime system for developing and another one which supports CM Services forreleasing the activities.

Development Configurations managed by CTS+ are named like the system in TMS. Thismeans that the name of the development configuration is the same as the SID of the systemthat you created in TMS. In addition, the name of the development configuration consiststherefore out of three letters.

Exclude from deployment is not supported. SCA-Export: patch name can be set by customers, SP / patch level only by SAP No build-options for CM Services in enhancement package 1 for SAP NetWeaver 7.0 Solution for maintenance tracks described on SDN

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3390 is not supported for CMServices.

Repair scenarios are not supported. Mixed scenarios where sources (Activities) are transported only from a DEV to TEST and after

that, only complete SCA files are transported to the PROD System are not supported.

The following figure shows the systems which are involved in the process and recommends where torun which component.

Figure 4: Recommendations what to run where

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3390


April 2013 11

CAUTIONThe figure above might give the impression that you don’t need an AS Java on your CTS+system. For setting up CM Services as described in this guide, this is true. But if you areusing or plan to use the CTS+ system for transporting e.g. Portal objects as well, youmight need it again. For transporting Portal objects, the recommendation is to use theDeploy Web Service on the CTS+ system.

This guide assumes that you stick to the recommendations and shows the configuration steps basedon them:

Use your SAP Solution Manager as CTS+ System.

CAUTIONKeep in mind that the CTS system has to be on enhancement package 1 for SAPNetWeaver 7.0 as a basis release. If you are using SAP Solution Manager for CTS+,make sure that your SAP Solution Manager is using this basis release at least. The SPnaming of SAP Solution Manager is different from its SAP NetWeaver Support Packagelevel.

Run the CM Services together with the Deploy WS on your NWDI. It is not recommended to use the Activity Transport if you are modifying ESS or MSS sources

delivered by SAP in enhancement package 1 for SAP NetWeaver 7.0. Create a URL favorite for the DI Export Web UI in your Browser. If you decide to use the Activity Transport, use it in combination with the SCA transport. E.g. if

you did a lot of changes to very different DCs, you should transport the complete SCA insteadof a lot of source files.

Sources should only be changed in the DEV system. For the Activity Transport Scenario it istechnically possible to access (via the respective development configuration) and change thesources for your target systems. This is absolutely not recommended. Please set DTR ACLsaccordingly for the DTR workspaces of all your target systems in your transport route.

If you already configured your NWDI and you are using tracks for your development process,you can continue to do so. CM Services and CMS can’t be used together e.g. in one transportroute or track, but you could use CMS for one development project and the CM Services foranother. Both of them could use the same DTR and CBS.


April 2013 12

6. Initial Setup and Configuration of CM ServicesIn this chapter, we assume that you start from zero – this means that neither CTS+ nor NWDI or SLDare configured up to now. Concerning NWDI only the Design Time Repository (DTR) and theComponent Build Service (CBS) are needed in case you use the development and transport optionsoffered by CM Services. Therefore the configuration of the Change Management Service (CMS) is notpart of this guide. If you already configured your SLD, CTS+-System, or NWDI, take a look at theappropriate sections in this guide anyhow to find out whether your configuration fits with the oneneeded for CM Services.This chapter concentrates on the initial setup and enablement of CM Services. For the configuration ofyour system landscape see chapter ‘System Landscape Configuration’ and the usage of developmentconfigurations is described in chapter ‘Development and Export Process’.

6.1AssumptionsWe assume that you are working with two dialog users: one who is a developer (nwdi_dev) and onewho is an administrator (nwdi_adm). In addition, technical users are needed to establish connectionsetc. The dialogue users are just examples. You can use other users / user IDs for sure. Make sure thatthe same user IDs and passwords are used in SLD, NWDI, CM Services and on the CTS+ System(ABAP).This guide assumes that you are using the CM Services and SLD on your NWDI system. This wouldmean that you use an NWDI on enhancement package 1 for SAP NetWeaver 7.0. If you are not ableto do so, please check the Appendix chapter ‘Configure Users and Groups manually on CM Servicesserver‘.In addition, we assume that you are already using Web Dynpro ABAP on your CTS+. If this is not thecase, take a look on the SAP Help Portal to learn how to activate Web Dynpro ABAP for a certainsystem:http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/e86de5008b4d9ae10000000a155369/frameset.htm

NoteIn addition you will need the ABAP Web Dynpro application CTS_BROWSER to createtransport orders and attach objects. You have to carry out certain configuration steps torun and use this application.http://help.sap.com/saphelp_nw70/helpdata/en/ea/6213584a3f49119eccd7d739e55d5d/frameset.htmYou can either activate the services now or at the end of the configuration.If you receive error messages when running this application later on or if you don’t wantto activate all ICF services read the error messages carefully and activate the servicesnamed within the error messages via transaction SICF at the end of the configuration.

NoteIf your CTS system includes SL Toolset 1.0 SP4 at least, you have to activate the serviceCTS_ORGANIZER. This is the new UI used to manage transport requests for non-ABAPsystems.

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/e86de5008b4d9ae10000000a155369/frameset.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/e86de5008b4d9ae10000000a155369/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/ea/6213584a3f49119eccd7d739e55d5d/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/en/ea/6213584a3f49119eccd7d739e55d5d/frameset.htm


April 2013 13

6.2Configuring SLD...

If you are using the SLD for the first time, you can simplify the initial configuration by executing theappropriate CTC template.

1. On your SLD system, in the SAP NetWeaver Administrator (http://<host>:<port>/nwa), chooseDeploy and Change Configuration Wizard.

2. Choose the NWA_01_This wizard will execute configuration for local SLD configuration task andthen Start.

The template will guide you through a few steps. Enter a password for the SLDDSUSERaccording to your policy and continue executing the template.

3. After the configuration wizard has finished successfully, choose Return to task list.

6.3Configuring NWDI...

If you are using the NWDI for the first time, you can simplify the initial configuration by executing theappropriate CTC template.

1. On your NWDI system, in the SAP NetWeaver Administrator (http://<host>:<port>/nwa), chooseDeploy and Change Configuration Wizard.

2. Choose the Initial setup of functional unit Development Infrastructure (DI all-in-one)configuration task and then Start.The template will guide you through a few steps. Enter the required data as shown in thefollowing screens.


April 2013 14

CAUTIONOne step asks you for a master password. Remember this password – you will need itlater on.


April 2013 15

NoteThis step creates the users NWDI_ADM, NWDI_DEV and NWDI_CMSADM for you.They are all using the master password that you entered.

In the following screen, you could select Connect to a remote SLD if you do not want to use thelocal SLD for NWDI. For this guide, we are going to use the SLD on the NWDI.

In the following screen, keep the default values or enter the appropriate data for CMS and thedomain. The template still configures CMS for you – you will not use it later on. Continueexecuting the template


April 2013 16

CAUTIONOn the following screen, make sure that Create a Track is not selected.

Now, the CTC template has been executed successfully.

3. If you like to use the Source Transport, you have to modify one Access Control List (ACL) inDTR. You have to grant permissions to the group NWDI.Developers. Log on to the DTR withuser NWDI_ADM. Use the following URL to edit the file acl.xml:http://<host>:<port>/dtr/ws/system/config/active/ACLs/byPath

http://pwdf6360:50000/dtr/ws/system/config/active/ACLs/byPath


April 2013 17

4. Edit the file by clicking on the button . You now have to create an Activity for this change.Click on Checkout.

Choose In Place Edit and add the line <privilege>export</privilege> to<principal>NWDI.Developers.

Save your changes.


April 2013 18


April 2013 19

5. Check in your changes.

6.4Mapping Roles in UMENow, you have to assign the actions and roles introduced by CM Services to the appropriate users.On your NWDI server, map the SAP_DI_ADMINISTRATOR role to the NWDI.Administrator groupand the SAP_DI_DEVELOPER role to the NWDI.Developers group.

1. Open the UME of your NWDI System. Use the URL http://<server>:<port>/useradmin.Search for the group NWDI.Administrator and select it. Go to the tab Assigned Roles,choose Modify.


April 2013 20

2. In the section Available Roles, enter sap_di_administrator in the Search Criteria field andchoose Go. Select SAP_DI_ADMINISTRATOR, choose Add, and then Save.

3. Proceed accordingly to map the SAP_DI_DEVELOPER role to the NWDI.Developers group.


April 2013 21

6.5Configuring ConnectionsAs a next step, you have to connect your NWDI system – where the CM Services run - and your CTS+system. This is done via two connections. One connection points from the CTS+ system to the NWDIsystem. It is needed to call the Deploy Web Services running on the NWDI when you import atransport request. The configuration for this connection is done on the CTS+ system in thetransactions LPCONFIG and SM59. For this destination, you have to create a user on the NWDI whichis then entered as connecting user in SM59.The second connection points from the NWDI to the CTS+ system, which means from Java to ABAP.This connection is created as a JCo connection/destination on the NWDI server and is required to beable to retrieve e.g. a transport request from CTS when exporting an Activity. For this connection, youhave to create a user on your CTS+ system (here: SolMan Solution Manager).

6.5.1 Configurations on the CM Services ServerThis chapter explains the basic steps for configuring the connection between the CM Services and theCTS+ system in short. For more information about the configuration, see the SAP Library at:http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2b/326d6274134cea8b217f24889d19c1/frameset.htm.

6.5.1.1 Creating User for RFC Destinations from CTS+ System to CMServices

This section describes how to create a user on the CM Services Server that is needed forcommunication between the CTS+ system and the CM Services.

1. On the start page (http://<host>:<port>) of your CM Services system, choose UserAdministration Create User. Follow the screens.




April 2013 22

2. On the following screen, enter a real password (you won’t have to change it later on), the lastname and choose technical user as security policy.

3. On the Assigned Roles tab page, assign the roles SAP_CTS_DEPLOY andSAP_CTS_DI_CONFIGURATOR to this user.

NoteIf your company policy says that you should only assign roles to groups, you can also doso in here. Create the user, create a group with the roles above and assign the user tothe group.For more information, seehttp://help.sap.com/saphelp_nw70ehp1/helpdata/de/2b/326d6274134cea8b217f24889d19c1/frameset.htm.

http://help.sap.com/saphelp_nw70ehp1/helpdata/de/2b/326d6274134cea8b217f24889d19c1/frameset.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/de/2b/326d6274134cea8b217f24889d19c1/frameset.htm


April 2013 23

6.5.1.2 Creating an RFC Destination from CM Services to CTS+1. In the SAP NetWeaver Administrator of your CM Services system, choose System Management

Configuration Destinations and then New. Enter sap.com/com.sap.tc.di.CTSserverin the Name field and choose type RFC.

2. Enter the required data as shown in the following screen.System: Server of the CTS+ systemSystem Number: Number of the CTS+ systemSystem ID: SID of your CTS+ communication systemClient: Client in which the Transport Organizer is running (same value as used whencreating the none-ABAP system on the CTS+ system for parameterNON_ABAP_WBO_CLIENT in the non ABAP system)

NOTEIn the Logon Data section, select Current User (Logon Ticket) as authentication for theconnection to the CTS communication system. We recommend that you use SSO.If you cannot use SSO or want to use a dedicated service user, select the ConfiguredUser option and enter your preferred language, a client, and an appropriate service userand password. Note that this configuration is not recommended.The permissions required for each user who should be able to use this connection aredescribed in the chapter ‘Creating a user for the developer’.


April 2013 24

3. Save your entries and choose Test Destination. Make sure that you receive the message Test issuccessful on top of the screen.

6.5.2 Configuring the CTS+ System

6.5.2.1 Creating a User for the DeveloperDue to the decision in Creating an RFC Destination from CM Services to CTS+ to use the LogonTicket option the user you are logged on to the Java system needs special permission on the CTS+system as well. Make sure that the user has assigned the correct role on the CTS+ system.

1. On your CTS+ system, call transaction SU01.2. Create the user NWDI_DEV

NoteYou have to create a user for every developer on the CTS+ system. The users arerequired on the CTS+ system e.g. to get a transport requests when exporting. You canuse the user IDs of your developers. Make sure that you use IDs which allow to be usedin SSO mode. NWDI_DEV is used as an example in this guide


April 2013 25

If the users already exist, continue with the profile that is required and assign it to all ofthe users.

3. On the Logon data tab page, don’t enter the master password as you have to change it whenlogging in the first time. Change the password to the master password you specified in chapterConfiguring NWDI. On the Roles tab page, assign the role SAP_CTS_PLUS. Make sure that thefollowing necessary values are assigned to this role (to do so, open transaction PFCG anddisplay the role SAP_CTS_PLUS. On the Authorizations tab page choose Display authorizationdata:

Authorization Check for ICF Access (object: S_ICF):ICF_FIELD: DEST, PROXY, SERVICEICF_VALUE: *

Authorization Check for RFC Access (object: S_RFC):RFC_NAME: CTS_WBO_DIS, EPSF, RFC1, SDIFRUNTIME, STPA, SYSTRFC_TYPE: FUGR

Administration Functions in the Change and Transport System (object: S_CTS_ADMI):CTS_ADMFCT: EPS1, EPS2

Authorization for file access (object: S_DATASET):ACTVT: 06, 33, 34, A6, A7FILENAME: *PROGRAM: CL_CTS_ASSIST_BROWSER=========CP, SAPLEPSF,SAPLSCTS_EXE_FILE, SAPLSCTS_RELEASE, SAPLSLOG, SAPLSTFI, SAPLSTPA,SAPLSTPP, SAPLSTRF, SAPLTMSM, SAPLTMST

Transport Organizer (object: S_TRANSPRT):ACTVT: 01 (Create or generate), 02 (Change), 03 (Display), 05 (Lock), 06 (Delete),23 (Maintain), 43 (Release), 50 (Move), 60 (Import), 65 (Reorganize), 75 (Remove), 78(Assign), 90 (Copy)TTYPE: CUST, DTRA, PIEC, TRAN


April 2013 26

4. If not all necessary values are assigned to role SAP_CTS_PLUS, copy this role ( ), name thenew role Z_CTS_PLUS, and choose Copy all.

5. Enter a description and click on Propose Profile Name to get an automatically generated profilename. Save your entries.


April 2013 27

6. Click on Change Authorization Data and assign all missing necessary values. Go one step back(F3) and save your entries.

7. On the User tab page, click on User Comparison and then on Complete comparison.8. Assign this newly created and activated role Z_CTS_PLUS to user NWDI_DEV (transaction PFCG,

Roles tab page). Remove the role SAP_CTS_PLUS.

6.5.2.2 Checking and Creating Logical Ports1. Two logical ports are needed for the communication between the CTS+ system and the CM

Services system: CTSCONFIG and CTSDEPLOY_DI. Check whether they are available on yourCTS+ system and if not create them as described in this chapter. Log on to your CTS+ systemin client 000 and call transaction LPCONFIG. Ignore the pop-up message.

CAUTIONWe don’t use CTSDEPLOY port in this guide as it might be already in use for othertransports on your SAP Solution Manager - e.g. portal content. For the CM Services, we


April 2013 28

need an additional port as we are going to use the Deploy Web Service on the NWDIsystem, not on AS Java of your CTS+ system

2. Enter CO_TDIDICONFIGURATION_SERVICE as Proxy Class and CTSCONFIG as Logical Port.

3. Click on Display. If the port does not exist, create it with the parameter values shown on thefollowing screenshot.

CAUTIONMake sure that Default Port is not selected and that the logical port is active.

4. Repeat steps 2 and 3 with proxy class CO_TFLDEPLOY_PROXY_VI_DOCUMENT and the logicalport CTSDEPLOY_DI. If the port does not exist, create it with the parameter values shown on thefollowing screenshot:


April 2013 29

ImportantPlease note that in this configuration, both ports use the same HTTP-destinationCTSCONFIG.

6.5.2.3 Checking and Creating RFC ConnectionsAn RFC connection is needed for the communication between the CTS+ system and the CM Servicessystem: CTSCONFIG. This is the destination that you have already specified in the logical port asHTTP destination in Checking and Creating Logical Ports. The required user CTS_RFC for this RFCconnection with special permission on the CM Services system has already been created in stepCreating User for RFC Destinations from CTS+ System to CM Services.

1. Log on to the client of your CTS+ system that you are using for transports (=where the transportorganizer web UI runs). Call transaction SM59 and open the HTTP Connections to ExternalServer section. Check whether the connection CTSCONFIG is already available. If not, create itwith the following parameter values:Enter CTSCONFIG as RFC Destination, a description, the Target Host, and as Service No theport of your server where the CM Services and the Deploy Web Service are running. Make surethat the Connection Type is G.

NOTEThe Deploy Web Service (CTSDEPLOY) for your portal/PI transports can be hosted on adifferent server. For Portal, the Deploy Web Services runs usually on the AS JAVA ofyour SAP Solution Manager. For CM Services the CTS Deploy Web Service on the CMServices server has to be used (see ‘Introduction’).


April 2013 30

2. On the Logon & Security tab page, select Basic Authentication and enter CTS_RFC as logonuser. Enter the password you have specified in Creating User for RFC Destinations from CTS+System to CM Services.

3. On the Special Options tab page, select No Timeout.

4. Choose Connection Test.

NOTEThe connection test only tests the connection to the server without using the specifieduser and password.


April 2013 31


April 2013 32

7. System Landscape ConfigurationAssuming that your CTS+ system and NWDI with CM Services are enabled, the following chapterdescribes how to setup your transport and development configuration landscape.

ExampleIn this guide a three system landscape example with DEV, TEST and PROD is used. So you need tosetup a non-ABAP DEV, TEST and PROD system in TMS of your CTS+ system. For each system,you have to decide if a development configuration is needed and if the system is a source and/ortarget system. In addition the transport routes have to be created accordingly.

When creating a development configuration for a system, DTR workspaces and CBS buildspaces arecreated automatically. But initially they are empty! Therefore you have to fill these buildspaces (andworkspaces) with the required libraries (compared to the CMS “Checking In Software ComponentArchives”). This is done with the help of a so called Upload system for which you create a transportrequest, attach the required SCA files and transport them at least to the DEV system. In case youenable the Source Transport, this transport request has to be imported into all target systems (here:TEST and PROD).

Source Transport (Activity and/or SCA based):UPLOAD: non-ABAP source systemDEV: non-ABAP source and target system with development configurationTEST: non-ABAP target system with development configurationPROD: non-ABAP target system with development configuration

Transport Routes:UPLOAD DEV: Consolidation RouteDEV TEST: Consolidation Route + Delivery RouteTEST PROD: Delivery Route

Deployable Transport (SCA):UPLOAD: non-ABAP source systemDEV: non-ABAP source and target system with development configurationTEST: non-ABAP target systemPROD: non-ABAP target system

Transport Routes:UPLOAD DEV: Consolidation RouteDEV TEST: Consolidation RouteTEST PROD: Delivery Route

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/44/312b1a8bea3ec8e10000000a1553f6/frameset.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/44/312b1a8bea3ec8e10000000a1553f6/frameset.htm


April 2013 33

CAUTIONThe following scenario is not recommended: Configure the TEST system as sourcesystem to be able to create a transport request, export and attach an SCA file (comparedto the CONS System in a CMS track) and then transport it to the PROD system.

Independent of the transport scenario (Source or Deployable Transport) the following configurationparts have to be done in any case (described in the following chapters):

1. Create a non-ABAP DEV System with Development Configuration (Source and TargetSystem)

2. Create a non-ABAP Upload System (Source System)3. Create a transport route between Upload and DEV system4. Create a transport request for the Upload System and attach all required libraries (dependent

SCA files)5. Import the transport request with the required libraries to the DEV system

7.1Creating a Non-ABAP System with DevelopmentConfiguration

The basic configuration for CM Services is done and you can create the non-ABAP systems and thetransport route configuration for your runtime systems on your CTS+ System. This chapter describeshow to configure the development system (DEV), which is a source (to be able to create a transportrequest and attach dip or sca files) and target system (for the deployment during the activationprocess triggered in NWDS) with a development configuration. This is true for all use cases using CMServices.

ImportantDon’t create a non-ABAP system for your NWDI. The transport route consists of theruntime systems.

1. On your CTS+ system (domain controller), call transaction STMS. In the System Overview,choose SAP System Create Non-ABAP-System.


April 2013 34

2. Enter the required data.

o System: Enter the SID of your development runtime system, for example, JD1.

TipIf the SID is already used, you can also use any 3 letter name that has not yetbeen used in the domain. It is not required that the runtime systems are shown inCTS by their real SID – but it simplifies keeping an overview if you do so.

o Communication System: Choose the system where you configured lpconfig andthe RFC destination CTSCONFIG. Usually, this is your CTS+ system.

o Development Infrastructure: Check this option so that a development configuration willbe created for your system JD1.

o Source System Settings: Activate the Transport Organizer to be able to createtransport requests for this system. Choose this option for each and every systemwhere you would like to do exports (usually, this should be done only for yourdevelopment system)

o Target System Settings: Specify your development runtime system by choosing themethod SDM/DC and enter host and system number for this Java system.

NOTEThis configuration is different from what you might know when using CTS+, forexample, for the Portal. The Development system has to have bothconfigurations, source and target system. The target system is needed to be ableto do deployments of your applications to this runtime during the activation stepvia NWDS/NWDI.

3. When first saving a non-ABAP system with development configuration (Create DevelopmentConfiguration is selected) additional data is required.

a. In the System Landscape Directory window, enter the URL of the SLD used by NWDIthat you would like to use for NWDI development (as specified when executing theNWDI CTC Template).


April 2013 35

b. Specify user and password to be used by CM Services to commnuicate with the SLD.Enter NWDI_CMSADM as user and the password of this user (for example, the masterpassword used during the execution of the NWDI CTC template).

c. Enter the user used by CM Services to communicate with DTR/CBS. This is also userNWDI_CMSADM with the appropriate password.

4. Save and distribute your changes.

5. Set user and password for the deployment. In case of SDM, you only have to enter a password.Leave the entry for User to SDM.

NOTEFor runtime systems with SDM (SAP NetWeaver AS Java 7.0 and enhancementpackages) use SDM as user. As of SAP NetWeaver AS Java 7.1 the Deploy Controller isused for deployments. In this case, enter a user with deploy permission and theappropriate password.

6. After the changes have been saved and distributed, the Development Configuration UI appears.


April 2013 36

7. Before being able to continue with configuring the Development Configuration, you have toadapt the transport tool parameters for the created non-ABAP system. So minimize this screenfor a while and go back to transaction STMS where you just created the non-ABAP system.Select this non-ABAP system in the System Overview.

8. On the Transport Tool tab page, change the DEPLOY_WEB_SERVICE value toCTSDEPLOY_DI and check if all other parameters are correct. Save your changes.

TipChange the DEPLOY_URL to the correct deploy port if you are using runtime systemswhich are on SAP NetWeaver 7.1 or higher or SAP NetWeaver CompositionEnvironment. For AS JAVA 7.1 and higher the deploy port has to be changed tohttp://<host>:5<instance number>04.


April 2013 37

7.2Configuring the Development ConfigurationNow you can start working in the Development Configuration UI that was opened in the browserduring the saving process of the non-ABAP system.

NOTEIf the UI is not open anymore, reopen it as follows:

i. On your CTS+ system, call transaction STMS.ii. In the System Overview, double click your non-ABAP system.iii. Choose the button Development Configuration.

The Development Configuration UI appears in a new browser window.

1. Enter the Repository Location (DTR) URL for the storage and versioning of sources and theBuild Tool Location (CBS) URL for building DCs (Development Components). Use the URLs ofyour NWDI server. Choose Confirm.

2. Now you can add Software Component Versions (SCV) that you want to be developed in thisDevelopment Configuration. Choose Add in the Software Component Definition section. Allavailable software components are read from SLD and are provided in a list.


April 2013 38

3. Filter the list according to the SCVs you want to add to the Development Configuration, selectthem, and choose Add, and then Close.

NoteIf the SCVs you want to add are not available in this list, define them in the SLD asdescribed in the SAP Library at:http://help.sap.com/saphelp_nw70ehp1/helpdata/en/6a/44b2420e71c511e10000000a1550b0/frameset.htm.

The SCVs are added to your Development Configuration now.

4. To view the dependencies of the SCVs, click on the triangle at the beginning of a row.

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/6a/44b2420e71c511e10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/6a/44b2420e71c511e10000000a1550b0/frameset.htm


April 2013 39

NoteThe software components of the second level which are not marked as ‘Developed’ haveto be imported into the development configuration as they are needed for the build. Formore information on how to do this, see Creating an Upload System.

5. Save your changes. Now, the links to Design Time Repository and Component Build Service atthe top of the screen are active.

Now the development system configuration is done. But before you can start working with thedevelopment configuration as described in chapter ‘Development and Export Process’ therequired libraries need to be imported with the help of a so called Upload System as explainedin the following chapters.

7.3Required Software Component ArchivesIn order to be able to develop an application for AS Java you need to import some basic libraries(required Software Component Archives) into CBS. To be able to do so, a transport request with theselibraries needs to be created and imported into the development system (for example, JD1) and allother systems of the transport route for which you created a development configuration(DI_SYSTEM=TRUE). For this transport request (and future transport requests with newer libraries,for example, after SP updates of your AS Java) you need an upload system. This upload system doesnot require a server or an installation of an AS Java. It is just a ‘dummy’ system that is needed to beable to create transport requests.

7.3.1 Initial Configuration of an Upload System1. On your CTS+ system, call transaction STMS. In the System Overview, choose SAP System

Create Non-ABAP System.


April 2013 40

2. Enter the required data. Make sure you do not select Create Development Configuration andActivate Deployment Service. This system is only needed as a source system.


7.3.1.1 Creating a Transport Route between Upload System andDevelopment System

1. On your CTS+ system, call transaction STMS and choose System Landscape.


April 2013 41

2. Switch to change mode and select your upload system and your development system from thelist of available systems and add them to the landscape.

3. Choose Add Transport Route and connect the systems.

4. Create a consolidation transport route and a transport layer.


April 2013 42

5. Save and distribute your configuration.

Now, the systems are connected and you can start using the route for transporting.

7.3.2 Transport and Import Required Software ComponentArchives

This chapter describes how to create a transport request, attach the required software componentarchives and import them to the development system.

TipAs the required libraries might be needed in case of Source Transport in all your targetsystems, it would be better to create the request and do the import into the DEV systemlater after your complete system landscape has been configured (with TEST and PRODin our example).


April 2013 43

7.3.2.1 Creating an Upload DirectoryAs a prerequisite you need an “inbox” where the files can be taken from. You can create this folder onthe client side as well as on the server side. If you choose to create the folder on the server side, seeSAP Note 1408532.

1. In your file system, create a new folder named, for example, “Inbox”.2. By default, the required files are stored in the folder usr/sap/trans/EPS/in of your AS Java

system. Copy the files for the SCAs that are defined (developed and required) in thedevelopment configuration to your inbox. Alternatively, you can share this folder.

CAUTIONMake sure that the SCA files and your development runtime have a correspondingrelease and SP level.

3. If you want to modify SCVs from SAP and you want the changes to be available in thedevelopment system, you would have to copy the relevant archives to your inbox to transportthem.

7.3.2.2 Creating the Upload Transport Request1. On the CTS+ system, call transaction STMS and choose Transport Organizer Web UI ( ).

2. Select your upload system, choose Copy ( ), and then Continue.


April 2013 44

A browser window opens.3. Choose Create Request, enter the required data, and choose Create.

A transport request is created.


April 2013 45

4. On the Object List tab page, choose Attach.5. Select the application NWDI, and Client or Server depending on where your inbox is located. If

your inbox is on client side, browse for the required SCA files and choose Ok. (This inbox wascreated on client side.)

CAUTIONUpload of big files from the client may fail. In this case, choose the option Server andupload the files from there (see SAP Note 1408532).

Repeat this step to attach all required SCAs to the request.


April 2013 46

6. Choose Release to release the request.

7. Select Status Released as soon as the release has finished. On the Logs tab page you can seethe target system information.

7.3.2.3 Import the Transport Request into Development System1. On the CTS+ system, call transaction STMS and choose Import Overview ( ).2. Double-click your development system and choose Refresh.


April 2013 47

3. Select the request and choose Import Request ( ).

4. Maintain the import properties according to your needs and choose Ok ( ).

5. Choose Yes to start the import.

6. Wait until the import is finished (use the Refresh option). The import has finished successfully.

Now the needed libraries (and sources if you want to modify some SAP or Partner SCVs) areimported into DTR/CBS of your development system and your developers can start working.

CAUTIONPlease don’t forget to import this transport request with the required libraries to all yourtarget systems in case your landscape is configured for Source Transport.


April 2013 48

7.4Landscape ConfigurationThe configuration that was described in the previous chapters is needed for both landscape scenariosshown in this chapter. The decision for transporting sources or deployables does not have anyinfluence on what has to be configured for the upload and the development system. Now, dependingon your transport scenario, the configuration of your target systems in your transport route might lookdifferent. This chapter focuses on the configuration of your target systems (here: TEST and PROD)and the required transport routes.

7.4.1 Landscape Configuration for Source TransportThe option to transport activities – which are the new/changed sources – through the completelandscape has the consequence that a rebuild has to be done for each and every system. Theprerequisite for being able to do a build is that a development configuration exists. So if you decide togo for this option, you would have to create a development configuration when creating the system inTMS. The landscape would then look like shown on the following figure.

Figure: Landscape for Activity Transports (and SCA Transport)

NoteA landscape that is configured for Activity Transport can be used for SCA transport aswell. Therefore you could also use a combination of both, e.g. the Activity transport on aregular level and the SCA transport from time to time. It depends on the amount ofchanges and your development process to decide when to use what. The ActivityTransport is much faster in case of small changes but in addition using the SCA transportgives you the option to get a consolidated status.

As you can see, each system configured in TMS has to have a development configuration and a JavaURL assigned as it acts as deploy target. As a consequence, Workspaces in DTR and Buildspace inCBS are created for each system. The name of the Buildspace is the same as the SID in TMS. InDTR, you will find the SID as part of the path to your active and inactive Workspaces.


April 2013 49

Whenever an import is started, a re-build is triggered for the SDAs which contain the changed sourcefiles and for all dependent SDAs. The sources are integrated into the respective DTR workspaces.If you use this option, you have to be aware that a re-build is done on each and every system – evenfor the productive one.To configure your systems in TMS accordingly, you have to set the option Development Configurationfor each and every system and define the Development Configuration in the dialog coming up in TMS.In our example it has to be done for the systems TEST and PROD. The following figures show as anexample what you should fill in when configuring the target systems (here: JQ1 as TEST system andJP1 as PROD system). Repeat these steps for all your target systems in your landscape.

1. On your CTS+ system, call transaction STMS. In the System Overview, create a new non-ABAPsystem for quality/test as a target system with development configuration. Save your entries.

2. Enter the SDM password.


April 2013 50

3. Repeat these steps to create a new system for production.

4. Save and distribute the changes.5. In the Development Configuration of JQ1 and JP1 copy the Development Configuration (see

provided feature “Copy Definition of Development Configuration from” for that) of JD1 and saveyour changes.

After you did these configuration steps for each system (here: TEST and PROD), you can create thetransport routes. You have configured a consolidation route between the Upload System and DEV.Now you need a consolidation route from DEV to TEST as you have to create transport requests forDEV. In addition, you would need a delivery route from DEV to TEST (to be able to import the required


April 2013 51

Software Component Archives created via transport requests in the Upload System) and a deliveryroute from TEST to PROD.

6. Call transaction STMS and choose Transport Routes.

7. Select your systems and add them to the landscape.

8. Add the transport routes.

9. Draw a line between JD1 and JQ1. Select Consolidation. Repeat that step and draw a linebetween JD1 and JQ1 and select Delivery.

CAUTIONNote that you have to configure two routes between development and test. Theconsolidation route is needed to export new developments from development and bringthem to the target systems. The delivery route is required to be able to transport all of therequests that where created for the upload system as well. Using source transportsrequires that all of the libraries are part of the test system and all other target systems inyour transport route.

10. Draw a line between JQ1 and JP1. Select Delivery.


April 2013 52


Other systems can for sure be part of the same landscape as well. All the options which are availablein TMS for creating landscapes can be used for Java landscapes as well.

7.4.2 Landscape Configuration for Deployable TransportThe second option for designing your landscape would be to export SCAs from the developmentsystem and import them into the test and production system which are pure deployable targets.The following figure shows how your landscape would look like in this case:

Figure: Landscape for transporting SCAs

CAUTIONA landscape that is configured for deployable transport only can’t be used for ActivityTransport (Source Transport).


April 2013 53

A development Configuration is needed for the development system only. After you have finished yourdevelopment, you would use the DI Export UI to attach the SCA to a transport request. The exportedSCA file always includes the sources. But if your landscape is configured for pure deployment only,the sources will be ignored and only the deployable will be used during the import process. Thismeans that the granularity of a transport is a whole SCA, not only the changes any more, but there isno need for re-builds on e.g. test and productive systems.From a configuration perspective, this would mean that you must not set the option CreateDevelopment Configuration for any other system than the development system. If you create a non-ABAP system in TMS, this would mean that you only have to define the settings in the section TargetSystem Settings. The following figure shows as an example the configuration for the PROD systemJP1. The same configuration is needed for our TEST system JQ1.

After having created the systems, you would have to add the transport routes. As described before, aconsolidation route between Upload and DEV system is required. In addition you need a consolidationroute from development (DEV) to the test (TEST) system. And a delivery route from TEST to PROD isrequired.


April 2013 54

8. Development and Export ProcessIn this chapter you can find out how the development configuration that you created above is used inthe SAP NetWeaver Developer Studio (NWDS). Creating a simple Web Dynpro application is used asan example to show the process. If you have already used NWDS and if you are familiar with thedevelopment process, you don’t have to go through the details of this chapter. In this case see chapter‘Activity Transport’ to learn what is different when releasing an Activity. Chapter ‘SCA Export andTransport’ explains the usage of the new Export UI to export sca files and attach them to transportrequests.

8.1Development ProcessThis chapter explains how to import and work with development configurations with the help of asimple Web Dynpro example. The checkin and activate step is shown as it is needed for bothtransport scenarios.

1. In the NWDS, open the Development Configurations perspective.


April 2013 55

2. Open the Wizard for Importing Development Configurations (Click on ).

3. Select remote and enter User name and Password.

4. The following warning message appears. Choose Ok.


April 2013 56

5. Enter the SLD URL and choose Ok.

6. The development configurations available on the respective SLD are shown. Choose the onethat fits (the one that was created before). Choose Next.

You can see a summary of the Development Configuration that you chose. Choose Finish.


April 2013 57

7. In the development Configurations perspective, go to the Inactive DCs.

8. Create a new development component project for one of your SCs: right-click on the SC.Choose Create a new development component project.

9. Enter the required data, choose Next.


April 2013 58

10. Choose New Activity, enter the required data, and choose Ok.

11. Choose Next and then Finish. A new development component has been created.


April 2013 59

12. The Web Dynpro perspective opens up. Create a new Web Dynpro component.

13. Enter the required data and choose Finish, and then Add.


April 2013 60

14. Assign the changes to an existing (or new) activity.

The following is shown:

15. Double-click on MyComponentView.


April 2013 61

16. Choose Outline.

17. On the Properties tab page, edit the value of the text field.


April 2013 62

18. Choose Save All Metadata ( ).

19. In the Web Dynpro Explorer, create a new application.

20. Enter the required data and choose Finish.


April 2013 63

21. Add the sources to DTR.

22. Select the Activity where you would like to add this application. Choose Ok. The application iscreated.


April 2013 64

23. Switch to the Development Configuration Perspective, on the Open Activities tab page, right-click your activity and choose Check in.

24. Enter the required data and choose Ok.


April 2013 65

25. After the check in has finished, activate your DC. Right-click on your Activity in the ActivationView.Activation means that the sources will be built in CBS and after a successful build the respectiveSDA files will be deployed to the development system. After that the sources are active andvisible to all.

26. Choose Open Request View.

Click Refresh from time to time until the activation has finished.


April 2013 66

Now the activity has been activated. In case you decide to transport the activity on source levelproceed with chapter ‘Activity Transport’. For the transport of the complete software componentarchive (SCA) see chapter ‘SCA Export and Transport’.

8.2Activity Transport

1. In the Transport View, right-click your activity, and choose Release.

2. A transport request has been created automatically due to the SMART request strategy. Releasethe transport. Select Monitor Request. This will open the Transport Organizer Web UIimmediately after the release has finished.


April 2013 67

After this process has finished, you see the following in the Transport View:

And in the Transport Organizer Web UI:


April 2013 68

The Object List contains the Development Infrastructure Package (DIP) files that were createdduring the release in NWDS. They contain the sources to be transported through the landscape.Releasing an Activity results in only one DIP file. The screenshot shows two DIP files as thesame request was used for another export as well in this example.Now you can proceed with the release of the transport request and import into the next targetsystem (TEST) in your transport landscape. For more details on that have a look athttp://help.sap.com/saphelp_nw70ehp1/helpdata/en/bb/6fab6036a146baa58e42fac032ab7b/frameset.htm .

NoteIn case of errors, see Troubleshooting.

8.3SCA Export and TransportBefore starting to use the export service, you should have setup a landscape on your CTS+ systemwhich contains all the systems where you would like to import the SCAs. You might e.g. have asystem named JQ1 which serves as testing system (TEST) and should therefore be the first onewhere you’d like to import the SCA. The SCA Export and Transport is possible for both landscapeconfigurations – source and deployable transport. The way how to use the DI Export UI does notdiffer. The exported SCA always contains the sources, but they will only be used in a landscape that isconfigured for source transport.

NoteThe export process will take all activated activities that are related to the SCA export. Foractivities that are listed as ‘Waiting’ in the transport view of the Developer Studio, theexport process triggers the automatic release.

1. On your CTS+ system, call transaction STMS. In the System Overview, double-click yourdevelopment system.

2. Choose Development Configuration.3. Log on with user nwdi_adm.

4. Choose the hyperlink DI Export Service or use the URLhttp://<host>:<port>/webdynpro/dispatcher/sap.com/tc~di~cts~config~webui/Export.




April 2013 69

5. Select your system ID, the system ID of your development system (here: JD1), select SCAExport and choose Next.

CAUTIONIt is recommended not to use the SDA Export except you really know what you do. Thisoption is only made for experts. You have to make sure that all dependent SDAs thatwere changed are part of the same transport request or were already transported.

6. Choose the SCA that you would like to export and choose Next.

CAUTIONYou can only export one SCA at a time. It is not possible to choose more than one line. Ifyou would like to attach more than one SCA to a transport request, you can do so bygoing through the Export steps twice.


April 2013 70

7. Decide whether you would like to include source pointer and / or archives in the SCA andchoose Next.

NotePlease notice that the exported SCA will always include the sources. But you have the option tooptimize the export step and amount of exported data. In case you check the checkmark“Include Sources”, the full content of the corresponding workspaces is physically exported. Thisis only required or recommended in case you transport sources and your source DTR is notavailable during import time. Or you need to archive your software components for backupreasons.It is recommended not to use this option as then the Design Time Repository (DTR) flags thecurrent sources in a workspace and only a logical export using source pointer is performed. Thisreduces the export time and the size of your SCA significantly.The flag “include Archives” is needed to add the build and deployable archives into the sca file.This is needed in case your landscape is configured for deployable transport.

8. If you used the Advanced option in the Stop on Error section, the extended text AdvancedOptions selected will become visible.

9. Due to the connection to your CTS+ system and its request strategy SMART, a transportrequest has been retrieved from CTS+ automatically. If you would like to, you can add a note tothe transport request that e.g. contains information about the SCA. Choose Next.


April 2013 71

10. The summary appears. To export the SCA file, choose Export.

11. After the export has finished successfully, the export log is shown at the bottom.


April 2013 72

12. In the Transport Organizer Web UI, on the Properties tab page, you can find out about theTarget system for this request. If there was more than one target system configured in CTS,then you would also be able to choose the target system in here.

Now you can proceed with the release of the transport request. In transaction STMS you can seethe transport request in the import queue of your test/quality system JQ1 (TEST). For moredetails on that have a look athttp://help.sap.com/saphelp_nw70ehp1/helpdata/en/bb/6fab6036a146baa58e42fac032ab7b/frameset.htm .

NoteIn case of errors, see Troubleshooting.




April 2013 73

9. Troubleshooting

When releasing an activity, the following errors may occur:

9.1CTS Transporter Exception

9.1.1 CANNOT_GET_DOMAIN

Reason:The communication system of your non-ABAP system JD1 is not maintained on the developer’sengine.Solution:

1. Go to C:\WINDOWS\system32\drivers\etc and open the file Services with an editor (forexample, Word pad).

2. Check if the sapms<SID> entry exist and if the port is correct. If not, correct them. For moreinformation, see SAP Note 1155884.

3. Restart the SAP NetWeaver Developer Studio.


April 2013 74

9.1.2 FILE_NOT_PERSISTABLE

Reason:RFC authorizations are missing.Solution:Apply SAP Note 1003674.


April 2013 75

9.2CTS Packager Exception “Access Denied”

Solution:See steps 3 to 5 in chapter ‘Configuring NWDI’.


April 2013 76

10. Appendix

10.1 Extending the LandscapeIn case you need to extend your landscape, you have to make sure to import previous transportrequests. For a system landscape that is enabled for source transport - target systems withdevelopment configurations – it is essential to import the required libraries.

We assume you created your new non-ABAP target system with or without development configurationas described before. In addition the required transport route is available. The next steps explain howto import transport requests (that have been already transported) to this new target system once. Forall upcoming transports this new target system will be delivered via the regular transport route.

1. On your CTS+ system, call transaction STMS. In the System Overview, select the system youwant to add a transport request to.

2. Choose Extras Other Requests Add.

3. Enter the transport request with the required files and choose Ok. The request has been addedto the queue and can be imported.

4. Select your requests in the import queue and import them.


April 2013 77

5. Repeat these steps for all new systems in your landscape.

10.2 Configure Users and Groups manually on CMServices server

If you run the CM Services on another server than your DTR and CBS, you can’t use the CTCtemplate Initial setup of functional unit Development Infrastructure (DI all-in-one) to set up the usersNWDI_CMSADM, NWDI_ADM and NWDI_DEV.

To set up these users manually you first need to create 2 groups, assign roles to the groups and finallycreate the users and assign them to the groups.1. Logon to UME on CM Services server (http://<host>:<port>/useradmin)2. Create the groups NWDI.Administrators and NWDI.Developers.3. Assign the role SAP_DI_ADMINISTRATOR to group NWDI.Administrators and role

SAP_DI_DEVELOPER to group NWDI.Developers. Optional: In case SLD is also located on CMServices Server add role SAP_SLD_ORGANIZER to group NWDI.Administrators andSAP_SLD_DEVELOPER to group NWDI.Developers

4. Create users (in dual stack case user creation might be possible only on ABAP stack):- user NWDI_CMSADM – used for communication between NWDI components. Make sure to

select the entry ‘Technical User’ as Security Policy.


April 2013 78

- user NWDI_ADM – used as demo logon user for admins.- user NWDI_DEV – user as demo logon user for developers.

NoteFor users NWDI_DEV and NWDI_ADM a password change after first logon will be necessary.

5. Assign group NWDI.Administrators to user NWDI_CMSADM and to user NWDI_ADM and assigngroup NWDI.Developers to user NWDI_DEV.


April 2013 79

11. AbbreviationsThe document uses several abbreviations. The long text for the abbreviations can be found in thistable.

Abbreviation Long Text

NW SAP NetWeaver

EHP1 SAP enhancement package1 for SAP NetWeaver 7.0

NWDI SAP NetWeaver Development Infrastructure

DTR Design Time Repository

CBS Component Build Service

CMS Change Management Service

BS SAP Business Suite

CTS(+) (Enhanced) Change and Transport System

PI / XI SAP NetWeaver Process Integration

SDM Software Deployment Manager

NWDS SAP NetWeaver Developer Studio

CE SAP NetWeaver Composition Environment

www.sdn.sap.com/irj/sdn/howtoguides

How To Setup CM Services - SAP · 6.3 Configuring NWDI ... The integration with CTS+ is possible...

Documents

Transcript of How To Setup CM Services - SAP · 6.3 Configuring NWDI ... The integration with CTS+ is possible...