Hyperion 11.1.2.x and EPM products logging level settings

During our 11.1.2.4 config, we had to update the logging.xml file for our Hyperion products.  Some settings that we came across helped us with troubleshooting Hyperion issues.

Below is the navigation path and what each setting means:

1 - Navigate to your Oracle Home Middleware location.  In my case i have it on my E drive
E:\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers

Then navigate to the product that you want to apply the settings for, such as:

Shared Services and EPM Workspace -> FoundationServices
Essbase Administration Services -> EssbaseAdminServices
Provider Services -> AnalyticProviderServices
Reporting and Analysis Framework -> RaFramework
Financial Reporting -> FinancialReporting
Financial Management -> FMWebServices
Planning -> Planning

1. Open logging.xml file in a text editor such as Notepad
2. Scroll down to the section starting with <loggers>
3. Change NOTIFICATION to any of the following logging levels.  NOTE, you will need to restart the services for the product that you are making changes to the settings.

Message Type	Level	Description
INCIDENT_ERROR	1	A serious problem that may be caused by a bug in the product and that should be reported to Oracle Support.  Examples are errors from which you cannot recover or serious problems.
ERROR	1	A serious problem that requires immediate attention from the administrator and is not caused by a bug in the product.  An example is if Oracle Fusion Middleware cannot process a log file, but you can correct the problem by fixing the permissions on the document.
WARNING	1	A potential problem that should be reviewed by the administrator. Examples are invalid parameter values or a specified file does not exist.
NOTIFICATION	1	A major lifecycle event such as the activation or deactivation of a primary sub-component or feature.  This is the default level for NOTIFICATION.
NOTIFICATION	16	A finer level of granularity for reporting normal events.
TRACE	1	Trace or debug information for events that are meaningful to administrators, such as public API entry or exit points.
TRACE	16	Detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem.
TRACE	32	Very detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem.