Application Services passes defined properties as environment variables to scripts running in a virtual machine. The external service version properties define the variables used in the scripts for the external service.
About this task
When you deploy an application with a preconfigured or custom external service, you cannot edit the property definitions or provider specification properties for that external service while the deployment is in progress.
Log in to Application Services as an application cloud administrator and an application publisher and deployer.
Familiarize yourself with the basic concepts of defining and configuring component properties and actions. See Developing Application Services Components.
To view examples about how to define an external service, selectto view the predefined services.
Verify that an external service version is available in Application Services. See Create an External Service in the Library.
- Open an existing external service version and click Edit.
- For the Property Name and Description, define a variable and add an optional description.
The property name cannot begin with a digit.
- To change the type, select a property type from the drop-down menu.
You cannot add types to the menu.
- Enter the value to substitute for this property when the script runs.
For example, for a property called http_port, you might type 80 in this field.Note:
For vCloud Director or vRealize Automation, if you add a value to the http_proxy, https_proxy, or ftp_proxy property with service scripts that use the darwin_global.conf file as a file source, when the script runs, these properties override any existing proxy information in the deployed application. Amazon EC2 does not require a proxy to deploy an application.
If the property type is set to Computed, you cannot type a value.
If the Required check box is selected and the Overridable in Blueprint check box is not selected, the property must have a value.
- From the Auto-Bind Tags drop-down menu, click New to select an Auto-Bind type to add the Property Descriptor tags to a property.
Tags designated only as Property Descriptor appear in the drop-down menu.
You can add multiple Auto-Bind tags.
For example, if the Auto-Bind type for the Apache 2.2.0 service appsrv_routes property is assigned as Consume, and the Auto-Bind type for the vFabric tc Server 2.1.0 service JVM_ROUTE property is assigned as Expose. The appsrv_routes property uses the JVM_ROUTE property values to customize itself. To allow Auto-Bind to connect to these service properties, you can add the Servlet Container and Route tags to the appsrv_routes and JVM_ROUTE properties, respectively. When you create an application that includes the vFabric tc Server and Apache services, the properties Auto-Bind to each other in the blueprint editor if there is a dependency between the two nodes.
- From the Auto-Bind Type drop-down menu, select an Auto-Bind type.
The Auto-Bind Type describes the role that a property is assigned to for autobinding in the blueprint canvas.
The property does not Auto-Bind.
The property value is set with autobinding.
The property can be used to customize another property value with autobinding.Note:
A property cannot have the Consume and Expose roles.
An Auto-Bind type of Consume or Expose requires at least one Auto-Bind tag to be defined for the property. Auto-Bind tags on the Consume property must be a subset of the tags on the Expose property. The tag sets do not have to be equal.
- Select the Required check box for properties that are required to deploy an application.
If any of the required property values are left blank, you are prompted to complete them before an application deployment.
If the property type is Computed, the Required check box is not applicable. If the property type is Content, the Required check box is selected by default and the Secured check box is not applicable.
For example, for an http_proxy_port property using the Apache JServ Protocol (AJP), you must set the value to 8009.
- Select the Secured check box for passwords you define or to obscure the values of other properties.
If a property is changed from Secured to Unsecured, Application Services resets the property value, for security purposes. You must set a new value for the property.
- From the Override drop-down menu, select a property override option.
Property is overridable in the application blueprint.
The cloud admin cannot view this property when registering the external service Instance to a deployment environment.
Cloud admin can override the property in the deployment environment.
The property appears in the application blueprint canvas and user can Auto-Bind to a property. The property value is not editable in the application blueprint.
Property is not overridable.
- Select the Overridable in Blueprint check box to allow users such as an application architect to override the value for the property in an application blueprint.
If the property type is Computed, the Overridable in Blueprint check box is not applicable.
If a property is not overridable in the blueprint, you cannot set the Auto-Bind type to Consume.
For example, the application catalog administrator might configure the vFabric tc Server service to have a JVM heap size of 512MB. But for large deployments, the application architect might change the setting to 1024MB.
- Click Delete to remove the selected row from the Properties section.
- (Optional) : Click Reset to revert to the original property value.
- Click Upload to import the property values to a selected CSV file.
- Save your external service property definitions.
What to do next
Specifying external service definitions has no impact on deployments unless you create an external service instance in a deployment environment to enable the external service definitions on all of the deployments under the deployment environment. See Map an External Service Instance.
Create provider specification for the custom external service version. See Create Provider Specification for an Advanced External Service Version.