Upgrading

From ControlTier

Jump to: navigation, search

These are the steps needed to upgrade to a new ControlTier point release.

Upgrade procedure

  1. Shut down all ControlTier processes. Things will break if you do not shut all the processes down.
  2. Run the installer against both server and clients.
  3. Start the server. Watch the logs and make sure the server started properly. You can also use jetty.sh check (Check status)
  4. Locate the controltier-seed.jar archive from the installer directory: (e.g. ControlTier-3.6.1/pkgs/ctl-3.6.1/lib/extensions/commander/jars/core-seed-3.6.1.jar)
  5. Load the new seed jar from the installer using either ProjectBuilder or Workbench for each project:
    • Option 1: ProjectBuilder: Run the load-library command:
      ctl -m ProjectBuilder -c load-library -- -jar /path/to/core-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".
  6. If you are using the elements library, also similarly load the new seed for that library (e.g. ControlTier-3.6.1/pkgs/ctl-3.6.1/lib/extensions/commander/jars/elements-seed-3.6.1.jar).
  7. Replace the old seed in the WebDAV with the new one:
    ctl -p anyProject -m davutil -c put -- -file /path/to/core-seed-3.x.x.jar -overwrite -url dav://seeds/core-seed.jar
  8. On all clients run ctl-project "install" action. Do it via ctl-exec:
    • ctl-exec -p project -- ctl-project -p project -a install
    • Optionally, you can do a clean re-creation of the CTL projects running through ctl-project (remove, create, install) to get a new baseline.
Personal tools
Namespaces
Variants
Actions
Navigation
Communication
Development
Toolbox
Print/export