Skip to main content

Install Hubble

Process Overview

The installation process involves connecting to the Object Repository, installation of the software, configuration of the application and deployment. The database connectivity layer is built into the application and is set up during the configuration stage of the process.

Object Repository - The Object Repository contains the application’s configuration information, objects such as hierarchies, Reusable Inquiry Objects and user-specific information. Report parameters are stored in the repository, but not the report results themselves.

The repository is on a PostgreSQL database. The application uses the repository to perform critical processes such as user verification and validation of permissions. The application has a built-in database layer that will allow access from the application to the database.

Installation and Configuration - The software is installed via a Windows Installer Component (msi file). Once the software is installed, the application needs to be configured and users set up via Administrator.

Software Installation

Our Customer Support Department will provide you with the installation file you need for the Hubble version you are installing. You will need to save this to the machine where you are going to install the software. Once it is saved, we will walk you through the Installation Wizard. The steps are listed below.

  1. In the Installation Wizard, you must first accept the End User License Agreement. In the next screen, choose the scope of the installation:

  1. Click Next.
  1. In the Destination Folder screen, click Change to change the location of the installation. You want to be sure you are not overwriting the existing version if you have another version installed, so you need to define a different location for the new version to be installed.

  1. Click Next.
  2. In the next screen, choose the type of setup required:

  1. Click Next.
  2. Click Install to compete the installation:

  1. Once the installation is done, you can rename the Program Menu Name from Hubble to the specific version name in order to distinguish one version from the other. Right-click on the Program Menu name, then click More > Open File Location:

    From there you can rename the shortcut, for example:

Tip: Upgrading to a newer Hubble version - It is recommended that you run the new version and current version in parallel. This enables you to complete a testing and user acceptance phase.

EBS Script

For Oracle e-Business Suite (EBS) users, installs and upgrades from one major Hubble product release to another require a release-specific script being run. The script will be run for the Schema username you have defined for the release. This script will grant the proper permissions to the ERP Tables we use in our product as well as generate the necessary views. One of the steps in the script includes the creation of a new schema for the EBS Data Connection. Following are important points regarding the new schema:

  1. In the script, you will be prompted to enter the name of the new schema. The default schema name is Hubble; however you need to be sure to change it so that you use a new name when creating a new schema. A best practice is to name the schema after the Hubble release so you can associate the schema name easily. An example for a schema name is “HUB19_3” or “HUB19_4”.
  2. The same situation exists for every EBS instance (which is the Hubble profile, e.g. PROD or DEV) you connect to within the product. For an upgrade to a major release, the script needs to be run over the data in each instance and the Hubble Data Connection(s) modified to have the new schema name being used in that Connection(s).
  3. If you are using Budgeting, you also need to run a separate database script that creates a schema to hold the budgeting tables.

Please contact our Customer Support Department for obtain the scripts or for any questions related to the scripts.

Deploying using Citrix

Once the software has been installed, it can be deployed in several ways. One way it can be published is via Citrix, and in order to do that, the Hubble application must first be installed on the Citrix server. For detailed information on publishing to Citrix, please refer to the product information provided by Citrix.

When following the steps detailed by Citrix, you will input specific information related to Hubble. Some examples are listed below.

  • When locating the application, on the Command Line, input the install path and executable file such as C:\ProgramFiles\InsightSoftware.com\Hubble\19.4\Hubble.exe
  • When locating the application, optionally you can input the working directory, which is the install path. An example is C:\Program Files\InsightSoftware.com\Hubble\19.4\
  • The icon is located in the install path, such as:
    • C:\Program Files\InsightSoftware.com\Hubble\Hubble_19.4\citrix_hubble.icon.ico

Deploying using ClickOnce

Hubble can also be deployed via ClickOnce, a Microsoft deployment technology that enables users to install and run an application with minimal IT involvement. See the Hubble Supplementary Deployment Topics Guide for information about deploying via ClickOnce.

Deleting the Application from a Workstation

Follow the steps below to delete the application from a workstation:

  1. Back up the repository from within your old version of Administrator.
  2. To prevent the occurrence of an orphaned repository database, delete the repository from within Administrator.
  3. Access Control Panel > Add/Remove Programs.
  4. Find the correct version of Hubble and select it.
  5. Click Uninstall.
  6. Review folders/files in the install path related to the removed version to verify removal. (The default install path for Hubble is C:\Program Files\InsightSoftware.com\Hubble... If the files are still present in the install path, you can delete them.