e2e change control management

50
SAP® Enterprise Support SAP Solution Manager Enterprise Edition E2E Change Control Management Overview SAP Solution Manager Product Management SAP AG

Upload: bhagawanth-reddy

Post on 20-Feb-2015

76 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: E2E Change Control Management

SAP® Enterprise SupportSAP Solution ManagerEnterprise Edition

E2E Change Control ManagementOverview

SAP Solution Manager Product ManagementSAP AG

Page 2: E2E Change Control Management

Motivation to Extend the Change andTransport System

© SAP 2007 / Page 2

Change and Transport System (CTS) and Netweaver DevelopmentInfrastructure provide powerful functions to control transports inABAP and JAVA.

What was missing?Synchronized import into double stack systems

A solution for the transport of Portal content

A central administration interface for all types of transports and systems

Tracking and management of Non-ABAP objects with Change Request Management

The open issues are addressed with the Enhanced Change andTransport System

Page 3: E2E Change Control Management

Enhanced Change and Transport System(CTS+)

© SAP 2007 / Page 3

Connect Java Systems to standard CTS

Non-ABAP applications inherit all properties of the ABAP Change andTransport System in terms of documentation, tracking and troubleshootingfeatures

Manage transport of ABAP and non-ABAP-objects centrally

Allows combined transports for mixed objects (ABAP, JAVA, …)

Allows synchronized changes to business processes which run in ABAPand JAVA

100% Compatible with SAP Solution Manager

No need for upgrade of Java landscapes

Page 4: E2E Change Control Management

Change and Transport System

Developer Studioand

NWDI

Developer Studioand

NWDI

ExchangeInfrastructure

IntegrationBuilder

ExchangeInfrastructure

IntegrationBuilder

ABAPWorkbench SE80

ABAPWorkbench SE80 Development

LandscapeQuality

LandscapeProductionLandscape

QualityComponent n

QualityComponent n

QualityComponent 1

QualityComponent 1

ProductionComponent nProduction

Component n

ProductionComponent 1Production

Component 1

.

.

.

.

.

.

chec

k in

Transport Transport

Deploy Deploy

SCA

Enterprise PortalContent

Administrator

Enterprise PortalContent

Administrator

EPA

One Transport Order

…(open Interface fornon-ABAP objects)

…(open Interface fornon-ABAP objects)

TPZ

Page 5: E2E Change Control Management

Transport of:Java-based and JEE-based objects

Software Component Archives (SCAs)Software Deployment Archives (SDAs)Enterprise Application Archives (EARs)

Portal-based objectsEnterprise Portal Archives (EPAs)Portal Application Archives (PARs)Knowledge Management objects (KMContent and KM Configurations) (SPS14)

PI/XI-based objectsIntegration Builder Objects (TPZs)

SLD Content (SPS13)Any Files (.doc, .xls, .xml, …)

Supported Solutions and Deployment Options

Deployment Options:SDMXISLDFS

Page 6: E2E Change Control Management

Transporting Non-ABAP Changes

Legend

logical transport route of non-ABAP objects

physical transport route of non-ABAP objects

check-in/check-out of non-ABAP objects

transport route of ABAP objects

ABAPTransportController

Non-ABAP

Virtual QAS Virtual PRD

Java DEV Java PRDJava QAS

SAP NetWeaver Application Server CTS+

Non-ABAPNon-ABAP

New System Type:

Virtual Non-ABAP System

Transport parameter

contain deploy options

Page 7: E2E Change Control Management

Enhanced Change and Transport System -Process

Web Service forDeployment

Web Service forDeployment

Web Interface toTransport Organizer

Assign archive totransport request

ABAP TransportController

Create TransportRequest

Portal - DEV

Create content

Portal - QAS

Portal - PRD

Release TransportRequest

Virtual QAS

Virtual PRD

Export JavaArchive

Call WebService (Close

Coupling)

Import

Import

Deploy

Deploy

Deploy

Deploy

Page 8: E2E Change Control Management

Export Java Archive to CTS (Close Coupling)

Page 9: E2E Change Control Management

Web UI – New with SPS13

Page 10: E2E Change Control Management

Web UI - Process

2007

1 Create Change Request2 Attach Object3 Optional: Display Request4 Release

1

2

3

4

Page 11: E2E Change Control Management

ABAP System Landscape vs. Java Track

ABAP Stack

Runtime

Java Stack

SAP NetWeaver - Production

SystemRuntime

Build Env.

Workbench

Repository

ABAP Stack

Runtime

Java Stack

SAP NetWeaver – Quality Assurance

SystemRuntime

Build Env.

Workbench

Repository

ABAP Stack

Runtime

Java Stack

SAP NetWeaver - Development

SystemRuntime

Build Env.

Workbench

Repository

PROD System

ABAP System

QA System

ABAP System

TMS: 3-System-Landscape

DEV System

ABAP System Consolidation Delivery

ChangeRequests

ChangeRequests

CMS: Track„QA System“

CONS System TEST SystemPROD System

Runtime System

TEST System

Runtime System

DEV SystemRuntime System

DevelopmentConfiguration

CONS System

Runtime System

DevelopmentConfigurationChange

RequestsSCASCA

assembly

Page 12: E2E Change Control Management

Synchronization of ABAP and Java Transports

CMS: Track

PROD System

TMS: 3-System-Landscape

DEV System

ABAP System

ABAP Stack

Runtime

Java Stack

SAP NetWeaver - Production

SystemRuntime

Build Env.

Workbench

Repository

ABAP Stack

Runtime

Java Stack

SAP NetWeaver – Quality Assurance

SystemRuntime

Build Env.

Workbench

Repository

ABAP Stack

Runtime

Java Stack

SAP NetWeaver - Development

SystemRuntime

Build Env.

Workbench

Repository

DEV SystemRuntime System

DevelopmentConfiguration

CONS System

Runtime System

DevelopmentConfiguration

SCA

ChangeRequests

SCA

assembly

QA SystemABAP System

PROD SystemABAP System

Java Runtime Java Runtime

ChangeRequests

SCA

deployment istriggered by tp

import

check-in to ABAPchange request

Page 13: E2E Change Control Management

Roadmap NWDI – CTS Integration

ABAP Java

SAP NetWeaver – DEV

TMS System-Landscape

ABAP Java

SAP NetWeaver – PROD

ABAP Java

SAP NetWeaver – QA

Runtime Systems

Single tools to configure the landscape and to perform transportsAutomated synchronization of the QA and PROD systems

QA System

ABAP System

Java System

DEV System

ABAP System

Java SystemDevelopmentConfiguration

PROD System

ABAP System

Java System

TransportRequestTransport

RequestTransportRequest

SCA

TransportRequestTransport

RequestTransportRequest

SCA

DeveloperStudio

Java Development Environment

Build Server(CBS)

Buildspace

Repository(DTR)

Workspace

Change Management Server (CMS) SCA

assembly & attach

Important

In addition the existing NWDI will be delivered infuture NetWeaver Releases as SAP‘s offering forJava-only landscapes.

++

Page 14: E2E Change Control Management

Combined transports for ABAP and JAVAobjects

Development Landscape QALandscape

ProductionLandscape

DevelopmentEnvironment

SE80

DS & DI

System

mySAP ERP

System

mySAP ERP

System

mySAP ERP

develop activate test release test useapprove

combinedtransports

combinedtransports

Page 15: E2E Change Control Management

Tracking of Changes

© SAP 2007 / Page 15

Use the Import History to find information on transports in Non-ABAPsystems:

Object ListsTransport Logfiles

The Import History can be called from any system in the TransportDomain

Page 16: E2E Change Control Management

Import History of Non-ABAP System

© SAP 2007 / Page 16

Page 17: E2E Change Control Management

Navigate into the Object List

© SAP 2007 / Page 17

Page 18: E2E Change Control Management

Navigate into the Transport Logfiles

© SAP 2007 / Page 18

Page 19: E2E Change Control Management

Import History of Non-ABAP System (Java)

Page 20: E2E Change Control Management

Navigate through the Object List (Java)

Page 21: E2E Change Control Management

Navigate through the Transport Logfiles (Java)

Page 22: E2E Change Control Management

Different Levels of Control

© SAP 2007 / Page 22

Change Request Management

SAP Solution Manager

Enhanced Change and Transport System (CTS+)SAP System ABAP Stack

ABAP

BetterControl

BetterControl

ImprovedDocumentation

ImprovedDocumentation

Java .net …..

Page 23: E2E Change Control Management

Central Control of Transports in SolutionLandscapes

© SAP 2007 / Page 23

TransportLandscape

CRM

TransportLandscape

EP

TransportLandscape

BW

TransportLandscape

ERP

TransportLandscape

PI

Development Landscape QALandscape

ProductionLandscape

DevelopmentEnvironment

SE80DS & DI

Portal ContentAdministrator

System

mySAP ERP

mySAP CRM

System

mySAP ERP

mySAP CRM

EnterprisePortal

System

mySAP ERP

mySAP CRM

EnterprisePortal

BW

EnterprisePortal

BW BW

ProcessIntegration

(XI)

ProcessIntegration

(XI)

ProcessIntegration

(XI)

DS & DI

SE80

SE80Integration

Builder

SE80DS & DI

SAP Solution Manager

Transport Control

Page 24: E2E Change Control Management

Scenario with XI Systems as of NW2004s/SP12

XISource System

ABAP stack

Java stack

XITarget System

ABAP stack

Java stack

Transport Route

Transport Request

ABAP Objects

Java Objects

Changes of ABAP objects arerecorded automatically by CTS

Changes of XI repository and XIdirectory objects have to bechecked in into an CTStransport request manually

One transport request maycontain the changedABAP objects and thechanged XI repository anddictionary objects as well

Import of the XI repository anddirectory objects into the Java stackof the XI system is controlled by thetransport control program tp

Technically the import into the Javastack is one additional import stepwhich starts the XI import client viathe CFS deploy web service

Imports can be scheduled andmonitored by TMS

Page 25: E2E Change Control Management

Transport Runtime with Systems NW04sSPS12

TMSDomain

Controller

ABAP

Java

ABAP

Java

ABAP

Java

ABAP

Java

CTS+

DeployService

CTS+

DeployService

CTS+

DeployService

CTS+

DeployServiceIB IB IB

NW04s SPS12

NW04s SPS12 NW04s SPS12 NW04s SPS12

Transport Transport

Double StackDev. System

Double StackQA. System

Double StackProd. System

SDM SDM SDM

Page 26: E2E Change Control Management

Transport Runtime with Systems NW04s <SPS12

Double StackDev. System

TMSDomain

Controller

ABAP

Java

ABAP

Java

ABAP

Java

ABAP

Java

CTS+

DeployService

CTS CTS CTS

IB IB IB

NW04s SPS12

NW04 SPS09NW04 SPS14 (PI)

Transport Transport

ABAPTransports

NW04 SPS09NW04 SPS14 (PI)

NW04 SPS09NW04 SPS14 (PI)

Double StackQA. System

Double StackProd. System

SDM SDM SDM

Page 27: E2E Change Control Management

Transport Runtime with systems NW04s <SPS12

TMSDomain

Controller

ABAP

Java

ABAP

Java

ABAP

Java

ABAP

Java

CTS+

DeployService

CTS CTS CTS

IB IB IB

NW04s SPS12

Transport Transport

JavaTransports

ManualUpload

of tpz, sca File

NW04 SPS09NW04 SPS14 (PI)

NW04 SPS09NW04 SPS14 (PI)

NW04 SPS09NW04 SPS14 (PI)

Double StackDev. System

Double StackQA. System

Double StackProd. System

SDM SDM SDM

Page 28: E2E Change Control Management

Transport Runtime with systems NW04s <SPS12

PortalDev. System

PortalQA System

PortalProd. System

TMSDomain

Controller

ABAP

Java

Java Java Java

CTS+

DeployService

SDM SDM

NW04s SPS12JavaTransports

ManualUpload

of epa File

NW04 SPS09 NW04 SPS09 NW04 SPS09

SDM

Page 29: E2E Change Control Management

Scenario with XI Systems < NW2004s/SP12

XISource System

ABAP stack

Java stack

XITarget System

ABAP stack

Transport Route

Transport Request

Java Objects

Transport Request

ABAP Objects

Transport Route

CTS+Server

Java stackNon-ABAPsystem in

TMS with adifferent SID

ABAP systemin TMS with

the SID of the“real” XIsystem

CTS+ Servercontrols the

imports into theJava stack of the

XI system

TransportOrganizer (SE09)of a CTS+ Server

is used to managethe transport

requests of theJava stack of the

XI system

Two transport routes andseparate transport requests

for the ABAP- and Javastack are required

Solution Manager and ChaRM canbe used to synchronize the

transport requests of the ABAP-and Java stack of the XI systems

Page 30: E2E Change Control Management

CTS+ Roadmap

SP18

Enhanced Change and Transport System in SAP NetWeaver 7.0SP12

Software distribution of:NetWeaver Portal (epa)XI objects (tpz)NWDI (sca, sda)ERP/ESSCRM (Java apps)

File system deployment

SP13

Software distribution of:Composition Environmentobjects (sca, sda)SLD objectsKM content

Close coupling check-in forNWDI, Portal and XI

Transport Organizer fornon-ABAP systems

EHP1

Software distribution of all relevantSAP objects

Object list of non-ABAP objectsavailable in CTS

Search functionality for non-ABAPobjects in SE03

Full integration of NWDI into CTS+

SP14

Close coupling check-in forSystem Landscape DirectoryKnowledge Management & Collaboration

Close coupling check-in without fileshare

Increased integration of NWDI into CTS+

Improved installation and configuration

Software distribution of non-SAP objects

File Streaming

Page 31: E2E Change Control Management

What are the recommendations from SAP?

CTS+ is the recommended transport tool for all SAP Business Suitecustomers to transport all kind of ABAP, non-ABAP and non-SAPobjects

NWDI is the development infrastructure for Java based developmentand will be fully integrated into CTS+

SAP Solution Manager on top of CTS+ offers methods andprocedures for efficient change request management

Page 32: E2E Change Control Management

SPS 13: Transport Routes

Transport Routes between non-ABAP DEV- and QA-systems

SP12Routes between CTS+ system andnon-ABAP QA systemsSeparate client needed for eachnon-ABAP DEV system for propertransport control (automatic targetsystem assignment, checkin folder)

SP13„Normal“ consolidation routesbetween DEV and QA systemsMultiple non-ABAP DEV systemscan be handled within one client inthe CTS+ server

Page 33: E2E Change Control Management

SPS 13: Transport Requests

Transport Requests contains the SID of the non-ABAP system

SP12Transport Requests arecreated with the SID of thecommunication system(the CTS+ server) as partof the request namee.g. OTOK000129

SP13Transport Requests arecreated with the SID of thenon-ABAP developmentsystem as part of the requestnamee.g. EPDK000129

Page 34: E2E Change Control Management

Strategy Parameters (1)

The process of releasing changes to the transport system has to fitto the overall company policy

the process isn‘t hard coded in the applications using the transport APIthe process can be configured in the transport system

The strategy parametersare part of the TMStransport toolconfigurationThey can be set for eachsystem

They are user independent

Page 35: E2E Change Control Management

SPS 13: Strategy Parameters (2)

WBO_GET_REQ_STRATEGYTagged

Transport Organizer Web UI (or ChaRM)has to be used to create a request for anuser and to mark them with a tagIf there is no tagged request found for agiven user, the application reacts with anerror

SmartIf there is no tagged request available foran user; the transport backend creates avalid requestThe export wizards in the applications arenever interrupted, because there is alwaysa valid request

WBO_REL_REQ_STRATEGYManual

Transport Requests can only be releasedusing the Transport Organizer Web UI orChaRM

AutomaticTransport Requests are automaticallyreleased from the Transport API after theobjects are attached to the request

Two parameters determine the behaviour of the Transport API

Page 36: E2E Change Control Management

SPS 13: Close Coupling – File Transfer

A share or mount has to be used to transfer the files from theapplication server to the CTS+ server

Transport Tool parameter NON_ABAP_WBO_INBOX has to be set for each development system(name of the folder in which the desired files can be found on the CTS server)

XIBecause XI systems are double stack systems, the files don‘t have to be transferred at all; they arecreated within the Java stack and they are used from the Transport Organizer running in the ABAPstack of the same system

XI Repository and XI Directory tpz files can be exported to the same folder (can be configured inthe XI system)After attaching a file to a request, the tpz file is deleted from that export directory

EP, NWDIThe need of a share for the close coupling scenario is a restriction especially in heterogeneouslandscapes (Windows, Unix)As of SP14 or SP15 the JCO connection already used to transfer the metadata will be used totransfer the files as well (via streams)

Page 37: E2E Change Control Management

SPS 13: Example: EP Close Coupling –Scenario 1

Scenario 1Generate and automaticallyrelease transport requests

Strategy:

Create new request if novalid request isavailable

Release transport requestautomatically afterattaching the epa file

Page 38: E2E Change Control Management

SPS 13: Example: EP Scenario 1 (1)

Content Developerdecides to export thepackageMyEntertainment

Page 39: E2E Change Control Management

SPS 13: Example: EP Scenario 1 (2)

Transport Backend generates atransport request

Transport Request, Owner andDescription are displayed in theexport wizard of the application

The filename of the portal archivewhich will be created duringexport is generated and can’t bechanged by the user

Page 40: E2E Change Control Management

SPS 13: Example: EP Scenario 1 (3)

The portal archive is exported andattached to the transport request

The transport request is automaticallyreleased and exported and is added tothe import queue of the configured QAsystem(s)

Page 41: E2E Change Control Management

SPS 13: Example: EP Scenario 1 (4)

The transport request is visible in the import queueof the QA system

Compared to loose coupling some additional metadata are stored in the file object which will allow tosearch for EP transport packages in transportrequests- SP13: name of transport package is displayed- SP14: SE03 can be used to search for packages

Page 42: E2E Change Control Management

SPS 13: Example: EP Close Coupling –Scenario 2

Scenario 2Create and release transportrequests manually

Strategy:

Don’t create new request ifno valid request isavailable; use transportorganizer Web UI tocreate a valid request

Don’t release the transportrequest after attachingthe epa file; usetransport organizer UIto release a request

Page 43: E2E Change Control Management

SPS 13: Example: EP Scenario 2 (1)

The related link „TransportRequests“ is used to startthe Transport Organizer WebUI before trying to exportportal content.

Remark: A How To guide willexplain how to create thechange management roleand how to create theserelated link

Page 44: E2E Change Control Management

SPS 13: Example: EP Scenario 2 (2)

Transport Organizer Web UI is started in a new window

A new transport request can be created or an existingone can be selected from the list of available requests

The new created or selected request has to be set asstandard request

Page 45: E2E Change Control Management

SPS 13: Example: EP Scenario 2 (3)

The previous selected transportrequest is displayed in theexport wizard

Page 46: E2E Change Control Management

SPS 13: Example: EP Scenario 2 (4)

The portal archive is exported andattached to the transport request

In this scenario the transport request isnot released and therefore can be usedto attach additional objects

Page 47: E2E Change Control Management

SPS 13: Example: EP Scenario 2 (5)

In this scenario several transportpackages can be attached to the sametransport request

Page 48: E2E Change Control Management

SPS 13: Example: EP Scenario 2 (6)

After attaching all desired transportpackages to a transport request,the Transport Organizer iViewhas to be used to release thetransport request

Before a transport request isreleased the user can check ifthe request contains all thepackages which shall betransported

Invalid packages can be removedfrom the transport request

Page 49: E2E Change Control Management

SPS 13: Example: EP Scenario 2 (7)

After releasing the transport request, the request appears inthe import queue of the configured QA system

The object list can be displayed via double click to therequest

Double click to an epa file displays the attributes (e.g. thepackage name and the deployment method)

Remark: the epa files are deployed into the target system inthe order they were attached to the request (Dateattribute)

The sequence of the epa files in the object list is thedeploy sequence

Page 50: E2E Change Control Management

© SAP 2007 / Page 50

Thank you!