An advanced external service requires you to create a provider specification. This specification is a set of one or more scripts that defines how an external service can be configured, updated, rolled back, and torn down in various service provider environments such as VMware Data Director or Amazon RDS. The provider specification also has properties that you can define to connect to the provider and the provider specific parameters.
About this task
You can view examples about how to create a provider specification for an external service from thepage.
You can change only the group membership settings for the external service. The new membership settings are then propagated to the service provider specifications of the external service.
User cannot update group membership of the service provider spec separately.
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.
If you plan to use a script that downloads software from an external Web site, verify that the virtual machine you use for deploying the application has access to an external network.
Verify that properties are defined for the external service version. See Application Services. See Create an External Service in the Library.
- Open an existing service version and click Create Provider Spec Version.
- Type the provider specification name and select Create Version.
- Specify major, minor, or micro release versions, with or without qualifiers.
The provider specification name stays the same.
- (Optional) : In the Description section, if you are creating a provider specification for a specific configuration, describe the configuration used and applicable requirements.
- In the Logical Templates section, if you set the supported OSes to Windows or Linux-based operating systems, the corresponding logical templates are available in the drop-down menu.
- Add applicable properties.
- From the drop-down menu, select a script type for your action script.
You can author in Bash or BeanShell script for Linux-based applications, or Windows CMD, PowerShell, or BeanShell script for Windows-based applications.
- In the Script column, click the hyperlink to open the Edit Script dialog box.
You can write the script or copy a script into the dialog box.
An application catalog administrator can parameterize the installation and configuration of services. The properties that are defined for a service can be used inside the script.
- Click the down arrow in the script type field to select an action script type for a life cycle stage.
- To insert the properties you defined, click the down arrow in the Select a property to insert list.
- (Optional) :
Select the Reboot check box to restart the virtual machine after the script runs successfully, during an application deployment.
- Click OK.
- In the Reboot column, select the check box so that the agent bootstrap can restart the virtual machine after an action script runs successfully.
After the virtual machine is restarted, the agent proceeds to the next life cycle stage script defined in the service version.
- Click Reset to clear the script.
This operation does not remove the row for the life cycle stage.
- When you are finished creating the provider specification version, click Save.
The provider specification version you created is added to the advanced external service.
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.
Add the external service to your application blueprint. See Add an External Service to an Advanced Blueprint.
Update external services or copy an existing external service. See Maintain External Service Versions.