Custom Hyperion Monitoring

The next step to proactively monitoring Hyperion after doing simple port monitoring is to simulate login behavior. Often, a service can be listening on the port, yet not responding. Only advanced monitoring can detect this. Advanced monitoring can be done with complex tools like Load Runner, but sometimes a simple script can replace expensive tools like Load Runner.


It is pretty simple to write some code that will simulate logging into workspace and generally validate other parts of the system.

Simulate Logging into Workspace: 


POST
/workspace/login
   sso_username=user
   sso_password=pw


Returns the SSO Token CDATA=..{SSO_TOKEN}....=


After parsing the SSO_TOKEN you can login to financial reporting with a POST to
   /hr/xml/HrConfig.jsp   passing in the sso_token variable 


Similararly, shared services can be checked in the exact same way, 
  POST to /interop/logon



Other simple pages to check using GET (no sso_token required)


/hfm/GlobalworkspaceNav/bpm/conf/HfmConfig.xml
/calcmgr/conf/CalcMgrConfig.xml
/HyperionPlanning/conf/HspJSConfig.xml



Once the basics are accounted for, even more complicated monitoring can be accomplished such as passing the sso_token to a smartcut to actually run a report. In this example it's best to have a test user set up in workspace where preview_pov is turned off, otherwise it will prompt for POV before displaying the report. 


For more details check out this post:
http://www.oracle.com/technetwork/oem/grid-control/overview/wp-ats-hyperion-load-testing-1-133775.pdf