Hyperion Documentation

Employees may leave their job for whatever reason, so it is important to keep your Hyperion environment documented and up-to-date.  This information shouldn’t change significantly, but sometimes there is a datacenter move, upgrade or company policies may require a password change. 

The most crucial information to keep track of and updated are the admin and user accounts that were used to install and configure Hyperion.  This would include the Windows/Unix account, database account (or schemas), the WebLogic account created during Hyperion setup, the Hyperion admin account, and external directory account such as MSAD. 

The server account is important because Oracle recommends any time that Hyperion needs to be reconfigured, it should be done by the same account that was used to install and configure Hyperion.  This is especially true on Unix/Linux systems where the user account used to install Hyperion has special permissions that other users don’t.  And sometimes it’s necessary to re-run the configurator because of patching or an issue comes up that requires reconfiguration. 

Database accounts need to be documented and maintained because this can be necessary to collect data for troubleshooting.  When submitting an Oracle ticket, Oracle will often ask for a zip file generated by their RDA utility and they may ask for information from the database.  If the option is specified from RDA to collect database information, it will ask for the database password.  Another occurrence that database information is necessary is if passwords need to be changed due to company policy, these passwords need to be updated in Hyperion.  It’s important to understand which product belongs to which database or schema. 

Finally, another account that is rarely used but should not be forgotten is the WebLogic account.  WebLogic is an integral part of Hyperion and sometimes tuning or troubleshooting is required within WebLogic itself.  I have seen many cases where WebLogic was causing problems or tuning needed to be done within WebLogic, but the client did not have the WebLogic account.  If this is the case, WebLogic and Hyperion web applications must be reconfigured with a new password which costs extra time. 

Although documentation gets treated as a secondary part of the process, it is best done during the installation and implementation.   The benefits to doing the documentation is not limited to what is referenced above, having the information will support troubleshooting, efficiency and consistency, training, and understanding.

Benjamin Johnson

Senior IT Consultant – The EGP Family of Companies