mO SharemO Share

We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!

Configuring the Cube Manager

Owned by Aparajita Basu Roy
Last updated: Mar 05, 2024
3 min read

 

The Cube Manager now needs to be configured after the version update to Ginesys 11.145.9.

IMPORTANT

Note:

  1. Oracle Enterprise Edition is not supported. The Ginesys Version will not be updated in this case.

    1. There may be other reasons for the software version not being updated.

  2. Custom logic, if applied, in generic cubes will be overwritten with generic behavior; if required the custom logic has to be re-applied with the help of Ginesys Care.

  3. Schedules already defined for Cubesets will be terminated and have to be re-scheduled after Cube Manager setup is done.



 

Configuration /Setup of Cube Manager

  1. Clients who wish to implement Cube Manager in Ginesys Database Server itself can use the  /wiki/spaces/SUP/pages/1388085417 

    1. 1 (One) Connection Model can be created by clicking on the check-boxes – Same as Ginesys Database Server; this will ensure that the same server name appears in both Cube Read Database and Cube Write Database connections.

      Steps to Configure:


      1. In Cube Read Database check the box - Same as Ginesys Database Server.          

      2. In Cube Write Database check the box - Same as Ginesys Database Server.

      3. Click on Configure button on bottom left of window to save, test connection and configure the new Cube Manager.


  2. Ginesys Users implementing Cube Manager in a separate database server apart from the Ginesys Database Server will use the/wiki/spaces/SUP/pages/1388085417 – where the Cube Write Database server is separate from Ginesys Database Server.

    1. There are two databases – Ginesys Database Server (live database) and another reporting database server where all the reporting data is written.

    2. The data for report generation is read from Cube Read Database and reflected in the data of the reporting server at the time of cube refresh.

    3. In this case, users will specify Cube Manager server name as Cube Write Database, Ginesys Database Server Database in Cube Read Database.

    4. Steps to Configure:

      1. In Cube Read Database check the box - Same as Ginesys Database Server.          

      2. In Cube Write Database provide the Host, Port (1521), Service etc.

      3. Now click on the Test Connection button. If your connection details are successful, then the message shows - Test Connection successful.

      4. Click on Configure button on bottom left of window to save the connection and configure the new Cube Manager.

    5. Important Note: Although 2 (Two) Connection Model with separate Read database is possible, Ginesys does not recommend this model as it does not provide much performance optimization.

  3. Clients who wish to implement independent Cube Manager report database along with separate servers for Stand-by database and Ginesys Database Server, i.e. /wiki/spaces/SUP/pages/1388085417 will have to mention separate Cube Read Database connection and Cube Write Database connection for Cube Manager.  

    1. Steps to Configure:

      1. In Cube Read Database provide the Host, Port (1521), Service etc.

      2. Now click on the Test Connection button in the 2nd section. If your connection details are successful, then the message shows - Test Connection successful.

      3. In Cube Write Database provide the Host, Port (1521), Service etc.

      4. Now click on the Test Connection button in the 3rd section. If your connection details are successful, then the message shows - Test Connection successful.

      5. Click on Configure button on bottom left of window to save the connection and configure the new Cube Manager.





To go back to the main page click on Managing the Cube Manager