3.0.2.0 Release Notes

Open Pace 3.0.2 is the last planned Open Source deployment of the Pace Application Suite. This release delivers some minor bug fixes, product improvements, as well as Open Pace re-branding modifications.

Most of the modifications delivered in Open Pace 3.0 and Open Pace 3.0.2 are cosmetic in nature. However some of these re-branding changes will directly impact the implementation, installation, and upgrade of Pace (see below and the 3.0.0.0 Release Notes):

Full LDAP Support - Open Pace Administration Console

The most significant improvement in this release is LDAP support for the Open Pace Server Settings application. With this latest enhancement, the Open Pace Adminstration Console now fully supports administration by an LDAP user, once the LDAP user has been given Administrative Access to the Open Pace Server.  (See LDAP Integration for the Open Pace Admin Console and LDAP User Node for more information)

Manual Pace Project XML Conversion Process

  • Before upgrading to Open Pace from a commercial release of Pace Planningall local and server Pace projects must go through a manual conversion process to be compliant with the XML Header changes that were implemented in Open Pace 3.0.
  • This conversion process is a manual step, but a Powershell script is provided to assist with this process
  • This step must be done before upgrading to Open Pace
    • Otherwise the project  XML will be in a corrupted state after the upgrade and the Pace Server will not be able to start successfully.  
    • Running the conversion script after the upgrade will not resolve any of the corruption issues

Open Pace 3.0.2 Server - Linux Default Installation Folder Has Changed

  • The default Open Pace installation directory for the Linux version of the Open Pace Server has been updated to: /opt/open-pace   
  • In versions 3.0 and prior, the default installation directory was: /opt/pace

Please refer to the Open Pace Installation Directory Reference for more information.

Essbase Upgrade Warning

If upgrading to Essbase 11.1.2.4.007 or above, it will be necessary to set the “QUERYRESULTLIMIT” Essbase configuration setting on each Essbase database used by Pace. Please refer to Install and Configure Oracle EPM in the Open Pace Installation Guide.for more information.


Open Pace Server

Bug

  • [TTN-2687] - Clean up extra server log messages
  • [TTN-2718] - Mishandling of Shared Hierarchies in UOW Construction
  • [TTN-2719] - Filtered Subtotal Members appearing in User Selector on Measures Dimension


Improvement

  • [TTN-2114] - Improve error handling for invalid data cache intersections
  • [TTN-2642] - Duplicate Measure - Better Error Handling
  • [TTN-2677] - Update Pace Server Installer - LINUX
  • [TTN-2684] - Clean up pace.log messages
  • [TTN-2692] - Open Source Installer Updates
  • [TTN-2700] - Pace Open Source Code Re-Branding
  • [TTN-2711] - WinWrapperforPaceAC Rebranding
  • [TTN-2728] - Pace Server Application Restart App - Re-Branding
  • [TTN-2729] - Pace Server Installer - Remove unneeded components



Open Pace Client

Improvement

  • [TTN-2707] - Test Harness Rebranding
  • [TTN-2708] - Stress Tester Rebranding
  • [TTN-2709] - Pace API Rebranding
  • [TTN-2710] - Pace Client GUI Modifications (Rebranding)



Open Pace Administration Console

Bug

  • [TTN-2555] - Create new project wizard using Essbase outline does not handle invalid connector well
  • [TTN-2670] - Problem with importing a project after a fresh AC installation
  • [TTN-2685] - Investigate and address Support Request issues on fresh AC/Pace Install
  • [TTN-2715] - No response from Test Application Button when Server Connector is first created
  • [TTN-2717] - Can't set "Default Server" on new project
  • [TTN-2720] - Upload User Security option missing from individual Security User node
  • [TTN-2731] - Set Default Server on Project Import
  • [TTN-2732] - Set Enabled box as default when Adding new Server Connector


Improvement

  • [TTN-1718] - Server Settings Web Application - LDAP users can't login
  • [TTN-2680] - Auto generation of support request from the Admin Console (OS Updates)



Open Pace 3.0.0.x - Known Issues

Default Pace Server Installation with Shared Derby Instance

An issue arises when the default Pace Server installation process is used to create an addtional Pace Server instance that shares the Derby instance from a Pace Server instance installed on the same server environment. The Derby "hibernate.connection.url" values (for each of the 3 Derby databases) will be slightly off resutling in errors when attempting to start the second Pace Server instance.


See line 09 - "....Derby/SVR1/data/SVR11/paceclientcache.." should be "....Derby/SVR1/data/SVR1/paceclientcache.."


Sample Errored Connection String
<list>
  <RdbProps>
    <name>pafClientCache</name>
    <hibernateProperties>
      <property name="hibernate.connection.username" value="pafsys"/>
      <property name="hibernate.use_identifier_rollback" value="true"/>
      <property name="hibernate.connection.password" value="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"/>
      <property name="hibernate.dialect" value="org.hibernate.dialect.DerbyDialect"/>
      <property name="hibernate.connection.url" value="jdbc:derby://localhost:1527/C:/Program Files/Open Pace/Derby/SVR1/data/SVR11/pafclientcache"/>
      <property name="hibernate.show_sql" value="false"/>
      <property name="hibernate.bytecode.use_reflection_optimizer" value="false"/>
      <property name="hibernate.connection.driver_class" value="org.apache.derby.jdbc.ClientDriver"/>
    </hibernateProperties>
    <version>1</version>
  </RdbProps>


The workaround is to manually edit the "paceRDBClientDataSources.xml" of the additional Pace Server instances, fix the "hibernate.connection.url" scripts, and restart the Pace Server.


Pace Admin Console & Internet Explorer Compatibility

The Open Pace Administration Console requires Internet Explorer 11 to be installed on any machine that the Administration Console is installed on. See the Open Pace Compatibility Guide for more information.


Session Locks

Session locks is an Open Pace Client feature that was implemented in 2.8.4.0. Though enabled, the locking of Attribute intersections in the Session Lock Grid is not supported at this time, do to some known issues.


<isMeasureAlloc> Tag

A new Pace rule tag called "<isMeasureAlloc>" has been added for future use. It should not be used at this time. (The default value is "false").


Importing Cell Notes & Member Tags from all versions of Open Pace prior to 2.8.2

This issue impacts the upgrade process of any version of Open Pace prior to version 2.8.2 

The Open Pace Administration Console, versions 2.8.2 and above, can't import Cell Notes/Member Tags exported in a binary format from any version of Open Pace version prior to 2.8.2. 

However, Cell Notes/Member Tags exported in an XML format, from Open Pace 2.8.1.1 or older, can be imported into Open Pace 2.8.2 or higher, after first manually modifying the export file using the following procedures:

  1. Make a backup copy of the Cell Notes/Member Tags XML export file 
  2. Open the Cell Notes/Member Tags export file in a text/XML editor (Notepad++, a free open-source multi-file type text editor is a good one, but any text editor that can handle large files will suffice)
  3. Replace all the occurrences of "com.palladium.paf.server.client" with “com.pace.server.client”
  4. Save these changes and close the text editor.

The default file type for import/exporting Cell Notes/Member Tags has been changed to 'XML',  from 'Binary', in this release.


Program%20Files folder

The creation of this folder on the Pace Server is a by-product of Pace Server start up process. This is a known JBoss issue and should be resolved in the next Open Pace release, when a more recent version of JBoss is bundled with Pace.

JBoss is the default Java application server bundled with Open Pace


Automated Pace Service Install/Uninstall

Now, when then Pace Server is installed on a computer running Microsoft Windows, the Pace Server installer will attempt to install the Pace and Derby servers as Microsoft Windows services. If these services already exist (from a previous Pace Server installation), this step will silently fail with no adverse effects. 

Correspondingly, now when the Pace Server is uninstalled, the Pace and Derby services will be automatically removed.


Pace Server Upgrade Instructions

The Pace Server uninstaller, prior to version 2.8.3.4, doesn't uninstall the Pace and Derby services automatically. If these pre-existing services are not removed before the Pace 2.8.3.4 Server is installed, then these services will not be automatically uninstalled when the Pace 2.8.3.4 Server uninstaller is run at some point in the future. Therefore, before upgrading to the Pace 2.8.3.4 Server, the pre-existing Pace & Derby services should first be manually uninstalled by selecting the corresponding shortcuts from the "Open Pace" Program Files menu.

The automatic installation of the Pace & Derby services is now the default behavior of the Pace Server installer. If it is not desirable to have the Pace and Derby servers installed and run as Microsoft Windows services, then after the Pace Server installer has completed one of the following actions should be taken:

  1. Disable the Pace & Derby services in the Microsoft Windows "Services Panel" or
  2. Remove the Pace & Derby services by selecting the corresponding shortcuts from the "Open Pace" Program Files menu.

Potential Pace Server Installer Issue - Managed Instance Issue

In the situation where a user has manually uninstalled a previous version of Pace Server, the installer may "get confused' and still think that there is an existing installation to upgrade, instead of trying to do a fresh install. In this case the following error may be displayed: "An error occured while trying to manage the selected instance". If this occurs, delete the contents of the hidden windows directory: "C:\Program Files\Zero G Registry", and re-attempt the Pace Server installation process.