Introduction
The CXO-Cockpit Data Warehouse Adapter is meant to replicate data that is not in the source system for example an excel sheet with data. This data can be loaded via the Data Warehouse Adapter into an CXO OLAP Cube. The OLAP Cube is then used as main source for reporting in the CXO-Cockpit. The normal reports can be used to analyze and categorize the uploaded data. In this way powerful analyses can be made on additional information that normally is not loaded in the source systems. It is easy to access and maintain. The Data Warehouse Adapter has the following process:
- Copy or load data from a sheet into a Data Entry template.
- Save the data input into the Fact Database
- Processing the CXO OLAP Cube with the data from the Fact database
- Data is visible in the reports
Architecture
...
Configuration
For the Data Warehouse Adapter it is required to setup the Dimension Mapping. The Dimension Mapping maps the Standard CXO-Cockpit Dimensions to the OLAP Dimensions of the Source System.
Next to the Dimension Mapping setting the Period Frequency is a mandatory step during the initial roll-out of the Data Warehouse Adapter. You need to define the Period dimension members to be used and map them to the parent members of the Period hierarchy.
...
Introduction
The OneStream Adapter integrates with OneStream XF via the Marketplace XF. This is done by exporting the data and Metadata from OneStream via the Adapter API to make it visible in CXO.
Architecture
Configuration
Additional notes:
- CXO OneStream Dashboard is a custom business rule loaded within the OneStream environment, which is hosted on Microsoft Azure.
- The CXO OneStream Dashboard initiates a connection with the CXO software running within the TMF corporate network.
- The CXO OneStream Dashboard sends both metadata and data to the CXO OneStream Adapter API.
- All communication is sent over secure channels (HTTPS)
- To ensure that only the CXO OneStream Dashboard is able to call the CXO OneStream Adapter API the API is protected with the OpenID-Connect protocol, using the Client Credentials scenario. This works as follows:
- In the CXO Identity Provider a set of client credentials – client ID and client secret – is created specifically for the CXO OneStream Dashboard.
- The credentials are configured in the CXO OneStream Dashboard.
- The credentials are used to retrieve an access token for the CXO OneStream Adapter API. The token is valid for one hour.
- The access token is sent along with every request to the CXO OneStream Adapter API. The API validates the token to make sure the request is coming from a trusted source.
- To completely configure the CXO OneStream Dashboard it requires four settings:
- Public URL to CXO Identity Provider
- Public URL to CXO OneStream Adapter API
- Client ID
- Client secret
...