Server administrators can redeploy the remote applications
for remote document generation after upgrading Rational® Publishing Engine.
Procedure
- Deploy the Remote services application.
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
- For more specific steps on deploying and starting the Remote
services application for Rational Publishing Engine,
see the topics for each application server:
- Deploy the Reporting data services application.
Note: - If you are upgrading from 1.1.2.2 or earlier, you must deploy
the Data Services application again.
- If you are upgrading from 1.2, 1.2.0.1, or 1.2.1, there are no
changes to the Data Services application, so you are not required
to deploy the application again.
- For more specific steps on deploying and starting the Data
Services application for Rational Publishing Engine,
see the topics for each application server: