...
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="5209eacb43bf49be-5e4a8b8b-422e4c99-939cbdb6-165f543696056c587bb423e4"><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> |
...
A Stack is simply a grouping of Applications and Containers by Environment. Stacks allow Moves to answer the question 'What is the container for Application 'X' in Environment 'Y'. Once you create a Stack, you can add containers to it for each environment. When we subsequently configure an application, we will tell it what Stack is associated with that application. (So, for example, the application 'OGS Application' might reference 'OGS Stack'. 'OGS Stack' references containers for 'Production', 'QA', and 'Development'). By looking at these relationships, Moves knows which container to deploy to when asked to deploy to a particular environment.
...
- OC4J Container (deploys to Oc4j containers)
- Mock Container (does nothing, used to test workflows)
In the future we will implement other containers according to MIT needs (tomcat/weblogic etc).
For the Oc4j container, the deployerUrl must be configured. This is the url you would normally type if you are manually deploying an application using the oracle admin_client.jar utility. Typically you will use a deployerUrl of the form deployer:oc4j:opmn://server-name:port-number/application-name for OAS clusters. You will use a deployerUrl of the form deployer:oc4j:localhostserver-name for OAS standalone instances. The deployment process essentially just runs the admin_client program.
...
Below is the configuration page for containers.
Moves will need to know
- Where is your oc4j home directory (so it can locate the admin_client.jar program)
- What is the deployer url for the cluster (or standalone instance)
- What is the username and password to use for the target container
The following checklist should help you successfully configure a container.
- Start off by making sure you have network access between the Moves Server and the Container you wish to deploy to.
| Anchor | ||||
|---|---|---|---|---|
|
...