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.
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: