Today I am going to look at using ODI to control running of the batch client and add in some error handling functionality. Unfortunately there are no adaptors or API available to use with ODI and EPMA so I am going to use the OS command tool to run the EPMA batch client.
Today I am going to look at automating the process using the EPMA batch client and then move on to using ODI to take over control.
Now you don’t have to use ODI as other methods could be used to populate the tables but I am going to use it as it offers such flexibility around transformations and automation in a controlled environment.
At first there was only Smart View available as a standalone installer, no Excel add-in, Financial Reporting Studio, EAS or Essbase Studio console installers were available.
It wasn’t until a patch release in 184.108.40.206 that the Excel add-in was made available as a standalone installer.
I ended up with a set of tables ready to be populated with metadata though I am not going populate them just yet as I think it is worthwhile running through an interface import profile first.
In this part I want to look at interface tables and end up with them built ready to load metadata into.
It is not just a case of updating Smart View as the essbase server and APS need to be patched to 220.127.116.11.102 be able to use this new functionality.
This is probably one of the few posts that I don’t have to spend hours taking screen shots and uploading them.