7.0

Table Of Contents
What to do next
Add the start instances action to the entitlement that includes the Amazon catalog item. See Entitle Users
to Services, Catalog Items, and Actions.
Troubleshooting Incorrect Accents and Special Characters in XaaS Blueprints
When you create XaaS blueprints for languages that use non-ASCII strings, the accents and special
characters are displayed as unusable strings.
Cause
A vRealize Orchestrator configuration property that is not set by default, might be enabled.
Solution
1 On the Orchestrator server system, navigate to /etc/vco/app-server/.
2 Open the vmo.properties configuration file in a text editor.
3 Verify that the following property is disabled.
com.vmware.o11n.webview.htmlescaping.disabled
4 Save the vmo.properties file.
5 Restart the vRealize Orchestrator serv er.
Publishing a Blueprint
Blueprints are saved in the draft state and must be manually published before you can configure them as
catalog items or use them as blueprint components in the design canvas.
After you publish the blueprint, you can entitle it to make it available for provisioning requests in the
service catalog.
You need to publish a blueprint only once. Any changes you make to a published blueprint are
automatically reflected in the catalog.
Publish a Blueprint
You can publish a blueprint for use in machine provisioning and optionally for reuse in another blueprint.
To use the blueprint for requesting machine provisioning, you must entitle the blueprint after publishing it.
Blueprints that are consumed as components in other blueprints do not required entitlement.
Prerequisites
n
Log in to the vRealize Automation console as an infrastructure architect.
n
Create a blueprint. See Checklist for Creating vRealize Automation Blueprints.
Procedure
1 Click the Design tab.
Configuring vRealize Automation
VMware, Inc. 376