Known problems Decision Optimization Center V3.8

Content

Following are some known problems for Decision Optimization Center:

1. Manual installation of Decision Optimization Center Optimization Server and Data Server on WASCE as described in the documentation fails because of a new JMS resource group.
   Solution: Use the command tool to install Decision Optimization Center Optimization Server and Data Server on WASCE as described in the documentation. See http://www.ibm.com/support/knowledgecenter/SSQVNT_3.8.0/ilog.odms.ide.odm.server.help/OptServer_Install/topics/WASCE_2CommToolInstall.html.
   
   
2. In the Manual installation of Decision Optimization Center Optimization Server and Data Server for WebSphere Application Server section of the documentation (step 4 and step 7), the file identified to be selected (odme-application-mgmt-ear.ear) is incorrect.
   Solution: Select optim-server-mgmt-ear-x64_win64.ear (or the Linux or AIX version of the module).
   
   


3. For Server editions on AIX and Linux platforms, the .odmapp file for the Nurses example is not shipped in the Decision Optimization Center installation.
   Solution: The .odmapp file must be generated from the command line using the odmdeploy tool:
   <installdir>/Server/bin/x86-64_linux/odmdeploy.sh <installdir>/Server/examples/Nurses/Nurses
   This generates the deployed application as <installdir>/Server/examples/Nurses/Nurses/deploy/Nurses_odm.odmapp
   
   


4. The URL of the Decision Optimization Center Console provided in the documentation (Installation Guide for WebSphere Application Server Community Edition (WASCE) section) is incorrect.
   Solution: The URL for the Console is https://localhost:8443/odme/console/ .
   
   
5. When adding a new database connection (in the Data Source Explorer in the Data perspective), the JDBC driver definitions for Oracle and MS SQL Server are initially missing from the list of predefined drivers. This is because the associated driver jars are not delivered with the product.
   Solution: You can download these jars from the Oracle and Microsoft web sites. To have a driver listed, close the IDE, copy the driver jar (ojdbc6.jar for Oracle, sqljdbc4.jar for MS SQL Server) to the directory <installdir>\Developer\ide\eclipse\dropins\oplide\plugins\ilog.odms.ide.odm_3.8.0.xxxxxxxx-xxxx, then restart the IDE. The new driver will now be listed with the rest of the predefined JDBC drivers.
   
   
6. In version 3.8, the Decision Optimization Center IDE does not initially start with the ODM Enterprise perspective. This is due to an Eclipse issue and will be corrected in a future release with Eclipse 4.3.
   Solution: In the meantime, you can manually switch to the ODM Enterprise perspective after starting the Developer IDE. To change perspectives either click the Open Perspective button or choose Window > Open Perspective > Other in the main menu. In the list that is displayed, select ODM Enterprise.
   
   
7. Inappropriate memory settings might result in an out-of-memory exception when running multiple big solves in parallel on the Optimization Server.
   Solution: When configuring the WAS application server that hosts the Decision Optimization Center Optimization and Data Server, ensure that you have properly adjusted memory settings.
   For more information, refer to the memory management section on this page: http://www.ibm.com/support/knowledgecenter/SSQVNT_3.8.0/ilog.odms.ide.odm.server.help/OptServer_Install/topics/WASAdditionalInfo.html.