cm services and cms in sap netweaver 7.3

CM Services and CMS in SAP NetWeaver 7.3

October 2013 Public

2013 SAP AG. All rights reserved. 2 Public

Disclaimer

This presentation outlines our general product direction and should not be relied

on in making a purchase decision. This presentation is not subject to your license

agreement or any other agreement with SAP. SAP has no obligation to pursue any

course of business outlined in this presentation or to develop or release any

functionality mentioned in this presentation. This presentation and SAP's strategy

and possible future developments are subject to change and may be changed by

SAP at any time for any reason without notice. This document is provided 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 assumes no responsibility for errors or omissions in this

document, except if such damages were caused by SAP intentionally or grossly

negligent.


Agenda

CM Services

1. Scope in SAP NetWeaver 7.3

a. With CTS

b. Stand-alone

2. Services in Detail for SAP NetWeaver 7.3

3. CTC for creating SCs

4. Configuration in NWDS

5. Recommendations

CMS

1. New in SAP NetWeaver 7.3 SP 10


Scope in SAP NetWeaver 7.3

The scope for CM Services in SAP NetWeaver 7.3 is the same as in enhancement

package 1 for SAP NetWeaver 7.0

PLUS what is described on the following slides.

In SAP NetWeaver 7.3 there are two options for using CM Services:

Integrated with CTS (using a CTS system on enhancement package1 for SAP NetWeaver 7.0 SP7 at least) to make use of transport functionality

Stand-alone with import and export functionality


Agenda

CM Services


a. With CTS

b. Stand-alone




5. Recommendations

CMS



Runtime Systems

TMS System-Landscape Configuration DI Development Configuration

TMS DEV System

Build Server

(CBS)

Buildspace

Repository

(DTR)

Workspace

NWDI

Java Development Environment

Developer

Studio

Dev. Config

TMS TEST System TMS PROD System

Java URL Java URL Java URL

TEST

TEST

TEST

DEV

TEST

PROD

SDA SDA SDA SDA

check In

activate

CM Services

SDA SDA

Transport

Request

DIP

Transport

Request

DIP

DIP

Activity DIP

SDA SDA

Release

Activity

SDA Transport based on Activities


Creating Development Configurations

Create system in TMS and mark it as system with Development Configuration

Development Configuration is created automatically, fill in the details

Start Development Configuration Management from TMS for changes

Create

System Change

System


Agenda

CM Services


a. With CTS

b. Stand-alone




5. Recommendations

CMS



NWDI

CM Services, CTS+ and NWDI

Source

Storage

Versioning

Archive

Storage

Config.

Management

Packaging

Build

Support Archive

Storage

Packaging

Source

Storage

Versioning

Config.

Mgmt DTR: Source Storage

&

Versioning

CBS: Build Support

&

Archive Storage

DI CM

Services: Config. Mgmt,

Synchronize

(Import) & Export


Runtime Systems

CM Services in Stand-alone Mode

TEST DEV PROD

DI Export Web UI

SCA SCA SDA

SUM SUM

SCA

Build Server

(CBS)

Buildspace

Repository

(DTR)

Workspace

NWDI

Java Development Environment

Developer

Studio

activate

check In

CM Services*

DI Synchronize

(Import) Web UI

Fill workspaces

and

buildspaces

SCA

Direct user action

Data is taken


Creating Development Configurations

Open NetWeaver Administrator of NWDI Server (where CM Services run)

Create Stand-alone Development Configuration


Agenda

CM Services



a. Development Configuration Management

b. Synchronize Service

c. Export Service

d. History Service

e. Import Service



5. Recommendations

CMS



CM Services in Detail (1/3)

Development Configuration Service

Made for managing Development Configurations

Integrated in process flow for creating non-ABAP systems in TMS (if used with CTS+)

Create Development Configurations in Stand-alone mode (if not connected to CTS+)

UI can be called from TMS or NetWeaver Administrator

Define build options

Exclude Software Components from deployment

Configure export modes

New in SAP NetWeaver

7.3 compared to SAP

NetWeaver 7.0 including

Enhancement Package 1



Synchronize Service

Made for synchronizing the NWDI with the runtime system (import only SCAs

into NWDI fitting to runtime system) - filling workspaces and buildspaces

UI can be called from History and Import Service UI

Replacement for upload system in CTS+

Export Service

Made for Exporting SCAs (or SDAs)

UI can be called from within Developer Studio or Development Configuration

Management

Possibility to export more than one SC at once

Set SP and / or patch level for SCAs in customer namespace



History Service

Made for finding out what has been imported / synchronized and exported

UI can be called from Export and Import Service UI

Import Service

Made for filling workspaces and buildspaces if you cannot use Synchronize

Service

UI can be called from Development Configuration Management

To be used in Stand-alone mode only


Agenda

CM Services





c. Export Service

d. History Service

e. Import Service



5. Recommendations

CMS



Development Configuration Management

System Landscape Directory

CTS

DevConfig

Info on SLD

(including User)

and CM

Services URL

Details on

DevConfig



Local Settings if used with CTS+

Repository and

Build Location

Information on

Runtime System

as defined in TMS

Include in /

Exclude from

Deployment

Define

transport

options



Local Settings in Stand-alone Mode

Repository and

Build Location

Runtime

System

Include /

Exclude from

Deployment

Inbox and Outbox



Software Component Definition

Build options: enter

e.g. paths to jdk if

same CBS is used to

manage development

for different releases

Software

Components

including

dependencies

Compare SCs in

list with SLD and

adapt to SLD state

if needed


Agenda

CM Services





c. Export Service

d. History Service

e. Import Service



5. Recommendations

CMS



Synchronize Service How to reach it

Call it via Link

in Import or

History Service

Call it via Related

Links in Development

Configuration

Management or via

link in Import, Export

or History Service


Synchronize Service Step 1

Choose

development

configuration

Get differences between runtime

systems and DTR / CBS



Define Inbox Path to

the SCAs deployed on

runtime system

The SCAs needed to set up the development configuration have to be

available in the folder that you enter in here. Two options to achieve this:

Copy the files from the runtime system to the system where you use the CM Services and use the target folder as Inbox Path.

Create a share to the original place of the SCAs that is accessible for the user SAPService of the CM Services system.


Synchronize Service Step 3 Decide on Actions

Click on Details

for more

information

File that is going

to be imported



Summary start

synchronization


Agenda

CM Services





c. Export Service

d. History Service

e. Import Service



5. Recommendations

CMS



SDA Export in Developer Studio

Release activities in the IDE

Attach the corresponding SDA(s) to

a Transport request retrieved from

CTS

Predecessor activities and build

dependencies are taken into

account to make sure that a

consistent state is transported.

SDAs involved can be part of

different SCs


Export Service How to reach it

Transport view in

developer studio

shows menu entry

to open Export UI

Use Related Link Export Service in Development Configuration Management


Export Service Stand-alone - Step 1

Choose a

Development

Configuration



Choose SCA(s)

to be exported



Maintain SP and

Patch Level for your

own components



Summary shows choices

made in previous steps

including current and new

SP and patch level


Export Service with CTS Step 1

Choose Development

Configuration and

decide if SCAs or SDAs

should be exported



Choose the SCAs

(or SDAs) that

youd like to export



In this case, only

components with

vendor sap.com had

been chosen setting the SP and patch level

is not possible

Choose Export

options



Transport request is

retrieved from CTS -

do changes if needed



Summary of the

settings made start export to attach the files

to the transport request


Agenda

CM Services





c. Export Service

d. History Service

e. Import Service



5. Recommendations

CMS



History Service

Call it via link in

other services

Choose a time frame, filter

for a specific Development

Configuration


Import History - Log

Imports for a specific

Development Configuration

Detailed Log

for the import

selected above


Agenda

CM Services





c. Export Service

d. History Service

e. Import Service



5. Recommendations

CMS



Import Service

Can only be used with Stand-alone Development Configurations

Start it e.g. from the Related Links in the Development Configuration

Management

Step 1: Choose

Development

Configuration


Import Service Step 2

Choose SCA

to be imported


Import Service Step 3

Results of

Validation -

Start Import


Agenda

CM Services




a. How to use it

b. How to reach it


5. Recommendations

CMS



CTC for creating new SC - Step 1

URL of SLD where

to store the SC

definition and

UID / PW



Name, Vendor

and release of

new SC assign to product if

required



Choose template

to get dependent

SCAs


CTC for creating new SC - Step 3a

Upload xml file

with dependency

templates if

required



Template

executed new SC created


Agenda

CM Services




a. How to use it

b. How to reach it


5. Recommendations

CMS



On Development Infrastructure Main Page


From Development Configuration Management


In NWA


Agenda

CM Services





5. Recommendations

CMS



Configure SLD

Enter SLD URL


Import Development Configuration

Step 1:

Choose SLD

as Source

Step 2:

Logon to NWDI


Select Development Configuration

Step 3:

Use filters to find the

Development

Configuration needed

Step 4:

Check details

and finish the

import


Agenda

CM Services





5. Recommendations

CMS



Recommendations

Use SAP Solution Manager as CTS System

Use the CM Services on your NWDI

Use Activity based SDA transport (Export Mode - Deployable Export - Activities)

Take a look at the following notes

1003674 Enhancement for non-ABAP systems in CTS

1361909 CM Services in CTS+

1775838 - CMS / CM Services: What to use in which scenario?


Agenda

CM Services





5. Recommendations

CMS



Multiple RFC Destinations in CMS

/dtr

Multiple RFC Destinations

Available starting with

SAP NetWeaver 7.30 SP

10

Define RFC Destination

per Track if needed

RFC Destination has to

be defined beforehand

Standard destination is

entered by default

Maintain Destination

provides more details

Thank you


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.

National product specifications may vary.

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.

SAP 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 other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.


2013 SAP AG. Alle Rechte vorbehalten.

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden.

Einige der von der SAP AG und ihren Distributoren vermarkteten Softwareprodukte enthalten proprietre Softwarekomponenten anderer Softwareanbieter.

Produkte knnen lnderspezifische Unterschiede aufweisen.

Die vorliegenden Unterlagen werden von der SAP AG und ihren Konzernunternehmen (SAP-Konzern) bereitgestellt und dienen ausschlielich zu Informationszwecken. Der SAP-Konzern bernimmt keinerlei Haftung oder Gewhrleistung fr Fehler oder Unvollstndigkeiten in dieser Publikation. Der SAP-Konzern steht lediglich fr Produkte und Dienstleistungen nach der Magabe ein, die in der Vereinbarung ber die jeweiligen Produkte und Dienstleistungen ausdrcklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zustzliche Garantie zu interpretieren.

SAP und andere in diesem Dokument erwhnte Produkte und Dienstleistungen von SAP sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und verschiedenen anderen Lndern weltweit. Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark.

cm services and cms in sap netweaver 7.3

Documents

sap netweaver

sap ag

cts system

public scope

system change system

public nwdi

public agenda

public disclaimer