You can deploy the monitor
and control servlet on IBM® WebSphere® Application Server 7.0
using these steps.
Before you begin
You must install
WebSphere Application Server 7.0
and
Rational® Publishing Engine with
the
monitor
and control servlet feature
before you can deploy the
monitor
and control servlet.
Procedure
- Open the administrative console in a browser. Example: http://localhost:9043/ibm/console/logon.jsp
- Deploy the Rational Publishing Engine monitor
and control servlet.
- Expand Applications and
click New Application.
- Click New Enterprise Application.
- In the Path to new application section,
select Local or Remote,
depending on where the rpemc.war file is in
relation to the application server.
- Click Browse and
locate the rpemc.war file. The
default location is: %RPE_HOME%\web services\rpemc\rpemc.war
- Select Fast Path - Prompt only
when additional information is required and click Next.
- Accept the default settings in
the following windows and click Next.
- Select installation options
- Map modules to servers
- Map virtual host for web modules
- In Map context roots for web modules,
enter the context root as /rpemc. The
context root is a part of the URL used for configuring the client.
- In the Summary window,
click Finish and Save directly
to the master configuration.
- Configure the security roles:
- Click .
- Click Create and
create two users: rpe_admin and rpe_client.
- To associate roles, click . WebSphere Application Server displays
the two users you defined as their roles for the monitor
and control servlet:
- rpe_mc_client
- rpe_mc_admin
- Associate the rpe_mc_client role
with the rpe_admin and rpe_client users.
- Select rpe_mc_client.
- Click Map users.
- In the Search String field, enter rpe* and
click Search.
- In the Available column, press the CTRL key, and then select rpe_admin and rpe_client.
Click the Add arrow to add the users to the
Selected column.
- Click OK.
- Associate the rpe_mc_admin role
with the rpe_admin user.
- Select rpe_mc_admin.
- Click Map users.
- In the Search String field, enter rpe* and
click Search.
- In the Available column, select rpe_admin and
click the Add arrow to add the user to the
Selected column.
- Click OK.
- Click OK and Save directly
to the master configuration.
- Change the class loader policies:
- Click .
- In the Class loader order section, select Classes
loaded with local class loader first (parent last).
- In the WAR class loader
policy section, select Single class loader for application.
- Click Apply and OK.
- Update the security settings:
- Click .
- In the Application security section,
select the Enable application security check
box.
- In the Java 2 security section, clear
the Use Java 2 security to restrict application access
to local resources check box.
- In the Authentication section, click .
- Select Authenticate only
when URI is protected.
- Click OK and Save directly
to the master configuration.
- Start the monitor
and control servlet application:
- Click . The rpemc.war application
you added is listed as the application name you entered.
- Select the monitor
and control servlet application.
- Click Start. The following confirmation message displays: Application rpemc.war_application on
server server1 and node IBM-74569A1E1EFNode01 started
successfully.
- Test the monitor
and control servlet:
- Log out of the WebSphere Application Server administrative
console.
Note: You must log out of the administrative
console. Because basic authentication is used, only a single session
per browser can exist. If you do not log out of the WebSphere Application Server administrative
user, you cannot access the Rational Publishing Engine resources
to which only the rpe_admin has access and you receive
the following message: Error 401: Unauthorized.
- Open http://server:port/rpemc/ui/index.html in
a browser.
- Log in with the rpe_admin credentials. If it is configured correctly, you can view the user interface
of Rational Publishing Engine monitor
and control servlet.
- Click Refresh Jobs. The current
jobs display.
What to do next
On the end user computers, specify the URL
of the monitor
and control servlet for
a remote server. See Setting monitor and control servlet preferences.