Configuring Tomcat Memory and Classpath Settings
This step is mandatory when you upgrade from iObeya 4.20 to iObeya 4.31 or when you upgrade Tomcat (changing default configurations).
The latest version of iObeya requires to:
review Tomcat memory settings.
Procedures and guidelines for configuring memory and classpath settings are fully documented in our installation guide.
install and use jemalloc to optimize memory allocation if you only upgrade iObeya on a Linux environment (or Unix-based environment).
Procedures for installing and using jemalloc are fully documented in our installation guide.
You need to ensure that your Tomcat is configured following our recommendations before moving to the next step.
Upgrading your Facade API
If the Facade API has been configured and installed on your on-premises environment since version 4.36, you need to update it each time a new version on-prem is released.
Since iObeya 4.36, the Facade API and Services Hub are available for on-demand installation in your on-premises environment. These components need to be configured and installed with the help of our Support team.
The Facade API simplifies integrations with iObeya. Find out more here.
The Services Hub introduces new capabilities to enhance your experience. Find out more here.
Restarting iObeya
Process time of the migration jobs can differ based on the size of your iObeya platform.
To finalize the upgrade of your iObeya platform:
Start Tomcat.
The automated job MandatoryMigrationChecksJob will be automatically launched. You cannot access iObeya web application during this process.
When the first job is completed, iObeya is accessible and the job LongRunMigrationChecksJob is launched.
Connect to the administration platform and check the status of these 2 jobs.
The iObeya web application is accessible and you can use it while the job LongRunMigrationChecksJob runs.
It finalizes applying the required changes added in the new version.
You can also check the status of these two jobs by monitoring the iObeya logs files (app.log and error.log).