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”
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”