Abdul Razack RIG US, SAP Labs

Transcription

1 Using CMS Abdul Razack RIG US, SAP Labs

2 What is CMS Landscape Directory Change Management Service Central User-Management SDM Name Server Design Time Repository Component Build Service Runtime J2EE application NetWeaver Developer Studio HTTP connection SAP AG 2004, Java Development Infrastructure Overview / 2

3 Compares with TMS [ABAP] DV2 Transport Domain Transport Domain DEV CON PRO ABAP src 1.0 ABAP src 2.0 Central Development TRANS Consolidation Production SAP AG 2004, Java Development Infrastructure Overview / 3

4 What function does it provide Source Code Control Components Distributed versioning Encapsulation Conflict resolution Change tracking Controlled usage Nested components Landscape Administration Administration cockpit Propagation Configuration templates Build Support Logical systems Production units Automated propagation Approval process SAP AG 2004, Java Development Infrastructure Overview / 4 Build on demand Predefined build scripts Activation

5 Development Life-Cycle Management Overview ADMINISTRATION / QM DEVELOPMENT ADMINISTRATION Product and Application define Track & Dev. Config. import Development release SL Change Mgmt. prepare Delivery define Next Release 1. SLD: Define software to be developed Define a product Define one or more software components (SCs) that form the product 2. CMS: Define development landscape Define a track for the specific release of the SC Development configurations are generated for each development state of an SC (DEV or CONS) 3. Dev. Studio: Edit and build development objects Use the SAP NetWeaver Developer Studio with access to the SAP NW JDI for all development projects Release objects for further processing by QM/Admin. 4. CMS: Define further use of SCs Transport into next dev. steps, quality assurance, and assembly using the Change Management Service 5. CMS: Deliver SCs and patches Deliver software component versions building products as well as support packages 6. CMS: For the next SC release define a new track SAP AG 2004, Java Development Infrastructure Overview / 5

6 Java Software Lifecycle Management - Roles SAP AG 2004, Java Development Infrastructure Overview / 6

7 CMS - Definition of Tracks and Development Configurations ADMINISTRATION / QM DEVELOPMENT ADMINISTRATION Product and Application define Track & Dev. Config. import Development release SL Change Mgmt. prepare Delivery define Next Release 1. SLD: Define software to be developed Define a product Define one or more software components (SCs) that form the product 2. CMS: Define development landscape Define a track for the specific release of the SC Development configurations are generated for each development state of an SC (DEV or CONS) SAP AG 2004, Java Development Infrastructure Overview / 7

8 A track consists of (CMS-) systems. A track comprises configurations and runtime systems (systems in CMS) required for developing software component versions. It ensures stable states of deliverables used by subsequent tracks. Track Dev. Configuration SC_DEV Dev. Configuration SC_CONS Workspaces Workspaces Buildspace Buildspace Central Development Consolidation Test Production SAP AG 2004, Java Development Infrastructure Overview / 8

9 Tracks are defined using the CMS landscape configurator [demo] SAP AG 2004, Java Development Infrastructure Overview / 9

10 Development configurations are created during track definition. Development Objects Retrieve dev. configuration DTR /ws_dev /ws_cons Retrieve storage location of dev. configuration /inactive /active SLD CMS (Landscape Configurator) /inactive /active /bs_dev /bs_cons Register dev. configuration CBS Binaries of used SCs During the track definition in CMS, workspaces and buildspaces are created. They obtain relevant versions of source objects and binary archives according to the definition of SCs to be defined and used SCs. This combination will be stored in the CMS as development configuration. The CMS registers it in the SLD so that it can be found across the entire landscape. The local IDE retrieves the storage location of dev. config. from the SLD and retrieves the data from the appropriate CMS server. SAP AG 2004, Java Development Infrastructure Overview / 10

11 Transport using CMS ADMINISTRATION / QM DEVELOPMENT ADMINISTRATION Product and Application define Track & Dev. Config. import Development release SL Change Mgmt. prepare Delivery define Next Release 1. SLD: Define software to be developed Define a product Define one or more software components (SCs) that form the product 2. CMS: Define development landscape Define a track for the specific release of the SC Development configurations are generated for each development state of an SC (DEV or CONS) 3. Dev. Studio: Edit and build development objects Use the SAP NetWeaver Developer Studio with access to the SAP NW JDI for all development projects Release objects for further processing by QM/Admin. 4. CMS: Define further use of SCs Transport into next dev. steps, quality assurance, and assembly using the Change Management Service SAP AG 2004, Java Development Infrastructure Overview / 11

12 Consolidation, assembly Transport manager Import in consolidation system of the track Assembly of product version Quality manager Controls consolidation and test steps Additional quality assurance SAP AG 2004, Java Development Infrastructure Overview / 12

13 Using CMS Transport Studio [demo] SAP AG 2004, Java Development Infrastructure Overview / 13

14 ADMINISTRATION / QM DEVELOPMENT ADMINISTRATION Delivery Product and Application define Track & Dev. Config. import Development release SL Change Mgmt. prepare Delivery define Next Release 1. SLD: Define software to be developed Define a product Define one or more software components (SCs) that form the product 2. CMS: Define development landscape Define a track for the specific release of the SC Development configurations are generated for each development state of an SC (DEV or CONS) 3. Dev. Studio: Edit and build development objects Use the SAP NetWeaver Developer Studio with access to the SAP NW JDI for all development projects Release objects for further processing by QM/Admin. 4. CMS: Define further use of SCs Transport into next dev. steps, quality assurance, and assembly using the Change Management Service 5. CMS: Deliver SCs and patches Deliver software component versions building products as well as support packages SAP AG 2004, Java Development Infrastructure Overview / 14

15 Approval tests and delivery Transport manager Quality manager SAP AG 2004, Java Development Infrastructure Overview / 15

16 Delivery Process - Shipment to Customers Unique problem for business application software vendors: Customers need to modify standard software Need delivery format including all types of executables and sources Need complete build environment Need concepts for handling of modifications SAP Customer Applications Applications With NWDI NetWeaver NetWeaver jars, java sources, dictionary, NetWeaver NWDI package format enables shipment of various software types (e.g. jars, java sources and dictionary) Build services at customer site allow recompilation of modified sources A source code control system based on distributed versioning Enables controlled source delivery between different locations (e.g. SAP customer) Allows conflict resulotion between customer modifications and new SAP deliveries SAP AG 2004, Java Development Infrastructure Overview / 16

17 Transport Between Tracks Track A Track A Track B Track B Track C Track C Dev. Configuration SC_Dev Dev. Configuration SC_Cons 1 Workspaces Change Request Workspaces Comp. A Version i Comp. A Version i 2 Comp. B Version j Buildspace Buildspace Central Development Consolidation Test SAP AG 2004, Java Development Infrastructure Overview / 17

18 Steps needed to transport XI objects with CMS Create a user with the role SAP_XI_CMS_SERV_USER in the XI server Provide the url to Dev, QA and Prod repository servers e.g ( Create tracks with repository type XI with the above user SAP AG 2004, Java Development Infrastructure Overview / 18

19 Step contd.. Activate CMS by setting the com.sap.aii.ibrep.core.cms.activated flag to true in both Integration Directory and Repository. Also set the following flags com.sap.aii.ibrep.core.cms.enablecltransport=true com.sap.aii.ibrep.core.cms.enabletransportwizard=true com.sap.aii.ibdir.core.cms.enabletransportwizard=true The above flags need to be set in the exchange profile SAP AG 2004, Java Development Infrastructure Overview / 19

20 CMS with XI Once the flags are enabled, the XI export shows two options SAP AG 2004, Java Development Infrastructure Overview / 20