Financial Performance Management Application Logs

Planning Logs

Default Log Location	Log File Name and Contents
C:/MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/Planning0/logs	Planning_ADF.log—ADF (Oracle Application Development Framework) information You cannot delete this log while the Oracle Hyperion Planning server is running. The log is recreated if the server is restarted.
EPM_ORACLE_INSTANCE/diagnostics/logs/planning Logs in this folder can be deleted.	UserProvisionSync.log—Security refresh information, such as provisioning or "user not found" issues Use this log to troubleshooting synchronization issues between Planning and Oracle Hyperion Shared Services. Planning utility logs—A log for each Planning utility

To change the logging level for a Planning application server:

1. Log in to a Planning application as the administrator or owner.

2. Select Administration, then Application, and then Manage Properties.

3. Select the System tab.

4. Set DEBUG_ENABLED to true.

5. After changing log levels, restart the Planning application server for the changes to take effect.

Financial Management Logs

Table 3-15 Financial Management Log Files

Component	Default Log Location	Log File Name and Contents
Oracle Hyperion Financial Management	EPM_ORACLE_INSTANCE/diagnostics/logs/hfm	xfm.odl.<APPLICATION_NAME>.log—Financial Management Application Server core activity (per application) oracle-epm-fm-hsx-server.log—Financial Management Java Server log oracle-epm-fm-bi-publisher.log—Logs for Financial Management to BI Publisher interaction oracle-epm-fm-hsx-registry.log—Logs for Financial Management to Shared Services Registry interaction oracle-epm-fm-lcm-client.log—Logs for Financial Management to Oracle Hyperion Enterprise Performance Management System Lifecycle Management interaction SharedServices_Security.log—Logs for Financial Management to Shared Services Security API interaction Note the following: UsedCPU=n.nnnnn;—total processor CPU usage (sum of all processes CPU usage); ProcUsedCPU=n.nnnnn;—current XDS process CPU usage;
Financial Management Web Application	MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/HFMWeb0/logs/hfm MIDDLEWARE_HOME/user_ projects/domains/EPMSystem/servers/HFMWeb0/logs/	oracle-epm-fm.log—Financial Management Java web application activity oracle-adf.log—Financial Management ADF logs HFMWeb0.log—Financial Management domain logs HFMWeb0diagnostic.log— Financial Management domain diagnostic logs oracle-jrf.log—Financial Management JRF logs
Financial Management Web Services	MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/HFMWeb0/logs/hfm	epm-fm-webservices.log—Oracle WebLogic Server web service activity for Oracle Hyperion Financial Close Management

Profitability and Cost Management Logs

Table 3-16 Profitability and Cost Management Log Files

Default Log Location	Log File Name and Contents
Oracle Hyperion Profitability and Cost Management: MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/Profitability0/logs	hpcm.log—Profitability and Cost Management activity

Creating a Separate Log File for Persistence Messages

For Oracle Enterprise Performance Management System instances installed as compact deployment, messages from other installed EPM System products are also directed to the hpcm.log file. The logging.xml file can be edited to redirect these messages to a new log file called persistence.log. You may find advantage in splitting the persistence messages to a separate log file even for standard deployments. For compact deployments, the logging.xml file is located at <MIDDLEWARE_HOME>\user_projects\domains\EPMSystem\config\fmwconfig\servers\EPMServer0. For standard deployments, the logging.xml file is located at <MIDDLEWARE_HOME>\user_projects\domains\EPMSystem\config\fmwconfig\servers\Profitability0.

To create a separate log file:

1. Edit the logging.xml file and define a new log handler within the <log_handlers> section. Here is a suggested definition for a new handler:

   <log_handler name="persist-handler"
   class="oracle.core.ojdl.logging.ODLHandlerFactory">
   <property name="path"
   value="${domain.home}/servers/${weblogic.Name}/logs/persistence.log"/>
   <property name="maxFileSize" value="20000000"/>
   <property name="maxLogSize" value="100000000"/>
   <property name="useSourceClassAndMethod" value="true"/>
   </log_handler>

2. Alter the logger for org.eclipse.persistence in the <loggers> section to point to the new handler, as in the example below, where the handler name has been changed from epmpcm-handler to persist-handler.

   <logger name="org.eclipse.persistence" level="NOTIFICATION:16"
   useParentHandlers="false">
   <handler name="persist-handler"/>
   </logger>

Financial Close Management Logs

The default location for these Financial Close Management logs is MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/FinancialClose0/logs:

• FinancialClose0.log—Close Manager web tier activity

• FinancialClose.log—Close Manager activity

• FinancialClose0-diagnostic.log—Close Manager web tier activity, with more diagnostic messages than FinancialClose0.log

• AccountReconciliation0.log—Account Reconciliation Management web tier activity

  Note:

  If Account Reconciliation Management is deployed to same server as Financial Close Management, you might not have AccountReconciliation0.log.

• AccountReconciliation.log—Account Reconciliation Management activity

Tax Management Logs

Table 3-17 Tax Management Logs

Default Log Location	Log File Name and Content	Rotation
MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/TaxManagement0/logs	TaxSupplementalSchedules.log	maxFileSize = 10485760 bytes maxLogSize =104857600 bytes
MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/TaxManagement0/logs	TaxOperations.log	maxFileSize = 10485760 bytes maxLogSize =104857600 bytes
MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/TaxManagement0/logs/taxprov	oracle-epm-tax-prov.log	maxFileSize = 1000000 bytes maxLogSize = 5000000 bytes