Installing UrbanCode Velocity with Docker Compose#
Install UrbanCode™ Velocity into the Docker Compose container orchestrator.
The ID that you use to install the product must be able to make changes to the host environment. The tools required by all installation scenarios include the following items:
- Docker installed on the host system.
Internet connection. During installation, files and container images are retrieved from remote locations. If you are unable to access the internet during installation, you can download the files beforehand and perform an offline installation.
Note: The installation files used for offline installation are not the same as those used for internet-connected installation. Ensure that you download the right file for you installation environment.
UrbanCode™ Deploy Version 6.2.3 and later. Although not strictly required, many UrbanCode Velocity features assume integration with UrbanCode Deploy. It doesn't matter which product you install first.
If you are using an UrbanCode Deploy version prior to V6.2.5, you must install the patch located at the following website: http://public.dhe.ibm.com/software/products/UrbanCode/plugins/ucsync/patches/ibmucd/. Select from the index the appropriate version that is installed on your computer.
UrbanCode Velocity can connect to an UrbanCode Deploy server on the same network. If you install UrbanCode Velocity with Kubernetes, the Kubernetes cluster must be on the same network as the UrbanCode Deploy server.
In addition to the requirements for all installation scenarios, the following items are required for Docker Compose systems:
- Docker Compose version 17.09.0-ce, build afdb6d4 and later
- CPU with 4+ cores.
- 8GB RAM
- 8GB storage
- If you are installing the product on Red Hat Enterprise Linux®, you need RHEL 7 or later.
Get an access key. The access key enables you to complete installation. Visit the UrbanCode Velocity web portal to obtain your key. After completing the form, you can copy the access key. Store the key in a readily-available location; you use it during installation.
Note: Make sure that you select a key for the product version that you want to install. Keys for the Standard Edition do not work with the Community Edition and vice-versa.
The installation instructions describe installing the product on all supported operating systems. The downloaded executable file steps you through the installation process and sets your installation parameters.
Download the installation file for your environment.
Note: For macOS and Linux installations, set the appropriate permissions before running the file:
sudo chmod +x.
- Linux: https://hcl-velocity-binaries.s3.amazonaws.com/velocity-se-hcl-install-latest-linux
- Windows: https://hcl-velocity-binaries.s3.amazonaws.com/velocity-se-hcl-install-latest-win.exe
- Mac OS: https://hcl-velocity-binaries.s3.amazonaws.com/velocity-se-hcl-install-latest-macos
- Run the downloaded executable file.
Complete installation by responding to the prompts described in the following steps.
When the script starts, you are prompted to accept the license. You can explicitly accept the license without viewing it by appending the following parameter to the command:
At the Please enter your Velocity access key prompt, enter your SE version access key.
If you previously installed an SE version, the already-configured key is the default value.
Note: Make sure that you enter the key for the right version.
At the Choose the platform prompt, select
At the Enter the location where the Velocity files will be installed prompt, enter the location where you want to install the product files.
Files are copied to the specified directory in a subdirectory named
At the Please enter the hostname where you will run Velocity prompt, enter the host name where users can access the Web UI.
The default value is
The host name must resolve to a name on your DNS server, or in the server's hosts file. On Linux, the file location is etc/hosts; on Windows, the location is C:\Windows\System32\drivers\etc\hosts.
At the Enter the desired port where Velocity will run prompt, enter the port number for the Web UI.
The default value is
If you are performing an off-line installation, at the Choose how to receive offline docker images for velocity prompt, select one of the following options.
- Local File System. Copy images to the file system and manually load them into the local Docker registry.
- Local Docker Registry. Load images into the local Docker registry. This requires the Docker client on the host where the installation script is running.
- Remote Docker Registry. Load images into the local Docker registry, and then tag the images and push them to a remote Docker registry. This requires the Docker client on the host where the installation script is running. The images are loaded on the local host.
Complete installation by changing to the directory where you installed the product, and start Docker Compose. For example:
~/projects/velocity-se/ docker-compose up -d
The UrbanCode Velocity images are pulled from Docker Hub and configured for Docker Compose.
Access the UrbanCode Velocity Web UI. The URL is https://hostname:port, where
port are the values that you set during installation. The initial user name is admin and the default password is admin.
Installation properties are stored in the [installation_folder]/docker-compose/.env file. You can edit the properties appropriate for your environment. The env file contains a description for all installation properties, including the following properties:
The product access key obtained earlier.
The domain of the URL the users will use to access Velocity. The value is usually the hostname of the virtual machine where Docker Compose is running.
To complete installation, replace the supplied SSL public certificate and private key with your own copies. You can use OpenSSL to generate your own key with a command similar to the following example:
openssl req -newkey rsa:2048 -nodes -keyout key.pem -x509 -days 365 -out certifcate.pem
Place your self-generated key and certificate in the [velocity-install-folder/product_version_number/conf/ssl folder.
After you purchase the product, you receive a permanent access key, and a license key.
Parent topic: Installation