Redeploying the remote applications after a Rational Publishing Engine upgrade

Server administrators can redeploy the remote applications for remote document generation after upgrading Rational® Publishing Engine.

Before you begin

Upgrade Rational Publishing Engine.

Procedure

  1. Deploy the 2.0 web app.
    Important: After you upgrade to version 2.0.1 and redeploy the web app, you must log in to the web app, clear the web browser cache and then log in again. Otherwise you may be unable to successfully generate documents for any existing reports.
    Note: You can update your existing reports so that they have the latest properties. If there is a new property in this release that you want to use in an existing report, you can open your existing report, make a change, and then save the report. Your report can now make use of any new properties that were added in version 2.1.
  2. Deploy the Remote services application. If you deployed the web app, you might not need the remote services applications, as most of the tasks can be achieved via the web app.
    Note:
    • If you are upgrading from 1.1.2.2 or earlier, you must deploy the Remote services application again.
    • If you are upgrading from 1.2, 1.2.0.1, 1.2.1 or 1.3, you are not required to deploy the Remote services application again. However, to use the features that are contained in a later release, you must deploy the Remote services application again. It is recommended to keep the version of the Remote services application in line with the version of the Rational Publishing Engine client applications you are using, but it is not required.
      Important: Changes are made to the report scheduling feature in the Remote services application during the upgrade to version 1.2.1.1 that affect the rollback process. If you upgrade the Remote services application but do not upgrade the Launcher application, do not roll back the Remote services application unless you back up the rpe_scheduler directory. After you roll back the Remote services application, replace the rpe_scheduler directory with the backup.
      • Apache Tomcat: CATALINA_HOME\bin\rpe_scheduler
      • Apache Tomcat as a Windows service: CATALINA_BASE\bin\rpe_scheduler
      • WebSphere Application Server: WASInstallDir\AppServer\profiles\profile\rpe_scheduler

Feedback