Friday, November 11, 2016

Changes in 11.1.2.4 compared to 11.1.2.x

1. OS support added for Windows Server 2012 (all SP levels inc)/R2
2. OS support removed for Windows Server 2003
3. Client OS support added for Windows 8.1 and Windows Server 2012 (all SP inc/R2)
4. Client OS support removed for XP and Vista
5. Browser support added for Internet Explorer 11.x and Firefox 31.x ESR
6. Browser support removed for Internet Explorer 7 and 8
7. No changes in Oracle database repository support though Microsoft SQL Server 2012 (all SP levels inc) has been added
8. No changes in supported versions of Microsoft Office which are 2007/2010/2013
9. Websphere application server support removed
10.Smart View compatible version for 11.1.2.4 is 11.1.2.5.400

There are some caveats on the above so for more detailed information check out the support matrix.

Key Points:

versions of jdk and jrockit have not been updated from 11.1.2.3

The configuration to Shared Services and Registry Database has no changes.

product configuration options are very similar to that of 11.1.2.3

Removal of DCOM and the web server from the FM configuration.

Under FDMEE the register HFM adaptor is no more now that HFM has moved into the Java world so it will be built into FDMEE by default.

The deploy application server still has the annoying deploy to single managed server enabled by default which I quickly deselected.

The essbase configuration has a new additional option to set the binding host name which I know will help in cluster configurations.

Oracle Configuration Manager (OCM) Registration has been removed

Financial Management is down to two services instead of four.

IIS is very quiet indeed with no FDM and no FM now that it has fully moved in to java web application world.

Earlier versions you need to install Database client, both 32 and 64, in a sequence but not any more (May be from 11.1.2.2, we don’t have that headache) and even ODI repository comes with EPM as FDMEE from 11.1.2.3.

installation all components to a single schema, which is possible but we would prefer to have separate schema for separate components for better management.

No comments:

Post a Comment