Prior to Installation

This section provides detailed instructions and essential steps to follow prior to installing the new version of Hubble Desktop. It covers the backup processes for the Object Repository and Budgeting/Planning data, as well as the creation of new databases, schemas, or libraries to ensure a smooth and successful upgrade.

Hubble Object Repository

Hubble Desktop is a Microsoft .NET Windows application that operates under a two-tier architecture. The application has its own built-in database connectivity layer, which submits queries directly to the ERP database, independent of the ERP application. The software configuration and inquiry parameters are stored in a centralized database, known as the Object Repository, created during the initial installation.

All persisted information for Hubble is stored centrally in the Object Repository, including but not limited to:

• Report Definitions:

  • Hierarchies

  • Formatting

  • Calculations

• Profile Definitions:

  • ERP Table mappings

  • ERP Environment Information

  • Hubble Configuration options

• User Definitions:

  • ERP Username

  • User Capabilities

  • User Permissions

The Object Repository is hosted on the customer database (MS SQL, Oracle, iSeries). The object repository data should be included in the customers daily database backup schedule. For convenience, the object repository data will be backed up from within the current Hubble Administration tool into a backup file, which will be used later to restore into the new versions separate Object Repository.

Object Repository Backup Process

1. Log in to the Hubble Administration Tool for your current Hubble application.

2. In the Main tab of the Hubble Administration Tool, locate the second line that establishes a connection to your object repository. This may have a client-specific name or be titled Repository Database Connection. Expand this item to see your object repositories listed.

   The following screen shot is an example; your object repositories will be named according to your naming convention.

   

3. Select the current object repository that you want to back up for the upgrade.

4. From either the ribbon or the right-click menu, select Login.

   

5. In the Repository Login dialog, enter the login name and password specified for an administrator user.

6. Click Login. The Repository icon will change from grey to yellow if the login credentials are correct.

7. Once logged in, navigate using the icons in the left-hand panel or double-click on folders in the right-hand panel as necessary.

8. Select the repository you wish to back up and click Backup on the Ribbon, or right-click on the repository and select Backup. Depending on the amount of data in your repository, where the data is being backed up to, and other factors, this process may take several minutes to several hours.

   

9. You will be prompted to save the RDF file to the location of your choice.

Tip: It is recommended to save the backup files in a designated backup folder and include specific repository information (such as the repository name) in the file name for easy identification.

In later versions of Hubble , the following message is displayed when the backup is complete:

Budgeting/Planning Backup Process (if Budgeting/Planning are used)

1. If still logged into the Administration Tool, continue to step 2. Otherwise, follow steps 1 through 4 under Object Repository Backup Process to log into the Administration Tool again.

2. Expand Data Sources and highlight Profiles.

3. Right-click on the specific profile that has the budget database defined that needs to be backed up.

4. Select Backup Budget Database.

   

5. Windows Explorer will prompt to save the Budget Database in a specified location. The Budget Database file will be saved with a .bdb file extension. As with the object repository, this process may take several minutes to several hours.

6. Once completed, an Information dialog will notify that the Budget Database has been successfully backed up.

Create a new Database, Schema, or library for the new Object Repository

To keep the new version of the object repository separated from the current version, it is recommended that the database administrator (DBA) create a new database, schema, or library to host the new versions object repositories tables.

Details on the requirements to create a database, Schema or Library can be found in the ERP Database Connections section of the Administration and Configuration Guide for the version of Hubble you are installing, as referenced in the Additional Resources section.

The database user account used by Hubble to connect to the database, Schema or Library must have database permissions to allow Hubble to create and update the object repository tables in the new database, schema or Library.

After this has been created, the DBA will need to write down the connection details to the new Database, Schema or Library for you/the Hubble Administrator. The details should include:

1. Server type (Microsoft SQL Server, Oracle, or IBM DB2)

2. Server name or ip address (aka Host Name in IBM DB2)

3. User name and password (or schema name and password)

4. Database name (if using Microsoft SQL Server)

5. Service name or SID, plus the port number (if using an Oracle server)

6. Default Library and Library List (if using an IBM DB2)

Create a new Budgeting Database, Schema, or library (if Budgeting/Planning is used)

Before upgrading, a database administrator must create an empty database, schema, or library for the budget repository (separate from the Object Repository). This Budget Database is used to hold records of budgeting data, history, setup information, workflow status, and data entry tables. The Budget Database is required for those implementing Budgeting or Strategic Planning functionality.

Details on the requirements to create a database, schema, or library can be found in the Budget Database Setup section of the Budgeting and Planning Guide for the version of Hubble being installed, as referenced in theAdditional Resources section.

After this has been created, the DBA will need to provide the connection details to the new database, schema, or library to the Hubble Administrator. The necessary details are documented in the section titled "Create a New Database, Schema, or Library for the New Object Repository."

Additionally, Hubble Planning allows users to create forms in DX (Designer Express) using data from any JDE table. If this functionality is used, there may be custom planning tables in the current budgeting database. Because they are custom, Hubble will not create the tables automatically for the new version. Therefore, it is necessary to work with the DBA to create the custom tables in the new budgeting database. If unsure whether custom planning tables are being used, below is a list of the standard budgeting tables. Provide this list to the DBA to ascertain if custom tables are being used. If they are, request that those tables be manually created in the new database. Any tables that exist in the budgeting database other than the tables listed below are custom.

Table 1: Standard Hubble Budgeting Tables

Note: If upgrading from a version prior to 2015.1 with Budgeting, create a support case and request an upgrade of the budget database to 2015.1. Significant changes in version 2015.1 make this step mandatory to ensure the budgeting tables properly upgrade to later versions.