IBM ILOG ODM Enterprise v3.6.0 Fix Pack 1
-----------------------------------------

Installation information
========================
This fix pack is designed to install “on top of” existing installation of IBM ILOG ODM Enterprise v3.6.0 as an upgrade. Executing the installer (.exe/.bat on windows, .bin on AIX) updates several components of ODM Enterprise v3.6.0 installation, including the Optimization Server EAR files. These EAR files are deployed on the embedded WAS during the initial installation of ODM Enterprise Developer Edition, and need to be redeployed to v3.6.0.1 code level.

If you are using an embedded WAS Optimization Server with the ODM Enterprise Developer Edition, you must execute a script to upgrade the EAR modules after installing this fix pack, as described below.

Upgrade automatically
---------------------
You can redeploy your EAR files automatically by launching the upgradeServer.bat file on Windows in %ODME_HOME%/server/configure-scripts/was-resources. The script will upgrade the embedded WAS Optimization Server. 

Upgrade manually
----------------
You can redeploy your EAR files manually as follows:

Launch the WAS Administrative console (through the Open WebSphere Server Console menu, after having ensured that the WAS instance is running).

Select Applications > Application Types > WebSphere enterprise applications in the left panel of the console.

Select optimserver-mgmt-ear:

Click the Update button.

Check Replace the entire application.

Look up the EAR file in %ODME_HOME%/server/ears.

On the next screen, select the Fast Path, then accept the defaults until the ultimate panel is displayed, and then click Finish.

Repeat the same steps for odme-application-mgmt-ear, odme-data-mgmt-ear, and optimserver-processor-ear.

You might need to restart the applications for the changes to take effect.

 
Fixed Issues
============
This fix pack resolves following issues:

ODM Enterprise IDE
------------------
- The ODM Enterprise IDE was running slow and was consuming too much memory when several columns were part of a foreign key.
- Using a WHERE clause on a string in SQL entered through the database data source editor caused single quotation marks to be replaced by double quotation marks.
- When reverse engineering a database schema to create a Data Model, foreign keys were disabled in the mapping editor (and hence could not be mapped) even after the parent tables had been mapped.

ODM Studio
----------
- ODM Enterprise 3.6 introduced a regression in the capabilities of the docking framework. It was no longer possible to rearrange windows horizontally and vertically. 
- Menus and actions were not correctly updated when switching to another view by clicking the view title bar.
- The ODM Studio default settings captured in odmStudioDefaultSettings.xml were not used.
- View hooks were passed an incorrect data location for the pivot table cell data when the filters were active.
- Clearing a large number of pivot table cells was slow.
- Large pivot tables were very slow on startup and during zoom changes compared with v3.5 (taking minutes instead of seconds)
- The version of JViews Enterprise installed in Developer/JViews was not using the same fix pack as the JViews libraries delivered under the "lib" folder of the ODM Enterprise installation.
- Exporting a scenario whose Data Model had derived columns as foreign keys caused an incorrect relational model schema to be generated.
- For Derby databases, indexes were not created which resulted in performance regression during data checking.
- Creating a scenario with workspace.createChildScenario(-1) failed if a scenario named "Scenario 0" existed.
- Derived table dependencies were resolved in the wrong order.

Deployment
----------
- Any JBoss configuration which used automated scripts failed on the Windows 64-bit platform.
- odmdeploy was not correctly handling backslashes in the deployment settings during deployment on AIX platform.
- Automatic configuration of WebSphere Application Server v6.1 (installScript.sh) on AIX failed when executed with the "auto" option.

Examples
--------
- The Nurses example was performing slowly when deleting thousands of Nurses.
- IloTableDateHook.getReferenceValue was not correctly written in the case where the order of the columns in the view was not the same as the order in the data table.


Enhancements
============
- New synchronized support for the Object Model
- Support for Date-related data types
- New API to store and restore ODM Studio view set configurations
- New Custom Task configuration properties for the Optimization Server
- Performance Improvements made to the Data Server
	- Object value caching
	- Optimized communication between the Data Server and ODM Studio


Limitations
===========
Following are known limitations on top of what existed in ODM Enterprise v3.6.0
- Date, time and timestamp limitations
	- Chart views do not support the date related types.
	- When copying Timestamp values to Excel, milliseconds are lost.

