...

Cluster

Enter here the name of the HFM cluster registered on the CXO-Cockpit application server. Registering the cluster can be done with the HFM Windows Client that must be installed on the CXO-Cockpit server. Note that the cluster-name is not (always) equal to the name of the HFM Application Server. Ask your HFM Administrator for further details.

...

• It must be provided (have access to) the HFM application that will be used;
• Within this application it must be able to read all meta-data and data;
• It must be able to run Extended Analytics.

If these requirements are not met, extractions will fail.

...

Enter the name of the DSN (Data Source Name) that will be used for feeding the extracted data into the correct CXO-Cockpit database. Entering and registering a DSN must be done on all HFM Application Servers that are part of the Cluster.

...

The actual data and meta-data extraction using Extended Analytics is done by the ETL Tool (CXO_Cockpit.exe). This tool is not installed via the CXO-Cockpit installer and must be copied to a certain location, usually ..\Program Files\CXO Solutions\. Here you can enter the path where this tool can be found.

...

One of the options for Extended Analytics is to exclude the extraction of dynamic accounts (accounts defined in HFM with the DYNAMIC attribute). Dynamic accounts can be based on complex calculations which may involve multiple sub-cubes. Extracting this type of accounts can sometimes be very time-consuming and can cause a serious perfomance drop on the HFM Application servers. Unless you absolutely need dynamic accounts, it is advisable to tick this exclude checkbox. Note that we offer a powerful and easy-to-use method to define dynamic accounts within the CXO-Cockpit Design Studio (/wiki/spaces/CXO62/pages/105733568Cube Calculations).

Check data for Org. by Period

...