You can configure the properties and action scripts of the services and application components to customize your application deployment.

Prerequisites

Procedure

  1. Select a service or application component and edit the information on the Details and Actions tabs below the blueprint.

    Only those properties that the application catalog administrator designated as overridable can be changed on the application blueprint.

    On the Actions tab, scripts are accessible for all stages of the component's life cycle, including install, configure, start, update, rollback, and teardown. An application catalog administrator can edit a service script from Library > Services.

  2. To edit a property, click the property in the table.

    If you have a single or clustered node, you must provide a value for the required property in at least one of the life cycle stages of the property. For example, to run an Apache Tomcat server, Java is required and the JAVA_HOME property value must be set.

    The Edit Property dialog box appears.

  3. (Optional) : To bind a property to another property or artifact, select the property value or artifact name from the Blueprint Value drop-down menu in the Edit Property dialog box.

    Binding to another property lets you customize a script based on the value of other node's run time property values such as IP addresses. Binding to an artifact lets you use a component without knowing its physical location.

  4. When you are finished creating the blueprint for the application, click Save.

    Application Services checks the application topology you created and displays a message box listing any errors. For example, you see a message if a property type that you selected is not compatible with a script type, or if a service or component is missing a required script. Some errors require correction before you can save the application.

What to do next

Create a deployment profile. See Create a Deployment Profile.