Installation
Update CXO to version 20.4.??? (or higher)
Install Identity Provider (Restart server after installing .NET core hosting bundle)
Install Oracle EPM Cloud Adapter
Install pre-requisites .NET 5.0 Hosting Bundle:
https://dotnet.microsoft.com/download/dotnet/5.0Run installer
Create IIS website for Oracle Epm (Application Pool should have "No Managed Code")
Create Client in CXO Identity Provider
Identity Provider configuration
Create new Generic Client
Check “Allow Offline Access” checkbox
Add Following Scopes:
User profile
User groups
Add Redirect url(-s) in following format {OraclEPMAdapterUrl}/signin-oidc
Add Post Logout Redirect URI’s in following format {OraclEPMAdapterUrl}/signin-oidc-auth
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
SSAS cube
Run configuration database creation command: e.g.
.\CXO.Adapter.OracleCloudEpm.Cli.exe create-configuration-db server-name:cxo-dev-sql02 database-name:oracleEpmConfigTest authentication-type:Proprietary username:cxo password:somePassword
Parameters:server-name: name of the server on which the database should be created
database-name: name of the database to be created
authentication-type: windows / proprietary
username: SQL user name (if authentication-type == proprietary)
password: SQL user password (if authentication-type == proprietary)
See CXO.Adapter.OracleCloudEpm.Cli.exe help for detailed description of the command
Run set-authentication-settings command:
e.g. .\CXO.Adapter.OracleCloudEpm.Cli.exe set-authentication-settings idp-authority:https://cxoUrl/idp idp-client-id:clientId idp-client-secret:secret
See CXO.Adapter.OracleCloudEpm.Cli.exe help for detailed description of the command
Run create-source-in-adapter command
e.g. .\CXO.Adapter.OracleCloudEpm.Cli.exe create-source-in-adapter source-type:pbcs source-name:source factdb-name:factdb-name factdb-server:factdb-server factdb-authentication-type:1 ssas-server-name:ssas-server-name ssas-database-name:ssas-database-name ssas-cube-name:ssas-cube-name
Important: The name of the source should be the same as name of the source in CXO
See CXO.Adapter.OracleCloudEpm.Cli.exe help for detailed description of the command
Restart IIS Application Pool for Oracle EPM Adapter
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
Configure data export job
See sections below for more details
Configure metadata export job
For Gjensidige, there should already be a metadata job defined for the old adapter. We could reuse that, if there are no weird values.
Steps to perform:
Go to Overview screen
2. Go to Dimensions tab, click Export button on the right.
3. On the export metadata screen you will see the existing CXO job, might be others as well.
a. Review existing job, if there are no weird values we can reuse it. (all delimiters should be same)
b. If needed, create new job. See two screenshots below
Configure data export job
For Gjensidige there will not be a data job yet, so it needs to be created.
Go to the Overview screen
Choose Export Data in the dropdown on the right side of the screen
Create a new data job
Specify the following values:
Location: Outbox
Pick right cube
Choose a delimiter, preferably set it to “Other” and use “|”
Smart Lists are not used currently
Dynamic Members: Exclude
Decimals: none (or discuss with Gjensidige
Slice definition: take Account on rows, Period on columns, set default slice values for all dimensions incl. POV. Note: this configuration will not be used in the actual data extraction, as it will be input to the job API call.
Oracle EPM adapter configuration
For Gjensidige: Check the old PBCS configuration for connection info, dimension mappings etc.
Set up connection information (see old PBCS)
Map the Oracle dimensions to CXO dimensions (see old PBCS)
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
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)
Location of the log files:
CLI command {CXO-Installation-Dir}\Oracle Cloud EPM Adapter\Extraction\logs
Web application {CXO-Installation-Dir}\Oracle Cloud EPM Adapter\Web API\logs
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.