Installing IBM Quick Deployer into IBM UrbanCode Deploy

Prerequisites

To successfully install IBM Quick Deployer, you must have the following:

• The Quick Deployer zip file, which you can download from the Package Content page.
• A running UrbanCode Deploy server. See System requirements for the supported version.
• The URL to the UrbanCode Deploy server, and an authentication token with admin privileges.
• A Linux system that has Java 6 or higher installed. You run the script on a Linux system. This can be the same system upon which the UrbanCode Deploy server runs, or it can be another Linux system.

Installation steps

1. On a Linux system that has Java 6 or higher installed, extract the contents of the Quick Deployer .zip file.
2. On the same Linux system, ensure that the JAVA_HOME environment variable is set to point to the location of the Java Runtime Environment (JRE). If necessary, run the export command to set the JAVA_HOME environment variable. For example:
   • export JAVA_HOME=/usr/lib/jvm/jre.
3. Run the setup.sh script. Use the UCD_SERVER argument to identify the URL to the UrbanCode Deploy server. Use the UCD_TOKEN argument to identify the UrbanCode Deploy server authentication token. To capture all of the console output, you might want to direct the output to a log file. For example:
   • sh setup.sh UCD_SERVER=https://ucd1.host.example.com:8443 UCD_TOKEN=99eb2bb3-aa81-998f-aab4-d990bfa6ff5c |& tee console.log

Note: When you run the setup.sh script, it creates a working directory. Before you run the script again (for example, to specify a different target UrbanCode Deploy server), delete that working directory. Otherwise, the script completes but fails to create component versions.

Results

After the script finishes, examine the console output or log file to ensure that it completed successfully. The output should show the following eight phases of work:

• STAGE 1 : user inputs
• STAGE 2 : download ucd cli client
• STAGE 3 : create UCD QD CLM team
• STAGE 4 : import QD application
• STAGE 5 : import QD components
• STAGE 6 : create QD tags
• STAGE 7 : create QD default environment
• STAGE 8 : create QD environment blueprints

The last action that the script performs is to create default application blueprints. For example:

• Creating default blueprints
• log4j:WARN No appenders could be found for logger (org.apache.http.impl.conn.PoolingClientConnectionManager).
• log4j:WARN Please initialize the log4j system properly.
• log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
• Created default-dept
• Created default-D4-vanilla
• Created default-D4-CLM
• Created default-D4-SSE
• Created default-E1-CLM
• Created default-E1-SSE

Miscellaneous

Notes:

• Throughout the IBM Quick Deployer wiki the screen captures are for reference only.
  In some cases if the functionality they display has not changed in the latest release they will be from a previous release

Related topics:

• Quick Deployer
• Quick Deployer setup and run

External links:

• Collaborative Lifecycle Management
• Continuous Engineering
• UrbanCode Deploy

Additional contributors: MichelleCrane, NathanBak, ChristianLopez