Deployment - Serena Software

serena.com

Deployment - Serena Software

Managing Development Across Distributed and Mainframe

Michael Troth

Senior Software Engineer, Serena Software

1 Copyright ©2008 Serena Software, Inc.


Session Overview

Dimensions Overview

Server/Agent Platform Support

Network Nodes

Repository Organization

Deployment/Deployment Areas

Build Management

More About Mainframe

Additional Resources

2 Copyright ©2008 Serena Software, Inc.


Dimensions Overview

• Integrated change, configuration, build, and release

management tool.

• Provides a flexible process model for managing any type

of object.

• Enforces responsibility via user roles, rules, and

privileges throughout the process model.

• Provides ability to track and audit change through item

history, change requests, baselines, and projects.

• Integrated deployment and build management across

platforms.

3 Copyright ©2008 Serena Software, Inc.


4 Copyright ©2008 Serena Software, Inc.

Dimensions Network Diagram


Server/Agent Platform Support

Server:

• Win2k3 Server, Solaris, AIX

Agent:

• Win2k3 Server, Solaris, HP-UX, AIX, zOS, RH and SLES

Linux

** Please see the Readme document from the latest

service release for detailed platform support information.

5 Copyright ©2008 Serena Software, Inc.


• A network node is any node/computer where a

Dimensions server or agent is running.

• A node is defined to Dimensions by the administrator and

given a logical name which user’s can use to access it.

• Once defined, the user can send/receive files to/from that

node by including it in the file specification on an

operation:

For example:

DEV-WIN32-1::c:\build\myarea\foo.c

DEV-ZOS-1::MTROTH.MYAREA.C(FOO)

Network Nodes

6 Copyright ©2008 Serena Software, Inc.


• Mainframe nodes can handle both the traditional file

system (PDS, PDSEs, etc) and USS HFS file systems.

• Two logical nodes are typically created for a single

physical mainframe node – one for each file system type.

For example:

MVS-NODE: OS: Unix, File System: MVS

USS-NODE: OS: Unix, File System: OS

Network Nodes

• The Dimensions clients and server will do their best to

“mangle” filenames from distributed to traditional

mainframe (PDS, PDSE) formats.

7 Copyright ©2008 Serena Software, Inc.


8 Copyright ©2008 Serena Software, Inc.

Network Nodes


9 Copyright ©2008 Serena Software, Inc.

Network Nodes


Repository Organization

• Base Database: the basic instance of the process model

which defines the rules used for development.

Ex: Accounting

• Product: a major unit of development

Ex: Payroll, Accts Payable, Accts Receivable

• Design Part: a logical subdivision of the Product

Ex: Salary, SS Withholding, Fed Tax, State Tax,

• Item: a base asset

Ex: calc.cpp, acct_procedures.doc, sscalc.cobol

• Item Format/Build Type: an Item attribute which indicates

the format or build type of an item.

10 Copyright ©2008 Serena Software, Inc.


Repository Organization

• Project: a working collection of item revisions.

• Request: a collection of item revisions for a specific

change. These can also be inter-related/hierarchical.

• Baseline: a snap-shot collection of item revisions.

• If desirable, Item Format/Build Type, Design Part,

Project, and even Product are all good ways to subdivide

an application by platform.

• However, Design Part and Item Format/Build Type are

commonly used for teams wishing to have a single

Project spanning a multi-platform release.

11 Copyright ©2008 Serena Software, Inc.


12 Copyright ©2008 Serena Software, Inc.

Repository Organization


• Each repository item can be assigned a type.

Item Lifecycles

• Each item type has it’s own lifecycle.

• An Item’s status (per revision) is the same across the

entire Base Database.

13 Copyright ©2008 Serena Software, Inc.


Deployment

• Lifecycle (called Global Stage Lifecycle) of user-defined

stages in which Items follow through a Project.

For example:

DEV => UNIT TEST => SYSTEM TEST => RELEASE

• GSL is unique per Base Database.

• Items are deployed from one stage to the next in the

Project.

• An Item’s stage is unique to the Project.

14 Copyright ©2008 Serena Software, Inc.


15 Copyright ©2008 Serena Software, Inc.

Deployment


Deployment

• Two types of Deployment model (since 10.1.3):

Baseline – all Items related to a baseline are deployed at

the same time. Request deployments are not allowed.

Request – Item and Request deploy operations are valid

but Baseline deployment is not allowed.

• Two ways to trigger Deployment:

Manual – deployment occurs only when a deploy

command is issued.

Automatic – deployment occurs automatically when an

Item reaches a specific lifecycle state.

16 Copyright ©2008 Serena Software, Inc.


17 Copyright ©2008 Serena Software, Inc.

Deployment


Deployment Areas

• A disk area on a Dimensions node which contains a copy

of the Items at a given stage of the Project.

• One or more deployment areas can be assigned to a

stage of a Project.

• Provides the ability to replicate the Project to multiple

nodes/platforms.

• Can be filtered by file pattern, design part, item format,

and/or item type. Provides control on which items are

included or excluded from a given area.

• Project setting available to control whether items are

moved or copied from one stage area to the next.

• Pre and post event scripts available.

• Use credential sets to manage user ids/psws.

18 Copyright ©2008 Serena Software, Inc.


19 Copyright ©2008 Serena Software, Inc.

Deployment Areas


20 Copyright ©2008 Serena Software, Inc.

Deployment Areas


• Web based admin tool for all platforms.

• Uses versioned build configurations which describe what

to build, how to build, and where to build it.

• One to many build configurations per Project.

• Build configuration is platform specific.

Build Management

• Powerful, flexible scripting language for tailoring build

scripts.

• Any command line driven build tool can be used (JCL for

zOS).

• zOS build tool provided with Dimensions zOS option

• Ongoing status of build execution via web browser –

even for mainframe builds.

21 Copyright ©2008 Serena Software, Inc.


Build Management

• Build logs collected automatically and placed on build

server – including mainframe.

• Closed-loop builds (output collection) provided via build

area scanning or analysis of a Bill of Materials (BOM)

report (when available) using upload rules for new item

creation.

• BOM format published in build documentation – can be

provided by any build tool.

• Post-build dependency relationships made in the

database between Items based on BOM data.

• Can be used for non-build activities – remote job

execution with central logging.

22 Copyright ©2008 Serena Software, Inc.


23 Copyright ©2008 Serena Software, Inc.

Build Management


24 Copyright ©2008 Serena Software, Inc.

Build Management


25 Copyright ©2008 Serena Software, Inc.

Build Management


26 Copyright ©2008 Serena Software, Inc.

Build Management


General Considerations

• When using a multi-platform Project, build and collect

targets into unique directories unless their names are

unique.

• For mainframe, Project directory structures are folded

into dataset qualifiers so naming restrictions apply.

• For mainframe, repository item names need to adhere to

mainframe naming standards.

• Item libraries for repository items can be on any platform

– recommend choosing the platform with the best backup

solution.

27 Copyright ©2008 Serena Software, Inc.


More About Mainframe

• Mainframe capabilities are just an extension to the core

Dimensions functionality – same process model,

approvals, roles, item revisions, etc. as all other

platforms.

• Mainframe node looks/feels like any other Dimensions

node.

• Ability to move files around Dimensions network using

any of the clients (desktop, web, command line, and

ISPF).

• Native batch and ISPF client interface

• Support for executing remote tasks from any Dimensions

client

28 Copyright ©2008 Serena Software, Inc.


• Dimensions DTK support for user-written extensions

• Dimensions agent handles file movement to/from z/OS

file systems in the security context of the authenticated

user:

• Support for PDS/PDSEs and sequential/QSAM in fixed,

variable, undefined, blocked, and unblocked formats.

• Support for HFS

• Automatic EBCDIC/ASCII translation with code page

support for text files.

• Support for item library storage on USS

• Fully SAF (security) compliant

More About Mainframe

29 Copyright ©2008 Serena Software, Inc.


More About Mainframe

• “Traditional” mainframe build engine

• Build optimization available for “weeding out”

unnecessary build steps.

• Build administration done via web client.

• Build scripts tailorable via standard scripting engine.

• Dependency monitoring via SVC watcher exit which

provides bill of materials reporting for each build step.

• Full progress and error reporting back to Dimensions.

• Utilization of local metadata for build optimization.

• Load module foot printing.

30 Copyright ©2008 Serena Software, Inc.


Additional Resources

• Slides from session “Crossing the Chasm for Application

Deployment

• Dimensions CM 10.x – Developer’s Reference

• Great resource about templates and syntax

• Dimensions CM 10.x – Dimensions Build User’s and

Administrator’s Guide

• Everything you wanted to know about build

• Dimensions CM 10.x - Dimensions for z/OS User's and

Administrator's Guide

• zOS jocks only!

• Dimensions CM 10.x - Process Modeling User's Guide

• Areas, lifecycles, item formats, and much more…

31 Copyright ©2008 Serena Software, Inc.


32 Copyright ©2008 Serena Software, Inc.

Questions

More magazines by this user
Similar magazines