Incorta Analytics

Installation Guide
Reviewed December 6, 2017
INCORTA ANALYTICS INSTALLATION GUIDE, Reviewed December 6th, 2017

COPYRIGHT © 2017, INCORTA AND/OR ITS AFFILIATES. ALL RIGHTS RESERVED.

INCORTA IS A REGISTERED TRADEMARK OF INCORTA INCORPORATION AND/OR ITS

AFFILIATES. OTHER NAMES MAY BE TRADEMARKS OF THEIR RESPECTIVE OWNERS.

This software and related documentation are provided under a license agreement containing
restrictions on use and disclosure and are protected by intellectual property laws. Except
as expressly permitted in your license agreement or allowed by law, you may not use, copy,
reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish
or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited. The
information contained herein is subject to change without notice and is not warranted to be
error-free. If you find any errors, please report them to us in writing. If this software or related
documentation is delivered to the U.S. government or anyone licensing it on behalf of the U.S.
government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S.
government customers are "commercial computer software" or "commercial technical data"
pursuant to the applicable federal acquisition regulation and agency-specific supplemental
regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject
to the restrictions and license terms set forth in the applicable government contract, and, to the
extent applicable by the terms of the government contract, the additional rights set forth in far
52.227-19, Commercial computer software license (December 2007).

This software is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including
applications, which may create a risk of personal injury. If you use this software in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy
and other measures to ensure the safe use of this software. Incorta corporation and its affiliates
disclaim any liability for any damages caused by use of this software in dangerous applications.

This software and documentation may provide access to or information on content, products
and services from third parties. Incorta corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third party content, products and
services. Incorta corporation and its affiliates will not be responsible for any loss, costs, or damages
incurred due to your access to or use of third party content, products or services.

Author: Ahmed H. Elkady.

Contributors: Matthew Halliday, Tamer Mahfouz, Hichem Sellami, Dave Wrubel, Mohamed Obide,
Klaus Fabian, Mohamed El Prince, Ahmed Eltanahy.
Contents

Contents  3
Introduction  4
Pre-Installation Requirements  5
System Requirements  5
Memory Sizing & Disk Utilization  5
Database-Related Requirements  6
Java Requirement  7
Ports Requirements  8
Font Requirements  12
Libraries Requirements  12
Configuring two database users  14
Details  14
For Fresh Installations  14
For existing installations  15
Installing Incorta Analytics  16
Installation Steps  17
Upgrading Incorta Analytics  34
Before you upgrade...  34
Upgrading  34
Uninstalling Incorta Analytics  36
Before you uninstall...  36

3 | Incorta Inc. Copyright © 2017

Introduction 1

Welcome to the Incorta Analytics Installation guide. This guide is divided into
the following sections:
Pre-Installation Requirements
This section contains information about the minimum requirements for your
system to install Incorta Analytics successfully.
Installing Incorta Analytics
This section contains the different options available for installing Incorta
Analytics. It also includes the steps of the installation process.
Upgrading
Read this section if you already have an Incorta Analytics installation and
you would like to upgrade the version installed on your system.It contains
information about the steps of the upgrade process.
Uninstalling Incorta Analytics
This section contains instructions to uninstall an existing Incorta Analytics
installation.

4 | Incorta Inc. Copyright © 2017

Pre-Installation Requirements 2

System Requirements
1. Incorta Analytics can be installed on the following operating systems:
• Linux 64-bit.
• Mac OS 10.9 and 10.10.
• Windows 64-bit.
2. At least 16 GB RAM, depending on the amount of your data.

Memory Sizing & Disk Utilization

Memory Requirements
Incorta Analytics compresses the data on ingestion. Typical compression rates
are between 1-3X. Compression varies depending on the cardinality of the data.
In addition to the data memory requirements Incorta Analytics also requires
30% of working memory and indices. With Oracle E-Business Suite data, we
recommend a conservative compression rate of 1.5X, which includes all the
required memory for running Incorta Analytics.
The following table provides a sample of an Oracle E-Business Suite
environment, along with the sizing information for the Incorta Analytics
E-Business Suite Accelerators. Note that only columns with analytical value get
imported, and not the full tables.

Source Size Incorta Size

Table Name (GB) Rows (M)
(GB)

RA_CUSTOMER_TRX_ALL 2.5 1.4 13

RA_CUSTOMER_TRX_LINES_ALL 71 23.9 471

RA_CUST_TRX_LINE_GL_DIST_ALL 25 20.0 300

HZ_PARTIES 14 7.3 90

5 | Incorta Inc. Copyright © 2017

 Disk Requirements
Incorta Analytics stores data on disk in a compressed format with compression
rates between 1-10X, and 2x for EBS data. Incorta Analytics High Availability
configuration requires double the disk space.

Supported RDBMS for Metadata:

Incorta Analytics requires one of the following RDBMS for its metadata:
• Derby (For demos and proof-of-concept (POC) installations).
• MySQL.
• Oracle.

Database-Related Requirements
Incorta Analytics requires one of the following RDBMS for its metadata:
• Derby (For demos and proof-of-concept (POC) installations).
• MySQL (5.1 or 5.5 is recommended).
• Oracle.
For Oracle and MySQL databases, you must provide a connecection to an
empty database, if you are not using High Availability configuration.
When installing Incorta Analytics on an Oracle, or MySQL, database, the user
needs to be granted certain privileges in order to complete the installation
successfully. To avoid authorization issues with the database during the
installation process, if the user does not have all privileges, ensure at least the
following are granted to them before starting the installation process:

For the Oracle database:

1. CONNECT.
2. ALTER TABLE.
3. CREATE TABLE.
4. INSERT.
5. CREATE INDEX.
6. CREATE OR REPLACE SYNONYM.
7. CREATE OR REPLACE TRIGGER.

6 | Incorta Inc. Copyright © 2017

 For the MySQL database:
1. CONNECT.
2. CREATE TABLE.
3. ALTER TABLE.
4. INSERT.
5. DROP TABLE.
6. CREATE INDEX.

Java Requirement
Incorta does not support Java SDK 1.8.0.151 and above. To update your server
to use the proper java version, please apply the following steps:
1. Download Oracle Java 8 u144 and install from the Oracle website:
http://www.oracle.com/technetwork/java/javase/downloads/java-archive-
javase8-2177648.html.
2. Configure JAVA_HOME after the java installation.
JAVA_HOME and JRE_HOME need to be configured to point to the
"Java8u144" version before starting the Incorta application server.

For MacOS, you may use the following commands in a terminal:

Command:
$ export JAVA_HOME=$(/usr/libexec/java_home -v 1.8.0_144)
$ export JRE_HOME=$JAVA_HOME/jre

For CentOS and Redhat:

Command:
$ ls -l /usr/lib/java

Sample Output:
lrwxrwxrwx. 1 root root   16 Jan 25  2017 default -> /usr/java/
latest
drwxr-xr-x. 9 root root 4096 Jan 25  2017 jdk1.8.0_144
lrwxrwxrwx. 1 root root   22 Jan 25  2017 latest -> /usr/java/
jdk1.8.0_144

7 | Incorta Inc. Copyright © 2017

 If more than one java files are installed, set JAVA_HOME to Java8 u144
Command:
$ export JAVA_HOME=/usr/java/jdk1.8.0_144
$ export JRE_HOME=$JAVA_HOME/jre

For Ubuntu:
Command:
$ ls -l /usr/lib/jvm

Output:
jdk1.8.0_144

Command:
$ export JAVA_HOME=/usr/lib/jvm/jdk1.8.0_144
$ export JRE_HOME=$JAVA_HOME/jre

Note:
• Incorta Analytics requires JDK, NOT JRE.
• For Windows users, after the JAVA installation is complete, configure
JAVA_HOME, by going to Control Panel > System > Advanced System
Settings > Environment Variables and:
a. click New (add the Variable Name 'JAVA_HOME' and add the
variable value <jdk.release number_path>)
b. look for, and double-click, the variable 'Path' to edit its value. Add
the full path to your jdk bin folder to the list of paths that already
exist, and separate it with a ";".

Ports Requirements
This section explains the ports required by the Incorta Analytics Server at
startup. Ensuring to have the ports listed below available will help avoid startup
failure. While some of these ports are installation parameters that could be set
and changed to different values during the installation process, others are of
fixed values and CANNOT be changed. However, they all need to be made
available for the Incorta Analytics Server at startup. Please refer to the following

8 | Incorta Inc. Copyright © 2017

 table for a summary of these ports:
Access Type Installation
Where to change
Port# Access Type Note Purpose Parameter Notes
it
(Y/N)

Tomcat <INSTALLATION
Incoming/
8005 shutdown Y _PATH>/server/
Outgoing
port conf/server.xml

<INSTALLATION
Incoming/ Tomcat HTTP
8080 HTTP traffic Y _PATH>/server/
Outgoing port
conf/server.xml

Tomcat <INSTALLATION
Incoming/
8443 HTTPS traffic HTTPS for Y _PATH>/server/
Outgoing
SSL conf/server.xml

<INSTALLATION
Incoming/ Tomcat AJP
8009 Y _PATH>/server/
Outgoing port
conf/server.xml

This is not related to

Apache Web incorta.
Incoming/ HTTP/S Also; ports 80 and
80 Server (if N Admin Task
Outgoing traffic 443 should be open
installed)
by default.

PLEASE DO NOT
Accessed CHANGE. This port is
locally by <INSTALLATION currently hard coded
7777 Internal the Incorta Phantom JS N _PATH>/start- in the server. Any
Analytics exportserver.sh changes will break
Server the send-dashboard-
by-email feature.

9 | Incorta Inc. Copyright © 2017

 Access Type Installation
Where to change
Port# Access Type Note Purpose Parameter Notes
it
(Y/N)

<INSTALLATION
_PATH>/
2181 Internal Zookeeper N
zookeeper/conf/
zoo.cfg PLEASE DO NOT
CHANGE. Changing
these default ports
Only if have a special
Drill will be process. Users need
Drill HTTP
accessed to refer to Zookeeper
Incoming/ Port (i.e.
8047 via the web N Default Value and Drill docs to
Outgoing Drill Web
(which is not change them. Or
Console)
recommend- simply make sure
ed) that the ports are
available on the
machine hosting
Drill rpc user the Incorta Analytics
31010 Internal N Default Value
server port * Server.

Accessed The Drill ports can be

Drill rpc reconfigured from the
locally by
31011 Internal bit server N Default Value following directory:
the Incorta
control port * <INSTALLATION_
Server
PATH>/dir/conf/drill-
override.conf
Drill rpc bit
31012 Internal server data N Default Value
port *

If the client (e.g.,

Tableau) exists on a
Incoming/ Drill Engine remote server, this
5438 N TMT/Admin UI
Outgoing (SQLi) port must be open
for remote access.
If the client (e.g.,
Incorta Tableau) exists on a
Incoming/ remote server, this
5436 Engine N TMT/Admin UI
Outgoing port must be open
(SQLi)
for remote access.
If Spark exists on a
Incoming/ Spark remote server, this
7077 Master Port N port must be open
Outgoing configuration
for remote access.

If Spark exists on a
Incoming/ Spark remote server, this
7078 Worker Port N port must be open
Outgoing configuration
for remote access.

For Spark master, this

port must be open
Incoming/ Spark Master Spark for remote access to
9091 N
Outgoing Web UI Port configuration monitor the Spark
jobs and logs.

For Spark worker, this

Spark port must be open
Incoming/ Spark for remote access to
9092 Worker Web N
Outgoing configuration monitor the Spark
UI Port
jobs and logs.

10 | Incorta Inc. Copyright © 2017

 The Shutdown Port: 8005: is the shutdown port for the Incorta Analytics Server,
and it needs to be accessed by incoming and outgoing data. This port can be
configured during the installation process, or changed in the XML file located in
the path: <Installation_Directory>/server/conf/server.xml.
The HTTP Port: 8080: can be configured during the installation process, or
changed in the XML file located in the path:
<Installation_Directory>/server/conf/server.xml.
If it is configured on the Incorta Analytics Server, then it should be made
available at startup.
The HTTPS Port: 8443: can be configured during the installation process, or
changed in the XML file located in the path:
<Installation_Directory>/server/conf/server.xml.
The AJP Connector Port: 8009: is the port for the Apache Web Server. It
can be configured during the installation process, or changed in the XML file
located in the path: <Installation_Directory>/server/conf/server.xml.
There are two cases for the Apache web server setup:

CASE 1 - If the Apache web server is installed on the Incorta Analytics

Server: make sure that the HTTP/S port ”80” (default) has incoming and
outgoing data access. Additionally, the AJP connector port “8009” ( in this
case) must be free internally on the Incorta Analytics Server to communicate
between the Incorta Analytics and the Apache web servers. No incoming
and outgoing data access is required.
CASE 2 - If the Apache web server is NOT installed on the same Incorta
Analytics Server: not only must the HTTP/S port ”80” (default) be available
and have incoming and outgoing data access, the AJP connector port
“8009” (in this case) must also have an incoming and outgoing data access.
The Apache Web Server Port: 80: is the default port for the Apache Web
Server (if installed). It can be changed in the Apache server configuration.
The PhantomJS: 7777: is an internal port that is accessed by the Incorta
Analytics Server locally to enable the send-dashboard-by-email feature. No
incoming and outgoing data access is required. It CANNOT be set or changed.
The High Availability (HA) Port: 2181: is an internal port that will be used as
the cluster coordinator once the High Availability feature is released. It will then
require incoming and outgoing data access. However, currently, no incoming
and outgoing data access is required. It can be set or changed.
The Drill Bit Server Port: 31011: is an internal port that is used as the Drill-bit
Server, and it is accessed by the Incorta Analytics Server locally. It CANNOT be
set or changed.

11 | Incorta Inc. Copyright © 2017

 The Drill-RPC Server Port: 31010: is an internal port that is used as the Drill-
RPC Server, and it is accessed by the Incorta analytics Server locally. It CANNOT
be set or changed.
The Drill HTTP Port: 8047: is the port used for the Drill HTTP client access. It
needs to have incoming and outgoing data access.

Font Requirements
Below is a list of the required font families by Incorta Analytics:
• Lucida Grande
• Lucida Sans Unicode
• Verdana
• Arial
• Helvetica
• Sans-serif
If you are using an older version of Red Hat (lower than version 6.6), you would
need to perform the following step:
Copy the java fonts from jdk to:

$home/.font

and refresh the cache using the following command:

fc-cache -vf

Libraries Requirements
Before starting the installation process, type:

cd /user/lib64
ls -l libfreetype

Three files should be returned, one of which should be "libfreetype.so.6".

If these files do not exist, you may need to install the required library and its

12 | Incorta Inc. Copyright © 2017

 dependent packages, by typing:

sudo yum install freetype

sudo yum install fontconfig

or you can list the libraries needed to install:

sudo yum install fontconfig freetype libfreetype.so.6

libfontconfig.so.1 libstdc++.so.6

13 | Incorta Inc. Copyright © 2017

 Configuring two database users 3

This section explains how to define two different Oracle users for an Incorta
instance. This feature could be used so that the Incorta Analytics user doesn't
have to obtain full access to the Incorta metadata schema.

Details
Two users will need to be created:
• User 1:
(INCORTA_OWNER) is the owner of the metadata performing the installation
to the metadata tables, and will have DDL access.
• User 2:
(INCORTA_USER) is the Incorta Analytics user, and will only have DML access
to the objects.
Note: This feature is only applicable to the Oracle Metadata.

For Fresh Installations

To configure two database users for new installations:
1. Create a new Oracle user (e.g. INCORTA_OWNER).
2. Grant this user ALL Privileges to their own schema.
3. Create another Oracle user (INCORTA_USER).
4. Run the installer, and follow the steps of the installation wizard.
5. In the Database Parameters screen, tick the checkbox to define a DDL user.
6. Enter the username and password for the DDL user to create the Incorta
Analytics metadata.

Note:
Do not create a default tenant during the installation process. That is,
in the "Create a Tenant" step of the installation wizard, make sure the
"Create a default tenant" checkbox is unchecked.

14 | Incorta Inc. Copyright © 2017

 7. If you have Incorta Analytics version 2.8, go to step 8. Grant select, insert,
update, and delete to the new INCORTA_USER on all of the INCORTA tables
owned by the INCORTA_OWNER in this example.
8. Create a tenant using the Tenant Management Tool (TMT). For more
information, refer to the TMT chapter in the Incorta Analytics Administrator
Guide.

For existing installations

When configuring two database users during an upgrade, there are two
scenarios:
1. Current installation works with only one DB user while two different users are
needed to handle the Incorta Analytics metadata. In this case, the following
steps will have to be performed manually before the upgrade process takes
place:

• Create a new Oracle user, e.g. INCORTA_USER.

• Grant select, insert, update, and delete to the new INCORTA_USER on all of
the Incorta tables owned by the DDL user.
• Modify the "server.xml" file in the installation directory:
<INSTALLATION_PATH>/server/conf/server.xml
and add the following properties:

a. factory = "org.apache.tomcat.jdbc.pool.DataSourceFactory"
b. initSQL = "ALTER SESSION SET CURRENT_SCHEMA = <INCORTA_
OWNER_NAME>"

Example:
<Resource name="jdbc/incortaDB" auth="Container" type="javax.
sql.DataSource" driverClassName="oracle.jdbc.driver.
OracleDriver" testOnBorrow="true" validationQuery="select 1
from Dual" url="jdbc:oracle:thin:@<HOSTNAME>:<DATABASE_
PORT>:<DATABASE_NAME>" username="<INCORTA_USER_
USERNAME>" password="<INCORTA_USER_PASSWORD>"
maxActive="500" factory = "org.apache.tomcat.jdbc.pool.
DataSourceFactory" initSQL = "ALTER SESSION SET CURRENT_
SCHEMA = <INCORTA_OWNER_USERNAME>" />
2. The current installation already works with two different Oracle users. In this
case, run the installer until the it automatically detects that two users are already
defined. It will then ask for the DDL password to execute the upgrade process.

15 | Incorta Inc. Copyright © 2017

 Installing Incorta Analytics 4

This chapter provides step-by-step instructions to install Incorta Analytics.

Step 1:
Incorta Analytics can be installed using its wizard. It is important that you read
the Pre-Installation Requirements carefully beforehand, in order to prepare your
system for a successful installation.

Step 2:
a. Locate and unzip the file "incorta-package.zip".
b. Locate and open the file "incorta-installer.jar", which can be found in the
unzipped "incorta-package" folder.

c. Follow the installation wizard. For detailed information about the wizard
steps, refer to the Installation Steps section in this guide.

16 | Incorta Inc. Copyright © 2017

 Installation Steps
This section explains the installation wizard steps:
1. Read the Welcome page, then click Next.

2. Read and accept the License Agreement, then click Next.

17 | Incorta Inc. Copyright © 2017

 3. Choose a location for the installation or accept the default location, then
click Next. (Note: If you are planning to use big data (e.g. spark, drill),
please ensure that the Incorta installation path does not contain spaces (e.g.
“Incorta Analytics” is not good.)

a. Select an installation folder, then click Open.

b. If you choose the same location as a previous installation with the same
name, a file-replacement warning message will appear.

18 | Incorta Inc. Copyright © 2017

 4. Choose a type for your installation, then click Next. If you select
"Advanced", go to step 6. (Note: To set up High Availability (HA), select
"Advanced".)

5. Select a database type and click Next.

If you select "MySQL", go to step 10.
If you select "Oracle", go to step 11.
If you select "Embedded" (which is for demos and proof-of-concept
installations only), go to step 12.

19 | Incorta Inc. Copyright © 2017

 6. To set up High Availability (HA), select "Advanced" and click Next. Note
that the database used must be configured to support clustering. For load
balancing, refer your system admin to the "Configuring an Apache HTTP
Server" section in the Incorta Analytics Admin Guide.

20 | Incorta Inc. Copyright © 2017

 7. Select "New Cluster" to create a new cluster or "Join Cluster" to join an
existing one. If you select "New Cluster", provide a unique node name,
cluster name, and the Zookeeper URL.

Note:
• The Node Name field is optional. If provided, the node name
must be unique and cannot be used when creating a new node
within the same cluster. If left blank, the node would be named
after the host name and the tomcat port number in the format:
<hostName_tomcatPortNo>.
• The Zookeeper must be up and running, and highly available,
before starting the nodes. To start the shipped Zookeeper
(recommended only for POCs and demos):
a. Go to the installation path.
b. Use the command ./start-zookeeper.sh.
• The default port no for the shipped zookeeper is:
<hostName>:2181.
• In the zookeeper URL field, specify the server IP address, where
the zookeeper is installed. Avoid using "localhost" as this would
result in a connection failure to the zookeeper server for non-
primary nodes.

21 | Incorta Inc. Copyright © 2017

 8. If you select "Join Cluster", provide a unique node name that has not
already been taken by another node in the existing cluster. If you do not
provide one, the node will be named after the host name and the tomcat
port number in the format: <hostName_tomcatPortNo>.

9. Select a database type and click Next. If you select "Oracle", go to step 11.

22 | Incorta Inc. Copyright © 2017

 10. Enter the MySQL database connection parameters and click Next. Go to
step 12.

Note:
• Ensure that the database port is open and accessible through
the IP address.
• First-node installations must have an empty database with no
tables, whether the installation type is "Typical" or "Advanced".
• For advanced "Join Cluster" installations, ensure the database is
that of the Incorta metadata.

11. Enter the Oracle database connection paramteters. To add an Oracle DDL
user, tick the checkbox at the bottom, then click Next.

23 | Incorta Inc. Copyright © 2017

 Note:
• Ensure that the DML user can connect to the database and that
the DDL user has the required privileges listed in the Database-
Related Requirements section.
• Ensure that the database port is open and accessible through
the IP address.
• In first-node installations the DDL user must have an empty
database with no tables, whether the installation type is
"Typical" or "Advanced".
• For advanced "Join Cluster" installations, ensure that the
database is that of the Incorta metadata and that the DDL user is
the Incorta metadata database owner.

12. The following two steps will help you configure Tomcat (Incorta Analytics
default application server). Change the port numbers if needed, and click
Next.

24 | Incorta Inc. Copyright © 2017

 Note:
• It is important to enable the https protocol in order use the Box,
Drop Box, and Google Drive file system connectors.
• If you choose to enable HTTPS, you will need to note the
HTTP redirect port number to access the Incorta Analytics
web application. Otherwise, you will need the HTTP
Connector port number. (i.e. You will need to type "http://<IP
Address>:<Tomcat Connector (or Redirect) Port>/incorta" in the
address bar of your browser.)

13. Enter the allocated memory for the application server. This amount depends
on the amount of data you want to load into Incorta Analytics, and the
amount of memory available in your server. Then, provide a username and
password for the Tomcat administrator and click Next.

25 | Incorta Inc. Copyright © 2017

 14. Enter the system tenant parameters and click Next.

26 | Incorta Inc. Copyright © 2017

 Note:
If this is an HA installation, provide a system tenant path that is shared
with, and accessible by, all the servers in the cluster.

15. Choose whether or not to create a default tenant (which may be used as a
starting point to your development) and include the sample data shipped
with Incorta Analytics, and click Next. You can also create a tenant later
using the Tenant management Tool (TMT).

Note:
A default tenant is not needed in the case where existing tenants will
be imported into this installation.

16. Select the administrator credentials for the Incorta Analytics application, and
click Next. This is different from the Tomcat server administrator credentials.

27 | Incorta Inc. Copyright © 2017

 Note:
• For the Tenant Path field, make sure you choose a location with
sufficient disk space to place the "Tenants" folder. It does not
have to be in the same location as the installation folder.
• If you opted for an HA installation, provide a tenant path that is
shared with, and accessible by, all the servers in the cluster.
• Empty fields are not allowed in the Administrator's name, email,
and password fields.

17. Enter your email information for services that need to send password-reset
emails and sharing notifications. Tick the "Enable Sharing Notification"
checkbox at the bottom if you like to receive dashboard sharing
notifications, then click Next.

28 | Incorta Inc. Copyright © 2017

 18. Review the summary of your installation, then click Next. Otherwise, click
Previous to modify your settings.

29 | Incorta Inc. Copyright © 2017

 19. When the installation is completed successfully, click Done.

Now that Incorta Analytics is installed successfully, you can access it by going to
the installation folder location (e.g. <Incorta_path>/IncortaAnaltyics) to start the
Tomcat server by typing the command:
./start.sh

For Windows, go to the Incorta installation folder and run the following
command to start the Incorta Analytics (tomcat) Server.

start.bat

30 | Incorta Inc. Copyright © 2017

 Note:
For Windows users, in order to launch the tomcat and export servers,
they would need to go to the Incorta installation folder and do the
following:
1. Run start.bat to start the Incorta Analytics (tomcat) Server.
2. Run start-exportserver.bat to start the export server.
3. Run open-browser.bat to start the Incorta Analytics application in a
browser.

To access the Incorta Analytics web application, open a browser and type
"http://<IP Address>:<Tomcat Connector (or Redirect) Port>/incorta" in the
address bar (Refer to the port number you chose in step 12).

Additional Information

Restarting the Incorta Analytics Server:

a. Go to <Incorta_path>/IncortaAnalytics and run the following command to
check if the server is running:

ps aux | grep java

31 | Incorta Inc. Copyright © 2017

 b. If the server is running, and you want to restart it, you have to kill the server
first.
c. You can stop the server using the command :

./stop.sh

d. Use the command in step a to make sure the process is stopped. If it is not
stopped, you can kill it using the kill command.
e. Now you can start the server using the command:

./start.sh

Checking the Incorta Analytics logs:

You may check the log information by checking the appropriate log files:
a. For engine-related log information, check the "catalina.out" file in the path:

<Incorta_path>/IncortaAnalytics/server/logs

b. For log information related to the server and the loader, go to:

<Incorta_path>/IncortaAnalytics/server/logs/incorta

and check the files, "incora-server.<ActivityDate>.log" and "incorta-

loader.<ActivityDate>.log", respectively.

Changing the Installation Parameters:

a. HTTP Port:
Open the file <Incorta_path>/IncortaAnalytics/server/conf/server.xml,
and look for the following section:

<Connector port=”8000” protocol=”HTTP/1.1”

connectionTimeout=”20000” redirectPort=”8443”
URIEncoding=”UTF-8” />

32 | Incorta Inc. Copyright © 2017

 b. Application server admin information:
Open the file <Incorta_path>/IncortaAnalytics/server/conf/tomcat-users.xml,
and look for the following string:

<user username=”admin” password=”incorta” roles=“manager-

gui”/>

33 | Incorta Inc. Copyright © 2017

 Upgrading Incorta Analytics 5

This section contains information about the steps needed to upgrade your
version of Incorta Analytics.

Before you upgrade...

1. You need to have Incorta Analytics already installed on your system.
2. You need to have full access to the Incorta Analytics installation folder (e.g. /
IncortaAnalytics/IncortaAnalytics).
3. Back up:
a. the Incorta Analytics metadata for MySQL or Oracle database.
b. the derby folder "derbydb" located in the installation folder, for Embedded
database.
c. the tenants, by exporting them individually.

Upgrading
The upgrade process takes place automatically in the installation wizard when
prompted to specify an installation location. If another installation already exists
in this location, the installer implicitly checks and recognizes it is an upgrade.
During the upgrade, the installer checks for two things:
• The Oracle database installation: If it is a two-user Oracle database
installation, it requests the password for the DDL user.
• Tomcat Manager: If it is installed, it will prompt the user to either keep it or
remove it. If it is not installed, it will give the option of installing it.

To start the upgrade process:

1. Locate and go to the folder where the installer file (i.e. incorta-installer.jar)
exists.
2. Open the installer file and follow the installation wizard.
3. Select the existing installation location as the installation folder when prompted,
then click Next.

34 | Incorta Inc. Copyright © 2017

 4. Confirm that you want to upgrade the installation and replace the existing files.

5. When the upgrade process is completed successfully, click Done to exit the
installer.

35 | Incorta Inc. Copyright © 2017

 Uninstalling Incorta Analytics 6

Before you uninstall...

As a precaution, it is advisable that you back up:
a. the Incorta Analytics metadata for MySQL or Oracle database.
b. the derby folder "derbydb" located in the installation folder, for Embedded
database.
c. the tenants, by exporting them individually.

To uninstall Incorta Analytics from your system:

1. Go to the location of the uninstaller folder "uninstaller", which can be found in
the installation folder "e.g. IncortaAnlaytics".
2. Run the uninstaller file "uninstaller.jar".

36 | Incorta Inc. Copyright © 2017

www.incorta.com
@incorta | facebook.com/incorta
2755 Campus Drive
San Mateo, CA 94403
Incorta Inc. Copyright © 2017