enhanced change and transport system...the transport organizer web ui can be called from the...

1

Enhanced Change and Transport SystemNew Features in SAP Enhancement Package 1 for SAP NetWeaver® 7.0

Karin Sudrow, SAP AGNovember 2008

2

© SAP 2008 /

Disclaimer

This presentation outlines our general product direction and should not berelied on in making a purchase decision. This presentation is not subject toyour license agreement or any other agreement with SAP. SAP has noobligation to pursue any course of business outlined in this presentation or todevelop or release any functionality mentioned in this presentation. Thispresentation and SAP's strategy and possible future developments aresubject to change and may be changed by SAP at any time for any reasonwithout notice. This document is provided without a warranty of any kind,either express or implied, including but not limited to, the implied warrantiesof merchantability, fitness for a particular purpose, or non-infringement. SAPassumes no responsibility for errors or omissions in this document, except ifsuch damages were caused by SAP intentionally or grossly negligent.

3

© SAP 2008 /

Abbreviations

For a better readability, the following abbreviations will be used for this presentation.

Change Management ServiceCMS

SAP enhancement package 1 for SAP NetWeaverEHP1

SAP NetWeaver Process IntegrationPI / XI

Software Deployment ManagerSDM

(Enhanced) Change and Transport SystemCTS(+)

SAP NetWeaver Development InfrastructureNWDI

SAP NetWeaver Composition EnvironmentCE

SAP NetWeaver Developer StudioDS

Component Build ServiceCBS

Design Time RepositoryDTR

4

© SAP 2008 /

1. CTS+ Basics2. News for the Transport System

2.1 Transport Organizer Web UI2.2 Creating Systems with Development Configuration2.3 System Specific Import and Export Permissions2.4 Deploy via Deploy Controller

3. News on Using CTS+ for Different Applications3.1 Master Data Management3.2 Single System Track in CMS3.3 Activity Transport3.4 SCA / SDA Transport

4. Summary and Outlook

Agenda

5

© SAP 2008 /

VariousTransportTools

Situation before Enhanced CTS –Various Transport Tools are Used

MultipleDevelopmentWorkbenches

MultipleTypes ofBackends

CTSCTS

SAP NetWeaverAS Java

SAP NetWeaverAS JavaXI/PI SystemXI/PI SystemSAP NetWeaver

AS ABAPSAP NetWeaver

AS ABAP ......

File System,CMS

File System,CMS File SystemFile System CMSCMS ......




AS ABAP ......Portal Systemon SAP NetWeaver

AS Java

Portal Systemon SAP NetWeaver

AS Java

NWDIon SAP NetWeaver

AS Java


AS Java

ESR/PI/XISystem

on SAP NetWeaver(Dual Stack)

ESR/PI/XISystem


SAP NetWeaverAS ABAP

SAP NetWeaverAS ABAP ......

......

SAP offers many Tools and Workbenches to develop applications or create content for end users. There arealso many different tools which are used for transporting the applications from a development system to aproductive system through a system landscape. In some cases, the tool supports a transport like e.g. CTSdoes it for the ABAP workbench. In other cases like e.g. in the Portal, there is an import and an exportmechanism available, but the system administrator has to take care that the files are available at the rightlocations when performing an import.

There is a difference between Export / Import and Transport. Export / Import means that the changes made inan application or newly created content can be collected and then exported in a file-format. This file needs tobe stored somewhere. An administrator has to upload the file to the target system and start the import ordeployment. Transport includes logistics for the exported files. The administrator has to start the import, but hedoes not have to take care of the location of the files. In addition, there is an option to track what has beenimported, to monitor the results and to get reports on import status. CTS does all this for ABAP basedprogramming and customizing.

6

© SAP 2008 /

Enhanced CTS –One Transport Tool for Multiple Content Types

Enhanced CTSEnhanced CTS

MultipleDevelopmentWorkbenches




AS ABAP ......SAP NetWeaverAS Java



AS ABAP ......Portal Systemon SAP NetWeaver

AS Java

Portal Systemon SAP NetWeaver

AS Java


AS Java


AS Java

ESR/PI/XISystem


ESR/PI/XISystem


SAP NetWeaverAS ABAP

SAP NetWeaverAS ABAP ......

......

One centralTransportTool

MultipleTypes ofBackends

Enhanced CTS offers the possibility to transport objects created in other languages than ABAP via theChange and Transport System of ABAP. The goal is to have one transport tool which supports allworkbenches and applications when it comes to transports. The tools for creating applications and creatingcontent remain the same. Options to attach objects or content to a CTS Transport Request can be integratedinto the different workbenches. The level of integration is different for different workbenches. Enhanced CTSaims for a unified single transport tool which simplifies the life of an administrator who is responsible forperforming imports. He has to access only one tool to start imports for very different backends. Deploymenttools are called automatically. With CTS, it is very easy to monitor what has already been imported and if theimport went well. The queues and the history in CTS provide a good overview on what has to be imported andwhat is already imported. The integration of CTS+ into the different workbenches is an evolutionary process.CTS+ integration into the different applications and workbenches is planned to be announced in the releasenotes of the appropriate application as soon as it is provided.

7

© SAP 2008 /

Enhanced CTS – Supported Object Types

The ABAP Change and Transport System (CTS) has been enhanced with SAPNetWeaver 7.0 SPS 12 to be capable of transporting

non-ABAP objects.

Object types supported with enhancement package1Java-based and JEE-based objects

Software Component Archives (SCAs)Software Deployment Archives (SDAs)Enterprise Application Archives (EARs)DTR-Activities in DS (DIPs)

Portal-based objectsEnterprise Portal Archives (EPAs)Portal Archives (PARs)KM Documents and Configurations

PI/XI-based objectsIntegration Repository design objects, Integration Directory configuration objects, ABAP Mappings

SLD ObjectsMDM (specific set of data model objects)Any Files (.doc, .xls, .xml, …)

Please check thesystem requirements tosee which SP level isneeded to support theobject type

This slide lists the object types which can currently be transported via CTS+. Not all of these objects typeswere supported with the first release of CTS+ (provided with SAP NetWeaver 7.0 SPS 12). A look into therelease notes both of CTS+ and the application is always advised to find out which objects are supported bythe release that you currently have in place. In addition, the level of integration is not the same for allsupported files. Some require manual work when attaching them to a transport request, for others, you needto do something in the target system of the application after the import.

‘DIP’ means Development Infrastructure Packages. It is a new file format used when Activities aretransported. Details are provided later on.

With MDM 7.1 the following set of data model objects can be transported from a source system to a targetrepository: Tables & Fields, Relationships, Languages, Roles, URLs (Web Links), XML Schemas, RemoteSystems, Ports, Validations and Calculations, Assignments, Workflows (new with MDM 7.1), Import Maps(new with MDM 7.1), Syndication Maps (new with MDM 7.1), Matching Rules including Matching Strategies(new with MDM 7.1)

8

© SAP 2008 /

Further Information

SAP Community NetworkCTS+: https://www.sdn.sap.com/irj/sdn/ctsHow-to Guides and other resources on CTS+:https://www.sdn.sap.com/irj/sdn/cts?rid=/webcontent/uuid/c0ce1dd8-c020-2b10-d080-a1cd3e985af1CTS+ Best Practice Guide:https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10456aac-44f7-2a10-1fbe-8b7bcd7bcd58

SAP Help Portal:CTS+:http://help.sap.com/saphelp_nw70/helpdata/EN/45/ec25370fdc3481e10000000a1553f6/frameset.htm

If you need more information about CTS+ and how it works, take a look at the links provided above.

https://www.sdn.sap.com/irj/sdn/cts

https://www.sdn.sap.com/irj/sdn/cts?rid=/webcontent/uuid/c0ce1dd8-c020-2b10-d080-a1cd3e985af1

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

http://help.sap.com/saphelp_nw70/helpdata/EN/45/ec25370fdc3481e10000000a1553f6/frameset.htm

9

© SAP 2008 /





Agenda

10

© SAP 2008 /

The Transport Organizer Web UI

Is an ABAP Web Dynpro Application

Has to be used to handle Transport Requests for non-ABAP objects / systemsDon’t use SE09

Is linked into Applications (PI, NWDI, DS, Portal, SLD…)

Provides features for managing Transport Requests

Create

Set as default

View attached objects

Attach objects

Release

…

The Transport Organizer Web UI is an ABAP Web Dynpro Application which has been introduced with SAPNetWeaver SPS 12. In SPS 13, a new version has been provided. The name of the ABAP Web Dynproapplication is CTS_BROWSER (from SPS 13 onwards). It is used to handle transport requests for non-ABAPsystems. If you know how to transport in ABAP: SE09 can’t be used for non-ABAP systems, theCTS_BROWSER has to be used instead.

The Transport Organizer Web UI provides the features that a developer in the applications needs to be able tohandle transport requests. He can e.g. create transport requests, attach objects and release the transportrequests. In addition, he can view the status of released requests.

The Transport Organizer Web UI can be called from the applications which provide an integration of CTS+into their export tools. The developer can then change a transport request or create a new one without havingto go to the CTS system. The Transport Organizer Web UI runs on the CTS system, but if Single Sign Onbetween the application and the CTS system is enabled, the developer’s experience is seamless. TheTransport Organizer Web UI can be called with several URL parameters. This is why it might show differentoptions when it is called from different places.

11

© SAP 2008 /

Set the Preselected Request

Button renamed – samefunctionality (was: Set as

Standard Request)

This slide and the following ones show changes for the Transport Organizer Web UI which are part of SAPenhancement package 1 for SAP NetWeaver 7.0.

The button Standard Request has been renamed to Preselected Request. If you mark on request and thenclick this button, the respective request will be marked by a red arrow and is used in applications whichprovide close coupling when exporting objects. If you mark the transport request which is already set aspreselected request and click on this button, the selection will be removed.

12

© SAP 2008 /

Attach an Object (Loose Coupling)

Button Attach has beenmoved to tab Object List

The button to attach an object manually to a transport request is now part of the tab Object List of therespective transport request. If an application provides loose coupling as integration level with CTS+, objectsare attached to a transport request via the Transport Organizer Web UI. The developer uses the Attachbutton. A pop-up window comes up where the developer can then browse for a file and attach it to thetransport request.

13

© SAP 2008 /

Work in Teams

The tab Team has been added.Several Users of one team can nowuse the same transport request to

collect all their changes andtransport them together

A new tab will be provided for modifiable transport requests. The tab is named Team. You can add severalusers to a transport request. When adding a user to the team, the option Preselected Request for added useris set by default. The request becomes the preselected request for the new team member. You can changethis option. And the new team member can do so as well when he open the Transport Organizer Web UI byjust marking another transport request and clicking on Preselect Request. All team members can add objectsto the same transport request. This helps making sure that all objects belonging to one new feature are part ofthe same transport request. Every team member can release the transport request. It is not necessary thateach team member releases the transport request. The whole transport request is released after one teammember did so.

14

© SAP 2008 /





Agenda

15

© SAP 2008 /

Create Development Configuration in CTS (1/2)

Create system withDevelopment Configuration

Access DevConf forexisting DI Systems

A Development Configuration is required if you are developing software based on the SAP Component Modeland if you are using SAP NetWeaver Development Infrastructure for managing sources and performing acentral build. The Development Configuration contains e.g. the location of the Design Time Repository (DTR)and the Central Build Space (CBS). One or several Software Components can be managed with oneDevelopment Configuration. The Configuration is stored in the SLD. The developer can import theDevelopment Configuration into his Developer Studio. After that, he can start developing or changing theSoftware Components assigned to the Development Configuration.

When creating a non-ABAP system, you can decide whether a development configuration is needed for thissystem. You can take a look which SLD is used. If you check the option Create Development Configuration,an additional browser window will come up when you save your system, where you can maintain the DTR andthe CBS and assign software components. The Parameter DI_SYSTEMS is added to the parameters for yoursystem on the tab Transport Tool.

It depends on the use case for which system you need a development configuration. The DevelopmentConfiguration is needed if you would like to use Activity Transport. Details on the Activity Transport areexplained later on. You need a Development Configuration for each system of one transport route if you wouldlike to use Activity Transport.

The Development configuration can be changed later on. You’ll find the button Development Configuration inthe details of each system where the parameter DI_SYSTEM is set to true. If you clicked on it, the sameconfiguration UI that was shown when the system was created will be displayed. You are then able to changethe configuration.

You can only configure one SLD. When you created the first system with a Development Configuration, youwill be asked to enter the URL of the SLD. This SLD will be used for all systems using DevelopmentConfigurations in this CTS System. The global parameter DI_SLD_URL is added to the parameters.

16

© SAP 2008 /

Create Development Configuration in CTS (2/2)

Define the CBS and DTRLocation for your Development

Configuration

Define theSCs

This slide shows a screenshot of the Development Configuration Service which is displayed when creating asystem with Development Configuration or clicking on the button Development Configuration of a DI system inTMS.

The Name of the Development Configuration is identical to the SID of the system in TMS. You can’t changethis behavior. As a consequence, only three letter acronyms are used as names of developmentconfigurations.

Click Confirm in the area Environment Definition to be able to change the Software Component Definition.

17

© SAP 2008 /





Agenda

18

© SAP 2008 /

System Specific Permissions

Only Developers shouldbe allowed to do exports

Only Administrators ofthe QA system should

be allowed to startimports

Only very fewAdministrators who know

e.g. about possibledowntimes should be

allowed to do imports forthe productive system

You can restrict the permissions that a certain user has for a specific system.

One scenario could be that a developer should only export the objects that he created. The import should bedone by someone else. The developer needs to have export permissions for the development system, but heshould not be able to start the import.

Another option would be to restrict the import permissions per system. Several administrators could have thepermission to start the import for the QA system but only a few should be able to import new stuff into theproductive system. This might be helpful if imports require post import steps that might include a systemrestart. Restarts have to be coordinated and agreed on within the company especially if productive systemsare concerned.

19

© SAP 2008 /

System Specific Permissions - Configuration

New options to set Authorizations for a role in PFCG:

S_SYS_RWBO

S_CTS_SADM

If you would like to restrict the permissions forgenerating requests

If you would like to restrict the permissions forimporting

The permissions for systems have to be set via a role in the transaction PFCG. This slide shows theauthorization objects which are used.

S_SYS_RWBO is used to restrict the permissions for creating transport requests. You have to enter theSIDs of the systems for which the user should be able to create transport requests.

S_CTS_SADM is used to restrict the permissions for importing.

If you need different settings for different users, you have to create different roles.

20

© SAP 2008 /





Agenda

21

© SAP 2008 /

Deploy via Deploy Controller

The texts now indicatethat the Deploy Controllercan be used as well

The DEPLOY_URL isgenerated automaticallyand has to be changed tothe port used by DeployController

Starting with SPS 14, you can use CTS+ for deploying on CE as well. With enhancement package1, this isalso visible in the wizard for creating non-ABAP systems. The texts in the UIs have been changedaccordingly. You still have to change the port manually. The DEPLOY_URL which is automatically createdwhen choosing the option SDM/DC uses the standard SDM port. This has to be changed: e.g. port 50004 isused instead of 50018 and an engine user with deployment rights has to be specified.

22

© SAP 2008 /





Agenda

23

© SAP 2008 /

SAP NetWeaver Master Data Management 7.1(MDM)

Loose Coupling Integration of MDMApplication Requirement: SAP NetWeaver MDM 7.1CTS+ Requirement: enhancement package 1 for SAP NetWeaver 7.0Transport is done via File System

ConfigureNON_ABAP_WBO_INBOX on source systemDEPLOY_OUTBOX on target systemMake sure that access rights are granted

Starting with SAP NetWeaver MDM 7.1 and enhancement package 1 for SAP NetWeaver 7.0, Loose Couplingis supported for MDM as well. In the case of MDM, transports are done via a file system. Therefore theparameter NON_ABAP_WBO_INBOX has to be set for the source system in Transaction STSM and theparameter DEPLOY_OUTBOX for the target system. As a file share is used for this transport, you have tomake sure that the share is accessible for both systems.

As MDM is a C++ based application there are no software Changes to be transported within the installedsystem landscape. The customer development and its changes are based on the MDM repository meta datadefinition. MDM repository meta data changes can be extracted and stored in MDM transport files. The CTS+system is then able to transport the changed file to the next system on the transport route. The deployed tothe target MDM repository has to be done manually. There is no automatic deployment available.

With MDM 7.1 the following set of data model objects can be transported from a source system to a targetrepository: Tables & Fields, Relationships, Languages, Roles, URLs (Web Links), XML Schemas, RemoteSystems, Ports, Validations and Calculations, Assignments, Workflows (new with MDM 7.1), Import Maps(new with MDM 7.1), Syndication Maps (new with MDM 7.1), Matching Rules including Matching Strategies(new with MDM 7.1)

24

© SAP 2008 /





Agenda

25

© SAP 2008 /

Single System Track

DEV System CONS System

DevelopmentConfiguration

transport

CMS Track


At least two DevelopmentConfigurations per track

Each transport requires a rebuild

Up to now Starting with EHP 1

Additional option: Single System Track

If consolidation stage for e.g. bugfixing and additional (integration) testsis not required

All activated changes will beassembled and exported

Only DEV system possibleOne time conversion is possibleNo way Back!

CMS Single System Track

DEV System

CM

S

Java URL


In the Change Management Service (CMS) of NWDI, tracks are created which represent the systemlandscape that you use for developing Java applications. A track consists of at least two and at most foursystems: Dev, Cons, Test and Prod. With enhancement package 1 it is now possible to create tracks whichconsist of just one system – the Dev system.

You can convert existing tracks into single system tracks. Only the development system remains whenconverting into Single System Track, all other systems are removed. A single system track consist of only onesystem, the dev system.

To organize the transports as in the regular development track, you will need to set up connections betweenthe different tracks (single system track or standard development track) to achieve the old track configuration.

You cannot perform consolidation with a single system track since all activated changes are assembled.

Everything that is activated in a Single System Track gets directly assembled, so you must remember torelease your changes immediately after the activation.

26

© SAP 2008 /

TESTPROD

JavaABAP

Runtime Systems

TESTTEST

JavaABAP

TESTDEV

JavaABAP

CMS – CTS+ IntegrationOptional: Single System Track

Build Server(CBS)

Buildspace

Repository(DTR)

Workspace

NWDI

Java Development Environment

DeveloperStudio

activate

& release

CMS Single System Track

DEV System

CM

S

Dev. Config

Java URLSCA

assembly& attach

TMS System-Landscape Configuration – Transport Route

TMS DEV System TransportRequestTransport

Request

TransportRequestTransport

Request

TMS TEST System TMS PROD System

SCA

TransportRequest

SCA

TransportRequestABAP

Java URL

ABAP

Java URL

ABAP

Java URL

You now have the option to create Single System Tracks in NWDI.

In case of Single System Tracks, the tab Consolidation in CMS is not available any more.

You can change a normal track into a Single System Track, but there is no way back.

This single system track offers the advantage that in case of dual stack systems the ABAP and the Java partof a transport can be imported via the same transport request. In case of separate systems for ABAP andJava, the import can be started from the same CTS system. The transport requests are then part of differentqueues, but only one tool needs to be used to start the import.

The disadvantages that you have to configure two systems and that the transport of the Java part can only beon the granularity of SCA remain the same as before.

27

© SAP 2008 /

Configuration of Single System Tracks

Set the option DevelopmentSystem Only to create asingle system track.

You can change existingtracks into Single SystemTracks

You can not revert thischange. Configuration ofConsolidation etc is lost if youconvert a track into a singlesystem track

28

© SAP 2008 /





Agenda

29

© SAP 2008 /

CMS Track Configuration

Development Consolidation Test Production

CMS Track


Buildspace

WorkspacesWorkspaces

CentralDevelopment

System

ConsolidationSystem

TestSystem

ProductionSystem


Buildspace


Runtime Systems

DEV CONS PRODTEST

What was the motivation for that change? Here you can see the classical design of a track in NWDI with 4runtime systems connected. This setup has some limitations that are explained on the following slide.

30

© SAP 2008 /

no reuse of ABAP transport knowledge – need to learn new conceptbuild transport routes with a limited number of systems in one tracksystem roles (DEV, CONS, TEST, PROD) are predefineddevelopment configurations and repair capabilities are predefined (DEV, CONS)no multiple direct successor systems for each system possible in one tracktransport granularity after assembly is the complete Software Component (SCA)no synchronized transports between different object types and other content

Transport via NWDI – CMS:LimitationsThe transport system CMS has the following limitations

PRODDEV CONS CMS Track 1

Asse

mbl

y

Appr

oval

PRODDEV CONS CMS Track 2As

sem

bly

Appr

oval

31

© SAP 2008 /

TMS System-Landscape Configuration – DI Development Configuration

CTS System Landscape Configuration

Runtime Systems

DEV CONS PRODTEST

PROD

Java URL

Dev. Config

Buildspace


Java URL

Dev. Config

Buildspace


Java URL

Dev. Config

Buildspace


Java URL Java URL

Dev. Config

Buildspace


Java URL

TMS DEV System TMS CONS System TMS TEST System TMS PROD System

TMS UploadSystem

Consolidation RouteDelivery Route

Dev. Config

Buildspace


Dev. Config

Buildspace


Here you can see a system landscape with a Development Configuration for each system. Activity Transporttransports the changed sources from one system to the next. This requires a build on each system. Youtherefore need a development configuration for each system in the transport route.

The landscape shown on this slide is not mandatory. It just shows that you could have all the systems that youknow from CMS also when using Activity Transport with CTS. But the landscape could look very different.With CTS you can use as many systems within your landscape as you want.

The upload system is needed to import the libraries needed for building applications into each system of thelandscape. The upload system is not a real runtime system. It is created as non-ABAP source system in TMSbut it is not a real system. It is only needed to create a transport request containing the required SCAs(SAPBUILDT.SCA, SAPJEE.SCA and SAPJTECHS.SCA). This transport request is then imported into eachsystem. Create the transport request again after each patch installation. In addition, the upload system isrequired if you would like to modify sources delivered by SAP (ESS or CRM) to import these sources.

32

© SAP 2008 /

Enhanced CTS –Advantages

PRODCONSDEV

Enhanced CTS allows touse the ABAP change and transport system (CTS) for all transportsbuild transport routes with an arbitrary number of systemsdefine arbitrary system rolesdefine multiple direct successor systems for each systemrepair capability in each system possible (development configurations)select single objects for transports in any system no assemblysupport synchronized transports between ABAP and Java or other content

System System...QA CONS PREPROD

PROD2SANDBOX

automatictransport ofobjects lists

automatictransport ofobjects lists

33

© SAP 2008 /

Runtime Systems

Dev. ConfigDev. Config

Activity Transport – The Process


TMS DEV System

Build Server(CBS)

Buildspace

Repository(DTR)

Workspace

NWDI


DeveloperStudio

Dev. Config

TMS TEST System TMS PROD System

release

Activity

Java URL Java URL Java URL

TEST

TEST

TEST

DEV

TEST

PROD

Repair capability

Rebuild

SDASDA SDASDA

Rebuild

check In

activate

CM Services*

*) CM Services are part of SAP NetWeaver usage type AS-Java

SDASDA

TransportRequest

DIP

TransportRequest

DIP

The option to transport an activity is available with a Developer Studio on enhancement package 1 for SAPNetWeaver 7.0 or enhancement package 1 for CE 7.1. To be able to use this option, the CTS Systemand the NWDI have to be on enhancement package 1 for SAP NetWeaver 7.0.

When releasing an Activity, a *.dip (Development Infrastructure Package) file is created and attached to thetransport request. It contains the changed source files.

The Activity Transport in Developer Studio via CTS+ offers the following advantages

Only one tool is needed to configure the landscape and to perform transports. Both is done in the CTSSystem.

The transport granularity is no longer an SCA. Single Activities/Sources can be transported. The file typeused is *.dip. An SDA is deployed to the runtime systems.

The step Deployment of the Transport log in CTS monitors the build process. The monitoring cantherefore be done via several tools: CTS Import Logs, Transport Organizer Web UI, Solution ManagerDiagnostics.

The Activity Transport is a Delta Transport on source code level. Therefore small changes in DEV resultin small transport files which again results in fast rebuilds and deployments.

The disadvantages of the Activity Transport are:

A rebuild is needed for every system and therefore also a corresponding Workspace and Buildspace

A Development Configuration needed for each System

Please be aware that this slide shows a logical view on the components and systems involved in the ActivityTransport. Especially the CM Services don’t have to be used on the NWDI System. We recommend thatyou use them on the Transport System.

34

© SAP 2008 /

Transport ActivitiesClose Coupling in Developer Studio

To release the changes – open the Transport View in Developer Studio.Select the activated Activity and choose Release.

Transport Method

Information aboutthe Transport

Request

Information for theCTS Administrator

Link to TransportOrganizer Web UI

Mark to startTransportOrganizer

If you would like to use Activity Transport in the Developer Studio, you have to import a DevelopmentConfiguration that was created for a DI system in TMS at first. After that you can start developing newcomponents or change existing ones that belong to the respective Development Configuration.

When you release an Activity in the Developer Studio, a Transport Request is used. The Transport Requestand the respective Transport Route depends on the Development Configuration for which you are developing.You can see the default transport request that has been taken from the CTS system for your user. If you setthe option Monitor Requests the Transport Organizer Web UI will be started after you clicked on Release. Youcould then see that the dip-file has been attached to the transport request and could release the transportrequest immediately.

35

© SAP 2008 /



3. News on Using CTS+ for different Applications3.1 Master Data Management3.2 Single System Track in CMS3.3 Activity Transport3.4 SCA / SDA Transport


Agenda

36

© SAP 2008 /

Runtime Systems

SCA Transport via DI Export Web UI


TMS DEV System

Build Server(CBS)

Buildspace

Repository(DTR)

Workspace

NWDI


DeveloperStudio

activate

TMS TEST System TMS PROD Systemexport &release SCA

Dev. Config


TransportRequest

TESTDEV PROD

DI Export Web UI

check In

SCA SCA

SDA

CM Services*

SCA

TransportRequest

SCA

A DI Export Web UI is planned to be provided with enhancement package 1 for SAP NetWeaver 7.0. It canbe used to attach SCAs or SDAs to a transport request. The DI Export Web UI hast to run on the same serveras the Deploy Web Service. The SCA becomes part of a Transport Request and can be transported throughyour system landscape via this transport request.

The Advantages of an SCA Transport via the DI Export Web UI are:One tool is used to configure the landscape and to perform transportsPure Deployment to target system – no rebuild neededDirect attachment of SCA without CMS Administration step (CMS Web UI)

The disadvantages of transporting and SCA are:No repair capabilities in target systemTransport granularity is SCA

37

© SAP 2008 /

SCA Export via DI Service Export UI (1/3)

1. Select a Systemand an Export Mode

2. Select a SoftwareComponent

40

© SAP 2008 /

Runtime Systems

SDA Transport via DI Export Web UI


TMS DEV System

Build Server(CBS)

Buildspace

Repository(DTR)

Workspace

NWDI


DeveloperStudio

activate

TMS TEST System TMS PROD Systemexport &release

Dev. Config


TESTDEV PROD

DI Export Web UI

check In

SDA TransportRequest

SDA

TransportRequest

SDA

SDA SDA

SDA

CM Services*

For exporting SDAs, the same UI as for exporting SCAs is used. In the first step is to decide whether youwant to export SCAs or SDAs.

The Advantages of an SDA Transport via the DI Export Web UI are:One tool is used to configure the landscape and to perform transportsPure Deployment to target system – no rebuild neededThe transport granularity is SDA

The disadvantages of transporting and SDA are:No repair capabilities in target system

You have to select the SDAs that you want to transport, manually. If you forget to transport one SDA thatwas changed, your application might not run in the target system or might not show the expected behavioras older SDAs are used together with the new one.

41

© SAP 2008 /

SDA Export via DI Export Web UI (1/3)

1. Select a Systemand an Export Mode

2. Select a SoftwareComponent and one

or several DCs

This slide and the following ones show the process for attaching an SDA to a transport request via the DIExport Web UI. The first step is to decide about the source system and whether you would like to transport anSCA or an SDA. In this example, we will use SDA. In case of an SDA Export, the next step is to choose aSoftware Component. The DCs belonging to this component will be displayed and you can mark the ones thatyou would like to transport.

42

© SAP 2008 /


3. Set Options

4. Transport Requestis taken from CTS

In the third step, you can decide on the criteria for stopping the export in case of errors. In the fourth step aTransport Request is displayed. The request is made for the system that was chosen in the first step. Also inhere, you will have the option to change the Transport Request by clicking on the link Transport Requests.The Transport Organizer Web UI will open up. In addition, you can add a note that will again become part ofthe documentation of the Transport Request.

43

© SAP 2008 /


5. Summary ofsettings which will beused for the Export…

... And informationabout Export

In the last step, you can see a summery of the DCs that will be exported and on the settings that you made.Now the export can be started. After the export, you’ll receive a message on the same screen, that the exportis finished. If you scrolled down to the bottom, you’ll find a log for the export.

44

© SAP 2008 /



3. News on Using CTS+ for different Applications3.1 Master Data Management3.2 Single System Track in CMS3.3 Activity Transport3.4 SCA / SDA Transport


Agenda

45

© SAP 2008 /

NWDI - CTS Integration

Current CMS

Attach toTransportRequest afterapproval

Attach toTransportRequest afterassembly

SingleSystemTrack

New CM Services

Creation ofDevConfigvia CTS/TMS

Attach Activityin DS

SCA, SDA export inDI Export Web UI

AttachSDA withinDS

SP12/13 SP14 EHP1 Future

…………

…………

Switch to maintenance mode /No further development ofNWDI CMS

Future development

The left side of the picture – Current CMS - shows features which are available in CMS or will be provided inenhancement package1.

With SAP NetWeaver 7.0 SP12/13 a CTS+ Integration into CMS is provided in the Approval tab.With SAP NetWeaver 7.0 SP14 a CTS+ Integration into CMS is provided in the Assembly tabWith enhancement package 1 for SAP NetWeaver 7.0 you can use a Single System Track in CMS

The right side – New CM Services - shows the functionality which will be provided via the new CM Services.The first delivery of the CM Services is planned for enhancement package 1 for SAP NetWeaver 7.0. Therewill be no new features provided in CMS. Maintenance is ongoing for sure.CM Services are part of SAP NetWeaver usage type AS-Java (CTS-System, e.g. Solution Manager). TheTransport System needs to have enhancement package 1 for SAP NetWeaver 7.0 installed.With enhancement package 1 for SAP NetWeaver 7.0 the following services are planned to be provided:

You can create a Development Configuration from within CTS when creating a new non-ABAP system.You can attach an Activity to a transport request by the help of new functionality in Developer Studio (asdescribed before).A new DI Export Web UI offers the possibility to attach SCAs and SDAs to a transport request (asdescribed before). A link to call this service is available from the Development Configuration UI.

The CM services have to run on the same system as the Deploy Web Service.Additional services are planned for the future. One example is the option to attach an SDA to a transportrequest in the Developer Studio. In addition, it is planned to integrate the services into the SAP NetWeaverAdministrator.You can use the services provided with enhancement package 1 for SAP NetWeaver 7.0 if they providebenefits for you. But there are no migration tools available yet from CMS to CM Services.The CM Services are not part of CE, except for the option to attach an Activity to a transport request in theDeveloper Studio. A delivery with CE is planned for the future. To be able to use the Activity Transport in CE,you have to use a NWDI on enhancement package 1 of SAP NetWeaver 7.0.

46

© SAP 2008 /

Outlook - Grow when Your Needs Grow

DSLocalDevConfLocalBuild

add CTS+TransportsReportingComplexlandscapes

addSolution ManagerChange RequestManagementEnd to EndProcess Integration

Option for gradual approach is plannedfor next releases after enhancementpackage 1 for SAP NetWeaver 7.0

LocalDevelopment

TeamDevelopment

DevelopmentLandscape

Company wideChange Management

addNWDI Server:

Versioning(DTR)

Central Build(CBS)Global

DevConfin NWA

On the previous slides, we have seen the CM Services which are planned for enhancement package 1 forSAP NetWeaver 7.0.If these offerings of the CM Services are beneficial for you, you can start using them with enhancementpackage 1 for SAP NetWeaver 7.0.The support for the classical CMS continues – but there is no developmentof new major features.Also CMS offers an integration with CTS+ (in the assembly step in SAP NetWeaver 7.0 SPS 14 integrations,Single System Tracks could help as well).There is no migration process from CMS to CM Services so far (it's planned for the next version of CMServices). You might have to set up new processes and change configurations when moving to CM Services.So please think what offers the biggest benefits. Is it e.g. the Activity or SDA transport or more the CTS+support in general? If it is the second, don’t invest to much in the CM Services right know.This slide shows what we plan for the future and it might be even more beneficial. The idea is that you canstart with simple development processes. One or two developers can start testing the development on SAPNetWeaver by just using the Developer Studio or they can even start with an application. They will use a localDevelopment Configuration and a local build.If after a while, you have more developers or decide that you need e.g. an option for versioning or for centralbuild (Global Development Configurations), you can add an NWDI server. The CM Services that we haveseen before are planned to be provided in the SAP NetWeaver Administrator. This will offer the option to useDTR and CBS and to use the new services for exporting. You don’t need a CTS+ system in this step. You canthen do manual exports and imports, but no automated transports based on transport routes .If you have a need for transports and reporting or if your system landscape becomes more and more complex,you could add a CTS+ server later on and profit from the integration of CTS+ in the different tools. CTS+ willhelp you organizing your landscape and automate and monitoring transports.The final step would be to use Solution Manger for End to End ProcessesThis option to grow with your landscape offers the chance to increase functionality when your processes askfor it. You can start simple. Enhancing your processes will be possible at any time.

48

© SAP 2008 /

Copyright 2008 SAP AGAll 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 changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayedare the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, orother items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie diedazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namenvon Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.

Alle Rechte vorbehalten.