Changing the JRE of UrbanCode Deploy Server and Agents

Beginning in version 6.2.2, the IBM UrbanCode Deploy Server (and agent relays) require Java Runtime Environment (JRE) or Java Development Kit (JDK) version 8.

Are you planning an update of your uDeploy Server and Agents? Do you have an old JRE?  Here the steps to update you JRE*:

*The new JRE must be from the same vendor as the current JRE

Changing or updating the JRE of Server
  • Install the new JRE
  • Stop the Server
  • Update the location of the JRE in the following files:
    • In the file
      server_install/bin/set_env

      set the value of the JAVA_HOME system variable to the location of the JRE.

    • In the file
      server_install/conf/server/installed.properties

      set the value of the install.java.home property to the location of the JRE.

  • Start the Server

Continue reading “Changing the JRE of UrbanCode Deploy Server and Agents”

Execute wsadmin Script with UrbanCode Deploy

The WebSphere Application Server wsadmin tool provides the ability to automate configuration tasks for your environment . It supports a full range of product administrative activities such as configure and administer application servers, application deployment, and server runtime operations.

UrbanCode WAS Deploy plugin has a step called:  Execute wsadmin Script

Open the step:

Continue reading “Execute wsadmin Script with UrbanCode Deploy”

Environment Gates & Version Statuses

Do you want to take control on which version of your application can be deployed into Production environment? IBM UrbanCode Deploy Environment Gates and Version Statuses can help you.

This example will show you how to define policies to allow Production deploy only if application has passed QA environment deploy.

Go to Settings -> Statuses

Add a new Version Status and name it:  QA PASSED

Continue reading “Environment Gates & Version Statuses”

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”

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”