Skip to content
  • There are no suggestions because the search field is empty.

Streamlining Innoslate Setup from an Existing Enterprise Environment

Efficiently Integrating Innoslate with Your Established Enterprise Infrastructure

The Innoslate Enterprise Installer provides a guided setup to configure core components—such as database connection, authentication, and licensing—immediately after installation. These settings are saved in a `settings.properties` file. If you already have a properly configured `settings.properties` file from a previous Innoslate installation, you can skip the setup wizard and proceed with an automated installation by using your existing file. To support a streamlined installation, the following sections provide prerequisites, comprehensive instructions, and troubleshooting resources to help ensure a smooth, efficient deployment experience.

Prerequisites

  • Administrative privileges: Please ensure you’re running the installer and managing files as an administrator on the machine where Innoslate is being installed.
  • Existing `settings.properties` file:  Ensure your settings.properties file is complete and valid from a working Innoslate instance. It should include all necessary configurations (e.g., database credentials, license key, authentication type). It can be found along this file path within the Innoslate4 directory: C:\Innoslate4\apache-tomcat\webapps\innoslate4\WEB-INF (The directory may differ based on your environment—adjust the path as needed).
    • Note, due to the Java 21 updates in Innoslate v4.12, the SAML Authentication parameters and configuration MUST be modified. Please see: SAML Authentication for Java 21
  • Apache Tomcat: Review any custom settings from your previous Tomcat configuration and prepare to manually apply them to the new environment. Do not copy configuration files (e.g., server.xml, web.xml) from previous Tomcat versions to Tomcat 11, as they are incompatible.
  • System requirements: If new, verify your environment meets Innoslate's requirements (e.g., Windows Server 2019 or later, sufficient RAM).
  • Backup: Always back up your system before modifying files or services.
  • Remove previous Innoslate installation: If you are installing the new version of Innoslate on the same machine and drive, uninstall any earlier version before proceeding (may require system reboot).
  • Installer: Download the latest Innoslate Enterprise installer:

Step-by-Step Instructions

Step 1: Run the Innoslate Installer

  1. Locate the downloaded installer (e.g., `Innoslate_4.12.1.0-setup.exe`).
  2. Right-click the installer and select "Run as administrator".
  3. If prompted by Microsoft Defender or User Account Control (UAC), click "Yes" or "Run Anyway" to proceed.
  4. In the setup wizard:
  • Click "Next" on the welcome screen.
  • Accept the license agreement by selecting "I Agree" and clicking "Next"
  • Ensure Innoslate4 and Service components are selected (default).
  • Choose the installation directory (default: `C:\Innoslate4`) and click "Next".
  • Click Install to begin the file extraction and component setup.

5. Wait for the installation to complete (this may take several minutes), then unclick "Launch Innoslate Setup" and select "Finish".

uncheck setup 4.12 bypass

Step 2: Stop the Innoslate Service

  1. Open the Services management console:

    • Press Win + R, type services.msc, and press Enter.

  2. Locate Innoslate4 in the list.
  3. Right-click Innoslate4 and select Stop. Alternatively:
    • Open Command Prompt as administrator.
    • Navigate to C:\Innoslate4\utilities and run stop_innoslate_service.cmd
  4. Wait for the service to stop completely (this may take a few seconds). 

Step 3: Update Apache Tomcat Configuration Files (if needed)

  1. Identify and locate critical Apache Tomcat configuration files in your environment:
    • server.xml: Located in C:\Innoslate4\apache-tomcat\conf. This file defines the Tomcat server configuration, including ports, connectors, and host settings.
    • web.xml: Located in C:\Innoslate4\apache-tomcat\conf. This file contains default settings for all web applications, such as servlet mappings and security configurations.
  2. Back up both server.xml and web.xml before making any changes.
  3. If you have custom configurations from a previous installation (e.g., modified ports, SSL settings, or context parameters), copy the relevant sections from your backed-up server.xml and web.xml files to the new installation's files.
  4. Important:
    • Ensure any changes to server.xml (e.g., port numbers) do not conflict with other services on the system.
    • Validate the XML syntax after editing to avoid startup errors.
    • Ensure appropriate file permissions to ensure the Tomcat service user can read these files.
  5. Save the updated files.
  6. Restart the Apache Tomcat Server to apply the configuration changes. Note: We highly suggest you restart the Apache Tomcat Server after applying the above settings, as an extra security measure that the files are saved.
    • Open Command Prompt as administrator.
    • Navigate to C:\Innoslate4\apache-tomcat\bin.
    • Run shutdown.bat to ensure the Tomcat server is 
      fully stopped (if not already stopped in Step 2).
    • Run startup.bat to start the Tomcat server.
    • Wait 1-2 minutes for the Tomcat server to fully start.

Step 4: Prepare and Place the `settings.properties` File

  1. On your Windows system, navigate to the Innoslate web application directory within your chosen installation folder:
    • `C:\Innoslate4\apache-tomcat\webapps\innoslate4\WEB-INF\`
      (Note: Exact path may vary if you changed the installation directory; replace `C:\Innoslate4` accordingly.)
  2. If a `settings.properties` file already exists in the new WEB-INF delete it.
  3. Important:
    • Ensure file permissions allow read/write access.
    • Validate the file syntax (it's a standard text file; no JSON or YAML). Common errors include missing values, spaces or invalid property names.
  2. Copy the existing `settings.properties` file into this directory, overwriting any defaults.

Step 5: Restart the Innoslate Service

  1. Open the Services management console:
    •  Press `Win + R`, type `services.msc`, and press Enter.
    • Alternatively:  
         Open Command Prompt as administrator.  
         Navigate to `C:\Innoslate4\utilities` and run restart_innoslate_service.cmd
  2. Locate "Innoslate4" in the list.
  3. Right-click "Innoslate4" and select "Restart".  
  4. Wait 1-2 minutes for the service to fully restart.

Step 6: Verify the Configuration

  1. Open a web browser and navigate to `http://localhost:8080/` (or your configured host/port)
    • Alternatively, navigate to "C:\Innoslate4\utilities" and run launch_localhost.cmd".
  2. You should land directly on the Innoslate login page (not the setup wizard) dependent on your Authentication type. 
    • Be sure to log in with your Super Admin credentials from the `settings.properties` file (e.g., `ADMIN`).
  3. Check key configurations:  
    • Login to Innoslate and create a test project.
      • Test features like AI integration, file uploads, email and/or reports to ensure they match your original setup.
  4. Review logs for errors:  
    • Check `C:\Innoslate4\logs\catalina.out` or the Tomcat logs in the installation directory.

Troubleshooting

  • If the setup wizard appears, the settings.properties file may be invalid or misplaced. Verify the file's contents, permissions and location.
  • If the service fails to start, check catalina.out for errors related to server.xml, web.xml, or settings.properties.
  • Ensure the Tomcat service user has read/write permissions for all modified files.
  • If port conflicts occur, review server.xml for duplicate or reserved ports (e.g., 8080, 8005).
    • Ensure previous Innoslate version is uninstalled if the port is occupied.