Enterprise 4.11 Installation

Comprehensive Installation Guide: Meeting Requirements, Preparing the Environment, Step-by-Step Installation, and Notes.

Sections Available in Enterprise Installation

Function	Description
Installation Requirements	Discover the specific hardware, software, and system prerequisites needed for a successful Enterprise V4.11 installation
Pre-Installation	Prepare your device step-by-step instructions, including tasks such as system configuration, database setup, and user account management.
Installation Instructions	Follow the detailed installation steps provided in the guide to install Enterprise V4.11 on Innoslate.
Innoslate Setup	To successfully set up Innoslate, follow the detailed steps provided in this section.
Troubleshooting	Install seems to not be working? Check out our troubleshooting tips.
Configuration Notes	Settings.Properties File

Installation Requirements

Minimum Requirements:

• Operating System: Windows 10, 11, Server 2016/Server 2019/Server 2022
• Processor: Dual Core Processor
• RAM: 4GB RAM
• Hard Drive Space: 10GB Free Hard Drive Space, a Solid State Drive is recommended (500MB is required for Innoslate Server Files)
• Database: PostgreSQL or Microsoft SQL Server 2008 or higher (Full Text Search must be on in SQL)

Recommended Requirements:

• Operating System: Windows 10, 11, Server 2016, Server 2019, Server 2022
• Processor: Quad Core Processor
• RAM: 8GB RAM
• Hard Drive Space: 25GB Free Hard Drive Space, a Solid State Drive is recommended (500MB is required for Innoslate Server Files)
• Database: PostgreSQL or Microsoft SQL Server 2008 or higher (Full Text Search must be on in SQL)

Pre-Installation Checklist

• Install a compatible database: Innoslate supports SQL Server 2008 (or later) and PostgreSQL.
• Create the database in SQL or PostgreSQL.
• Confirm that the following ports are open: 8080, 8005, and either 1433 or 5432, based on your specific database configuration.
• Check the system minimum installation requirements.
• Please note that usernames and passwords for any accounts in your database application or Innoslate cannot contain the following special characters:
  
  a. #                                                                            b. %
  c. ^                                                                            d. &
  e. +                                                                            f.  "
  g.  '                                                                             h. \
  i.  {                                                                             j.  }
  k. |                                                                             l.  !
• Enterprise users must generate a unique Innoslate License ID from the machine on which Innoslate will be used before they can receive their official License Key. Steps for retrieval of this code are provided in Steps 3 & 4 in the Setup section below. Skip this step if you already have a license.
• Download Innoslate Enterprise v4.11 with this link (once you click on this link the file will start to download): Innoslate 4.11| Installer

Installation Instructions

1. Run the Innoslate Enterprise v4.11 installer as an administrator.
2. Microsoft Defender may recognize an unverified app. Proceed by clicking "Run Anyway".
   
3. The next prompt will come up to permit Innoslate to make changes to your computer. Click “Yes” to continue.
   
4. The Innoslate Setup Wizard will open. Click “Next” to continue:
   
5. The wizard should prompt to agree to the license agreement. Click “I Agree” to continue.
   
6. Ensure the Innoslate4 and Service components are checked for installation. Click ‘Next’ to continue.
   
7. Choose the destination folder (default is C:\Innoslate4) and click "Install".
   
8. Wait for completion and click "Finish".

The setup will launch in your browser; if not, navigate to http://localhost:8080/setup/.

Optional: You can skip the Innoslate Setup if using a pre-configured settings.properties file, copy it to C:\Innoslate4\apache-tomcat\webapps\innoslate4\WEB-INF and restart the Innoslate service.

Innoslate Setup

1. Select Begin Setup.

2. Accept the Innoslate End-User License Agreement and click ‘Next:

• Innoslate
• Sopatra
• Omni (both Innoslate and Sopatra)

Drop your license key file, or click to select and upload the license key file, and click on ‘Validate’. Confirm the correct license count and expiration date pop-up. Click ‘Next’ to continue.

6. Proceed to the next step to establish the database connection between Innoslate and your database application. Enter the host location, port number, database name, and database administrator credentials.

Since this step varies based on your selected database application, refer to the tips below for relevant information.

• Make sure the database has been created before this step.
• The “Username” and “Password” fields are for the database administrator credentials.
• If the database application resides on a separate machine, please enter the corresponding IP address or machine name in this field, as this will vary based on your network configuration.
• PostgreSQL’s default port is 5432 and SQL Server is 1433. If this has been changed for your configuration, please reflect the proper port for your environment.
• The database connection string will populate as you fill in the fields above it. Fill out the fields on this page to access your database per your configuration.
• Pool information is regarding the JDBC Pool configuration. The default is recommended.

7. Once validated, you will get the “Database Successfully Connected” prompt. Click ‘Next’ to the Authentication Step.

8. Authentication options are Native, CAC, PKI, LDAP, SAML & OAUTH. This step will include the necessary details needed for the selected authentication. Once selected, click 'Next.'

You can always pick Native for now, then go back and configure your authentication type after install. If this route is selected, please contact Support for the corresponding documentation. 

9. This step is to set up your Innoslate System Administrator account, also known as the "Super Admin". Note, the Super Admins have complete access to configure Innoslate, adding/removing licenses from the install, and adding/removing organizations. Note, if you do not add this account to any organization created within your configuration, this user will still be able to log in without taking a license.  Under the Additional Admin Users portion, users may be designated here to be an additional Admin or have access to the Support Dashboard to reset passwords or help users with their account ('Support Users').

Once this has been filled out and all the fields are cleared with the green check mark, click on the ‘Next’ button.

10. The file system page manages blob objects and file configurations for Innoslate uploads and report downloads. 

• We suggest the default for the File Information for 100MB max file upload and 10,000,000 max entities in a report as users get started. This can always be reconfigured again later.
• Filesystem information is for persistent files (blobs), and this file will usually be located on the machine it is installed on. You can also put it on an AWS Simple Service Storage (S3), particularly useful for Amazon Web Services environments.

11. Click ‘Next’ to configure Innoslate for email notifications. For users who want to have their email notification system set up, fill out the fields to reflect your environment (Mail Security, Mail Host, Mail Port, Mail Username and Password and other preferences). You can also set up with no email notifications and go back to set this up after installation. Click 'Next' once completed.

12. This step is to set up your browser's cache options. Once selected, click 'Next.'

• Native cache option is to use Innoslate’s Tomcat
• Redis Cache option is for users using the Redis software as their cache management system (enter Redis URL, Port and Password).

13. Configure Innoslate to your chosen AI Provider (Open AI, Ask Sage, Azure AI) for Chat AI and Image AI tools. Required fields vary by provider, but generally include URL, API Key, Model, and Org Key (for Open AI).

14. At this stage, you will see a representation of your settings.properties file, which serves as the configuration file for Innoslate. This view in the Setup summarizes all the configurations you have established in the prior steps. Take a moment to review the information you've entered to ensure everything is accurate. If any adjustments are necessary, you can use the previous and next navigation buttons provided in the Setup. Once you are satisfied with your review and all details are correct, proceed by clicking 'Next.'

After setup, your settings.properties file can be found along this file path: C:\Innoslate4\apache-tomcat\webapps\innoslate4\WEB-INF.

15. The Finish Step requires applying the settings configured. At this step, click ‘Apply Settings’. 

16. Click 'Finish' then restart the Innoslate service by restarting the Innoslate4 Window's service or by running restart_innoslate_service.cmd found in the utilities folder in Innoslate4. 

After Setup

1. Access the login page by opening your web browser and entering the designated URL (http://localhost:8080/ or any other specified configuration) and login as the Super Admin.

2. Set Up Organizational Sandboxes (Organizations).

Notes:

• The entity limit zero (0) indicates unlimited entities.
• Do not use the slug 'socket'. This is already reserved and used internally in the application.

Troubleshooting

• Innoslate Service did not install correctly and is missing: Attempt to refresh the list of services, and if Innoslate4 does not show up on the list, then navigate to the installed drive to locate the folder called “Innoslate4.” Click on the folder and then navigate to the “utilities” folder. In that folder, there should be a utility called “install_innoslate_service.” Click on that, and the Innoslate service will be installed. Then, run the “restart_innoslate_service” batch file to start up the service.
• Unable to connect to database:
  • Check the connection to your database server (whether it be SQL server, or PostgreSQL) and verify that the service is running and that the database is created.
  • Check that the database admin credentials are correct, then check to make sure the username and password for the database admin credentials don’t contain special characters (e.g. # % ^ & + “ ‘ \ { } \).
  • Check if the database name is correct. If all of the above settings are correct, check with your systems administrator for troubleshooting help. We usually find that firewalls to the ports are blocked 
  • Check to make sure Full Text Search is enabled. You can determine if Full-Text Search is installed and enabled by querying the database. Use this Query:
    • • "SELECT SERVERPROPERTY('IsFullTextInstalled')"
    • If the query returns 1, then Full-Text Search is enabled. If it returns 0, then Full-Text Search is not enabled and you will need to run SQL Server Installation Center to add the Full-Text Search feature.
• Java version issues: Locate the “Utilities” folder and click “set_java_home_path.” This batch file will attempt to locate your java home path, and if java is not installed, it will install it automatically.
• Browser setup was interrupted: If you accidentally closed the browser before setup was complete or if your internet connection failed, then you need to start the process over again, navigate to the “utilities” folder (C:\Innoslate4\utilities), and click on “launch_localhost_setup.” This batch file will bring up your browser and start the setup process for you.
• Innoslate hangs/won’t start: Make sure your Innoslate service is running via Windows Services.

Configuration Notes

See Settings.Properties File.

 

To continue learning about Enterprise User Guides, Click Here.

(Next Article: Innoslate's API)