How To... Setup CM Services

Transcription

1 SAP NetWeaver How-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

2 Copyright 2013 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, 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 are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, 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 and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in 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 affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way.

3 Document History Document Version Description 1.00 First official release of this guide 1.10 Updated Recommendations

4 Typographic Conventions Type Style Example Text Example text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Emphasized words or phrases in body text, graphic titles, and table titles Icons Icon Description Caution Note or Important Example Recommendation or Tip Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

5 Table of Contents 1. Scenario System Requirements Background Information Introduction Landscape Options Source Transport Deployable Transport (SCA Transport) Recommendations & Restrictions Initial Setup and Configuration of CM Services Assumptions Configuring SLD Configuring NWDI Mapping Roles in UME Configuring Connections Configurations on the CM Services Server Configuring the CTS+ System System Landscape Configuration Creating a Non-ABAP System with Development Configuration Configuring the Development Configuration Required Software Component Archives Initial Configuration of an Upload System Transport and Import Required Software Component Archives Landscape Configuration Landscape Configuration for Source Transport Landscape Configuration for Deployable Transport Development and Export Process Development Process Activity Transport SCA Export and Transport Troubleshooting CTS Transporter Exception CANNOT_GET_DOMAIN FILE_NOT_PERSISTABLE CTS Packager Exception Access Denied Appendix Extending the Landscape Configure Users and Groups manually on CM Services server Abbreviations... 79

6 1. Scenario Starting with enhancement package 1 for SAP NetWeaver 7.0, SAP provides the first version of the CM Services (Change Management Services). CMS provides the functionality to perform two different tasks. The first task is the system administration part where you setup a track in order to create a transport landscape for your runtime systems and the second task is the configuration of so called development configurations for your development 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 a CTS+ 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 first task 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 CM Services. Therefore a CMS track is not needed on the Java side. With the close integration of CM Services with the mechanism of the enhanced Change and Transport System (CTS+) you can manage 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 or SCA transport) or you can transport deployables (SCAs). For the transport of sources, you can decide on which granularity level you want to transport. The transport of source changes on a small granular level 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 the Transport View in the Development Configuration Perspective of the NWDS. When releasing an activity the sources are exported and attached to a transport request in CTS+. The file format of the attached activity package is called *.dip (Development Infrastructure Package). Transporting sources through the system landscape requires a development configuration (with DTR workspaces and CBS buildspace) for each target system that is part of the transport route in your landscape. The import is started from the import queue of your target system on the CTS+ system. Compared to the transport of deployable units the import process for sources triggers a rebuild within each CBS buildspace. The SDAs that are affected by the changed sources will be re-built and deployed to the target runtime system. 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 DC that 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. CAUTION Keep in mind that as a consequence of the Source Transport, sources are available in the corresponding DTR workspaces for all systems of your landscape even for the productive system. Therefore you should set ACLs in these workspaces to prevent an accidentally source change by your developers. For more details take a look at the SAP library 101/frameset.htm. April

7 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 configure your landscape. The second scenario offered by the CM Services is the transport of deployables (SCA and SDA for experts). The developer activates his activities and an administrator/project lead manages the export of the corresponding software components by the use of a new DI Export UI. During the export the sca file is attached to a CTS+ transport request. Imports are again done via TMS in the CTS+ system. To setup such a scenario, a development configuration is needed only for your development system. All other 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 system landscape ready for the use of CM Services. The required configuration steps to enable the CM Services are described step-by-step. The two landscape scenarios or options (Source Transport and Deployable Transport) are explained for a simple transport landscape and the development process is shown 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 SAP NetWeaver 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 SAP NetWeaver 7.0 or higher with the components o DTR (Design Time Repository) (Usage Type DI) o CBS (Component Build Service) (Usage Type DI) Note It is possible but not recommended to use the components DTR and CBS of NWDI on a release lower than enhancement package 1 for SAP NetWeaver 7.0. For more details and restrictions see SAP Note The NWDI component CMS is still part of the usage type DI installation (NWDI) but not needed or used in case your development and transport process is based on CM Services. Nevertheless you can use CMS and CM Services in parallel. SAP NetWeaver Developer Studio (NWDS) on enhancement package 1 for SAP NetWeaver Composition Environment 7.1 or on enhancement package 1 for SAP NetWeaver 7.0 or higher. April

8 CAUTION If you plan to develop Web Dynpro for Java, make sure that the Runtime Systems and the NWDS are on the same release and SP level. System Landscape Directory (SLD): no special requirements but make sure your SLD content is always up to date Runtime Systems: no special requirements CAUTION If you plan to develop Web Dynpro for Java, make sure that the Runtime Systems and the 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 SAP NetWeaver 7.0. The recommendation is to setup CM Services on the NWDI system. CAUTION Following the recommendation requires that your NWDI is on enhancement package 1 for 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. Note Please always check the central CM Services SAP Note Background Information Documentation about CTS+ in the SAP Library at: htm Documentation about CM Services in the SAP Library at: htm Best Practice Guide for Implementing CTS+ (does not include CM Services): 8b7bcd7bcd58 SAP Notes: Central CM Services Note: Central note on CTS+: CMS / CM Services What to use in which scenario: April

9 4. Introduction Mainly 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 NWDI and 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 and how you could use them. One option for the CTS+-System would be to use the SAP Solution Manager. Take a look in the Best Practice Guide for Implementing CTS+ to read more about possible system landscapes and options for setting up CTS+ in general. CAUTION Keep in mind that the CTS system has to be on enhancement package 1 for SAP NetWeaver 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 SP naming of SAP Solution Manager is different from its SAP NetWeaver Support Package level. Starting with enhancement package 1 for SAP NetWeaver 7.0, SAP provides CM Services as part of each AS Java. So CM Services and some other components (e.g. SLD, Deploy WS) are available on both systems (NWDI and CTS+). It is up to you and depends on the scenario on which server you want to use CM Services and the Deploy Web Service. Please take a look at the chapter April

10 Recommendations & Restrictions before you start. CAUTION For the usage of CM Services (e.g. Activity Transport and/or SCA Transport) you have to use the CM Services on the same system as the Deploy Web Service - in that use case you can t separate these two components. For more Information on the Deploy Web Service, take a look at 9c1/frameset.htm. Note If you are already using CTS+ for other scenarios e.g. for transporting Portal objects, you might already have configured a Deploy Web Service. This does not influence your decision on where to run the CM Services. The configuration for the Deploy Web Service in 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 RFC Connections ). 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 package 1 for SAP NetWeaver 7.0) only in case you see advantages in the newly provided features. Then you don 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 new development landscapes, you can use CMS and CM Services in parallel. In both cases DTR is needed to store the sources and CBS will build the components and store the archives. The migration from 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 system landscape for transport and with development configurations and how to work with the newly provided features by CM Services. The configuration steps how to setup CM Services initially are explained in chapter Initial Setup and Configuration of CM Services. In case the CM Services are already enabled in your system landscape, you need to decide which kind of landscape option (see chapter Landscape Options ) you want to enable. Depending on the scenario, the system landscape configuration described in chapter System Landscape Configuration looks different. Chapter Development and Export Process focuses on the development and export process and explains how to work with development configurations in the NWDS, how to bundle an activity for being transported via CTS+ and how to export a software component archive (SCA) to be attached to a CTS+ transport request with the new Export UI. 4.1Landscape Options This guide is based on a landscape example with three runtime systems: a Development (DEV), a Test (TEST) and a Production (PROD) System. There are basically two options how you could transport your Java based development objects using CM Services: 1. Source Transport (Granularity Options: Activity or SCA) 2. Deployable Transport (SCAs) April

11 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. The main 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 Deployable Transport a development configuration is needed just for the Source/Development System. Note In case you enable your landscape for transport option 1 you have the possibility to transport on a small granularity level the so called Activity Transport. Or you can transport the complete software component (SCA) as well. In case your landscape is enabled for option 2 only, a transport on the level of small source code changes (Activity Transport) is not possible. Usually you transport the complete SCA. It is recommended not to use the SDA Export except you really know what you do. This option is only made for experts. You have to make sure that all dependent SDAs that were changed are part of the same transport request or were already transported. CAUTION In case you decide to use the Source Transport, you have to setup each target system with a development configuration. It is not possible to have e.g. the DEV system with a development configuration, the TEST without and the PROD again with a development configuration. A so called mixed scenario concerning development configurations is not possible and not supported! Let s look at the two options in more detail. 4.2Source Transport We assume the system landscape with DEV, TEST and PROD is setup and configured with a development configuration for each system in the transport route. That means your landscape is configured and ready for source transport. The steps how to do so are explained in chapter System Landscape Configuration. For such a landscape you have now the possibility to transport your source changes based on Activities 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 the process of transporting Activities works. Consider this as a logical view on the components involved in the process. April

12 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 your NetWeaver Developer Studio and to synchronize the sources if you would like to change an existing application. The first two steps (checkin and activate) after having finished your development in the NWDS remain the same it doesn t make any difference if you are using CM Services or CMS. Checking in an activity and activating it are unchanged. During the activation process the changes will be deployed to the DEV system. This hasn t changed compared to the CMS behavior. Only when releasing an Activity, you will find a new dialog. A transport request from CTS+ will be provided or you can create a new one by the help of the Transport Organizer Web UI (a Web Dynpro ABAP application that runs on the CTS system). The DIP-file containing the changed source files is attached to the transport request by then. With this, the developer has finished his work in the Developer Studio. As a next step, the transport request has to be released. This could be done either by the help of the Transport Organizer Web UI or in an automated way. Note Both, the behavior of the CTS+ System when asking for a request and what happens after having attached something depend on the transport strategy that you have configured. It is possible to let the system create requests and to make it release them automatically. Take a look at the parameters for details: ae4/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 of the changed DCs and the dependent ones will be done for the TEST system and the respective CBS buildspace is updated. The sources will become part of the respective workspaces for the TEST Development Configuration in DTR. After that, your new or changed application will become available April

13 via deployment on the TEST system and is ready for import into PROD. Here the same process is being 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 and Transport. Note Please keep in mind, that the usage of the DI Export UI is exactly the same for the SCA transport with or without sources. The sources of an SCA file will be assembled in both cases. But it depends on the landscape configuration what will happen during the import process. In a source transport enabled landscape, the DI CM Services will trigger the DTR workspace update, CBS rebuild and deployment to the target system. In a landscape that is configured for deployable transport only, the sca file will be deployed to the 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 is possible 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. A Development Configuration is only required for the development (DEV) system. All other systems in your transport route are pure deploy targets where you d like to import your application. For these systems 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 Note From the developer point of view, nothing has changed. You have to import the Development Configuration and synchronize the sources at first. After that, you can start developing. Checking in and activating the changes is done as described before. You April

14 can release the activity, but in case your changes will be transported via SCA export, you don t need to do it explicitly. That means the export process will take all activated activities that are related to the SCA export. For activities that are listed as Waiting in the transport view of the Developer Studio, the export process triggers the automatic release. To export and attach the SCA to a transport request a new UI is used - the DI Export Web UI. You can call this UI from the Development Configuration UI (see chapter SCA Export and Transport for more details). 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 that are to be developed in this system. The Export UI will guide you through the process of adding the SCA to a transport request. For this process, the same is valid as it was for the Activity Transport: a Transport Request can be taken automatically from the CTS+ system or you can create one by the help of the Transport Organizer Web UI. Also after having added the SCA to the request, the request can be released automatically or manually this depends on the transport strategy that you configured. As mentioned before, the activities related to the SCA export that are listed as Waiting in the transport view of the NWDS are released automatically after the export was done. April

15 5. Recommendations & Restrictions This chapter covers some recommendations and restrictions but in general you should check the CM Services central Note and (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. Check whether the CM Services offer benefits for you and if yes, use them. If not, you can continue using CMS. There are some restrictions for the usage of CM Services in enhancement package 1 for SAP NetWeaver 7.0 that you should take into consideration: CM Services require a NWDS on enhancement package 1 for SAP NetWeaver 7.0 or enhancement package 1 for SAP NetWeaver Composition Environment 7.1 for releasing the activity to CTS+. If you develop Web Dynpro for a runtime system which is not yet on enhancement package 1 for SAP NetWeaver, you have to use one NWDS on the release that fits to your runtime system for developing and another one which supports CM Services for releasing the activities. Development Configurations managed by CTS+ are named like the system in TMS. This means that the name of the development configuration is the same as the SID of the system that you created in TMS. In addition, the name of the development configuration consists therefore 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 is not supported for CM Services. 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 to run which component. Figure 4: Recommendations what to run where April

16 CAUTION The 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 are using or plan to use the CTS+ system for transporting e.g. Portal objects as well, you might need it again. For transporting Portal objects, the recommendation is to use the Deploy Web Service on the CTS+ system. This guide assumes that you stick to the recommendations and shows the configuration steps based on them: Use your SAP Solution Manager as CTS+ System. CAUTION Keep in mind that the CTS system has to be on enhancement package 1 for SAP NetWeaver 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 SP naming of SAP Solution Manager is different from its SAP NetWeaver Support Package level. 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 instead of a lot of source files. Sources should only be changed in the DEV system. For the Activity Transport Scenario it is technically possible to access (via the respective development configuration) and change the sources for your target systems. This is absolutely not recommended. Please set DTR ACLs accordingly 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 transport route or track, but you could use CMS for one development project and the CM Services for another. Both of them could use the same DTR and CBS. April

17 6. Initial Setup and Configuration of CM Services In this chapter, we assume that you start from zero this means that neither CTS+ nor NWDI or SLD are configured up to now. Concerning NWDI only the Design Time Repository (DTR) and the Component Build Service (CBS) are needed in case you use the development and transport options offered by CM Services. Therefore the configuration of the Change Management Service (CMS) is not part of this guide. If you already configured your SLD, CTS+-System, or NWDI, take a look at the appropriate sections in this guide anyhow to find out whether your configuration fits with the one needed for CM Services. This chapter concentrates on the initial setup and enablement of CM Services. For the configuration of your system landscape see chapter System Landscape Configuration and the usage of development configurations is described in chapter Development and Export Process. 6.1 Assumptions We assume that you are working with two dialog users: one who is a developer (nwdi_dev) and one who is an administrator (nwdi_adm). In addition, technical users are needed to establish connections etc. The dialogue users are just examples. You can use other users / user IDs for sure. Make sure that the 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 would mean that you use an NWDI on enhancement package 1 for SAP NetWeaver 7.0. If you are not able to do so, please check the Appendix chapter Configure Users and Groups manually on CM Services server. In addition, we assume that you are already using Web Dynpro ABAP on your CTS+. If this is not the case, take a look on the SAP Help Portal to learn how to activate Web Dynpro ABAP for a certain system: t.htm Note In addition you will need the ABAP Web Dynpro application CTS_BROWSER to create transport orders and attach objects. You have to carry out certain configuration steps to run and use this application. rameset.htm You 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 want to activate all ICF services read the error messages carefully and activate the services named within the error messages via transaction SICF at the end of the configuration. Note If your CTS system includes SL Toolset 1.0 SP4 at least, you have to activate the service CTS_ORGANIZER. This is the new UI used to manage transport requests for non-abap systems. April

18 How To Setup CM Services 6.2Configuring SLD If you are using the SLD for the first time, you can simplify the initial configuration by executing the appropriate CTC template. 1. On your SLD system, in the SAP NetWeaver Administrator ( choose Deploy and Change Configuration Wizard. 2. Choose the NWA_01_This wizard will execute configuration for local SLD configuration task and then Start. The template will guide you through a few steps. Enter a password for the SLDDSUSER according 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 the appropriate CTC template. 1. On your NWDI system, in the SAP NetWeaver Administrator ( choose Deploy 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 the following screens. April

19 CAUTION One step asks you for a master password. Remember this password you will need it later on. April

20 Note This 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 the local 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 the domain. The template still configures CMS for you you will not use it later on. Continue executing the template April

21 CAUTION On 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) in DTR. You have to grant permissions to the group NWDI.Developers. Log on to the DTR with usernwdi_adm. Use the following URL to edit the fileacl.xml: April

22 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

23 April

24 5. Check in your changes. 6.4Mapping Roles in UME Now, you have to assign the actions and roles introduced by CM Services to the appropriate users. On your NWDI server, map thesap_di_administrator role to thenwdi.administrator group and thesap_di_developer role to thenwdi.developers group. 1. Open the UME of your NWDI System. Use the URLhttp://<server>:<port>/useradmin. Search for the groupnwdi.administrator and select it. Go to the tab Assigned Roles, choose Modify. April

25 2. In the section Available Roles, entersap_di_administrator in the Search Criteria field and choose Go. SelectSAP_DI_ADMINISTRATOR, choose Add, and then Save. 3. Proceed accordingly to map thesap_di_developer role to thenwdi.developers group. April

26 6.5Configuring Connections As 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 NWDI system. It is needed to call the Deploy Web Services running on the NWDI when you import a transport request. The configuration for this connection is done on the CTS+ system in the transactions LPCONFIG and SM59. For this destination, you have to create a user on the NWDI which is 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 be able to retrieve e.g. a transport request from CTS when exporting an Activity. For this connection, you have to create a user on your CTS+ system (here: SolMan Solution Manager) Configurations on the CM Services Server This chapter explains the basic steps for configuring the connection between the CM Services and the CTS+ system in short. For more information about the configuration, see the SAP Library at: htm Creating User for RFC Destinations from CTS+ System to CM Services This section describes how to create a user on the CM Services Server that is needed for communication between the CTS+ system and the CM Services. 1. On the start page ( of your CM Services system, choose User Administration Create User. Follow the screens. April

27 2. On the following screen, enter a real password (you won t have to change it later on), the last name and choose technical user as security policy. 3. On the Assigned Roles tab page, assign the rolessap_cts_deploy and SAP_CTS_DI_CONFIGURATOR to this user. Note If your company policy says that you should only assign roles to groups, you can also do so in here. Create the user, create a group with the roles above and assign the user to the group. For more information, see 9c1/frameset.htm. April

28 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. Entersap.com/com.sap.tc.di.CTSserver in the Name field and choose typerfc. 2. Enter the required data as shown in the following screen. System: Server of the CTS+ system System Number: Number of the CTS+ system System ID: SID of your CTS+ communication system Client: Client in which the Transport Organizer is running (same value as used when creating the none-abap system on the CTS+ system for parameter NON_ABAP_WBO_CLIENT in the non ABAP system) NOTE In the Logon Data section, select Current User (Logon Ticket) as authentication for the connection 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 Configured User option and enter your preferred language, a client, and an appropriate service user and password. Note that this configuration is not recommended. The permissions required for each user who should be able to use this connection are described in the chapter Creating a user for the developer. April

29 3. Save your entries and choose Test Destination. Make sure that you receive the message Test is successful on top of the screen Configuring the CTS+ System Creating a User for the Developer Due to the decision in Creating an RFC Destination from CM Services to CTS+ to use the Logon Ticket 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 transactionsu Create the usernwdi_dev Note You have to create a user for every developer on the CTS+ system. The users are required on the CTS+ system e.g. to get a transport requests when exporting. You can use the user IDs of your developers. Make sure that you use IDs which allow to be used in SSO mode. NWDI_DEV is used as an example in this guide April

30 If the users already exist, continue with the profile that is required and assign it to all of the users. 3. On the Logon data tab page, don t enter the master password as you have to change it when logging in the first time. Change the password to the master password you specified in chapter Configuring NWDI. On the Roles tab page, assign the rolesap_cts_plus. Make sure that the following necessary values are assigned to this role (to do so, open transaction PFCG and display the role SAP_CTS_PLUS. On the Authorizations tab page choose Display authorization data: Authorization Check for ICF Access (object:s_icf): ICF_FIELD: ICF_VALUE: * DEST,PROXY,SERVICE Authorization Check for RFC Access (object: S_RFC): RFC_NAME: RFC_TYPE: CTS_WBO_DIS, EPSF, RFC1, SDIFRUNTIME, STPA, SYST 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: FILENAME: * 06, 33, 34, A6, A7 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

31 4. If not all necessary values are assigned to rolesap_cts_plus, copy this role ( ), name the new rolez_cts_plus, and choose Copy all. 5. Enter a description and click on Propose Profile Name to get an automatically generated profile name. Save your entries. April

32 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 rolez_cts_plus to usernwdi_dev (transactionpfcg, Roles tab page). Remove the rolesap_cts_plus Checking and Creating Logical Ports 1. Two logical ports are needed for the communication between the CTS+ system and the CM Services system:ctsconfig andctsdeploy_di. Check whether they are available on your CTS+ system and if not create them as described in this chapter. Log on to your CTS+ system in client 000 and call transactionlpconfig. Ignore the pop-up message. CAUTION We don t use CTSDEPLOY port in this guide as it might be already in use for other transports on your SAP Solution Manager - e.g. portal content. For the CM Services, we April

33 need an additional port as we are going to use the Deploy Web Service on the NWDI system, not on AS Java of your CTS+ system 2. EnterCO_TDIDICONFIGURATION_SERVICE as Proxy Class andctsconfig as Logical Port. 3. Click on Display. If the port does not exist, create it with the parameter values shown on the following screenshot. CAUTION Make sure that Default Port is not selected and that the logical port is active. 4. Repeat steps 2 and 3 with proxy classco_tfldeploy_proxy_vi_document and the logical port CTSDEPLOY_DI. If the port does not exist, create it with the parameter values shown on the following screenshot: April

34 Important Please note that in this configuration, both ports use the same HTTP-destination CTSCONFIG Checking and Creating RFC Connections An RFC connection is needed for the communication between the CTS+ system and the CM Services system: CTSCONFIG. This is the destination that you have already specified in the logical port as HTTP destination in Checking and Creating Logical Ports. The required usercts_rfc for this RFC connection with special permission on the CM Services system has already been created in step Creating 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 transport organizer web UI runs). Call transactionsm59 and open the HTTP Connections to External Server section. Check whether the connectionctsconfig is already available. If not, create it with the following parameter values: EnterCTSCONFIG as RFC Destination, a description, the Target Host, and as Service No the port of your server where the CM Services and the Deploy Web Service are running. Make sure that the Connection Type isg. NOTE The Deploy Web Service (CTSDEPLOY) for your portal/pi transports can be hosted on a different server. For Portal, the Deploy Web Services runs usually on the AS JAVA of your SAP Solution Manager. For CM Services the CTS Deploy Web Service on the CM Services server has to be used (see Introduction ). April

35 2. On the Logon & Security tab page, select Basic Authentication and entercts_rfc as logon user. 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. NOTE The connection test only tests the connection to the server without using the specified user and password. April

36 April

37 7. System Landscape Configuration Assuming that your CTS+ system and NWDI with CM Services are enabled, the following chapter describes how to setup your transport and development configuration landscape. Example In this guide a three system landscape example with DEV, TEST and PROD is used. So you need to setup 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/or target system. In addition the transport routes have to be created accordingly. When creating a development configuration for a system, DTR workspaces and CBS buildspaces are created automatically. But initially they are empty! Therefore you have to fill these buildspaces (and workspaces) with the required libraries (compared to the CMS Checking In Software Component Archives ). This is done with the help of a so called Upload system for which you create a transport request, attach the required SCA files and transport them at least to the DEV system. In case you enable 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 system DEV: non-abap source and target system with development configuration TEST: non-abap target system with development configuration PROD: non-abap target system with development configuration Transport Routes: UPLOAD DEV: Consolidation Route DEV TEST: Consolidation Route + Delivery Route TEST PROD: Delivery Route Deployable Transport (SCA): UPLOAD: non-abap source system DEV: non-abap source and target system with development configuration TEST: non-abap target system PROD: non-abap target system Transport Routes: UPLOAD DEV: Consolidation Route DEV TEST: Consolidation Route TEST PROD: Delivery Route April

38 CAUTION The following scenario is not recommended: Configure the TEST system as source system to be able to create a transport request, export and attach an SCA file (compared to 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 configuration parts have to be done in any case (described in the following chapters): 1. Create a non-abap DEV System with Development Configuration (Source and Target System) 2. Create a non-abap Upload System (Source System) 3. Create a transport route between Upload and DEV system 4. 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 Development Configuration The basic configuration for CM Services is done and you can create the non-abap systems and the transport route configuration for your runtime systems on your CTS+ System. This chapter describes how to configure the development system (DEV), which is a source (to be able to create a transport request and attach dip or sca files) and target system (for the deployment during the activation process triggered in NWDS) with a development configuration. This is true for all use cases using CM Services. Important Don t create a non-abap system for your NWDI. The transport route consists of the runtime systems. 1. On your CTS+ system (domain controller), call transactionstms. In the System Overview, choose SAP System Create Non-ABAP-System. April

39 2. Enter the required data. o System: Enter the SID of your development runtime system, for example, JD1. Tip If the SID is already used, you can also use any 3 letter name that has not yet been used in the domain. It is not required that the runtime systems are shown in CTS by their real SID but it simplifies keeping an overview if you do so. o Communication System: Choose the system where you configuredlpconfig and the RFC destinationctsconfig. Usually, this is your CTS+ system. o Development Infrastructure: Check this option so that a development configuration will be created for your system JD1. o Source System Settings: Activate the Transport Organizer to be able to create transport requests for this system. Choose this option for each and every system where you would like to do exports (usually, this should be done only for your development system) o Target System Settings: Specify your development runtime system by choosing the method SDM/DC and enter host and system number for this Java system. NOTE This configuration is different from what you might know when using CTS+, for example, for the Portal. The Development system has to have both configurations, source and target system. The target system is needed to be able to do deployments of your applications to this runtime during the activation step via NWDS/NWDI. 3. When first saving a non-abap system with development configuration (Create Development Configuration is selected) additional data is required. a. In the System Landscape Directory window, enter the URL of the SLD used by NWDI that you would like to use for NWDI development (as specified when executing the NWDI CTC Template). April

40 b. Specify user and password to be used by CM Services to commnuicate with the SLD. EnterNWDI_CMSADM as user and the password of this user (for example, the master password 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 user NWDI_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 tosdm. NOTE For runtime systems with SDM (SAP NetWeaver AS Java 7.0 and enhancement packages) use SDM as user. As of SAP NetWeaver AS Java 7.1 the Deploy Controller is used for deployments. In this case, enter a user with deploy permission and the appropriate password. 6. After the changes have been saved and distributed, the Development Configuration UI appears. April

41 7. Before being able to continue with configuring the Development Configuration, you have to adapt the transport tool parameters for the created non-abap system. So minimize this screen for 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 to CTSDEPLOY_DI and check if all other parameters are correct. Save your changes. Tip Change the DEPLOY_URL to the correct deploy port if you are using runtime systems which are on SAP NetWeaver 7.1 or higher or SAP NetWeaver Composition Environment. For AS JAVA 7.1 and higher the deploy port has to be changed to number>04. April

42 7.2Configuring the Development Configuration Now you can start working in the Development Configuration UI that was opened in the browser during the saving process of the non-abap system. NOTE If the UI is not open anymore, reopen it as follows: i. On your CTS+ system, call transactionstms. 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 the Build Tool Location (CBS) URL for building DCs (Development Components). Use the URLs of your NWDI server. Choose Confirm. 2. Now you can add Software Component Versions (SCV) that you want to be developed in this Development Configuration. Choose Add in the Software Component Definition section. All available software components are read from SLD and are provided in a list. April

43 3. Filter the list according to the SCVs you want to add to the Development Configuration, select them, and choose Add, and then Close. Note If the SCVs you want to add are not available in this list, define them in the SLD as described in the SAP Library at: 50b0/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. April

44 Note The software components of the second level which are not marked as Developed have to be imported into the development configuration as they are needed for the build. For more 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 at the top of the screen are active. Now the development system configuration is done. But before you can start working with the development configuration as described in chapter Development and Export Process the required libraries need to be imported with the help of a so called Upload System as explained in the following chapters. 7.3Required Software Component Archives In 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 these libraries needs to be created and imported into the development system (for example, JD1) and all other 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 does not require a server or an installation of an AS Java. It is just a dummy system that is needed to be able to create transport requests Initial Configuration of an Upload System 1. On your CTS+ system, call transactionstms. In the System Overview, choose SAP System Create Non-ABAP System. April

45 2. Enter the required data. Make sure you do not select Create Development Configuration and Activate Deployment Service. This system is only needed as a source system. 3. Save and distribute your changes Creating a Transport Route between Upload System and Development System 1. On your CTS+ system, call transactionstms and choose System Landscape. April

46 2. Switch to change mode and select your upload system and your development system from the list 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

47 5. Save and distribute your configuration. Now, the systems are connected and you can start using the route for transporting Transport and Import Required Software Component Archives This chapter describes how to create a transport request, attach the required software component archives and import them to the development system. Tip As the required libraries might be needed in case of Source Transport in all your target systems, it would be better to create the request and do the import into the DEV system later after your complete system landscape has been configured (with TEST and PROD in our example). April

48 Creating an Upload Directory As a prerequisite you need an inbox where the files can be taken from. You can create this folder on the client side as well as on the server side. If you choose to create the folder on the server side, see SAP Note In your file system, create a new folder named, for example, Inbox. 2. By default, the required files are stored in the folderusr/sap/trans/eps/in of your AS Java system. Copy the files for the SCAs that are defined (developed and required) in the development configuration to your inbox. Alternatively, you can share this folder. CAUTION Make sure that the SCA files and your development runtime have a corresponding release and SP level. 3. If you want to modify SCVs from SAP and you want the changes to be available in the development system, you would have to copy the relevant archives to your inbox to transport them Creating the Upload Transport Request 1. On the CTS+ system, call transactionstms and choose Transport Organizer Web UI ( ). 2. Select your upload system, choose Copy ( ), and then Continue. April

49 A browser window opens. 3. Choose Create Request, enter the required data, and choose Create. A transport request is created. April

50 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 was created on client side.) CAUTION Upload of big files from the client may fail. In this case, choose the option Server and upload the files from there (see SAP Note ). Repeat this step to attach all required SCAs to the request. April

51 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 see the target system information Import the Transport Request into Development System 1. On the CTS+ system, call transactionstms and choose Import Overview ( ). 2. Double-click your development system and choose Refresh. April

52 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) are imported into DTR/CBS of your development system and your developers can start working. CAUTION Please don t forget to import this transport request with the required libraries to all your target systems in case your landscape is configured for Source Transport. April

53 7.4Landscape Configuration The configuration that was described in the previous chapters is needed for both landscape scenarios shown in this chapter. The decision for transporting sources or deployables does not have any influence on what has to be configured for the upload and the development system. Now, depending on your transport scenario, the configuration of your target systems in your transport route might look different. This chapter focuses on the configuration of your target systems (here: TEST and PROD) and the required transport routes Landscape Configuration for Source Transport The option to transport activities which are the new/changed sources through the complete landscape has the consequence that a rebuild has to be done for each and every system. The prerequisite for being able to do a build is that a development configuration exists. So if you decide to go for this option, you would have to create a development configuration when creating the system in TMS. The landscape would then look like shown on the following figure. Figure: Landscape for Activity Transports (and SCA Transport) Note A landscape that is configured for Activity Transport can be used for SCA transport as well. Therefore you could also use a combination of both, e.g. the Activity transport on a regular level and the SCA transport from time to time. It depends on the amount of changes and your development process to decide when to use what. The Activity Transport is much faster in case of small changes but in addition using the SCA transport gives 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 Java URL assigned as it acts as deploy target. As a consequence, Workspaces in DTR and Buildspace in CBS are created for each system. The name of the Buildspace is the same as the SID in TMS. In DTR, you will find the SID as part of the path to your active and inactive Workspaces. April

54 Whenever an import is started, a re-build is triggered for the SDAs which contain the changed source files 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 even for the productive one. To configure your systems in TMS accordingly, you have to set the option Development Configuration for 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 an example what you should fill in when configuring the target systems (here: JQ1 as TEST system and JP1 as PROD system). Repeat these steps for all your target systems in your landscape. 1. On your CTS+ system, call transactionstms. In the System Overview, create a new non-abap system for quality/test as a target system with development configuration. Save your entries. 2. Enter the SDM password. April

55 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 save your changes. After you did these configuration steps for each system (here: TEST and PROD), you can create the transport 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 for DEV. In addition, you would need a delivery route from DEV to TEST (to be able to import the required April

56 Software Component Archives created via transport requests in the Upload System) and a delivery route from TEST to PROD. 6. Call transactionstms 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 line between JD1 and JQ1 and select Delivery. CAUTION Note that you have to configure two routes between development and test. The consolidation route is needed to export new developments from development and bring them to the target systems. The delivery route is required to be able to transport all of the requests that where created for the upload system as well. Using source transports requires that all of the libraries are part of the test system and all other target systems in your transport route. 10. Draw a line between JQ1 and JP1. Select Delivery. April

57 11. Save and distribute your changes. Other systems can for sure be part of the same landscape as well. All the options which are available in TMS for creating landscapes can be used for Java landscapes as well Landscape Configuration for Deployable Transport The second option for designing your landscape would be to export SCAs from the development system 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 CAUTION A landscape that is configured for deployable transport only can t be used for Activity Transport (Source Transport). April

58 A development Configuration is needed for the development system only. After you have finished your development, you would use the DI Export UI to attach the SCA to a transport request. The exported SCA 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. This means that the granularity of a transport is a whole SCA, not only the changes any more, but there is no 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 Create Development 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 Target System Settings. The following figure shows as an example the configuration for the PROD system JP1. 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, a consolidation route between Upload and DEV system is required. In addition you need a consolidation route from development (DEV) to the test (TEST) system. And a delivery route from TEST to PROD is required. April

59 8. Development and Export Process In this chapter you can find out how the development configuration that you created above is used in the SAP NetWeaver Developer Studio (NWDS). Creating a simple Web Dynpro application is used as an example to show the process. If you have already used NWDS and if you are familiar with the development 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 and Transport explains the usage of the new Export UI to export sca files and attach them to transport requests. 8.1Development Process This chapter explains how to import and work with development configurations with the help of a simple Web Dynpro example. The checkin and activate step is shown as it is needed for both transport scenarios. 1. In the NWDS, open the Development Configurations perspective. April

60 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

61 5. Enter the SLD URL and choose Ok. 6. The development configurations available on the respective SLD are shown. Choose the one that fits (the one that was created before). Choose Next. You can see a summary of the Development Configuration that you chose. Choose Finish. April

62 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

63 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

64 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

65 14. Assign the changes to an existing (or new) activity. The following is shown: 15. Double-click on MyComponentView. April

66 16. Choose Outline. 17. On the Properties tab page, edit the value of the text field. April

67 18. Choose Save All Metadata ( ). 19. In the Web Dynpro Explorer, create a new application. 20. Enter the required data and choose Finish. April

68 21. Add the sources to DTR. 22. Select the Activity where you would like to add this application. Choose Ok. The application is created. April

69 23. Switch to the Development Configuration Perspective, on the Open Activities tab page, rightclick your activity and choose Check in. 24. Enter the required data and choose Ok. April

70 25. After the check in has finished, activate your DC. Right-click on your Activity in the Activation View. Activation means that the sources will be built in CBS and after a successful build the respective SDA files will be deployed to the development system. After that the sources are active and visible to all. 26. Choose Open Request View. Click Refresh from time to time until the activation has finished. April

71 Now the activity has been activated. In case you decide to transport the activity on source level proceed with chapter Activity Transport. For the transport of the complete software component archive (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 thesmart request strategy. Release the transport. Select Monitor Request. This will open the Transport Organizer Web UI immediately after the release has finished. April

72 After this process has finished, you see the following in the Transport View: And in the Transport Organizer Web UI: April

73 The Object List contains the Development Infrastructure Package (DIP) files that were created during 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 the same 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 target system (TEST) in your transport landscape. For more details on that have a look at meset.htm. Note In case of errors, see Troubleshooting. 8.3SCA Export and Transport Before starting to use the export service, you should have setup a landscape on your CTS+ system which contains all the systems where you would like to import the SCAs. You might e.g. have a system named JQ1 which serves as testing system (TEST) and should therefore be the first one where you d like to import the SCA. The SCA Export and Transport is possible for both landscape configurations source and deployable transport. The way how to use the DI Export UI does not differ. The exported SCA always contains the sources, but they will only be used in a landscape that is configured for source transport. Note The export process will take all activated activities that are related to the SCA export. For activities that are listed as Waiting in the transport view of the Developer Studio, the export process triggers the automatic release. 1. On your CTS+ system, call transactionstms. In the System Overview, double-click your development system. 2. Choose Development Configuration. 3. Log on with usernwdi_adm. 4. Choose the hyperlink DI Export Service or use the URL April

74 5. Select your system ID, the system ID of your development system (here: JD1), select SCA Export and choose Next. CAUTION It is recommended not to use the SDA Export except you really know what you do. This option is only made for experts. You have to make sure that all dependent SDAs that were 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. CAUTION You can only export one SCA at a time. It is not possible to choose more than one line. If you would like to attach more than one SCA to a transport request, you can do so by going through the Export steps twice. April

75 7. Decide whether you would like to include source pointer and / or archives in the SCA and choose Next. Note Please notice that the exported SCA will always include the sources. But you have the option to optimize 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. This is only required or recommended in case you transport sources and your source DTR is not available during import time. Or you need to archive your software components for backup reasons. It is recommended not to use this option as then the Design Time Repository (DTR) flags the current sources in a workspace and only a logical export using source pointer is performed. This reduces 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 Advanced Options selected will become visible. 9. Due to the connection to your CTS+ system and its request strategy SMART, a transport request has been retrieved from CTS+ automatically. If you would like to, you can add a note to the transport request that e.g. contains information about the SCA. Choose Next. April

76 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

77 12. In the Transport Organizer Web UI, on the Properties tab page, you can find out about the Target 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 transactionstms you can see the transport request in the import queue of your test/quality system JQ1 (TEST). For more details on that have a look at meset.htm. Note In case of errors, see Troubleshooting. April

78 9. Troubleshooting When releasing an activity, the following errors may occur: 9.1CTS Transporter Exception CANNOT_GET_DOMAIN Reason: The communication system of your non-abap system JD1 is not maintained on the developer s engine. Solution: 1. Go toc:\windows\system32\drivers\etc and open the fileservices with an editor (for example, Word pad). 2. Check if thesapms<sid> entry exist and if the port is correct. If not, correct them. For more information, see SAP Note Restart the SAP NetWeaver Developer Studio. April

79 9.1.2 FILE_NOT_PERSISTABLE Reason: RFC authorizations are missing. Solution: Apply SAP Note April

80 9.2CTS Packager Exception Access Denied Solution: See steps 3 to 5 in chapter Configuring NWDI. April

81 10. Appendix 10.1 Extending the Landscape In case you need to extend your landscape, you have to make sure to import previous transport requests. For a system landscape that is enabled for source transport - target systems with development configurations it is essential to import the required libraries. We assume you created your new non-abap target system with or without development configuration as described before. In addition the required transport route is available. The next steps explain how to import transport requests (that have been already transported) to this new target system once. For all upcoming transports this new target system will be delivered via the regular transport route. 1. On your CTS+ system, call transactionstms. In the System Overview, select the system you want 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 added to the queue and can be imported. 4. Select your requests in the import queue and import them. April

82 5. Repeat these steps for all new systems in your landscape Configure Users and Groups manually on CM Services server If you run the CM Services on another server than your DTR and CBS, you can t use the CTC template Initial setup of functional unit Development Infrastructure (DI all-in-one) to set up the users NWDI_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 finally create the users and assign them to the groups. 1. Logon to UME on CM Services server ( 2. Create the groupsnwdi.administrators andnwdi.developers. 3. Assign the rolesap_di_administrator to groupnwdi.administrators and role SAP_DI_DEVELOPER to groupnwdi.developers. Optional: In case SLD is also located on CM Services Server add rolesap_sld_organizer to groupnwdi.administrators and SAP_SLD_DEVELOPER to groupnwdi.developers 4. Create users (in dual stack case user creation might be possible only on ABAP stack): - usernwdi_cmsadm used for communication between NWDI components. Make sure to select the entry Technical User as Security Policy. April