Hyperion Logging Level Increase

How to increase logging level for Hyperion Components. 

  How to Change the Logging Levels for Hyperion EPM Products in Release 11.1.2.x (Doc ID 1158016.1) 

Navigate to MIDDLEWARE_HOME/user_projects/domains/domain name/config/fmwconfig/servers/ Ex.: Oracle_Home\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers 

For the Product, select the corresponding managed server name: 

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 

Open logging.xml file in a text editor. 

Scroll down to the section starting with Change NOTIFICATION to any of the following logging levels: 

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. Save the logging.xml file and restart the service(s) for the corresponding Product. 

 More information about changing logging levels and management of log files can be found in Oracle Enterprise Performance Management System Installation and Configuration Troubleshooting Guide, available for download from EPM Documentation Library. 

 Thanks,

Mady

DRM URL not working in any browser after upgrading to 11.1.2.4.350

 Recently, I came across one issue while upgrading DRM from 11.1.2.4.346 version to 11.1.2.4.350.

DRM 11.1.2.4.350 version needs .Net Framework 4.7.2 as a pre-requisite for upgrade.

We have installed 4.7.2 version and tried to setup DRM 11.1.2.4.350 version.

Everything went well, but URL notworking at all in any browser even in IE. We will through Event logs, settings, Compared with Other systems. Nothing major we found. In Event logs, it's showing .Net framework setup not done properly. So, we removed .net and updated again after restarting Server. But same issue.

We tried below: DRM Uninstalled, and restarted server, then installed DRM again, still issue persist.

Tried with same as above with .net framework also, same results. same issue.

Now, after spending some more time, we found one error in Event viewer.

Error is referring that web.config file is having temp folder path which doesn't exist. I have removed that path and saved web.config file.

Now URL is working fine in all browsers.

Thanks,

Mady

IE supports Hyperion 11.1.2.4 ??

 IE supports Hyperion 11.1.2.4 ??

Yes, Microsoft going to stop IE support and pushing Microsoft Edge to all clients for better usage.

What about Hyperion? Yes, Hyperion Workspace URL doesn't work on Microsoft Edge or Google Chrome.

So, Our Next option is Patching....!!! ONE MORE OPTION IS THERE, WE CAN USE FIREFOX...!

For this update Oracle released patches, by applying below patches Hyperion Workspace URLs we can access using Microsoft Edge, Chrome also.

Customer Recommended Browser Support Added for Google Chrome and Microsoft Edge with EPM System Releases Beginning with Release 11.1.2.4 (Doc ID 2675883.1)

DETAILS

Please be advised that Oracle Hyperion Enterprise Performance Management System release 11.1.2.4 added browser support for Google Chrome and Microsoft Edge. You must update to the following supported releases:

Hyperion Shared Services 11.1.2.4.100+ (Patch 31319089. Use Patch 31574562 for release 11.1.2.4.9xx)

Hyperion Planning, Hyperion Capital Asset Planning, Hyperion Workforce Planning, Hyperion Project Financial Planning 11.1.2.4.009+ (Patch 29889455)

Hyperion Calculation Manager 11.1.2.4.014+ (Patch 28557058)

Hyperion Financial Reporting 11.1.2.4.712+ (Patch 30670918. Use Patch 30671119 for release 11.1.2.4.9xx)

Hyperion Financial Management 11.1.2.4.208+ (Patch 28511735)

Hyperion Financial Close Management and Hyperion Tax Governance 11.1.2.4.253+ (Patch 29060830)

Hyperion Tax Provision 11.1.2.4.202+ (Patch 25316913)

Hyperion Financial Data Management 11.1.2.4.220+ (Patch 25312033)

Hyperion Profitability and Cost Management 11.1.2.4.130+ (Patch 29461894)

Hyperion Workspace 11.1.2.4.825+ (Patch 31124100. Use Patch 31486872 for release 11.1.2.4.9xx)

Hyperion Data Relationship Management 11.1.2.4.350+ (Patch 31420887)

Additionally, you must also update Oracle JDeveloper / Application Development Framework 11.1.1.7.1 (Patch 31246831).

Workspace started support for Chrome and Edge browsers from PSU 11.1.2.4.825

- 31124100. This patch was made available from JUN-01-2020.

HFM PSU 11.1.2.4.208 was made available from JAN-07-2019.

HFM PSU 11.1.2.4.209 was made available from APR-09-2020.

Change the PSU accordingly in this document

EXCEPTIONS

Oracle JDeveloper / Application Development Framework does not apply to Hyperion Data Relationship Management or Hyperion Workspace.

Please see the Supported Platforms Matrix for a complete list of certified platforms.

Thanks,

Mady

Hyperion Weblogic Patching

 Patching must be go through Readme steps, but here we will see high level steps.

Download and copy weblogic patch into cache dir in below path: D:\Oracle\Middleware\utils\bsu\cache_dir

Go to path using cmd D:\Oracle\Middleware\utils\bsu and execute below command.

bsu.cmd -install -patch_download_dir=D:\Oracle\Middleware\utils\bsu\cache_dir -patchlist=FMJJ -prod_dir=D:\Oracle\Middleware\wlserver_10.3

We need to install this patch in all server, wherever we have domain deployed. 

Note: Stop all services before this patching. Check any WebLogic installed already in the system. If yes, remove that patch and then install above patch.

Thanks,

Mady

EPMA - Clustering - Load balance

How can we do EPMA Clustering / Load balance??

How to load balance EPMA server? Is it possible?

No, We can't load balance EPMA Server, you can configure EPMA dimension server and EPMA (other service name) in second node. 

EPMA Server must be in first server along with EPMA Data sync and EPMA Web Tier, in next server do not install EPMA Server, only select EPMA dimension server and EPMA Web Tier.

If we install itself, by default with configuration EPMA all 3 services will get created. So, needs to uncheck this while doing installation itself.

In case, if we install and configured all 3 services in both servers. Then stop or disable EPMA Server in second server.

Thanks,

Mady

How to change Essbase Arbor Path

 If you want to edit Arbor path in Configuration console, in case of wrongly updated or moving new drive, need to follow below steps to edit Essbase Arbor Path in Configuration console.

First execute below command which will enable config task for configuration again.

Go to this path using cmd Oracle/Middleware/user_projects/epmsystem1/bin

resetConfigTask.bat -product EssbaseServer -task RegisterEssbaseAsMultipleAgent

Then Launch ConfigTool again and check Essbase Server for configuration. Essbase Arbor path will be in edit mode, where you can change or update to new path. Execute configuration and check out Essbase path.

Copy applications from old path to New Arbor Path. Try to access those applications using EAS Console.

 Wrong ARBORPATH on Essbase Instance (Doc ID 1910743.1)

Thanks,

Mady

Hyperion SSL Implementation

SSL is important for security and sometimes needs to be implemented in Hyperion environment depending on an organization’s security requirements.  This can be expensive and time-consuming or simple depending on the implementation.

Hyperion has three ways of implementing SSL which are:

Full Implementation – implementing SSL in WebLogic, Oracle HTTP server, and IIS (if used).

OHS Implementation – implementing SSL in Oracle HTTP Server only.

Network Implementation – implementing SSL at the network level on a device such as a load balancer.

Full SSL implementation is the most complex setup and costlier since multiple certificates are needed.  Keystores need to be generated and managed, the OHS wallet needs to be managed, and a lot more configuration, testing, and troubleshooting are needed.  The benefit of a full implementation is that this is the most secure method.

OHS SSL implementation is simpler and requires minimal configuration.  The SSL certificate is managed in the OHS wallet and EPM configuration is relatively simple.  This implementation is less secure than a full implementation, but can still be secure if the Hyperion servers are isolated on their own subnet and access is only given to the OHS server.  Only one SSL certificate is required per OHS server so cost is minimal.

Network SSL implementation is the simplest method and good for security if the network is setup correctly.  Two SSL certificates are added to an external device such as an SSL Off loader or load balancer.  One certificate is needed for external communication between users and the device, and a certificate is needed for internal communication among Hyperion applications.  Hyperion is configured normally, and the load balancer forwards all requests from OHS.

Performance can and should be a factor when considering SSL implementations.  A full SSL implementation can cause Hyperion to run slower.  For example, a client wanted a full SSL implementation in their dev environment.  SSL certificates were obtained for every server and software piece that required them.  After configuration was done and tested, the environment was released to users who reported that Hyperion was running slower than normal.  It would take a minute or two just to get Workspace to load up. After this report, SSL was only implemented in OHS in another environment, and the performance was a lot better.  After seeing this difference, SSL was redone in dev for OHS only, and performance increased.

Reference: https://www.excelglobalpartners.com/considerations-for-ssl-implementation-in-hyperion-environment/

Thanks

Mady