Release Management Migration to Bladelogic

Project Description

The solution is originally based on Tivoli. In 2009 a decision was made to phase put Tivoli and extend the solution to support also Marimba as a second Deployment channel. In 2012 the decision was made to eliminate the support for Tivoli and extend the solution to support also Bladelogic for servers as a third Deployment channel. This enables a smooth migration.
This solution was created in 2001/2002, is still used by approx. 1500 users in operations and onshore/offshore development, supports three different deployment products and two different operation systems, has approx. 8000 target systems and deploys up to 150.000 packages a month.

Financial Department
Financial Instruments
Market Interfaces
Departments - Products
Vendor - Involved Products
Technologies

Project Description

The solution is originally based on Tivoli. In 2009 a decision was made to phase put Tivoli and extend the solution to support also Marimba as a second Deployment channel. In 2012 the decision was made to eliminate the support for Tivoli and extend the solution to support also Bladelogic for servers as a third Deployment channel. This enables a smooth migration.
This solution was created in 2001/2002, is still used by approx. 1500 users in operations and onshore/offshore development, supports three different deployment products and two different operation systems, has approx. 8000 target systems and deploys up to 150.000 packages a month.

Financial Department

Financial Instruments

Market Interfaces

Departments - Products

Vendor - Involved Products

Technologies