Deploying RPE Monitor&Control on WebSphere Application Server 7

This is a step by step description of deploying the RPE Monitor&Control service on IBM WebSphere 7.

1         Prerequisites

1.1       WAS 7

Check for the list of supported WAS 7 versions.

1.2       RPE

RPE 1.1.2 can be used as there are no differences relevant to installing RPE Monitor&Control between RPE 1.1.2 and RPE

2         Deploy the RPEMC Application

2.1       Select the “New application” option

Provide the path to where the rpemc.war exists in your system, usually c:\Program Files\IBM\Rational\Publishing Engine\\web services\rpemc\rpemc.war

2.2       Preparing for the application installation – use defaults

2.3       Select installation options

You can change the suggested name “rpemc_war” to “rpemc”.

2.4       Install New Application – use defaults

2.5       Set context root to rpemc

You can use any other context but it is recommended to use rpemc to align with the infocenter and other enablement materials.

2.6       Review selections

2.7       Finish

3         Change class loading policy

Set the following options (if not set):

  • Classes loaded with local class loader first (parent last)
  • Single class loader

4         Configure Security

Set the following options (if not set):

  • Enable application security

NOTE: if you change any setting in this dialog or other security related dialogs you  MUST restart the server.

4.1       Global security

Set the following options (if not set):

  • Authenticate only when an URI is protected

4.2       Create users


  • Any names will do but its recommended to use names that relate to the role the user has ( “rpemc_admin” for an admin vs “bob” or “rpe_bob”)
  • You can create as many users as you need but usually one admin user and one client user are enough.

4.2.1       Create an admin user

4.2.2       Create a client user

4.3       Map users

4.3.1       Add the rpe_mc_client role to both users

4.3.2       Add the rpe_mc_admin to the admin user only

4.4       Review mappings and save

5        Stop and restart the server

This is needed for the “Global security” changes to take effect ( as requested when saving those changes)

6         Using the application

6.1       Start the application (if needed)

7         Using RPE Monitor&Control

NOTE: You need to use a different browser from the one you are logged into the WAS Console to clear the basic authentication cache in the browser.

The entry page of the Monitor&Control service provides the URLs you need:

  • the service URL to use in the clients
  • the URL to the Admin UI

7.1       The Service URL

Accessing this URL will result in the response below. The error indicates that the service is running but was not invoked with the correct arguments. This is expected behavior, the RPE software will provide the necessary arguments at runtime.

7.2       Configure the RPE Launcher/Studio with the Service URL

7.3       Make a test run

If RPE is configured to use the MC service than the RPE log must contain an entry stating “Job created on Monitor service”.

7.4       Click the Admin UI

You must be prompted to authenticate. If you are not prompted then:

  • you are using a browser where you are logged in WAS admin console
  • you have not setup security correctly ( including restarting the server)

7.5       Login into the Admin UI application

NOTE you must use the user with the rpe_mc_admin role.

7.6       Verify you can see the test job you’ve made from launcher

NOTE the job will most likely not be displayed in the default view, Running jobs, as it likely it was completed by now. Switch to the “All jobs” view.

7.7       Start a new execution in the RPE Launcher client and check if you can see it under the “Running” jobs

8         Debug

If you need debug information add the “” flag with the “true” value as a custom property of the RPEMC Application.

8.1       Open the Server general Properties page

8.2       Select Process definition under “Java and Process Management”

8.3       Select “Java Virtual Machine” under Additional Properties

8.4       Select Custom properties

Add the custom property.

8.5       Restart the server

To test the logging facility make a request to the RPE Monitor&Control Service

The System.out log file for the server log path (ex: C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1) must contain the “ERROR” information below, the same information shown in the response XML.


Author: Dragos Cojocari

Architect for Rational Publishing Engine

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s