Even if you use Application Services 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 Application Services to use a proxy for these cases.
About this task
You must complete this task before you create services and applications or before you deploy existing predefined sample services and applications.
Application Services 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 vRealize Automation Deployment Environment.
Log in to Application Services as an application architect and an application catalog administrator.
Verify that you have access to the virtual machine where Application Services 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 Application Services Appliance.
Familiarize yourself with the procedure for creating new services. See Add a Service to the Library.
- For vCloud Director or vRealize Automation, configure the Application Services virtual appliance to use a proxy.
- Log in to the Application Services virtual appliance as darwin_user.
- Enter su to switch to root user.
- Open the file /home/darwin/tcserver/darwin/webapps/darwin/conf/darwin_global.conf with a text editor.
- Update the proxy IP and port information and save the file.
The proxy URL format is http://proxy:PortNumber.
Existing predefined applications or library 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.
- Log in to Application Services as an application catalog administrator and define proxy-specific properties and scripts for a new service or an existing service.
- For a new service, add a service to the library.
- 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.
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.
- Add the following lines to the beginning of each action script for the service that requires a proxy:
# Import global conf . $global_conf
- Save the service.
- Log in to Application Services as an application architect and define proxy-specific properties and scripts in the application blueprint to configure an application to use a proxy while creating the application blueprint.
- 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.
- Add the following lines to the beginning of each action script for the application component that requires a proxy:
# Import global conf . $global_conf
What to do next
Register a cloud provider for your cloud environment. See Register the vCloud Director Cloud Provider and Template, Register the vRealize Automation Cloud Provider and Template, or Register the Amazon EC2 Cloud Provider and Template.