The new Oracle EPM System 22.214.171.124 was released recently and
it has some great enhancements especially for Financial Management. As one can
see from the new Support Matrix (http://www.oracle.com/technetwork/middleware/bi-foundation/oracle-hyperion-epm-system-certific-131801.xls),
Financial Management is available on the Exalytics platform now.
There were several changes needed on the architecture, to
make this work. Here is an updated architecture diagram, which is valid for the
Exalytics as well as the Windows platform:
Previously, Financial Management was dependent on DCOM
technology, which is only available on Windows operating systems. Starting from
126.96.36.199, TCP/IP is used to communicate between Financial Management processes.
As a result, there is no need to have Internet Information Server anymore,
which was acting for the Java based web user interface as a kind of translator,
between the web and the backend Financial Management application server.
As one can see from the above diagram, the process names
also changed slightly. On Windows operating systems, the process previously
known as HsxServer.exe can now be found as
HyS9FinancialManagementJavaServer_INSTANCE_NAME.exe. The HsvDataSource.exe is
now called XFMDataSource.exe. On Exalytics, the Java server can be found by
searching for the string HsxServer, the data source process is known as xfmdatasource.
With the new Consolidation Administration web user
interface, tuning is significantly simplified, no longer requiring, for
example, the addition of long keys to the Windows Registry. Financial
Management can now be tuned easily using the Consolidation Administration in
the web user interface:
Going through the list of options, looking at the default
values and the possible ranges show, that the defaults are increased from
previous releases. Therefore, Financial Management will utilize system
resources better by default.
Since servers nowadays are getting bigger and bigger,
Financial Management is now able to scale up a lot better on big machines. Up
to release 188.8.131.52, the maximum Number of Consolidation Threads (Configuration
setting: NumConsolidationThreads) was eight. This can now be increased up to
24, which is going to utilize big servers like the Exalytics box a lot better.
Have fun with the new release!