System Setup
Prerequisites
System Specification recommendations (Running owl-web and owl-core):
Operating System
RHEL6+ RHEL7+
Centos6+ Centos 7+
Linux version 4.14.62-65.117.amzn1.x86_64 (mockbuild@gobi-build-60009) (gcc version 7.2.1 20170915 (Red Hat 7.2.1-2) (GCC)) #1 SMP Fri Aug 10 20:03:52 UTC 2018
SUSE 12+
Hardware Based on Role (standalone, distributed, or fully-distributed)
Java Version
Oracle JDK version "1.8.0_152" +
Open JDK version 1.8.0+
Client Browser
Chrome 70.0.3538.102+
Firefox - 52.8.0+
Safari Version 12.0.1+
Support of IE 11.0+
Postgres Version
Owl come prepackaged with version 11.4 of postgres
Version 9.6.5 and above is supported if wanting to use an external metastore
User Privileges:
Installation is completed via tarball
User needs to be able to create directories, launch scripts, and start processes (java processes)
SUDO is not required
ULIMIT settings of 4096 or higher (see below)
All owl services typically consume about 428 threads.
During each owlcheck about 400 additional threads are consumed.
Thus 4096 threads can allow for about 9 concurrent owlcheck jobs (on a standalone install). If more are needed plan accordingly.
Default Ports used by Owl
2424 - OrientDB
5432 - Postgres
9000 – Owl-web
9091 – zeppelin
Planning the installation
It is alway best to consult the field team from Owl for more information about what options make the most sense for your environment.
Determine how we are planning to install Owl (standalone or distributed) as shown in Owl-Analytics Architecture section
Plan infrastructure, scale, and HA
Validate your system prereqs
Obtain the Packages from Owl
Installation Packages/Files (BOM)
demoscripts.tar.gz
log4j*
orientdb.tar.gz
owlcheck
owl-core-2.1.0-jar-with-dependencies.jar
owl-webapp-2.1.0.jar
owl-agent-2.1.0.jar
setup.sh
zeppelin-0.8.0-bin-all.tgz
owl-postgres.tar.gz
notebooks.tar.gz
owlmanage.sh
Last updated