Skip to main content

Getting Started with Administrator

Accessing Administrator

To access the Administrator Application, click on the cogwheel symbol on the Hubble login screen.

Hubble Repository Setup Wizard

The first time you open Administrator after installing it, the Hubble Repository Setup wizard dialog will automatically open.

The Hubble Repository Setup wizard is a tool for administrators to setup a connection to the repository.

You can close the wizard by clicking Cancel or by clicking the Close Window (X) on the top right corner of the wizard dialog.

If you close the wizard and need to open it again, click the Initial Setup button on the Home menu, or click New then Repository (this option will be disabled if a repository has already been setup.

The configuration carried out within the wizard is as follows:

  1. When the welcome page of the wizard comes up, click Next.
  2. In the Choose Configuration Method step, choose Read it from an existing Repository Selection file and then navigate to the saved .xml file by selecting the radio button and clicking the "…" button. (The .xml file is commonly found within the Hubble install directory.)

Click Finish to close the wizard and create your repository. connection It is then listed in the Main tab. For example:

Note: Only one repository can be assigned to a connection. If multiple environments are required, it is recommended that multiple servers are used.

Save the Repository Selection File

The Repository Selection File (or RepositorySelection.xml file) defines where the Object Repository is stored and how the software connects to it.

Once a new repository has been created or an existing one selected, the Repository Selection File should be saved in the Hubble directory for subsequent use for all users on that machine.

To save the Repository Selection File in the Hubble directory:

  1. In the left panel under Repository Database Connection, right-click on the repository for which you wish to save the Repository Selection File.
  2. Select Save Repository Selection.
  3. A Save As dialog will be displayed, allowing you to specify the directory.
  4. The file can be copied to other machines in order to use the same Repository selection.

    Note: If the RepositorySelection.xml file does not exist in the Hubble directory, the Login dialog will display the Initial Setup wizard, which will be used to select or create a repository.

You must be an administrator (having Windows administrative rights) in order to save into the installation folder as it is a protected folder. If you are not a local administrator of the workstation, you are not able to save the xml file into the Program File directory within Administrator.

There are 2 ways you can save the xml file into the install path outside of Administrator:

Option 1: Save the Repository Selection file to an allowed location and then move it into the install path from within Windows Explorer.

  1. When saving the Repository Selection file in Administrator, save it to My Documents on your Desktop.
  2. Use Windows Explorer to move or copy it to the Hubble installation folder (the default location for the installation folder is under Program Files).

Option 2: Run Administrator with Windows administrative rights.

  1. Right-click on the Administrator shortcut.
  2. Choose Run as Administrator.
  3. Save the xml file directly into the Hubble installation folder (the default location for the installation folder is under Program Files).
  4. If users try to launch Hubble without a RepositorySelection.xml file in the installation folder, an exception message displays.

Sign in to the Repository

Follow the steps below to log into the repository:

  1. After completing the initial setup wizard or manually creating a repository, you will see the Repository Database Connection you have just created appear in the left panel of Administrator.
  2. Open the Repository Login dialog by doing either of the following:
    1. Click on the underlying repository so the Ribbon automatically displays the Repository tab. Then click Login to open the Repository Login dialog.
    2. Double-click on the repository name to open the Repository Login dialog.
  3. In the Repository Login dialog, enter the login name and password that you specified in the Initial Setup for the Repository (e.g. 'Administrator').
  1. Click Login. The Repository icon will change from gray to yellow if you have correctly entered in your login credentials.
  2. Once Logged in, you can navigate using the + icons in the left-hand panel or click on the folder in the right-hand panel of Administrator.

Back Up the Repository

During the configuration of the application server, repository backups are scheduled. See the Hubble Supplementary Deployment Topics Guide for more information on this.

Alternatively, you can back up the repository manually by following the below instructions. If you do it this way, be sure to save the backup files to a network location that is included with your regular disaster recovery services.

Note: The Administration tool backup only backs-up Desktop objects. It does not backup Web objects (Web objects are stored outside of the Desktop table structure and are bridged with special views).
When the Web version is installed, the Application server will automatically backup the full repository each night.

To back up your repository:

  1. Log into your repository if you are not logged in already.
  2. Either select the repository you wish to back up and click Backup on the Ribbon or right-click on the repository and select Backup.
  3. You are then prompted to save the RDF file to the location of your choice.

    Note: It is recommended to put the backup files into a designated backup folder and in the file name include the specific repository information (such as the repository name) so that you can easily identify the backup files.

The following message is displayed when the backup is complete:

Once a repository is backed up, you can either use the Import function to bring in specific items from the backup, or the Restore function to bring in all items from the backup.

Restore a Repository from Backup

You can use the Restore function to add a new repository to an existing one or create a new one.

  1. Log into your repository if you are not logged in already.
  2. Right-click on the repository you wish to restore into and select Restore.
  3. When the Open File dialog opens, navigate to and select the Repository Data File (RDF) you want to restore.
  4. Click OK.
  5. When the restore has completed, save the repository selection file to the appropriate Hubble installation path.

The repository being restored will then be appended to the open repository. Any incompatible files will be reported through a message dialog.

When you restore into a repository that has existing data, it adds any new reports that are not currently there. If the same report already exists in the repository and it is in the restore, the restore will overwrite the existing report. If a report lives in the repository currently and the restore does not have the report, you will still have the report. If a profile was renamed, a restore will bring it in again with the original name; otherwise it will overwrite the profile/connections if they are the same name.

Restoring as part of an Upgrade

If restoring from backup as part of an upgrade to Hubble, you will receive a temporary license key which with which you must replace the old permanent license key. Once the upgrade is completed and has been checked as satisfactory, you will receive a new permanent license key to replace this temporary license key. See License Keys for further details.

After the upgrade, the profile wizard for each profile must be run. This is so that any new tables included in the upgrade (as listed in the Table Locations screen) can be registered. See Creating New Profiles for details of the profile wizard.

ERP Database Connections

Database Connections for JD Edwards

Create a New Database in Microsoft SQL Server

The steps for creating a new database are listed below; however be aware that these can vary depending on your version of Microsoft SQL Server. The links to documentation based on specific version numbers are listed below. If you still have further questions, please consult your Systems Administrator to complete this task.

From SQL Server Enterprise Manager:

  1. Select New Database.
  2. Provide a database name.
  3. Click OK.

For detailed steps on creating a database, refer to these instructions: http://msdn.microsoft.com/en-us/library/ms186312%28v=SQL.100%29.aspx

Create a New Database User

The steps for creating a new database user are listed below; however be aware that these can vary depending on your version of Microsoft SQL Server. The links to documentation based on specific version numbers are listed below. If you still have further questions, please consult your Systems Administrator to complete this task.

From SQL Server Enterprise Manager:

  1. Connect to the database server where the database has been created.
  2. In the left panel, expand Microsoft SQL Servers.
  3. Expand the SQL Server Group to be presented with a list of available servers.
  4. Select the server for which you wish to create a user.
  5. Expand the server selection.
  6. Expand the Security folder.
  7. Underneath the Security folder, right-click on Login.
  8. Select New Login.
  9. On the General tab of the SQL Server Login Properties - New Login dialog:
    1. Provide a name for the new user.
    2. Select the SQL Server Authentication option.
    3. Enter the password of your choice.
    4. For the default database, select the database created for the Hubble Object Repository.
  10. On the Server Roles tab of the SQL Server Login Properties - New Login dialog, leave the default selection.
  11. On the Database Access tab of the SQL Server Login Properties - New Login dialog:
    1. Highlight the database created for the Object Repository.
    2. Check the Permit item from the list of databases
    3. Select the database roles of public and db_owner.
  12. When you click OK, you will be asked to re-enter the new user’s password.
  • For detailed steps on creating a database user, refer to these instructions: http://msdn.microsoft.com/en-us/library/aa337545%28v=SQL.100%29.aspx

    • SQL Server Authentication Mode

    The Microsoft SQL Server Authentication mode must be set to SQL Server and Windows Authentication. (If the authentication mode is set to Windows Authentication only, you will not be allowed to log onto the SQL Server database with the designated database user.)

    To change the Server Authentication mode in SQL Server 2017, follow these steps:

    https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode

    For detailed steps on to do this in other versions of SQL Server, you can link to those instructions from this webpage.

    Create an Oracle Schema

    Since the process of creating new databases can be done in a variety of ways within Oracle, a step-by- step guide is not provided here. Rather, it is described at an abstract level and you may need to consult your DBA to complete this task.

    Prior to installing Hubble, you need to either create a new, empty Oracle database or a new schema within an existing Oracle database. No tables need to be created at this time; the Repository will be populated during the software configuration process.

    Create a New Library/Schema in IBM DB2

    Depending on the version of DB2 for i (formerly AS/400) you are in, the terminology will be different; what was called ‘library’ in older versions is now called ‘schema’ in newer versions.

    There are two ways in which you can create the library/schema with a SQL collection, either via SQL or the iSeries Navigator. In either case, the Object Repository requires that Journaling be enabled for the library/schema. This is because the database must allow support for database transactions.

    Option 1: Create the library/schema using a SQL command:

    1. On the AS/400, use the CREATE COLLECTION function. (Do not use the CRTLIB command.)

      2. Example: Create a library/schema called REPOSITORY:

      CREATE COLLECTION REPOSITORY

    Option 2: Create the library/schema using the iSeries Navigator:

    1. Right-click on the library/schema selection.
    2. Select New Library/New Schema.
    3. In the New Library/New Schema dialog, add a name for the new library/schema.
    4. In the list of options:
      1. For older iSeries versions, be sure to activate the option to Create as a SQL collection.
      2. For newer iSeries versions, be sure to uncheck the option to Create as a standard library.
    5. Click OK and the library/schema will be created.

    Database Connections for Oracle EBS

    Create Hubble Schema/Database User

    When creating a database connection for Oracle EBS a script must be run which will create a schema (database user) which will enable the Oracle EBS connection to be setup correctly, i.e. so as to provide access to EBS tables create the required views and functions.

    The script (script.sql) accompanies every EBS release as part of the installation. It is a lengthy set of SQL and PL/SQL instructions to be run by a DBA before a data source connection can be set up in Administrator and the Profile Wizard used.

    The database script is located in the Installation folder and can be accessed once the build is installed.

    To run the script:

    1. Open SQL Developer and connect to the database as 'SYSTEM' (password = 'Manager').

      Oracle 11i QA

      Hostname: ebs11qa (IP: 10.13.0.41)

      Port: 1521

      SID: QA

      Oracle R12 QA (DB version R12.1.3)

      Hostname: r12qa (IP: 10.13.0.43)

      Port: 1521

      SID: QA

      Oracle R12.2 VIS (DB version R12.2.4)

      Hostname: r12vis (IP: 10.13.0.45)

      Port: 1521

      SID: VIS

    1. Copy and paste the entire script into the connection window
    2. Select All and then Run Statement (Ctrl + Enter).
    3. Several fields must then be completed as follows:
      • Username - e.g. Q2015_1_40_076, Q2015_1_0_580
      • Enter Insight Password - (which is the same as username)
      • Enter existing Insight username to copy grants from - Leave it blank unless testing this feature
      • Enter - SYSTEM
      • Temporary tablespace - TEMP
      • Name to run script under - SYSTEM
      • Password - Manager
      • TNS_ADMIN entry - <blank>

        • After a moment, the following prompts will be displayed:

      • Create Index on FND_TABLES and FND_COLUMNS Y/N? - Y
      • Create indexes on FA_BOOKS and FA_DISTRIBUTION_HISTORY Y/N? - Y
      • Create indexes on PO_HEADERS_ALL and PO_LINES_ALL Y/N? - Y
  • Once the script is complete. check that the output is error free.

    • Database Connections for Oracle Active Data Guard (ADG)

    Hubble supports the use of an Oracle Active Data Guard (ADG) environment as the reporting DB connection. This allows the DB reporting overhead to be offloaded from the production environment onto an ADG environment copy of the DB.

    Configuring Hubble for an ADG Environment

    1. Oracle DBA - Create Temp Table Connection User. Create the Hubble temp table user on the DB which will be used for the Temp Tables using Script_Remote_Temp_Tables.sql. This will create the remote user used by the DB link which will allow Hubble to create Temp Tables
    2. Oracle DBA - Create DB Link- Create a DB link on the production DB to the Temp Table DB. This will be replicated onto the ADG environment and will be used to create temp tables when Hubble connects to the ADG environment. Provide the Hubble Administrator with the DB Link name.
      • Create public database link:
        mylink
      • Connect to:
        remote_username
      • Identified by:
        mypassword
      • Using:
        'myserver:1521/MYSID'.
    3. Oracle DBA - Create the Hubble Production Connection User. Run the script.sql on the Production DB to create the reporting connection user that will be replicated to the ADG environment and used by Hubble to run queries. After running script.sql, existing ADG connections will not function correctly until the validations actions from profile creation step of this guide are performed.
    4. Hubble Administrator - Build Hubble Repository. As described previously under Installation The repository can sit on one of our supported DB types e.g. Oracle, SQL Server. It cannot be on the ADG environment but could be on the Production, Temp Table DB or another DB.
    5. Hubble Administrator - Create a new connection with an Oracle ADG type. This will request details for the Production server details, the ADG server details and the Temp Table Link Name provided by the DBA. Refer to Creating a New Connection for further details.
    6. Hubble Administrator. Create a new Profile using the Profile wizard with the new ADG connection. Refer to Creating New Profiles for further details.