Installation and Conversion Notes
OpenEdge 11.4 Hot Fix
To install 2015 EE with Progress OpenEdge 11.4, you must install the appropriate hotfix for your platform:
• Linux: OE11.4 Hotfix10 minimum
• Windows or UNIX: OE11.4 Hotfix14 minimum
DB Connections Field
A DB Connections field was added to QDT’s Compiler Settings screen. This value was previously hard coded. The new field allows you to specify the number of databases that Enterprise Edition is connected to during database compilation.
QXtend and EAM Installation
To install QXtend and EAM in a 2015 EE environment, install QXtend first followed by EAM. To install QXtend in a 2015 EE environment with an existing EAM installation, do the following:
• In QAD EAM Configuration go to the Database Advanced Properties #2 screen and set the Maximum clients per server field to 50 for each of EAM database.
• Go into the QAD EAM configuration, reset the Generate Scripts for QAD EAM option, and re-run it.
• Restart your QXtend Installation.
EAM and Warehousing Installation Sequence
If you plan to install QAD Warehousing and QAD EAM in your QAD 2015 EE environment, you must install Warehousing before EAM. If you already installed EAM followed by Warehousing, the scripts generated by QDT are incorrect. To correct this issue, start QDT, go into the QAD EE configuration, reset the Generate Scripts for QAD EE option, and rerun it.
Adding Languages
When adding new languages to a QAD 2015 EE installation after QAD EAM was added, you may encounter a problem in the QAD UI Build. The qadui.log file will contain the following error:
There is no server for database /dr01/qadapps/eam1/db/eamprod. (1423)
To avoid this problem, ensure that the EAM databases are running before you attempt to add a new language and run a new QAD UI build. To start the EAM databases, use the start.eam.<env> script for UNIX systems and the start-eam-<env>.bat script for Windows systems.
Databases/AppServers Fail to Start During EAM Installation
The databases/AppServers may fail to start when EAM is installed after QAD EE installation. To resolve this problem, stop QAD EE and reattempt the QAD EAM install.