1.Set Java options prior to starting the application server. Use the EXPORT command or some equivalent method to set the options (all on one command line):

set JAVA_OPTS="-Xms2048m -Xmx2048m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+HeapDumpOnOutOfMemoryError -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" -Dcollaborati.connection.readTimeout=<number of minutes>

The last option relates to Collaborati. Default value is 60 minutes and it is rare that you would need to change it. If you anticipate dealing with unusually large volumes of data through Collaborati, you should set this option to a larger value, to avoid timeouts during synchronization. An example of large volumes would be timekeeper counts of 2000 or more.

2. Use JDK version 1.8 or higher.

3. Use the default Java security policy.

1.Make an adjustment to file teamconnect.properties. Extract the TeamConnect .war file from the TeamConnect .ear file, explode the .war file, and locate teamconnect.properties. Edit the file to remove this line:

## appserver.datasourcePrefix=java:comp/env/

2.Repackage the teamconnect.properties file into the .war file. Repackage the .war file into the TeamConnect .ear file.

3.Copy the TeamConnect .ear file into the /deploy folder of the production server.