Prepare your Environment

You can either use a hardened Virtual Machine (VM) provided by CA, or provision your own VM. 
You can either use a hardened Virtual Machine (VM) provided by CA, or provision your own VM. 
Use one of the following methods to prepare your environment:
Before You Begin
Provision the CA Provided VM
For your convenience, CA provides a hardened image to expedite the installation process. The hardened image is available in OVA format, which can be directly imported into VMware and most other common virtualization platforms. Use the CA provided hardened image if you do not want to set up a VM with CentOS installed. See CentOS Hardened Image for requirements.
Download the API Developer Portal Virtual CentOS <version>.ova from CA API Management Solutions and Patches
The following table contains links to VMware documentation that describe the import process for different vSphere versions.
vSphere Version
The following tasks are related to provisioning the CA OVA, as well as for securing the image and to perform future troubleshooting:
Configure Network Time
The hardened image is set up with 
 enabled, which is configured to connect to servers in the domain on the Internet to synchronize time. If the usage of internet time sources is undesirable or not possible in your network, you can reconfigure the system to use time sources on your LAN. For more information about how to configure chrony, see The RedHat documentation.
Configure Static IP Address and DNS
The hardened image is configured with 
 enabled by default. You must configure the server with a static IP address and configure DNS servers. For more information about how to configure networking and how to set a static IP address and DNS servers, see the RedHat documentation.
Provision Your Own VM 
You can provision your own VM for 
API Portal
. You assume the responsibility for having a working VM with CentOS 7.x installed and functional before proceeding.
To create your own VM on which to install CA API Developer Portal, verify that you meet the following requirements:
Configure Docker docker_gwbridge Network
This section applies 
 if you are using IP addresses in the range, either when provisioning the CA OVA or your own VM. If you are not using IP addresses in the range, skip this section.
If you are using IP addresses in the range on your network, perform the following steps to ensure that there is no conflict between the default Docker docker_gwbridge network and your existing physical network. Failure to do this can result in issues such as not being able to send mail through your external SMTP server.
Follow these steps:
  1. Select a network range that is not in use on your network. In the next example, it is assumed that is not in use, and is used as the default Gateway for this network.
  2. Enter the following command on each device that will be part of your Docker swarm to create the docker_gwbridge network:
    docker network create \ --subnet \ --opt \ --opt \ --opt \ --gateway \ docker_gwbridge
    This creates a network called docker_gwbridge on each device with the network range and a Gateway address of With this network in place, Docker will not attempt to create it with the default settings when initializing the swarm.
More information: