This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
install:guides:linux [2016/06/28 22:38] 127.0.0.1 external edit |
install:guides:linux [2026/07/25 14:23] (current) doc |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| # wget http://www.omnidex.com/downloads/omnidex/Linux/el5/omnidex.repo -P /etc/yum.repos.d | # wget http://www.omnidex.com/downloads/omnidex/Linux/el5/omnidex.repo -P /etc/yum.repos.d | ||
| + | |||
| + | |||
| + | For SuSE versions: | ||
| + | |||
| + | # wget http://www.omnidex.com/downloads/omnidex/Linux/el6/omnidex.repo -P /etc/zypp/repos.d | ||
| + | | ||
| == 3. Choose whether to use the latest stable version or the current development version == | == 3. Choose whether to use the latest stable version or the current development version == | ||
| Line 49: | Line 55: | ||
| == 3. Install Omnidex == | == 3. Install Omnidex == | ||
| + | |||
| + | For Red Hat or CentOS versions: | ||
| Once the Omnidex repository is copied, Omnidex can be automatically installed using the command: | Once the Omnidex repository is copied, Omnidex can be automatically installed using the command: | ||
| Line 71: | Line 79: | ||
| # yum remove omnidex | # yum remove omnidex | ||
| # yum clean metadata | # yum clean metadata | ||
| + | |||
| + | For SuSE versions: | ||
| + | |||
| + | Once the Omnidex repository is copied, Omnidex can be automatically installed using the command: | ||
| + | |||
| + | # zypper install omnidex | ||
| + | | ||
| + | You can update an existing version of Omnidex using the command: | ||
| + | |||
| + | # zypper update omnidex | ||
| + | |||
| + | You can remove an existing version of Omnidex using the command: | ||
| + | |||
| + | # zypper remove omnidex | ||
| + | |||
| + | If your repository is set to [omnidex-arch] as described above, you can view all available versions and install a particular version using the commands: | ||
| + | |||
| + | # zypper packages omnidex | ||
| + | # zypper install omnidex-<version> (eg. zypper install omnidex-5.3-08D.el6.linux) | ||
| + | |||
| + | Note: To install an earlier version of Omnidex than the version currently installed, first remove Omnidex and then clear the yum cache. | ||
| + | |||
| + | # zypper remove omnidex | ||
| + | # zypper clean | ||
| === Manual installation === | === Manual installation === | ||
| Line 106: | Line 138: | ||
| <code> | <code> | ||
| - | export LD_LIBRARY_PATH="opt/omnidex/lib:$LD_LIBRARY_PATH" | ||
| export CLASSPATH="/opt/omnidex/lib/Omnidex.jar:$CLASSPATH" | export CLASSPATH="/opt/omnidex/lib/Omnidex.jar:$CLASSPATH" | ||
| + | export LD_LIBRARY_PATH="opt/omnidex/lib:$LD_LIBRARY_PATH" | ||
| + | export LD_PRELOAD="<see below>" | ||
| </code> | </code> | ||
| To use OdxSQL as a Java client for testing purposes, you also must add the directory containing libjvm.so to LD_LIBRARY_PATH. | To use OdxSQL as a Java client for testing purposes, you also must add the directory containing libjvm.so to LD_LIBRARY_PATH. | ||
| + | |||
| + | Additionally, it is recommended to set LD_PRELOAD to Java's libjsig.so library due to known compatibility issues with Java's signal handling with other applications, including Omnidex. This is necessary to avoid unexplained aborts of the JVM when connecting to Omnidex processes, such as when setting up application pooling using DBCP. Instructions for setting this variable can be found at the following link: | ||
| + | |||
| + | https://docs.oracle.com/javase/8/docs/technotes/guides/vm/signal-chaining.html | ||
| + | |||
| === Install Omnidex to run as a service (optional) === | === Install Omnidex to run as a service (optional) === | ||
| - | Omnidex is usually run as a service, though it can be run in a console window as well. The files needed to set up Omnidex as a service are automatically placed in /etc/init.d upon installation. | + | Omnidex is usually run as a service, though it can be run in a console window as well. The files needed to set up Omnidex as a service are automatically placed in /etc/systemd/system upon installation. |
| The following commands are available to manage the Omnidex service: | The following commands are available to manage the Omnidex service: | ||
| <code> | <code> | ||
| - | service omnidexd start (start omnidex as a service) | + | systemctl start omnidex (start omnidex as a service) |
| - | service omnidexd stop (stop omnidex as a service) | + | systemctl stop omnidex (stop omnidex as a service) |
| - | service omnidexd restart (restart omnidex as a service) | + | systemctl restart omnidex (restart omnidex as a service) |
| - | service omnidexd status (check if omnidex is running as a service) | + | systemctl status omnidex (check if omnidex is running as a service) |
| </code> | </code> | ||
| Line 128: | Line 166: | ||
| <code> | <code> | ||
| - | chkconfig --add omnidexd (add omnidex service to startup) | + | systemctl enable omnidex (add omnidex service to startup) |
| - | chkconfig --del omnidexd (remove omnidex service from startup) | + | systemctl disable omnidex (remove omnidex service from startup) |
| - | chkconfig --list omnidexd (check if omnidex service is in the startup) | + | systemctl is-enabled omnidex (check if omnidex service is in the startup) |
| </code> | </code> | ||