Versions Compared

Version Old Version 13 New Version 14
Changes made by

Maarten Schilt

Tomasz Marcula (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Installation

  • Update CXO to version 20.4.??? (or higher)

  • Install Identity Provider (if not already installed) ===> not for first installation at Gjensidige

  • Install Oracle EPM Cloud Adapter

    • Install pre-requisistes: .NET 5.0 runtime => FIND URL

    • Run installer

  • Create IIS website for Web API

Identity Provider configuration

Not for first installation at Gjensidige

CXO configuration and source creation

  • Configure proper license key

    • Based on the client’s source, generate the right key using the License Key generator: Oracle EPM Planning / Oracle EPM Financial Consolidation and Close.
      Path to generator: \\cxo-fileserv\Data\Internal Tools\(not-released) LicenseKeyGenerator for B Licenses (with Oracle Cloud EPM adapter)

  • Create a new source system in the SSM for the correct source type: Oracle EPM Planning / Oracle EPM Financial Consolidation and Close. This should create:

    • Fact database

    • Oracle EPM configuration database

    • SSAS cube

  • Configure connection string to configuration database in appsettings.json for CLI/WebApi

  • Run database migration command on CLI: CXO.Adapter.OracleCloudEpm.Cli.exe migrate-database

  • (While story for bootstrapping a source in the adapter is not yet done):

    • Create a source record in the Source table in the configuration database

    • Create default dimension mapping records in the Dimension Mappings table in the configuration database

...

  • Run metadata extraction

    • Command:
      CXO.Adapter.OracleCloudEpm.Cli.exe extract-metadata source:<source-id-here>

    • Review hierarchies, add metadata filters for members that should be excluded from extraction

  • Run data extraction

    • Command:
      CXO.Adapter.OracleCloudEpm.Cli.exe extract-data source:<source-id-here> period:Jan year:FY2021 scenario:Forecast

  • Process cube from SQL Server Management Studio

Logging

  • The log level can be set in appsettings.json in "LogLevel" property (Both Web project and CLI project have own appsettings.json file)

  • Log files are split into two file types

    • nlog-all -contains cxo defined logs and logs generated by other Microsoft libraries. Usually it is more verbose

    • nlog-own-detailed -contains logs defined by cxo with more detailed information then info in “nlog-all“ and additionally filters logs created by Microsoft libraries.

  • Logging to the console in CLI tool

Changing log level influence not only logs level saved in the files but also information written to the console.