In releases of OpenEdge prior to version 12, the OpenEdge Management web application was hosted on Eclipse Jetty. Eclipse Jetty was, in turn, hosted as a plugin to the AdminServer. In OpenEdge 12, OpenEdge Management is hosted on a dedicated instance of Progress Application Server (PAS) for OpenEdge. This allows OpenEdge Management to run independently of the AdminServer, and also to manage multiple local as well as remote AdminServer instances.

Each PAS for OpenEdge instance has a conf/appserver.properties file in which you make updates to system properties. Several of the properties that were previously defined in the fathom.init.params file are moved into this conf/appserver.properties file as-is. Note the following updates that are required to the AdminServer configuration of OpenEdge Management.

System properties configuration file

Some properties in the appserver.properties file are new in OpenEdge 12 and replace values that were previously stored in the fathom.init.params file, as follows:

#Fri, 11 Jan 2019 18:03:26 +0530
# The appserver.properties file contains name-value Java properites used by
# the Progress Application Server (PAS) and web applications.
# Each non blank and non comment line will be defined as a java system property
# by prepending a '-D' and passed on the command line to the JVM via the
# JAVA_OPTS environment variable.
#
# Comment lines may be used by placing a pound signe (#) in column zero.  Trailing
# comments are not supported.
# You may use shell environment variable substitution using the form ${env-var-name}

# The release version of the Progress Application Server version
psc.as.version=4.0.0

# The type of PAS installation {standard|instance}
psc.as.type=instance

# The PAS installation OS type {windows|unix}
psc.as.os=windows

# The PAS installation personality type {appserver|tokenserver|fathom}
psc.as.personality=fathom


# windows service name used in windows registry for the service name
psc.as.winsvcname=cat


# Optional PAS instance name for tcman admin tools.  If not specified
# the instance name is the CATALINA_BASE's directory name "home"
psc.as.alias=ho

# Optional directory path of a PAS instance's parent
psc.as.parent=C:/oemgmt

# The PAS server & instances security policy {default|developer|production}
psc.as.security.model=production

# Indicator {true|false} of Windows OS service registration
psc.as.service=true

#OpenEdge installation directory needed for classic Adminserver libraries
Install.Dir=C:/dlc

#OpenEdge installation directory needed for PAS libraries
psc.as.oe.dlc=C:/dlc

#Fathom configuration file location
psc.oem.fathom.properties=${CATALINA_BASE}/conf/fathom.properties

#Fathom log file directory
psc.oem.logs=${CATALINA_BASE}/logs

#Fathom SNMP adapter state directory
psc.oem.snmp=${CATALINA_BASE}/work/snmp

#Fathom installation directory
psc.oem.install=${CATALINA_BASE}

#Fathom log file
psc.log.default=${CATALINA_BASE}/logs/fathom.log

#Fathom exception log file
psc.log.exceptions=${CATALINA_BASE}/logs/exceptions.log

#logging level for Fathom messages
LogLevel=3

#Local directory for Fathom configuration database
# configuration database will be created in a subdirectory of the specified directory
psc.oem.configdb.dir=${CATALINA_BASE}/work/

#Local directory for Fathom cache database
# graph cache database will be created in a subdirectory of the specified directory
psc.oem.activitydb.dir=${CATALINA_BASE}/work/

#User file location for Fathom logins
psc.oem.realm.properties=${CATALINA_BASE}/conf/fathomRealm.properties

#Permission policy file for Fathom user roles
psc.oem.realm.policy=${CATALINA_BASE}/conf/fathomRealm.policy

#Default location for Fathom trend database
psc.oem.fathom.trend=${CATALINA_BASE}/work/fathomdb/fathom.db

#OrientDB tuning parameters for cache and configuration database
storage.record.lockTimeout=75000

# max segment size for write ahead log (BI file equivalent) for cache and configuration databases
storage.wal.maxSegmentSize=32

# max size in MB of write ahead log for cache and configuration databases (value applies separately to each)
storage.wal.maxSize=256

# amount of memory in MB to allocate for cache and configuration databases
storage.diskCache.bufferSize=384

# controls memory allocation and pooling for lock manager pool
environment.lockManager.concurrency.level=8

# controls the number of files created per cluster for cache and configuration databases
class.minimumClusters=1

# Disable directIO access.  OrientDB use of Direct IO on Linux fails if the file system is on an NFS mount. This disables
# direct IO which is a bit sloewr, but prevents the file open problems.  This can safely be enabled
# on Windows, and non-NFS mounted drives on *nix.
storage.wal.allowDirectIO=false

#OpenEdge Management report generation directory. If not provided this uses $OEMWRKDIR/reports directory
#You may override the report directory by specifying an alternate value here
#psc.oem.reports=

# ensure snmp4j sends logging information to log4j
snmp4j.LogFactory=org.snmp4j.log.Log4jLogFactory

# Configure SLF4J compatible logger for OEM
psc.log.factory=com.progress.fathom.logging.LogSystemBridgeToSlf4JFactory

# Logback configuration file
logback.configurationFile=${CATALINA_BASE}/conf/logging.xml

fathom.properties

In OpenEdge 12, the fathom.properties file is moved from the <DLC>/properties directory to the <OEMgmt>/conf directory. In addition, some of the properties defined in this file are not used in Release 12. Some properties may still be viewable, but you must update the location in which they are stored if you want to retain them.

The following table lists the properties that are affected by the transition to Tomcat. Any properties not listed in this table remain unchanged in Release 12.

Table 1. Property changes
Property Name Description
WebServer.HttpEnabled This property remains in the user interface, and you can set it by using TCMAN to enable and disable the HTTP connector.
WebServer.HttpPort This property remains in the user interface and is stored in the <instance>/conf/catalina.properties file as thepsc.as.http.port property.
WebServer.HttpsEnabled This property remains in the user interface, and you can set it using TCMAN to enable and disable the HTTP connector.
WebServer.HttpsPort This property remains in the user interface and is stored in the <instance>/conf/catalina.properties file as the psc.as.https.port property.
SSLIdentityAlias This property remains in the user interface and is stored in the <instance>/conf/catalina.properties file as the psc.as.https.keyalias property.
SSLIdentityAliasPassphrase This property remains in the user interface and is stored in the <instance>/conf/catalina.properties file as the psc.as.https.keypass property.
SSLIdentityKeystorePathname