Changes to the installation process
If you installed previous versions of IBM OpenPages® with Watson™, you will notice many differences. In version 8.3, the Standard UI is no longer supported and it has been removed from OpenPages.
The following sections describe the main changes that impact installation, upgrade, and migration.
Changes to the installation server and app
- The File Backup and Restore operations have been removed from the installation app. The file-migration task in the deploy.properties file is no longer supported.
- The Oracle Text option has been removed from the Database Server card in
the installation app. The
oracle_enable_textparameter in the deploy.properties file is no longer used. Instead, enable Oracle Text manually after you install OpenPages.Alternatively, you can use the database scripts to create the database and have those scripts install Oracle Text as part of the database installation process. However, to install Oracle Text, the database scripts must be run from the database server. Installation of Oracle Text cannot be performed from a remote system.
Application files
The application files are now in taskui.war. The openpages.war and sosa.war have been removed.
During an upgrade, the installation server backs up custom files that are in sosa.war and restores them in taskui.war.
During a migration, you need to back up custom files and restore them manually.
Location for customized JSPs
<OP_HOME>/wlp-usr/shared/apps/op-apps.ear/openpages.war<OP_HOME>/wlp-usr/shared/apps/op-apps.ear/publishweb.war<OP_HOME>/wlp-usr/shared/apps/op-apps.ear/sosa.war<OP_HOME>/wlp-usr/shared/apps/op-apps.ear/publishweb.war<OP_HOME>/wlp-usr/shared/apps/op-apps.ear/taskui.warFramework generation
IBMOpenPagesFrameworkModelGenerator service. OpenPages now uses the Cognos® SDK to generate the framework. Note the following changes:BmtScriptPlayer.shis no longer used.- The
IBMOpenPagesFrameworkModelGeneratorservice is no longer used. - If you use Oracle and you use DQM framework models only, the 32-bit Oracle client software is no
longer required.
If you are upgrading or migrating and you want to continue to use CQM framework models, the 32-bit Oracle client is still required.
- The files and folders for framework generation are now stored on the OpenPages application servers. The
framework,FrameworkGeneration, andwlpfolders were removed from the reporting server, along with any files related to the framework.For example, model query subjects are now stored in <OP_HOME>/aurora/framework/conf/mqs. Previously, they were stored on the reporting server in the <CC_HOME>/framework/conf/mqs directory.
- Most properties have been removed from the
framework.propertiesfile. The remaining properties aredatasourcedatabase.schemasecurity.namespace
- The
cognos.framework.refresh.servletproperty was removed from theaurora.propertiesfile. - The Framework Port and Framework Output Directory
fields were removed from Report Server cards in the installation app. Also,
the
framework_portandframework_output_directoryproperties were removed from the deploy.properties file.
Location of Java on reporting servers
In OpenPages 8.3 and later, you must use the JRE that is provided with IBM® Cognos Analytics for reporting servers. In addition, you no longer need to copy the bcprov-jdk15to18-1.68.jar file from the application server to the reporting servers.
Other changes
If you are upgrading or migrating from 8.1 or earlier, see Notes for customers upgrading or migrating from 8.1 or earlier.