Configuring a Moves container

# The truststore and keystore must be correctly configured in moves.

# The line below is typical for OPS
webservices.trustStore=config/serverTrustStore.jks
# Developers should use
# webservices.trustStore=${user.home}/keystores/serverTrustStore.jks
webservices.trustStorePassword=changeit

# The line below is typical for OPS (on a DEV/TEST server)
webservices.keyStore=config/moves-test.jks
# Developers should use
# webservices.keyStore=${user.home}/keystores/moves-test.jks
webservices.keyStorePassword=changeit

# Since moves uses the roles database, we need to specify a roles 
# web service url and a function category. The following should work.
roles.function.category=APPM
webservices.mitroles.url=https://ws-test.mit.edu/uaws/services/ua

# If you are a developer, you may want to uncomment the following lines. These
# Allow you to use login locally, with all roles, instead of using the roles web service. 
# Change username and password to whatever you like.
# local.user.name=eotoole
# local.user.password=eotoole
# local.mitroles = MOVES_ADMIN, MOVES_MANAGER, MOVES_DEV, MOVES_QA, MOVES_TEST, MOVES_PROD
# local.authentication = true

# These properties are used to access the maven repository.
mit.maven.repository.username=moves#string
mit.maven.repository.password=dvtlsais

# Moves operates under the assumption that all oc4j containers in an environment type
# WILL HAVE THE SAME ADMINISTRATOR USERNAME AND PASSWORD. 
# Environment Types are Production, QA, Dev etc.
# The username is typically oc4jadmin, but the password is different for each environment type.
# (So all Production containers will have the same username and password, all Test containers 
# will have another password etc). 
# 
# Moves also allows you to create an arbitrary environment types.
# So today there exists P (Production), Q (QA), D (Development), but in the future we might add
# U (User acceptance testing) or other environments.Since it was a requirement that these usernames
# exist in the properties file, we use the convention:
# oc4j.deployer.username.[environmentTypeId]=[oc4j username]
# oc4j.deployer.password.[environmentTypeId]=[oc4j password]
#
# See examples below
#
# The moves App allows you to create arbitrary environments. The standard environments are
# P (Production), Q (QA), D (Development). Below we have properties to set the oc4j
# usernames and passwords for these environments. If you add new environments you need
# to add new properties
#
# So for example, if you add a UAT environment (U) you would add
# oc4j.deployer.username.U=[oc4j username]
# oc4j.deployer.password.U=[oc4j password]
#
# OC4J username and password to deploy applications to Dev environments (environmentTypeId=D)
oc4j.deployer.username.D=oc4jadmin
oc4j.deployer.password.D=XXXXXXX
#
# OC4J username and password to deploy applications to QA environments (environmentTypeId=Q)
# oc4j.deployer.username.Q=oc4jadmin
# oc4j.deployer.password.Q=[password]
# OC4J username and password to deploy applications to prod environments (environmentTypeId=P)
# oc4j.deployer.username.P=oc4jadmin
# oc4j.deployer.password.P=[password]