Table of Contents
It is a best practice to back up your AnthillPro server before upgrading. The minimum suggested backup is to backup the database. If you are using the embedded Apache Derby database, then a backup can be done through the AnthillPro Web UI on the System tab by following the Backup Settings link under the Server menu. Click the Backup Now button. The backup will take a few moments.
To backup other databases, please follow the procedures outlined by the respective database vendor.
Before running the upgrade script, you should shut down the server. To perform an upgrade, follow the installation instructions. See Installing AnthillPro.
| When using SSL, you need to turn it on for both the server and the agent -- otherwise the agents will not be able to connect to the server. If you are using the agent relay, ensure that SSL is turned on for all three components: server, agent, and agent relay. This rule also applies if using mutual authentication. |
When asked for the directory to install the server, enter the existing server directory.
To upgrade the AnthillPro Server:
Follow steps 1 to 5 of the installation process. See Choosing a Download to begin.
When prompted, give the current AnthillPro server directory. For example: C:\Program Files\anthill3\server (Windows) or /opt/anthill3/server (Linux).
The installer will ask you if you want to upgrade the existing server. Type Yes to upgrade or No to exit the installer. Once the upgrade is under way, the installer will use most of your existing values.
Provide the Home directory of the JRE/JDK used to run the server, if different from the original.
If the AnthillPro server is installed as a Windows service: Input the unique name in the dialog box and click OK to stop and remove service (Windows service will be recreated, if desired, at the end of the upgrade process).
If more than one instance of the AnthillPro server is installed as a Windows service, make sure the correct service name is entered.
See also Install as Windows Service.
Once the installer is complete, you can start the server.
You should upgrade the server before upgrading any agents. AnthillPro supports an auto-upgrade feature to upgrade running agents (see note below if upgrading from version 3.5 to 3.6).
The upgrade can be started in the AnthillPro Web UI under the Agents link on the System tab under the Environment menu. Click the Upgrade Agents button to begin the auto-upgrade process. All agents that are not the correct version and are online will be upgraded. The upgrade can take some time, so refresh the page to view progress.
If you need to manually upgrade an agent, stop the agent and follow the same instructions as an installation. When asked for the directory to install the agent, enter the existing agent directory.
Shut down the server and agent.
Follow steps 1 to 4 of the installation process. See Choosing a Download.
Give the Directory where the AnthillPro agent should be upgraded.
Input Y to upgrade an existing AnthillPro agent.
Give the home directory of the JRE/JDK used to run the agent.
Relay connection. Enter the default N if not using Urbancode's Distributed Servers product, available under separate license. If using Distributed Servers, see Installing Distributed Servers before continuing.
If you are interested in using the Agent Relay for agent-server
communication, contact info@urbancode.com.
Determine if internal communication should use SSL. Default is N.
| When using SSL, you need to turn it on for both the server and the agent -- otherwise the agents will not be able to connect to the server. If you are using the agent relay, ensure that SSL is turned on for all three components: server, agent, and agent relay. This rule also applies if using mutual authentication. |
If using SSL, determine if communication should be mutually authenticated. Default is N.
If the AnthillPro agent is installed as a Windows service: Input the unique name in the dialog box and click OK to stop and remove service (Windows service will be recreated, if desired, at the end of the upgrade process).
If more than one AnthillPro agent is installed as a Windows service, make sure the correct service name is entered.
See also Install Agent as Windows Service.
Beginning with version 3.6.3, AnthillPro provides an upgrade path for the Agent Relay. If you are using an older version (i.e., 3.6.2 or older), you will need to install version 3.6.3 in order to perform future upgrades.
| When using SSL, you need to turn it on for both the server and the agent -- otherwise the agents will not be able to connect to the server. If you are using the agent relay, ensure that SSL is turned on for all three components: server, agent, and agent relay. This rule also applies if using mutual authentication. |
Before performing the upgrade, stop the Agent Relay and backup the Agent Relay directory.
Run the install script in the Agent Relay installation package.
When asked for the directory, give the directory the old version is installed in.
The installer will ask you if you want to upgrade. Answer Y.
Follow the instructions for an installation.
See also Upgrade Distributed Servers and Installing Distributed Servers.
Beginning with version 3.6.3, AnthillPro provides an upgrade path for Distributed Servers. If you are using an older version (i.e., 3.6.2 or older), you will need to install version 3.6.3 in order to perform future upgrades.
Before performing the upgrade, stop Distributed Servers and backup the Distributed Servers directory.
Run the install script in the Distributed Servers installation package.
When asked for the directory, give the directory the old version is installed in.
The installer will ask you if you want to upgrade. Answer Y.
Follow the instructions for an installation.
See also Upgrade Agent Relay and Installing Distributed Servers.
We have seen some scalability issues with the embedded Apache Derby database. If you experience slowness in the AnthillPro Web UI or if the server process is taking up too much memory, it is likely time to migrate to a different database.
The AnthillPro command line installers include a database migration utility that exports your existing database data and imports it into another supported database. The following alternative databases are supported:
Oracle.
Use the JDBC driver for Oracle 10.2 or higher, regardless of what version of the database is used.
MySQL with InnoDB storage (works with 4.1.22 and later).
If using MySQL 5, use the 5.0.8 driver version. The 5.1 version has some bugs that will cause the AnthillPro server to throw an error. If you are using the 5.1 version, switch the driver jar file in the server's lib/ext directory and then restart.
It is also recommended that the InnoDB storage engine be used.
Microsoft SQL Server.
See the Installing AnthillPro for migrating server database.
These requirements apply if you want to use a database other than Apache Derby:
You must use one of the command line installers for installation.
You need to download the appropriate JDBC driver file for your database. These are typically downloaded from the database vendor.
You need to create an empty database for AnthillPro to use with a dedicated user.
The database migration should only be run after you have completed an upgrade to the version you are using to migrate. So if you download a new version and want to migrate, you must first do an upgrade.
To migrate the AnthillPro database:
Shut down the server.
Download the anthill3-<version>.zip file.
Expand the zip file using a tool like WinZip. Expanding will create an anthill3-install directory.
Open the anthill3-install directory created in the previous step in Windows.
Copy the JDBC driver file(s) of the database you are migrating to into the anthill3-install\lib\ext directory.
Run the migration script migrate-db.bat.
If the AnthillPro server is installed as a Windows service: Input the unique name in the dialog box and click OK to stop and remove service (Windows service may be recreated, if desired, in step 10).
If more than one AnthillPro server is installed as a Windows service, make sure the correct service name is entered.
Provide the directory where the AnthillPro server is installed.
Input Y to upgrade the existing server.
Provide the following:
Database type AnthillPro should migrate to [derby, oracle, mysql].
Database driver. See your database vendor documentation for the JDBC driver class to use.
Database connection string. See your database vendor documentation on the format of this value.
Database user name.
Database password.
Follow the remainder of step 7 through step 10 of the Windows installation process. See Windows Server Installation from zip File.
To migrate the AnthillPro database, follow the steps below:
Shut down the server.
Download the anthill3-<version>.tar.gz file.
Open a UNIX shell to the directory containing the above downloaded file.
Extract the downloaded
tar.gz file. Type tar -zxf
anthill3-<version>.tar.gz.
On some installations of Solaris and HP-UX the default tar
command will not properly handle our tar files. You may need to use
\ install GNU tar. When installing AnthillPro on
Solaris, it is recommended to use korn shell (ksh).
cd anthill3-install.
Copy the JDBC driver file(s) of the database you are migrating to into the anthill3-install/lib/ext directory.
Run the migration script ./migrate-db.sh.
During the migration you will be prompted for the following information:
Directory where the AnthillPro server is installed.
Database type AnthillPro
should migrate to [derby, oracle, mysql].
Database driver. See your database vendor documentation for the JDBC driver class to use.
Database connection string. See your database vendor documentation on the format of this value.
Database user name.
Database password.