As a cloud administrator, you can make Automation Assembler templates available in the Automation Service Broker catalog by adding an Automation Assembler content source and sharing the templates. The templates are the specifications for services or applications that you can deploy to your cloud providers.
After you import the Automation Assembler templates, you share them with project members so that they can deploy the templates. At the request time, the template is deployed to cloud zone account region or datastore that supports the template requirements.
Prerequisites
- Verify that the cloud templates that you are importing are deployable and released in Automation Assembler before you import them. See How to save different versions of a cloud template in Using Automation Assembler.
- If you want to share cloud templates that were created for another project with the members of this project, verify that you allow sharing in the Automation Assembler template settings.
Procedure
Results
The released Automation Assembler templates are imported into Automation Service Broker, shared in the catalog, and deployable.
What to do next
- If the deployment fails, click the deployment name and begin troubleshooting. See What can I do if an Automation Service Broker deployment fails. If you are an Automation Assembler cloud administrator, you can also do more extensive troubleshooting in Automation Assembler What can I do if an Automation Assembler deployment fails in Using Automation Assembler.
- If you want to control how long a deployment can exist, create a lease. See Setting up Automation Service Broker policies.
- To provide more or fewer user inputs at request time, you can create a custom form. See Customize an Automation Service Broker icon and request form.