JAVA Application Lifecycle Management - Development through Deployment

How can we work on multiple versions of our application, while guaranteeing no unplanned changes are introduced into production when fixes are required?

How can we reduce the time our people spend on destabilizing manual source code merging and unproductive ANT scripting?

How can an engineer clearly see the status of every file in their JAVA project allowing them to make informed development decisions?

How can we “deploy exactly what was tested” while taking into account that different environment variables are needed for our test and production environments?

JAVA Application Lifecycle Management – Development through Deployment - using the MKS Integrity Suite

• Robust, client server SCM solution • Manage distributed development • Ready for Websphere validated • “Checkpointing” provides reliable method to recreate a version or baseline

• Fully user configurable • Implement your development process

MKS Integrity Manager

Three key components:

User defined workflow

Change package integration with Source Integrity Enterprise Edition

Event triggers and command line

An automated repeatable Build Process: • Increases team productivity • Increases application quality.

Openmake

Client server build application

Build rules maintained on server

Includes what to build

And how to build it

Where to get source code

Dependency information

Openmake

Is used for:

Developers' Unit builds

Full system builds

Incremental Builds

Openmake

Fully integrated with Websphere

Changes made in J2EE project automatically update dependencies

ANT scripting can be eliminated

Can use Openmake for unit build

Openmake

Bill of Material (BOM)

Created at compile time

Complete list of every component

Complete dependency information

Provided in a report format

Can be "stamped" into the executable

Build & Deployment process becomes Repeatable, Enforceable and Measurable.

MKS Build & Deployment Module

Built on MKS Integrity Manager

Pre-configured workflow

Utilizes SIEE Change Packages

Integrates with Openmake

Enterprises have this solution in production today!

Real life use case:

There is an issue in the Minibank demo application that ships with Websphere Studio Application Developer. The problem will require changes to two files to fix the issue.

Will step through:

The assignment of development tasks

Source code modifications

Automatic triggering of a repeatable build

QA verification that every change is identified

Automated deployment of the new EAR

Project Manager uses Integrity Manager to assign development tasks.

Developer will use WSAD to edit source and access SIEE commands through RFWS validated integration.

Developer will now do an incremental unit build using Openmake.

Development changes are complete, the Build & Deployment module is now utilized.

Who can benefit from this solution?

We can work on multiple versions of our application, while guaranteeing no unplanned changes are introduced into production when fixes are required?

We can reduce the time our people spend on destabilizing manual source code merging and unproductive ANT scripting?

An engineer can clearly see the status of every file in their JAVA project allowing them to make informed development decisions?

We can “deploy exactly what was tested” while taking into account that different environment variables are needed for our test and production environments?

Questions & Answers