Defining Model Variables

You define model variables before you deploy a cartridge to a specific run-time environment.

To define model variables:

Create model variables.

See "Creating Model Variables" for more information.
Populate a field with the model variable.

When populating fields with model variables, use the following syntax:

%{VariableName}

where VariableName is the name of the model variable as defined on the Project editor Model Variables tab.

For example, Oracle recommends that you populate the Run As field on the Automation Plug-in Properties view Details tab with the default automation user variable. To use the delivered sample model variable (DEFAULT_AUTOMATION_USER), you populate the Run As field with the value %{DEFAULT_AUTOMATION_USER}.
Save, clean, and build the project.

See "Running Clean Builds" for more information.
Select Studio, then select Show Environment Perspective.
In the Environments tab, select the environment to which you want to deploy the cartridge.

See "Deploying Cartridge Projects from the Environment Perspective" for more information about deploying cartridges. See "Creating Run-Time Environments" for information about creating new environments.
Connect to the environment.

See "Testing Run-Time Environment Connectivity" for more information about connecting to the environment.
Define environment-specific values for model variables.

You define these values on the Model Variables tab. The system displays a list of all the model variables defined in the workspace (and any corresponding default values that you defined in the Project editor Model Variables tab. See "Studio Environment Editor Model Variables Tab" for more information.

Environment-specific model variable values override those that are defined in the Project editor. If you define fields with model variables but you do not define the model variable with a default value (in the Project editor Model Variables tab) or with an environment-specific value (in the Studio Environment editor Model Variables tab), Design Studio creates a problem marker. You cannot deploy a cartridge until you resolve all problem markers.