Upgrading the Akula Server
This document describes how to manually upgrade an Akula Server installation by using files downloaded from the Verivo DevCenter Downloads page (you must log in to access this page).
The Akula Server requires a database to store the configuration and run time information used by the server. The Akula Server includes an internal Apache Derby database that you can use to get up and running quickly in a development environment. While the Derby database is adequate for development work, it is not intended to function in a deployment environment. For deployment, Verivo recommends that you configure the Akula Server to use an external enterprise-class database, such as Microsoft SQL Server, MySQL, or Oracle.
The primary task for upgrading the Akula Server is to upgrade the database. On start up, the akula.war file automatically upgrades the database that it uses for configuration and run-time information. Therefore, most of the steps in the procedure below describe how to edit configuration files in the
AKULA_HOME directory to ensure that the akula.war file has proper access to the database to perform the upgrade.
Akula Server upgrade procedure
Back up the existing database used to store the configuration and run time information used by the Akula Server. This is the database specified in the
The akula.war file automatically upgrades its database when you first start it. Therefore, ensure that the username specified in the JNDI database resource definition has permissions to the database so that the akula.war file can modify the database tables and table schemas.
Edit the property files to add definitions to support features included in this version of Akula. The location and name of the file is:
AKULA_HOME/global/properties.xml. Add the following change:
This version of Akula includes a new app scope performance monitoring and reporting feature. To prevent performance degradation due to monitoring activities, the 3.0.0 server utilizes new queues to store data until they can be written to the Akula database. To support these queues three new properties are required as well as one new property for specifying how many days worth of data to preserve at any one time.
The number of rollup days should be set to 30 or less. The higher the number, the larger your Akula database will grow to maintain performance data. Also, with higher numbers come increasing wait times within the Web Management Console.
Ensure the required queues get started when your application server starts. For example, ensure the
AKULA_HOME/global/context.propertiesfile contains the following line.
Stop your application server and overwrite your existing akula.war with the new akula.war from the new release
Replace the old akz-protocol-handler-2.5.0.jar file with the new akz-protocol-handler-3.0.0.jar found in the Akula Server SDK
Update your classpath environment variables to reflect the new akz-protocol-handler. More information on setting classpaths for the akz-protocol-handler are available in the new installation setup instructions.
Remove application server temporary and working directories. For example, if using Tomcat, the following Tomcat folders should be deleted.
- Start your application server