Posted on

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.

Posted on

Stop WebSphere Application Server with uDeploy

When you want to stop a Cluster or a Server you need a component process well designed or your application process can fail.

Start with a Check Status step. It checks the status of the Server/Cluster and fails if the Server/Cluster is already stopped.

The second step, Stop Server, it doesn’t need explanations.

Then Wait for server or cluster to stop.
Here you can set the:
– Timeout (seconds) to wait for the server or cluster to stop before the step fails.
– Interval (seconds): The time to wait between status checks.

Finally, in case of Wait for Server/cluster to stop timeout we add a Terminate Server/Cluster step.

Have a nice day!

Posted on

Add Target to Module with uDeploy aka Map Module to Server

There is an excellent article written by Lara Ziosi (you can find it here) which inspired me to write this post and showing you how to add Target to Module with uDeploy.

In our scenario we have a WebSphere Application Server cell and we are going to install an ear and map a Web Module to a Web Server target.

Usually during ear installation  the target is an Application Server or Cluster but sometimes we need to map our application also to a Web Server like IHS, Apache or something else.

First of all create a component of type “WebSphere Enterprise Application”, then create two component processes. The first is a classic deploy process ( see Install Enterprise Application on WebSphere Application Server with uDeploy)  while the second :  “Add target To Module” has just one step:  “Add Target to Module” from the “Application Deployment for WebSphere plug-in“.

Simply fill the Module URI property with the Uri of the module. For example: ALPHA_WAR.war,WEB-INF/web.xml

Continue reading “Add Target to Module with uDeploy aka Map Module to Server“

Posted on

Use Precondition in uDeploy

Most steps in a process can have a precondition. The precondition determines whether the step runs.

Preconditions return Boolean values. If the precondition returns True, the step runs as usual. If the precondition returns anything other than True, the process skips that step.

Suppose we need to create a symlink but only under certain conditions. We create a Shell step:

Continue reading “Use Precondition in uDeploy”

Posted on

How to update configuration files with UrbanCode Deploy

How often do you need to update configuration files of your applications?
Do you need to automate this process? Let me show you how to do it with uDeploy.

We have a component and we are going create a component process.

Create a Shell step and call it “Clean Working Directory”. Then create a “Download Artifacts” and a “Replace Tokens” steps with properties below.

Clean Working Directory properties

Continue reading “How to update configuration files with UrbanCode Deploy”

Posted on

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”

Posted on

Replace Tokens

One of the most useful thing you can do with UrbanCode Deploy  is the “replace tokens” job.  SysAdmins deal everyday  with differents environments such as DEV,  SIT, UAT, PROD. Your application needs different values like hostname, url, port, log level and much more depending on the environment where it’s deployed.

When you need to automate deployment process you must get rid of these values. With UrbanCode Deploy (uDeploy) you can create environment variables, assign values to these variables for each environment and create a component process  who will replace  tokens.

What we need is a uDeploy Server running installation, at least one uDeploy Agent and a plug-in called File Utils plug-in . Then we create a Component, an Application and one Environment. See images below:

Our goal is to automate the process of deploying a configuration to different environments. Let’s create an Environment Property Definition in our component:

Continue reading “Replace Tokens”