From ControlTier
These are the steps needed to upgrade to a new ControlTier point release, for example from 3.4.6 to 3.4.8.
Upgrade procedure
- Shut down all ControlTier processes. Things will break if you do not shut all the processes down.
- Run the installer against both server and clients.
- Start the server. Watch the logs and make sure the server started properly. You can also use
jetty.sh check (Check status)
- Locate the controltier-seed.jar archive from the installer directory: (e.g.
ControlTier-3.4.5/pkgs/ctl-1.4.5/lib/extensions/commander/jars/controltier-seed-3.4.5.jar)
- Load the new seed jar from the installer using either ProjectBuilder or Workbench into each project:
- Option 1: ProjectBuilder: Run the load-library command:
ctl -m ProjectBuilder -c load-library -- -jar /path/to/controltier-seed-3.x.x.jar
OR
- Option 2: Workbench: Go to the Admin page (eg, http://strongbad:8080/itnav/do/menu/Admin) and press the "Import Seed" button and upload the jar file. Check the box "Restage all submodules of imported modules after import".
- Replace the old seed in the WebDAV with the new one:
ctl -p anyProject -m davutil -c put -- -file /path/to/controltier-seed-3.x.x.jar -overwrite -url dav://seeds/controltier-seed.jar
- On all clients run ctl-depot "install" action. Do it via ctl-exec:
-
ctl-exec -p project -- ctl-depot -p project -a install
- Optionally, you can do a clean re-creation of the CTL depots running through ctl-depot (remove, create, install) to get a new baseline.
| User Guide |
|---|
| | Introduction | | | | Projects | | | | Command dispatcher | | | | Packages | | | | Event logging | | | | Resource model | | | | Workflows | |
|
| Installation |
|---|
| | Requirements | | | | Installers | | | | Configuration | | | | Server | |
|
| Examples |
|---|
| | Scripting | | | | Services | | | | Builders | | | | J2EE | |
|
| Reference |
|---|
| | Ant | | | | Command-line utilities | | | | XML | | | | APIs | |
|