Page History

Starting with opCharts 2.0 and opEvents 1.2, all Opmantek products All Opmantek products (except opFlow 2.x) ship with our new interactive installer program which greatly simplifies installations and upgrades.

This  document explains the most essential installer features.

Starting the installer

The installer needs to run with root privileges.

Unpacking your product tarball creates a new directory called <Product Name>-<Version>/, e.g. opEvents-1.2.0/. Simply change into that directory, and then invoke the installer program:

...

Opmantek Applications Download Formats

In the past our applications were provided in the form of a compressed tar file, which required some manual steps for unpacking and installer invocation.
As of February 2016 we've switched to a self-extracting download format which make this aspect much more user-friendly.

When you download an Opmantek Application, the file will be called <product name>-<version>.run and your browser will likely prompt you regarding what to do with this '.run' file; you should tell it to Save the file. If you are installing the application onto a different system than the one where you downloaded the file, you'll have to use scp or some other file transfer method of your choice to transfer the .run file to the target system.

Starting the Installer

Starting the new self-extracting installer is trivial: you simply tell your shell to run it.

Assuming your downloaded file is called opProduct-version.run, you would do one of the following:

1. The simplest way to achieve this is to type "sh ./opProduct-version.run"
2. You can also modify the permissions of the .run file to indicate that it is executable, then start it directly
   To do so, you'd run "chmod u+x ./opProduct-version.run" followed by "./opProduct-version.run"

The installer will first run an archive integrity check, decompress the archive, then start the interactive phase of the installation.

Please note that the installer needs to run with root privileges, and will terminate with an error message if this requirement is not met.

Available Options

• You can see an overview of the available options related  to the self-extracting aspect when you run the file with --help.
  • --keep ensures the unpacked data left behind (in the opProduct-version directory) after the interactive installer component has finished.
  • --noexec causes no interactive installer component to be run.
    (The combination of --noexec and --keep provides the equivalent of unpacking the tar files provided with earlier releases.)
• An options for the interactive installer component must follow after a "--" delimiting argument.
  
  • If you want to perform a simulation run of the installation, use the -n option - the installer will only print what it would do, what files it would copy and so on, but will not perform any of these steps.

• • By default the installer is interactive and will prompt you for decisions and confirmations; If you want to run it in automatic batch mode, use the -y option. In this case all dialogs and prompts are automatically answered 'y'.
  • If you wanted to install the product into a non-standard directory, you can pass the argument -t <targetdir> to the installer component.

Logs and Backups

The installer saves a log of all actions taken, files copied etc. in the installation directory as install.log, ie. normally it'll be in /usr/local/omk/install.log. Subsequent upgrades or installations of other Opmantek products will add to that logfile, so you may very well want to remove or clear the install.log file before upgrading or adding extra software.

...

Please feel free to submit comment here or email us with your questions!