You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Administering Moves

The entities that need to be administered for moves are listed below.

  1. ContainerRequirements
  2. Repositories
  3. Environments
  4. Stacks
  5. Containers
  6. Applications

Container Configuration Requirements

For OAS deployments, ${user.home} is typically /home/oracle, and ${user.dir} is typically the oc4j j2ee/home directory

  1. each container must have a properties file called ${user.home}/sais-moves-web.properties.
  2. each container must have a folder called ${user.home}/sais-moves-web. The name of this folder can be overwritten using property name moves.home in ${user.home}/sais-moves-web.properties.
  3. The default maven home folder is ${user.home}/sais-moves-web/maven. (Typically this folder is a soft link to a specific distribution of maven like apache-maven-2.2.1). The name of this folder can be overwritten using property name maven.home in ${user.home}/sais-moves-web.properties.
  4. Subversion client must be installed. The command for running subversion must be svn, and must be in the path.
  5. The default subversion username is isdasnap. An alternate subversion username can be set using property name subversion.username in ${user.home}/sais-moves-web.properties.
  6. The default subversion private key location is ${user.home}/sais-moves-web/sais.private. An alternate subversion private key location can be set using property name subversion.private.key.location in ${user.home}/sais-moves-web.properties.
  7. The default

/sais-moves-web.properties.
in should have a folder called sais-moves-web contained in user.home. (The exac

/home/oracle/sais-moves-web/apache-maven-2.2.1

path to java
/home/oracle/product/10.1.3/jdk

working folder for maven builds and logs will be in $

Unknown macro: {user.home}

/sais-moves-web/ where user.home is currently /home/oracle
add a button to remove build artifacts > 30|60|90|366 days
add a button to remove db logs > 30|60|90|366 days

In general you should set entities up in the order that they appear above. The entities are described in detail below.

Repositories

Repositories are maven repositories, accessible to moves over http/https. An example is the the SAIS Group repository at https://mv-ezproxy-com.ezproxyberklee.flo.org/nexus/content/groups/saisGroupRepo. Maven has a well defined format, which specifies where to find an application within a repository. Each Application has an 'ArtifactId', a 'GroupId' and a 'Version'. So, for example, moves itself has artifactId=sais-moves-web, groupId=edu.mit.ist.es, versionId=2.0.0. Maven will translate this, by default into a final location of https://mv-ezproxy-com.ezproxyberklee.flo.org/nexus/content/groups/saisGroupRepo/edu/mit/ist/es/sais-moves-web/2.0.0/sais-moves-web-2.0.0.war" The properties you need to configure for a repository are:

  • server (e.g. maven.mit.edu)
  • port (e.g. null - if port is null, moves uses the default port for the protocol supplied)
  • protocol (e.g. https)
  • base url (e.g. /nexus/content/groups/saisGroupRepo)

Environments

Environments are really just a lookup that identifies the function of containers within a stack. The standard environments are 'Production', 'QA', and 'Development'. These are already set up when Moves is deployed, so they will not need to be changed. However, we allow creation of new future environments (for example 'Continuous Integration' or 'Staging').

Stacks

A Stack is simply a grouping of 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.

Containers

A container is the service that an application is deployed to. When you configure a new Container, you will be asked to select from one of the container types. The two container types that are currently available are

  • 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. (TODO: discuss the optional and required parameters in more detail)

Applications

Applications represent web apps (.war or .ear applications) that can be deployed to a container. (TODO: discuss the optional and required parameters in more detail)

  • No labels