Main navigation

Ear file Deployments to a Websphere Cluster, Step By Step

Deploying Your Ear File Can Be Challenging

I am often asked how to standardize an ear file deployment around a WebSphere Cluster. Deploying an ear file to a cluster can present challenges, particularly when attempting to accomplish the task with one-off deployment scripts written in any number of scripting languages. In this example, I am using the defined logic with our DeployHub Continuous Deploy solution, designed to standardize the application release automation process. This logic can be called by any external process such as a Jenkins continuous integration workflow, or CloudBees Continuous Delivery pipeline process.

Whatever you may be using to orchestrate the calling of your deployment does not matter much. What matters is the ability to create a reproducible ear file deployment that all team members, from development to operations, can understand and track.

Steps for Setting Up an Ear File Deployment in the Websphere Cluster

Get a list of the Servers that belong to the Cluster

Loop through the list of Servers in the Cluster and Stop the App on each one

Remove the App

Install the App

Apply warClassLoaderPolicy updates

Apply classLoader updates

Apply startingWeight

Loop through the list of Servers in the Cluster and apply the following if changed