UrbanCode Deploy Post Processing Script

Post-processing scripts run after a component/generic process step finishes.

Typically, post-processing scripts check if expected results occur. It can examine the step’s output log and run commands based on the result.

Steps can have default post-processing scripts. These scripts are included with the plug-in.

You can override the default post-processing script for a step or provide a post-processing script for a step that does not have one.

Important
Steps in component processes and generic processes can have post-processing scripts, but steps in application processes cannot.

Post-processing scripts are written in JavaScript.

Continue reading “UrbanCode Deploy Post Processing Script”

Massive copy of UrbanCode Deploy Plugins

Sometimes you might need to move your UrbanCode Deploy Source Configuration and Automation Plugins from one server to another one1.

Plugins are stored, as zip files, in:

/<ucd_install_dir>/appdata/var/plugins/command/repo

Copy all plugin files you need, from the above directory of the first server, to below directory of the second server:

/<ucd_install_dir>/appdata/var/plugins/command/stage

Restart the target server.

Log file will display loading of Plugins as in the excerpt below:

2020-05-02 15:56:23,754 UTC INFO PluginUpdate com.urbancode.ds.plugin.PluginUpdate - Loading com.urbancode.air.plugin.ServiceNow_28.zip…
2020-05-02 15:56:24,920 UTC INFO PluginUpdate com.urbancode.ds.plugin.PluginUpdate - Loading com.urbancode.air.plugin.DBUpgrader_3.zip…
2020-05-02 15:56:25,385 UTC INFO PluginUpdate com.urbancode.ds.plugin.PluginUpdate - Loading com.urbancode.plugin.WindowsSystemTools_23.zip.
  1. https://www.ibm.com/support/pages/how-do-i-mass-install-urbancode-deploy-plugins-new-server []

UrbanCode Deploy Blueprint Designer Create and provision new environments in the cloud

The Blueprint Designer is a separately-installed component that is included with the UrbanCode Deploy product suite.

While UrbanCode Deploy drives deployment automation of applications into existing environments, Blueprint Designer creates and provisions new environments in the cloud.

Blueprint Designer Licensing
The UrbanCode Blueprint Designer does not require separate or extra licenses. It can be used with all UrbanCode Deploy license scenarios.

Blueprint Designer provides a design tool to create full-stack environments using standard orchestration technologies, including OpenStack Heat and Terraform.

This post shows the OpenStack Heat orchestration. Terraform will be discussed later. Continue readingUrbanCode Deploy Blueprint Designer Create and provision new environments in the cloud

Stop, Start and Restart a Windows Service with UrbanCode Deploy

In this post I’m going to show you how to create a Generic uDeploy Process to manage Windows Services and how to use this Process as Template for Application Processes.

What we need is:

Below the Generic Process Windows Service Stop/Start/Restart flow:

Continue reading “Stop, Start and Restart a Windows Service with UrbanCode Deploy”

Create a UrbanCode Deploy Cluster using AWS

Let’s see how to install and configure a 2 node uDeploy cluster with Amazon Web Services (AWS).

First of all create 2 Linux Instances (if you are asking why not Microsoft Windows Server you can stop reading and go for a walk).

Choose your region and click on EC2, then “Launch Instance”:

Click next until “Configure Security Group”, then choose a name for your group like “uDeploy” and add rules to open inbound ports: 22, 8443, 7918, 7919 and 2049 like fig. below:

Continue reading “Create a UrbanCode Deploy Cluster using AWS”

Acquire Lock with UrbanCode Deploy on IBM WebSphere Application Server Network Deployment Environment

Who works everyday with IBM WebSphere Application Server Network Deployment knows a state of facts: Different users cannot make changes on a WAS DM Cell at the same time.

Let’s look at how it can be possible acquire an exclusive lock on a WAS DM Cell with IBM UrbanCode Deploy.

We have two different applications on the same WAS DM Cell and we want to deploy both without worrying about which deploy start first.

Create everything you need on uDeploy: Applications, Components, Component Process, Application Process, Resources and Environments as in the figures below:

Environment Name: WAS85 STAGING
First Application: Pet Store

Pay Attention: The environment name is: WAS85 STAGING. I’ll put this name for every application is running into my WAS DM Cell of Staging.

Continue readingAcquire Lock with UrbanCode Deploy on IBM WebSphere Application Server Network Deployment Environment

UrbanCode Deploy & JIRA Integration Part Two

In the first part of “UrbanCode Deploy & JIRA Integration” post we left us with an unsolved question.

How to pass a Jira issue nr. (issue_id) to the application process flow?

Application Process Properties is the solution.

Go to Applications -> “Your Application” -> Processes -> “Your Application Process” -> Configuration -> Application Process Properties

Create the property: issue_id

Now run the process:

Continue readingUrbanCode Deploy & JIRA Integration Part Two