7.4

Table Of Contents
n
Verify that a bridge network is available for linking services.
n
Verify that the internal port of the target service is published. For cross communication, the service
can be mapped to any other port but must be accessible from outside the host.
n
Verify that the service hosts are able to access each other.
Procedure
1 Log in to vRealize Automation.
2 Click Templates in the left pane.
3 Edit the template or image.
Option Description
To edit a template a Click Edit in the upper-right section of the template that you want to open.
b Click Edit in the upper-right section of the container that you want to open.
To edit an image. Click the arrow next to the image's Provision button, and click Enter additional
info.
4 Click the Basic tab.
5 In the Services text box, enter a comma-separated list of services that the container is dependant on.
6 In the Alias text box, enter a descriptive name for the service or comma-separated list of services.
7 Click Save.
Configure Exposed Services in Containers
You can use a unique host name for a load balancer by providing an address and a placeholder in your
container settings.
The placeholder determines the location of an automatically generated part of the URL. This value is
unique for each host name. The address supports the %s format character to specify where the
placeholder is located.
Note If the placeholder is not used, it is positioned as a prefix or suffix of the host name, depending on
the system configuration.
It is recommended you use a load balancer that can target requests to each node if you build an
application which includes a service that must be publicly exposed and which must also scale in and out.
After you provision the application, the load balancer configuration is updated whenever the service is
scaled in or out by vRealize Automation.
Prerequisites
n
Verify that Containers for vRealize Automation is enabled in your supported vRealize Automation
deployment.
n
Verify that you have container administrator or container architect role privileges.
Configuring vRealize Automation
VMware, Inc. 327