This page is for people responsible for installing moves, and getting it up and running on a new environment.
When deploying Moves in an OAS environment, ${user.home} is typically /home/oracle, and ${user.dir} is typically the oc4j j2ee/home directory
- each container must have a properties file called ${user.home}/sais-moves-web.properties.
- the container must have a datasource defined called jdbc/MitsisDS
The following properties are defined in ${user.home}/sais-moves-web.properties.(The list of default values can also be found by looking inside the exploded web archive in the file [sais-moves-web.war]/WEB-INF/classes/sais-moves-web.properties)
Property Name |
Required |
Default Value |
Description |
|---|---|---|---|
mail.smtp.host |
N |
outgoing.mit.edu |
This is the host for the smtp mail server that moves uses when sending notification emails. |
email.address.from |
N |
Moves Automated Email<moves-noreply@mit.edu> |
This is the "from" email address for notification emails |
wiki.help.root |
N |
https://wikis-mit-edu.ezproxyberklee.flo.org/confluence/display/SAISFRAMEWORK/Moves+Help/ |
This is the root for the moves help pages (including this file) |
mit.maven.repository.username |
N |
moves#string |
username for maven.mit.edu maven repository. This user must have read/write access to saisReleaseRepo. See the mit maven repository admin for details |
mit.maven.repository.password |
Y |
changeme |
password for mit.maven.repository.username |
webservices.keyStore |
N |
config/moves-test.jks |
path to the key store. The key store must be configured correctly for this application, as the application uses the mit roles service in sais-common. If this path does not begin with '/' then it will be relative to the current working directory. The current working directory is typically the oas j2ee/home folder for OAS deployments. |
webservices.keyStorePassword |
N |
changeit |
password for webservices.keyStore |
webservices.trustStore |
N |
config/serverTrustStore.jks |
path to the trust store. The trust store must be configured to include the MIT root certificate, since, at the time of this writing, the cert for https://mv-ezproxy-com.ezproxyberklee.flo.orgrequires the MIT root certificate in order to validate the trust chain. If this path does not begin with '/' then it will be relative to the current working directory. The current working directory is typically the oas j2ee/home folder for OAS deployments. |
webservices.trustStorePassword |
N |
changeit |
password for webservices.trustStore |
|
|
|
|
Oracle Application Server usernames and passwords:
Moves requires a username/password with admin privileges in order to deploy an app to a container. The IS&T infrastucture team uses a single username and password for each class of container. Thus, there is a single username/password for all OAS DEV servers, one for all QA servers, one for all Production Servers etc. To configure moves, we use the following property name pattern in ${user.home}/sais-moves-web.properties.
Property Name |
Required |
Default Value |
Description |
|---|---|---|---|
oc4j.deployer.username.[environmentTypeId] |
N |
|
Username for environment type [environmentTypeId]. |
oc4j.deployer.password.[environmentTypeId] |
N |
|
Password for environment type [environmentTypeId]. |
The Environment Type Id is a single letter (usually P for Production, T for Test etc). You can see a list of all of the environment types (and environment type ids) that Moves knows about by going to the Administration -> Environments page.
# OC4J username and password to deploy applications to Dev environments (environmentTypeId=D) oc4j.deployer.username.D=oc4jadmin oc4j.deployer.password.D=admin # OC4J username and password to deploy applications to QA environments (environmentTypeId=Q) oc4j.deployer.username.Q=oc4jadmin oc4j.deployer.password.Q=admin # OC4J username and password to deploy applications to prod environments (environmentTypeId=P) oc4j.deployer.username.P=oc4jadmin oc4j.deployer.password.P=admin