Handle multiple Websphere Application Server profiles with uDeploy

Do you have multiple WAS profile on the same host? Let’s see how to handle this configuration with uDeploy.

Go to Resources -> Agents -> [Click your WAS multi profiles host agent] -> Configuration -> Agent Properties.

Add the Property Name: websphere.profilePath and fill the value with the path of WebSphere Application Server profiles.

Eg. /usr/IBM/WebSphere/AppServer/profiles

Go to Resources -> Resource Tree and create a Top-Level Group.

Click beside the Top-Level Group: Actions -> Add Agent

Click Refresh link below.

Your Deployment Manager Profiles will appear.

For each WebSphereCell Dmgr click Configuration -> Basic Settings. Add missing values like, Cell Name, WebSphere User and Password, SOAP Port.

Go back to Resource Tree, click Actions beside each Dmgr profiles and click: Configure Using WebSphere Topology Discovery.

Your Cell topology will appear in a few seconds.

WebSphere Topology Discovery

The first thing to know about WebSphere and UrbanCode Deploy integration is the WebSphere Topology Discovery feature.  If you have a big IBM WebSphere Application Server (WAS) environment, full of Cluster,  Server and Application, UrbanCode Deploy (uDeploy) can really help you saving you time and makes access to many informations easier .

It makes it easier to set certain properties, such as cell name, node name, cluster name, server name and so on, by allowing you to import them into uDeploy.

What we need is a uDeploy Server running installation,  a uDeploy Agent running on the WAS Deployment Manager server and a plug-in called WebSphere Application Server – Deployment

Go to Resources -> Agents and click  the “Agent Name” (localhost in my case: ) then click Configuration -> Agent Properties (see images below)

Continue reading “WebSphere Topology Discovery”