Script:
Owner:
Subdir: cbaart
Blog ID: 95726135
Group ID: User ID: 94952375

My Profile

    I am currently Not Updated

Leader Spotlight

    WebSphere CloudBurst Appliance integrated with Deployit for applications on demand


    At XebiaLabs, www.xebialabs.com, we have recently been working on an exciting new integration for Deployit, our deployment automation product. We've created a Deployit plugin that allows you to deploy EAR files directly to virtual systems created by IBM's WebSphere CloudBurst Appliance (WCA).

    But a small piece of background first. Deployit and WebSphere CloudBurst Appliance both "deploy" things. But they deploy different things. Deployit deploys application artifacts and resources such as EAR files and data sources to middleware systems like WebSphere Application Server (but also HTML to web servers, MQ configuration to queue managers, etc.). The WebSphere CloudBurst Appliance on the other hand, deploys patterns (topologies) of virtual images to hypervisors. But not just any kind of virtual images. It is especially geared towards deploying middleware topologies. In other words, the software Deployit wants to deploy to! This means that the functionalities of WCA and Deployit are a perfect fit; have WCA deploy the middleware systems and have Deployit deploy applications to those middleware systems.

    In practice it works like this:

    1. From the Deployit UI, The user select the application artifacts and resources he wants to deploy.
    2. The user selects the WCA he wants to deploy to.
    3. The user enters the name of the CloudBurst pattern to deploy and the cloud group in which to deploy it.
    4. The user presses the "Deploy" button in Deployit to start the deployment.
    5. Deployit starts the pattern deployment in WebSphere CloudBurst Appliance.
    6. When the pattern deployment is finished, Deployit reads the information about the newly created virtual system and the middleware on it.
    7. And finally, Deployit installs the application on it, using the existing Deployit logic to deploy to WebSphere environments.

    As you can see from the screenshots, Deployit and WebSphere CloudBurst Appliance can be seamlessly integrated to give the user the ability to deploy his application to cloud environments without needing a lot of knowledge of cloud infrastructure and provisioning systems. This allows developers to set up new development environments from the Deployit self-service UI. It allows testers to set up their testing environments, often a bottleneck in enterprise development. And finally, it allows application deployers to deploy their applications to virtual environments.

    By combining the strengths of the WebSphere CloudBurst Appliance and the Deployit product, the WCA value proposition can be extended across the IT organization and it allows enterprises to go form on-demand infrastructure to on-demand applications!

    0 (0 Ratings)
    [ 349 views ] Leave a Comment

    How Deployment Automation for java apps bridge the gap between Dev and Ops.


     

    In my first blog on GWC I would like to present a business case that might be interesting for those working with IBM middleware in IT operations and development. The case is written by Wilco Koorn.

    Development and Operations departments have different, and at times opposite, objectives.

    The objective of Development is to produce a continuous stream of value by providing

    change, whereas the objective of Operations is to produce a continuous stream of value by providing stability.

    Studies indicate that especially the

    hand-over of software packages from Development to Operations causes a lot of idle waiting time and therefore lowers overall productivity. Hand-overs not only involve developers explaining to Operations what has changed in their code and how this might impact other components, but also rewriting deployment scripts and then retesting the application on a shadow server. These activities require a substantial amount of time.

    Eliminating hand-overs can be achieved by adopting a "self service" deployment model in the Development department. A necessary prerequisite for introducing self-service deployments is to first automate the entire deployment process.

    A case study made by airline company KLM/AirFrance proves the value of automating the deployment process and introducing self-service deployments. Without hiring additional Operations staff, KLM/AirFrance was able to cope with a 500% increase in the number of deployments per month. Thanks to deployment automation and self-service deployments, they now save $1 million annually in their entire software development and delivery chain.

    Read more in this paper www.xebialabs.com/bridging-gap-between-d...

     

    Trends like increased automation of business functions, introduction of a service-oriented architecture paradigm, ever more heterogeneous middleware environments and the emerging use of virtualization in datacenters have increased pressure on both Development and Operations. Moreover, business simply demands more agility from the IT organization.

    Development’s response to this demand is to adopt Agile methodologies, allowing them to provide more

    changes in a shorter timeframe. As a result, the Operations department has to cope with many more software updates to the development, test and production environments. This makes Operations’ objective to provide a stable infrastructure to end users an increasingly difficult task.

    3.2 (1 Ratings)
    [ 113 views ] Leave a Comment

    How Deployment Automation for java apps helped KLM

    Tuesday, August 31, 2010, 4:37 AM

    In my first blog on GWC I would like to present a business case that might be interesting for those working with IBM middleware in IT operations and development. BTW, this case is written by Wilco Koorn.

    Trends like increased automation of business functions, introduction of a service-oriented architecture paradigm, ever more heterogeneous middleware environments and the emerging use of virtualization in datacenters have increased pressure on both Development and Operations. Moreover, business simply demands more agility from the IT organization.

    Development’s response to this demand is to adopt Agile methodologies, allowing them to provide more

    changes in a shorter timeframe. As a result, the Operations department has to cope with many more software updates to the development, test and production environments. This makes Operations’ objective to provide a stable infrastructure to end users an increasingly difficult task.

    Studies indicate that especially the

    hand-over of software packages from Development to Operations causes a lot of idle waiting time and therefore lowers overall productivity. Hand-overs not only involve developers explaining to Operations what has changed in their code and how this might impact other components, but also rewriting deployment scripts and then retesting the application on a shadow server. These activities require a substantial amount of time.

    Eliminating hand-overs can be achieved by adopting a "self service" deployment model in the Development department. A necessary prerequisite for introducing self-service deployments is to first automate the entire deployment process.

    A case study made by airline company KLM/AirFrance proves the value of automating the deployment process and introducing self-service deployments. Without hiring additional Operations staff, KLM/AirFrance was able to cope with a 500% increase in the number of deployments per month. Thanks to deployment automation and self-service deployments, they now save $1 million annually in their entire software development and delivery chain.

     Please read the full story  www.xebialabs.com/bridging-gap-between-d...

     

    0 (0 Ratings)
    [ 120 views ] Leave a Comment

    Loading...