...
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="8f342900bb0320e7-ab1ac100-44ab4b85-ba4f8cfb-df692caa0deb2a31b9e1a933"><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!!!* The most common sources of error here are no network connection (firewall or ipconfig issues), bad usernames/passwords, incorrect deployer urls.
- 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 found in the previous step are correctly set up in the properties file. See Moves Property File settings, specifically the section 'Oracle Application Server usernames and passwords'.
- On the Administration->Stacks->Container page, make sure the environment type is correctly set, and that the deployerUrl matches the previous step.
- Save the container.
Use the Server Test Page! Simply click on the "container ping" icon (Anchor ServerTestPage ServerTestPage 
) for the container you want to test. The page should list the same applications as were listed in the prior step. If the Server Test Page returns an error, go through the steps above again. You will NOT be able to deploy to a container that does not return a successful response on the Server Test Page!
...