software configuration management für traditionelle mainframe · pdf file ·...

© 2017 IBM Corporation

Software Configuration Management für traditionelle Mainframe-Artefakte

March 2017

Tage der Anwendungsentwicklung, Böblingen

Dennis BehmIBM z Systems SoftwareTechnical [email protected]

+49-7034-6432353

mailto:[email protected]


Übersicht Software Delivery Pipeline

2

zO

SB

ac

ke

nd

Mid

dle

tie

rF

ron

ten

d

CommonSCM System

COBOL, PLI, JCL, JAVA, C,

..

Technology specific

Build

Jenkins, ANT, JCL, …

ArtefactRepository

TEST QS PRODDEV

Separation of Duties

Release Management

Quality Gates /

Approvals

zOS Build OutputsLoads, JCL, DBRM, ..

Dep

loym

ent

Au

tom

atio

n

WAR, EAR, XML, DML, DDL, Config, ..


Develop Unit Test Integration TestSystem

TestAcceptance Test

Production Deployment

Software Delivery LifecyclesGeneric Overview of Development and Test Principles

Use modern SCM systems and IDEs to speed up the developer

Deploy your application under test with a single click

Move from manual testing to a automated and focused approach to reduce test overhead


Rational

IBM Developer for z System (IDz) – eine moderne integrierte Entwicklungsumgebung (IDE)

für die Hostentwicklung

Rational Team Concert Enterprise Extensions – eine plattformübergreifende Lösung für das

Application Lifecycle Management (ALM)

4

RTC IDz


IBM ALM Lösung: Rational Team Concert for Enterprise Platforms

Rational Team Concert integriert in dem

kundenspezifischen Entwicklungsprozess

– Software Configuration Management,

– Build-Management

– Projektplanung und –steuerung,

– die Erfassung und Bearbeitung von

Arbeitsaufträgen (WorkItems)

Aufgabenbezogene Entwicklung und Staging

Dependency Based Builds

Collaborative Development

Open Lifecycle and Service ManagementIntegration Platform

Continuous Delivery

Projektleiter Tester

Agile Teams

Entwickler

Operations

Stakeholder

Rational Doors Next Gen | Rational Team Concert | Rational Quality Manager

Collaborative Lifecycle Management


Rational Team Concert basiert auf Jazz Technologie

SCM Work Items

Jazz Team Server

Build

Iterationsplanung Transparente Projektsicht


Rational Team Concert High-Level Architektur

7

RTC Server

Agent

Agent

Agent

Agent

Agent

Datenbank


Mainframe Entwickler-Cockpit

8


SCM

9


Verwaltung der unterschiedlichen Software Stände in Streams

10


Überprüfung von Programmierrichtlinien während des Check-ins

11


Freigaben können ein 4-Augenprinzip erzwingen

12


MainframeBuildmanagement

13


Dependency Based Build für Cobol, PLI und C/C++ für z/OS

Der Build berücksichtigt Abhängigkeiten zwischen den einzelnen Objekten innerhalb eines

Streams

– Es werden gezielt diejenigen Objekte umgewandelt, die geändert wurden und von

geänderten Objekten abhängig sind

14

Objekt A

(Cobol)Objekt B(Copybook)

Stream ENTW

Verwendet

Objekt C(Cobol)

Buildable

Files

Objekt A

Objekt B

Objekt C

zOS

Verwendet


Beispiel Build-Report

15


Build scope and differentiators

Build type Scope / build options Techno-

logoy

Use Case(s)

Team Build • Full build

• dependency based

build

• Subset build

ANT > Developers integrating their work

Personal

Build

• Dependency based

build of

Incoming/Outgoing

Changesets

• Subset build

ANT > Developers wanting to build up their personal

runtime library without affecting their teammates,

make use for STEPLIB for their personal tests

User Build • Build a single file

from your local

sandbox

JCL > Developers to compile their module under

development / under test for doing unit testing in

an isolated environment.

> Developer wanting to make sure a program

does not have any compilation errors and can

overwhelm the build queue


Build sequentially

Process one language definition

Process one buildable file

For all language definitions

For all buildable files (of lang def)

Process one language definition

N threads to processn buildable files

For all language definitions

For all buildable files

Build multi-threadedsince 6.0.2

Multi-threaded team builds

17


Staging & Deployment mit UrbanCode Deploy

18


Übergabe der Build-Ergebnisse meiner Arbeit in das Artefakt-Repository

19


Die angekommenen Artefakte

20


Orchestrierung der unterschiedlichen Anwendungskomponenten

21


Definition der Deploymentprozesse einer Komponente

22


Durchführung des Deployments

23


Durchführung des Deployments

24


UrbanCode Plugin Ecosystem


SW Architecture


Technical overview - Traditional Mainframe Artifacts

Build System

Post build script

z/OS DeployToolkit

Create new version

CodeStationin HFS

Server

Agent

Download artifacts

Deploy steps

Deploy data sets

PDS

Update Inventory status

z/OS LPAR, Build system z/OS LPAR

Note: LPARs can be the same or different LPARs

Store meta data

Store version artifacts

Deploy steps

deploy

CICSDB2

WASz

IMS

JCL

REXXTSO

MVSSHELL

CodeStation

in UCD

FTP or Copy

software configuration management für traditionelle mainframe · pdf file ·...

Documents