Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« FCCS: A Strategic Approach to Cost Effective Financial Close | Main | Action framework - An exciting feature of OBIEE »

Exploiting Hyperion for Scheduling Jobs !!

Problem Statement:

Have you ever faced a need to call batch files to update EPM system but no access to the server / environment ??

Windows task scheduler is disabled in Hyperion environment. Application backups are being manually triggered through batch scripts and there is a requirement to have it automatically scheduled for a particular time during the night, when none of the business users are accessing the application for development. The solution would be applicable for Hyperion version & later.


Solution Provided:

Conducted successful POC for multiple application backups through batch scripts scheduled in Hyperion workspace and ODI.


For Workspace:

1.      Create a Generic Job Application in workspace, enter the required parameters & click OK.

2.      Make sure, the MIME Type for (.bat) is predefined in Hyperion Workspace. If found missing, we need to add it manually to the existing list of MIME types.

3.      Now, import the batch script in the "Explore" menu of workspace as a Generic Job & select the created generic application in the dropdown.

Scheduling Process in Workspace:

1.      We can now test the batch file execution by a right-click on the Job Name & "Run as Job". Provide a path for output & click "Run"

2.      If successful, we can add a schedule to it, again by a right-click on the Job Name. Define the execution parameters & click "Finish".


For ODI:

1.      Create an ODI Package using Package Editor. Add an OS Command tool from the list of integrator tools available.

2.      Specify the location of batch script in the OS Command defined for the package.

Scheduling Process in ODI:

1.      Add a scenario to the package created for the backup.

2.      Under the scenario, right click on "Scheduling" and add a schedule.

3.      Define all the scheduling parameters, the logical agent and log level.

4.      To apply scheduling, we need to update schedules for the logical agent defined for the package.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles