Upgrade Guide

From DOC

Jump to: navigation, search

Contents

Overview

Please note that this upgrade guide does not apply to upgrades from beta4 to Tolven RC1. It applies to those who are already on Tolven RC1 but have an earlier installation kit without some later minor bug fixes. There should be no need to upgrade, unless the fixes are required, and the upgrade process is quite simple. Most fixes will be noted in the version notes of plugin org.tolven.assembler.pluginframework

The key points to note are that you probably already have a tolven-config directory and a directory called tolven-RC1 which both represent the default installation directory names.

Kit Installation

The simplest approach is to rename your current tolven-RC1 directory, and unzip the new one in its place. Next execute the following command in the bin directory: On Windows:

cd <install-dir>\bin
install

On Linux:

cd <install-dir>/bin
./install.sh

This install command will ask where the <config-dir> is, unless you happen to have the value set as an environment variable (see Installation Guide).

Kit upgrade is now complete, as as a sanity check, you can execute the following command: On Windows:

cd <install-dir>\bin
checkIntegrity

On Linux:

cd <install-dir>/bin
./checkIntegrity.sh

Upgrades To plugins.xml

Every effort is made to ensure that whatever <root> plugins are currently in <config-dir>/plugins.xml, will be valid for all such simple upgrades. Occasionally, there could be a change which does require attention. The latest plugins.xml files are always located in the <install-dir>/examples/rootPlugin directory, and should be close to what exists in the current <config-dir>/plugins.xml of previous versions.

Version 0.0.1

There were no notes for kits prior to version 0.0.1 of the kit. To determine the kit version execute:

tpf -version

If the option is not recognized, then the kit is prior to v 0.0.1.

Detailed fixes can be located here: org.tolven.assembler.pluginframework

checkIntegrity

The following command will do nothing but start up the Tolven Plugin Framework, at which time any major inconsistencies will become obvious:

On Windows:

cd <install-dir>\bin
checkIntegrity

On Linux:

cd <install-dir>/bin
./checkIntegrity.sh

New Root Plugins Of Interest

org.tolven.configurationmgr (Replacement for org.tolven.command.gui.cm)

org.tolven.appservermgr

org.tolven.appserverproperties (Replacement for org.tolven.config.appserverproperties)

org.tolven.ldapmgr

org.tolven.postgresqlmgr

org.tolven.oraclemgr

org.tolven.jbossmgr

org.tolven.passwordrecovery

org.tolven.deploy.pluginzip (For development environments)

Personal tools