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

UrbanCode Deploy & JIRA Integration Part One

Today I’m going to show you how to integrate UrbanCode Deploy with the well-known Atlassian Issue Tracking System Jira.

First of all we need the UrbanCode Deploy JIRA plugin .

Once downloaded and installed we will find a new menu item:  Issue tracking ->Jira Plugin into our step palette:

We will use, in particular, the Transition Issue step to put “IN PROGRESS” an open task and then, at the end of our Application Process flow, put the task in “DONE” status.

Continue readingUrbanCode Deploy & JIRA Integration Part One

UrbanCode Deploy – License Server Installation

To use IBM UrbanCode Deploy 6.x.x or 7.x.x, you need to install a Rational Common Licensing environment, import acquired licenses, and apply those licenses to the IBM UrbanCode Deploy servers and agents.

For enterprise environments configure IBM Rational License Key Server in a fault-tolerant configuration (redundant servers). Redundant servers are a system of three servers that work as a team to manage a single pool of floating license keys.

If one of the servers goes down, the other two license servers automatically continue managing the license pool. This type of redundant configuration requires that a minimum of two license servers are running at all times. If any two license servers no longer work, the third license server does not serve licenses. Two servers must be operating to serve licenses to clients.

Remember: You must have the license key file for redundant UNIX servers. Go to the Rational License Key Center and request a license for redundant servers. License Key Center will ask you for the primary, secondary and backup servers. Be sure to specify the redundant servers in the correct order:

Hostname1 is the primary server
Hostname2 is the secondary server
Hostname3 is the backup server

Continue reading “UrbanCode Deploy – License Server Installation”