Home arrow News and Events arrow Archived Items arrow Solution Demonstration Series (Feb-Apr)
Solution Demonstration Series (Feb-Apr)

Discover how we can enable you to more quickly deploy mission-critical applications and thus ensure that applications deliver value to the organisation as quickly as possible...

Whenever the rapid rollout of an application is important to the business, application release engineering and management is crucial. 

To succeed where competitors fail, organisations need to understand its market and often deploy in-house written applications. While such custom applications are often more critical to the business than commercial, off-the-shelf software, they can also be more complex to deploy, because of their many links to other internal systems or their high demand for processing, storage or network resources. These applications also often lack formal installation routines, or an ecosystem of best practices knowledge from other users. Yet, because of their value, a delay in their rollout can have immediate and dramatic effects on revenue, profits, market share and public perception of a company by delaying the time-to-market for new products or services.

Application release engineering and management is the often-complex process of packaging, testing and “promoting” application releases from the point at which the code is developed, until the finished application is deployed to users. For too many organisations, application release engineering remains a manual and error-prone process, which takes precious time and money to complete.

Identity Solutions’ application release management solution is based on the BladeLogic Application Release Manager (ARM), which au­tomates the packaging, promotion, deployment and selective rollback of application modules. BladeLogic ARM handles all the steps from the time the code is placed in a source control system until, and after it is released to the production environment. 

Among the unique capabilities the BladeLogic Application Release Manager provides are:   
  • Environment definition and consistency
    to allow release engineers to define each environment within the release process (such as development, Test, QA, staging, etc.) 
    Without an automated tool such as the BladeLogic Application Release Manager, companies must manually copy code and configuration parameters onto each system and ensure they have properly changed every command and parameter, creating a significant potential for human error.
  • Environment Sensitive Packaging
    to provide environment-specific settings in a release package such that the same package can be deployed across multiple environments (such as Test, QA and staging.) This parameterisation reduces complexity and cost by eliminating the need to recreate packages when moving from one environment to another.
  • Automated multiplatform packaging
    to identify, assemble and create application build packages for deployment across multiple platforms without the need for human intervention, which reduces the time, cost and risk of error involved in repackaging applications.
  • Composite packaging
    to allow multiple application components to be packaged for deployment across multiple plat­forms as a single build package with built-in transaction safety and rollback capability which eliminates complexity by reducing the number of packages what must be built to accommodate various platforms.
  • Creation of very granular roles-based permissions
    to allow organisations to determine, very specifically, which individu­als have authority to “promote” a package from one level to another, or to make changes to the package. For example, only an SOA expert can move a Web Service into Production. This greatly reduces errors associated with unauthorised changes to packages or their unauthorised promotion to another environment.
  • Automation of the packaging process and workflows
    when used in conjunction with the BladeLogic Orchestration Manager, the BladeLogic Ap­plication Release Manager provides automated workflows out of the box to support best practices in release management based on the IT Infrastructure Library (ITIL). The use of these two BladeLogic solutions can, for example, be used to trigger change approval processes as part of the execution of configuration changes, and integrate the configuration of test envi­ronments with the development of release packages, to ensure the consistency of these environments.
    Come to our demonstration of the application release management solution and discover how we can enable you to more quickly deploy mission-critical applications and thus reduce overhead costs, minimise the risk of application failure and ensure that applications deliver value to the organisation as quickly as possible.
 
Next >