...
Property Name | Description | ||
|---|---|---|---|
${groupId} | replaced with the groupId of the application being deployed | ||
${artifactId} | replaced with the artifactId of the application being deployed | ||
${version} | replaced with the version of the application being deployed | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4542446c20063dd9-9123c544-4e2a4cfe-99658f2e-40d6431a2ad2f09eb83df6f9"><ac:plain-text-body><![CDATA[ | ${app.[paramName]} | replaced with the parameter value with key 'paramName' of the application being deployed | ]]></ac:plain-text-body></ac:structured-macro> |
...
Environments are really just a lookup that identifies the function of containers within a stack. The standard environments are 'Production', 'QA' , and 'DevelopmentTest'. These are already should be automatically set up when Moves is deployed for the first time, so they will not need to be changed. However, we allow creation of new future environments (for example 'Continuous Integration' or 'Staging'). Note that the property file may need to be edited (and the moves application restarted). See the section 'Oracle Application Server usernames and passwords' in Moves Property File settings.
...