With vCloud Application Director you can create basic or advanced external services.

A basic external service does not have support for multiple service providers. You must define the logical template and have the option to add scripts for the CONFIGURE, UPDATE, ROLLBACK, and TEARDOWN life cycle stages. Some examples of a basic external service include, an existing database with the application schema installed, a SAAS application such as Workday, an LDAP server, or a Single Sign-On (SSO) server.

An advanced external service includes options for provider specifications that add support for multiple providers of the external service. After the advanced external service property values are defined in the provider specification, these values are populated in the external service instance when you map that instance to a deployment environment. For example, an external Oracle database can be provisioned and configured through VMWare Data Director or Amazon RDS. The external load balancer in an application can be implemented with an F5 load balancer instance or a software load balancer such as an Apache server.

You can share an external service publicly or privately in a group. Sharing is supported at the component level and not at the individual version level. When you share an external service, the external service instance profile are not shared. Each group must define an external service instance profile in its deployment environment.

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

Verify whether you must add items to the operating systems and descriptive tag lists. See Add Operating Systems to the Catalog and Add Tags to the Catalog.

To view examples about how to name or describe an external service, select Catalog > External Services to view the predefined external services.


On the vCloud Application Director title bar, click the drop-down menu and select Catalog > External Services.


Click New in the toolbar.


Set the name of the external service, add a description, and click Save.

Use a name that corresponds to the server or database that you are


Click Create External Service Version to create an external service version.

You can create multiple versions for an external service.


In the dialog box, select Basic or Advanced and click OK .


Complete the external service version information.

The external service version name stays the same.


Specify major, minor, or micro release versions, with or without qualifiers.

For example, you might use version numbers such as 1.0, 1.5, or 1.0.1-Dev.


(Optional) In the Description section, if you are creating an external service version for a specific database, describe the database version used and any applicable required configuration.


Click New to set the tags from the drop-down menu.

The tags group the external services and you can view them in their corresponding groups when you create a deployment blueprint for an application.

You can add multiple tags.


To create a tag that is not in the list, click Cancel, and select Catalog > Tags.


(Optional) In the Supported Components section, if only certain types of application component can run in this advanced external service, click New to specify those components here.

For example, only SQL scripts can run in a database server. The components that you select restrict what application components can be added to this advanced external service in an application blueprint. Leave this field blank if you can add components to the advanced external service.


Designate an operating system for the external service.


For the basic external service, select a Windows or Linux-based template from the drop-down menu in the Logical Template section.

The supported OS associated to the logical template is populated.


For the advanced external service, if the scripts used in the advanced external service can run only on particular operating systems, click New to add those operating systems in the Supported OSes section.

In the blueprint editor, vCloud Application Director prevents the external service from being added to a template unless the template contains one of these operating systems. Leave this field blank if the advanced external service can be used in any operating system.


To use an operating system name that is not in the list, click Cancel, and select Catalog > Operating Systems to create an operating system name.

Configure the external service version properties. See Define External Service Properties.