You can define new values for node properties, such as host name or vCPU. You can also define new values for application component and service properties that have the Overridable at Deployment check box selected in the application blueprint.

About this task

For successful deployment, assign a value to the required node properties from the library, blueprint, or deployment profile. The system defines node properties, such as memory allocation and number of CPUs, but you can override them. For example, a needed service might have a JVM heap size of 512 MB. But for a large deployment, you can override that setting and change the size to 1024 MB.

You can set a host name so that the virtual machine can be easily identified in the vCloud Director or vRealize Automation deployments. To generate unique characters you can append the ${random} expression at the end of a host name.

The cluster size of a clustered node can also be defined with new values.

Prerequisites

Procedure

  1. Verify that the properties you set in the blueprint appear accurately in the component tabs.
  2. (Optional) : Click the Service, Application Component, or Node tab.
  3. Select a specific service, application component, or node property.
  4. In the table, click the New Value column of a specific row and type the value to use in the deployment profile.

    For a deployment to Amazon EC2, you must change the global_conf property value to https://DarwinServerIP:8443/darwin/conf/darwin_global_noproxy.conf.

  5. To revert to the original value, click the Reset Value button (Reset the component value).
  6. (Optional) : In the Disk Mappings section, type a new integer value to increase or decrease the disk size.
  7. When you finish making changes, click Next.

Results

The Execution Plan tab appears.

What to do next

Review the provisioning tasks and dependencies in the execution plan. See Review the Execution Plan and Add Custom Tasks.