Skip to main content

This post is from the XebiaLabs blog and has not been updated since the original publish date.

Last Updated Aug 14, 2011 — DevOps Expert

Leveraging the IBM Workload Deployer CLI to automate WebSphere application deployment

DevOps
A few months ago I blogged about the integration between XL Deploy and IBM WebSphere CloudBurst (since renamed to IBM Workload Deployer). While that article gave an overview of the integration and included some nice screenshots, it did not really go into the details. Now is the time to explore the implementation of this integration.. Workload Deployer V3 and XL Deploy from XebiaLabs both "deploy" things, but they deploy different things. XL Deploy deploys application artifacts and resources, such as EAR files and data sources, to middleware systems like IBM WebSphere Application Server (but also HTML to web servers, IBM WebSphere MQ configurations to queue managers, and so on). IBM Workload Deployer, on the other hand, deploys patterns (or topologies) of virtual images to hypervisors -- but not just any kind of virtual images. IBM Workload Deployer is especially geared toward deploying middleware topologies. IBM Workload Deployer V3 is an updated and enhanced version of the WebSphere CloudBurst Appliance, renamed to reflect the expanded scope of workloads it can deploy, which are no longer limited to only WebSphere workloads. The content for this article (including screen captures) was created using a WebSphere CloudBurst Appliance, but everything noted here is equally applicable to IBM Workload Deployer V3. However, for the sake of consistency with the images presented, "WebSphere CloudBurst" is used throughout this article to refer to both products. In other words, IBM Workload Deployer deploys the middleware systems and XL Deploy deploys applications to those middleware systems -- complementary functionalities that form a perfect fit. At XebiaLabs, we have been working on two exciting new integrations for XL Deploy. We created a XL Deploy plugin that enables you to deploy EAR files directly to virtual systems created by IBM Workload Deployer V3 or its predecessor, IBM WebSphere CloudBurst Appliance V2. We also created a WebSphere CloudBurst script package to deploy application artifacts and resources on newly created virtual systems. This article explores two integrations between WebSphere CloudBurst and XL Deploy as a way of showing how you can leverage the WebSphere CloudBurst command line interface and script packages to integrate cloud deployment with your application deployment automation solution.read more

More from the Blog

View more
Jan 06, 2021

How testing automation can build a culture of QA while accelerating continuous delivery

DevOps
An organization’s level of automated test coverage is quickly emerging ...
Read More
Jul 30, 2020

Part 2: Is Technology Slowing Down Your Digital Transformation?

DevOps
In part one of this post, we shared insights from Andreas Prins’ webin ...
Read More
Jul 28, 2020

Part 1: Is technology slowing down your digital transformation?

DevOps
Digital transformation and the proliferation of technology affects eve ...
Read More
Jun 29, 2020

V4 of the Periodic Table of DevOps Tools is LIVE!

DevOps
The wait is over! Created by the DevOps community for the DevOps commu ...
Read More
Contact Us