Unsupported content


This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Using parameters in PaaS provisioning

When setting up service blueprints for platform-as-a-service (PaaS) provisioning with BMC Database Automation or any third-part provider, you can use parameters in various parts of the process. Parameters let users override values defined in the provider template and the service blueprint configuration.

Parameters differ from options, which let end users select from a predefined set of choices when requesting a service.

This topic includes the following subtopics:

Parameters for PaaS applications

PaaS applications can run software packages in the form of scripts. The script must be defined in BMC Database Automation as an Action, and the Action must be published to the product catalog. (Currently, the process of publishing the Action is different than the process for publishing a BMC Database Automation template.) 

If you define a SQL script as an Action and the script contains a parameter, the name of the parameter must be enclosed in curly brackets, and the name must begin with GAC_. For example, if you want the value of a parameter named "token" to be passed into SQL Action, the parameter in the SQL Action must be named {GAC_token}.

If you define some other type of script as an Action (for example, a Perl script or a software installation script) and you want to include parameters in the script, insert parameters according to the syntax of the script you are executing.

For detailed information about how Actions are constructed in BMC Database Automation, see Creating an Action and Actions environment variables.

Parameters for BMC Database Automation resources

For on-premise PaaS, PaaS resources are based on templates defined in BMC Database Automation. There are two categories of parameters that can be inserted into templates:  

  • User-defined—Parameters that must be set up in a BMC Database Automation template before the template is published to the product catalog. End users can provide input for user-defined parameters to override characteristics of the template.  For more information on setting up variables (that is, parameters), see Managing templates for Oracle on Linux and UNIX in the documentation for BMC Database Automation.


    Parameters placed in the non-editable or hidden sections of BMC Database Automation templates cannot be overridden. Do not place parameters in those sections if you want BMC Cloud Lifecycle Management to use those parameters.

  • Predefined—Parameters that can always be inserted into the resource set definition to override values specified in a service blueprint. The following predefined parameters are always available:

    Parameter namePurpose
    BmcDbName(Required) Defines the first eight characters of the name of the database being provisioned. This parameter is particularly important because you cannot deploy two databases with the same name to the same environment. The only way to specify the name when you are deploying more than one database is through the use of parameters.
    BmcDbEditionIdentifies the database edition being provisioned.
    BmcDbInstanceMemorySpecifies the amount of memory made available for a database instance.
    BmcDbMasterUserName(Required) Defines the master user for the database being provisioned.
    BmcDbMasterUserPassword(Required) Sets the password for the master user.
    BmcDbVersionSpecifies the database version you are deploying, such as

The name you assign to a parameter in the resource definition must exactly match the name in the list above or it must exactly match the name of the corresponding field as defined in BMC Database Automation template.

Related topics

Configuring service blueprint parameters

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.