Product

Home Product Screenshots Automated vs manual activities. The way to achieve compliancy.
Visit our brand websites for specific solutions

Versioning, automated deployment and Life Cycle Management for
Oracle OWB / ODI

Mainframe modernization and agility, using Life Cycle Management for
z/OS

Screenshots

Life-Cycle: Build

  • The scheduler triggers a build, based on schedule settings and if changes were found in the VCR (1)
  • A user forces a build on a scheduled project (2)
  • A user requests a build for a non-scheduled project
  • Builder builds code (3)
  • After successful build the result is stored in the Build Archive (4)
  • Corresponding source code is labelled/tagged in the VCR (5)
  • Developers are notified
The level with name "CONTBUILD" is involved in the "Build Life-Cycle" and has a ContinuousIntegration schedule. "The next scheduled Request"(1) indicates the time when IKAN ALM will check for changes in the VCR. A Build can be created manually by selecting the "Force" (2) icon. Click here for a larger image
IKAN ALM detected changes in the VCR and created a Build Request. The "Action Type" and "Description" indicate that this is a ContinuousIntegration Build, triggered by a Schedule. Click here for a larger image
The builder executes the build script (3). Click here for a larger image
The steps in the build process are traced. After a successful build, the result is stored in the Build Archive (4). The corresponding source code is tagged in the VCR(5). Click here for a larger image

Life-Cycle: Rebuild/Deploy

  • User requests the delivery of a build to the QA level (1)
  • Labelled code is retrieved from the VCR and copied to the QA build server (2)
  • After a successful build, the result is stored in the Build Archive (3)
  • The build result is retrieved from the Build Archive and distributed to the QA deploy server (4)
  • The build is deployed onto the QA Server (5)
  • All required parties are notified
The user requests the delivery of the build from the Build Life-Cycle to the QA level (1). Click here for a larger image
Labelled code is retrieved from the VCR and copied to the QA Build server (2). After successful build the result is stored in the build archive (3). Then it is copied from the build archive to the QA Deploy server (4) Click here for a larger image
The build is deployed on the QA server (5). Click here for a larger image

Life-Cycle: Deploy

In this scenario, the source code is not rebuilded, it is assumed that the code builded for QA can be reused for deployment on the production environment. Before production IKAN ALM enables approvals to be defined, as any change in the live world should be verified by a second party.

  • User requests the delivery of a build tot the production level (1)
  • The required approvals are notified
  • The responsible user approves the request (2)
  • The requested build is retrieved from the Build Archive and distributed to the production server
  • The build is deployed onto the production Server (3)
  • All required parties are notified
The user requests the delivery of the build from the previous Life-Cycles to the Production level. (1) Click here for a larger image
Before the build may be deployed to production, responsible users have to approve the request (2). Click here for a larger image
The build is deployed onto the production server (3). Click here for a larger image

Next: SolutionsNext page