Heads up! These docs are for Portofino 3, which is a legacy product. Check out Portofino 4!

In the basic configuration we suggested writing the configuration file to CATALINA_HOME/common/classes. This location is convenient because, keeping the configuration file separate from the installation, it is easier to upgrade Potofino. 

However, CATALINA_HOME/common/classes is visibile to all applications running within the application server. Now, if you have two instances of Portofino running on the same application server (of course under different contexts, e.g., "/app1" and "/app2"), both instances would see the same portofino-custom.properties file and both would use exactly the same configurations. This is clearly not desirable. 

To run multiple instances of Portofino correctly, you must provide each instance with its own portofino-custom.properties file. The correct location is


where APPLICATION_HOME is the deployment directory of the instance. 

Caution during upgrades

When you store the configuration file as described above, make sure you back it up before upgrading Portofino, as the upgrade process may delete or overwrite the file.

Further readings

For more information, see the tutorial on Deploying multiple Portofino instances from a single war.

Previous: Optimizing the configuration 

Next: Populating the database manually