...
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="0ff446be6330c1b1-72ac263b-451c4824-a6c3843c-2416aeb13c9f3df21f02d3a4"><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> |
...
- Start off by making sure you have network access between the Moves Server and the Container you wish to deploy to. (For non-local deployments you will need the IS&T infrastructure team to complete these steps).
- open a shell on the machine where Moves is running.
- cd to the ORACLE_HOME folder for this machine (typically /home/oracle/product/10.1.3/j2ee/home)
Wiki Markup type *java -jar admin_client.jar \[deployerUrl] \[oc4j-admin-username] \[oc4j-admin-password] -listApplications*. You should see a list of zero or more applications. *You MUST be able to execute this step without getting errors before even bothering returning to Moves!!!*
- Upon completion of this step, make a note of the deployerUrl, oc4j-admin-username and oc4j-admin-password.
- For the environment type that you will be using, verify that the oracle username and password are correctly set up in the properties file. See Moves Property File settings, specifically the section 'Oracle Application Server usernames and passwords'.
| Anchor | ||||
|---|---|---|---|---|
|
...