Even if you use vCloud Application Director only to deploy applications in a private cloud, some deployments might require access to URLs from outside the corporate firewall. For example, an action script might involve downloading application bits from an open-source Web site. You can configure vCloud Application Director to use a proxy for these cases.

You must complete this task before you create services and applications or before you deploy existing predefined sample services and applications.

vCloud Application Director also contains a proxy file called darwin_global_noproxy.conf, which does not define a proxy. You can specify this file as the global_conf property value if a deployment environment does not require a proxy. The Amazon EC2 deployment environment does not require a proxy to deploy an application.

The proxy support is now expanded from global level to deployment environment level. For more information, see Create a vCloud Automation Center Deployment Environment.

Verify that you have access to the virtual machine where vCloud Application Director is installed and have the password for logging in to the operating system with the darwin_user account. This password was set during installation. See Start the vCloud Application Director Appliance.

Verify that your vCloud Application Director user account has the ROLE_CATALOG_ADMIN catalog administrator role assigned to it.

Verify that your vCloud Application Director user account has the ROLE_APP_ARCHITECT application architect role assigned to it.

Familiarize yourself with the procedure for creating new services. See Add a Service to the Catalog.

1

For vCloud Director or vCloud Automation Center, configure the vCloud Application Director virtual appliance to use a proxy.

a

Log in to the vCloud Application Director virtual appliance as darwin_user.

b

Type su to switch to root user.

c

Open the file /home/darwin/tcserver/darwin/webapps/darwin/conf/darwin_global.conf with a text editor.

d

Update the proxy IP and port information and save the file.

The proxy URL format is http://proxy:PortNumber.

Existing predefined applications or catalog services that must access a repository by using a yum update or install command use the proxy specified in this file. The predefined services and applications have the script required to access this proxy.

2

Log in to vCloud Application Director as a user with the catalog administrator role and define proxy-specific properties and scripts for a new service or an existing service.

a

For a new service, add a service to the catalog.

b

In the new or existing service, add a property with the name global_conf to the service, of type Content, and define the value as https://DarwinServerIP:8443/darwin/conf/darwin_global.conf.

Caution

If you add a value to the http_proxy, https_proxy, or ftp_proxy property with service scripts that use the darwin_global.conf as a file source, when the service script runs, these configured properties override any existing proxy information in the application.

c

Add the following lines to the beginning of each action script for the service that requires a proxy:

# Import global conf
 . $global_conf
d

Save the service.

3

Log in to vCloud Application Director as a user with the application architect role and define proxy-specific properties and scripts in the application blueprint to configure an application to use a proxy while creating the application blueprint.

a

For the application component, add the global_conf property to the application component, of type Content, and define the value as https://DarwinServerIP:8443/darwin/conf/darwin_global.conf.

b

Add the following lines to the beginning of each action script for the application component that requires a proxy:

# Import global conf
 . $global_conf