Assess Need for New Connections

• Use existing connections unless you are pointing to a new server, database, User ID/Schema/Library, or using budgeting.

• In these cases, create a new connection from scratch or copy an existing connection and update it with new information.

• If you do not need a new connection, move to the next section.

• It is possible to update existing connections, but it is recommended to rename the connection to avoid it being overwritten during future backups and restores before go-live.

• The restore process appends data, so it will not affect new connections and profiles, or those with new names, since they are not in the backup.

• However, it will overwrite any existing connections and profiles that have not been renamed.

• Details on how to create a connection can be found in the Data Sources section of the Administration and Configuration Guide for the version of Hubble you are installing, as referenced in the Additional Resources section.

• To create a new connection from an existing one, follow the steps below and use the same section of the guide for additional information on each field, as needed.

Create a New Database Connection from an Existing One (if necessary)

1. In the Hubble Administrator, on the Main tab, log into your repository if you are not logged in already.

2. Expand the Data Sources node in the left panel and select Connections.

3. In the right panel, select the connection you would like to use to create a new connection and from the right-click menu, select Copy.

   

4. In the white space below your connections, go to the right-click menu and select Paste.

5. On the “Copy of” connection, go to the right-click menu and select Rename. Rename it as desired.

6. Right-click again on your new connection and choose Edit.

7. Select Configure.

8. Make updates to the connection:

   1. On the new connection, go to the right-click menu and select Edit.

   2. Select Configure.

   3. Update the necessary fields with information obtained from your DBA:

      • SQL Database: Update the Server, User name, password, and/or Database.

      • DB2 Database: Update the Host Name (aka Server name), User name, password, Default Library, and/or Library List.

      • Oracle Database: Update the Host Name (aka Server name), Service Name or SID, Port, User name (aka schema), and/or password.

Create a New Budgeting Connection

• Create a new budgeting connection as part of the upgrade. This will prevent test and production budget data from being intermingled while you run production in parallel during testing.

• Use the instructions above along with the budgeting connection information provided by your DBA to create the connection.

• Confirm with your DBA that any custom planning tables from your current version have been created in your new budget database. This step is crucial to avoid errors that could prevent you from adding or updating profiles.