While 17.4 continues to support Glassfish (4.1.2 and later), support for Glassfish will be removed in a future release. Use of Oracle WebLogic, ORDS Standalone Mode or Apache Tomcat is recommended instead.
Install on a New Server
One caveat to this approach is if you are upgrading ORDS at the same time as moving to Tomcat. In this case, you can complete the Tomcat install on the new server but won't be able to complete the ORDS install until your final cutover. This is because the install of a new version of ORDS upgrades objects on the database. You should not have two servers using different versions of ORDS hitting the same database.
Don't forget to locate the server as close as possible to the database server. Distance between your app server and your database will kill performance.
Take some time before you start the install and make sure you have the following information at hand:
- Information from all the databases serviced by your current ORDS server:
- Passwords for the ORDS database accounts in all of your databases (ORDS_PUBLIC_USER, ORDS_PUBLIC_USER, APEX_LISTENER and APEX_REST_PUBLIC_USER).
- The SYS password.
- Database server names, ports and SIDs.
- ORDS Configuration files from your old install. Also, take note of your jdbc connection pool settings, specifically (jdbc.InitialLimit, jdbc.MinLimit and jdbc.MaxLimit).
- A detailed run book which documents the steps you need to take to complete the install. You will be refining this before you do the PROD install, but it's good to have a starting point before you start DEV/TEST.
- Identify and download the latest stable versions of the software you will need:
- Java JDK
- Run load tests on the old environment to get a performance benchmark.
Get on the Latest Version of ORDS
Revisit Your ORDS Settings
In addition, if you are installing a new version of ORDS, make sure you are aware of any new settings that have been introduced. Make sure you are not running on default values.
Revisit Your Server Directory Structure
Don't Overcomplicate It
Also, don't just convert your old GlassFish settings to their Tomcat equivalents. This is especially true if you did decide to move to a new server. If the new server has more memory then you can dedicate some more memory to the JVM. If the new server has an extra CPU then you can bump up the 'acceptorThreadCount' to increase throughput.
Re-Run Your Load Tests
Keep tuning your Tomcat and ORDS configuration and re-running your load tests until you get the performance you need.
Don't wait until you are forced to make the move, plan and execute your migration now, while you are able to decide the when.