Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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

Oracle EPM system configuration

  • Make sure we have an account that we can use to connect from the adapter to the Oracle system

  • Configure metadata export job (not needed for Gjensidige, use the current values for metadata settings)

  • Configure data export job

    • Define file structure for exported data file

Oracle EPM adapter configuration

  • For Gjensidige: Check the old PBCS configuration for connection info, dimension mappings etc.

  • Set up connection information

  • Map the Oracle dimensions to CXO dimensions

  • Set default properties for metadata extraction: delimiters, job name, aliases

  • Configure data extraction settings

    • Set default properties: delimiters, job name

    • Set file structure, matching the configuration in the Oracle EPM system

      • Put it in the database in Source table: row, then column, then POV in order

    • Set data filters

      • 1 member expression per mapped dimension in DataFilters table, excluding period, year and scenario

  • Run metadata extraction

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

  • Run data extraction

  • Process cube from SQL Server Management Studio

  • No labels