{{Infobox
bodystyle = width:20em; |
title = Batch Loading for Hyperion Integration |
titlestyle = |
headerstyle = |
labelstyle = width:33% |
datastyle = |
image = !Hfmlogo_large.gif! |
imagestyle = |
header1 = |
label1 = Type |
data1 = CXO-Cockpit Process Automation |
header2 = |
label2 = Audience |
data2 = CXO-Cockpit Captain |
header3 = |
label3 = Dificulty |
data3 = Medium |
label4 = Applies to |
data4 = Hyperion Enterprise & Hyperion Financial Management |
Introduction
Source system integration is by default a manual process. With the CXO-Cockpit batchloading functionality it is possible to schedule a source system dataload using a timely interval. Using this functionality it will be possible to have the CXO-Cockpit data updated every week, every night or twice a day.
Pros and Cons
The most important benefits are:
- CXO-Cockpit is almost always up to date
- When the Captain forgets to start the update, it will be still executed at night
Some disadvantages are:
- Data is almost up to date, but not live.
- If the scheduling is done on a regular interval, you are lacking control over the timing of data refresh. This can be an issue when data is not ready for analysis.
Technical Process
- Extract from source system into staging database
- Process the data
- Process the cube
Source Systems
With the following source systems it is possible to configure a batch load:
How to configure the batch load
- Configure and schedule an Autopliot routine (Hyperion Enterprise only)
- Create a batch (.bat) file (see the source systems for exact commands)
- Schedule the task using the Windows Task Scheduler