Installation and Upgrade Guides › Policy Server Installation Guide › Configuring the OneView Monitor

Configuring the OneView Monitor

This section contains the following topics:

OneView Monitor Overview

System Requirements for OneView Monitor

Configure the OneView Monitor

Limitation of OneView Monitor GUI/IIS Web Agent on Same Machine

How to Configure the OneView Monitor GUI on Windows/IIS

How to Configure the OneView Monitor GUI on UNIX/Sun Java System

Start the OneView Monitor Service

Access the OneView Monitor GUI

Monitor a Policy Server Cluster

OneView Monitor Overview

The OneView Monitoring infrastructure consists of a number of modules that enable the monitoring of SiteMinder components. Included is the Monitor process that runs in the context of a Java Runtime Environment (JRE). The Monitor GUI’s HTML pages are generated by Java Server Pages (JSPs) and servlets hosted on a ServletExec servlet engine running on the same machine as the Policy Server.

The OneView Monitor utility monitors the following SiteMinder components:

• Policy Server
• Web Agents

Note: More information about using the OneView Monitor exists in the Policy Server Administration Guide.

System Requirements for OneView Monitor

The system to which you are configuring the OneView Monitor GUI must meet at least the following system requirements:

• JDK—The required version of the Java SDK is installed on the system.
• Servlet Engine—The required version of ServletExec is installed on the system.

  Note: The Policy Server installation kit includes the installation executable for ServletExec/AS at the following location:

  thirdparty-tools\servlet-engine-6.0
  

• Web server—A supported Web server is installed on the system.

Note: For a list of supported CA and third-party components, refer to the SiteMinder r12.0 SP3 Platform Support Matrix on the Technical Support site.

More information:

Locate the Platform Support Matrix

Configure the OneView Monitor

If you did not configure the OneView Monitor GUI when installing the Policy Server, you can configure it using the Policy Server Configuration Wizard.

You can find the following Policy Server Configuration Wizard executables in siteminder_home\siteminder\install_config_info for Windows and siteminder_home/siteminder/install_config_info for UNIX:

• ca-ps-config.exe

  Important! If you are running this wizard on Windows Server 2008, run the executable file with administrator permissions. Use these permissions even if you are logged in to the system as an administrator. For more information, see the release notes for your SiteMinder component.

• ca-ps-config.bin

siteminder_home

Specifies the path to where the Policy Server is installed.

Limitation of OneView Monitor GUI/IIS Web Agent on Same Machine

CA does not support the configuration of the IIS-based OneView Monitor GUI and the IIS Web Agent on the same machine if the Agent has Registration Services enabled. With this configuration, there is a conflict with the same instance of ServletExec.

How to Configure the OneView Monitor GUI on Windows/IIS

To configure the OneView Monitor GUI on Windows/IIS complete the following procedures:

1. Read the prerequisites to installing ServletExec on Windows.
2. Install ServletExec/ISAPI on Windows/IIS.

   Note: The Monitor GUI’s HTML pages are generated by Java Server Pages (JSPs) and servlets hosted on a ServletExec servlet engine running on the same machine as the Policy Server.

3. Assign modify permissions to the Internet guest account for the policy_server_home\monitor\settings folder.
4. Set permissions for the IIS Users.
5. If you did not have the Policy Server installation program auto-configure the OneView Monitor GUI, configure it by running the Policy Server Configuration Wizard.
6. Start the OneView Monitor service.
7. Access the OneView Monitor GUI.

Prerequisites to Installing ServletExec on Windows

Consider the following prerequisites before installing ServletExec:

• ServletExec is a third–party product. We recommend that you read the ServletExec documentation before installing the component.

  Note: For more information, see the New Atlanta web site.

• The Policy Server requires a 32–bit JDK when installed to a supported 64–bit Windows operating system. If you are installing ServletExec/AS 6.0 to a 64–bit Windows operating system, ServletExec requires a 64–bit JVM. If necessary, install a 64–bit JVM before installing ServletExec.

Install ServletExec on Windows IIS

Follow these steps:

1. If you have a previous version of ServletExec, back it up.
2. Run the ServletExec installation executable.

   Note: The Policy Server installation kit includes the installation executable for ServletExec/AS 6.0 at the following location:

   thirdparty-tools\servlet-engine-6.0
   

   Note: For more information about upgrading and installing ServletExec, see the New Atlanta documentation.

3. If you installed a 64–bit JVM as a ServletExec/AS prerequisite, complete the following steps:
   1. Use the Services control panel to stop the ServletExec service.
   2. (Optional) Uninstall the 64–bit JVM.
   3. Edit the StartServletExec.bat and StopServletExec.bat files to point to the 32–bit JVM.
   4. Use the Services control panel to start the ServletExec service.
4. Stop and restart the IIS Admin Web service and IIS Web server.

Set Permissions for IIS Users After Installing ServletExec

Since ServletExec/AS runs as part of the IIS process, it runs as different users at different times. As a result, you must set the following permissions for the ServletExec installation directory and subdirectories.

To set permissions for IIS users after installing ServletExec, Make sure the user that runs IIS (for example, Network Services) has read and write access to the entire directory tree under C:\Program Files\New Atlanta.

How to Configure the OneView Monitor GUI on UNIX/Sun Java System

To configure the OneView Monitor GUI on a UNIX/Sun Java System complete the following procedures:

1. Read the prerequisites to installing ServletExec.
2. Disable servlets in Sun Java System (Sun One/iPlanet) 6.0.
3. Install ServletExec/AS on UNIX/Sun Java System.
4. If you did not have the Policy Server installation program auto-configure the OneView Monitor GUI, configure it by running the Policy Server Configuration Wizard.
5. Start the OneView Monitor Service.
6. Access the OneView Monitor GUI.

Prerequisites to Installing ServletExec

CA recommends that you read the ServletExec documentation before installing ServletExec. If ServletExec is not running properly, then the OneView Monitor GUI does not work since it relies on ServletExec’s servlet engine.

You can access the ServletExec documentation on the New Atlanta Web site.

Disable Servlets in Sun Java System 6.0

Ensure you follow the steps in this section before installing ServletExec.

To disable servlets in Sun Java System 6.0

1. Open the Sun Java System Enterprise Administration Server home page by entering the following URL in a browser: http://<yourserver.com>:<portnumber>

   yourserver.com

   Specifies the domain name of the Enterprise Administration Server

   port

   Specifies the port number

2. In the Select a Server drop-down menu, select the target server, and then click Manage.
3. Select the Java tab.
4. Deselect Enable Java for class defaultclass and Enable Java Globally and click OK.
5. Stop and restart the Web server so the settings can take effect.

Install ServletExec/AS on UNIX/Sun Java System

The Monitor GUI’s HTML pages are generated by Java Server Pages (JSPs) and servlets hosted on a ServletExec servlet engine running on the same machine as the Policy Server.

To install ServletExec

1. Log in to the UNIX account where you want to install the Policy Server.

   Note: You must log in as the same user who installed the Sun Java System Web server.

2. Run the ServletExec AS installer.

   Note: For more information on running the ServletExec AS installer, refer to New Atlanta Communications' ServletExec documentation. Consider the following before installing ServletExec:

   • Make sure you have permission to create a new file in /tmp. New Atlanta recommends installing ServletExec in /usr/local/NewAtlanta. Installing ServletExec in /usr/local/NewAtlanta may change the permissions for the obj.conf file and the Sun Java System start script. After the installation, be sure the owner of obj.conf and the start script is the same user who owns the Web server.
   • When prompted, install a Web server adaptor and an instance of ServletExec.
   • When prompted, ensure that the installer does not modify the Web server's configuration files. If you let the installer modify the Web server’s obj.conf and magnus.conf configuration files, the Web server instance fails to run after you configure the OneView Monitor GUI on this instance.
3. After the installation program completes, restart the Web server.

More Information:

Start the OneView Monitor Service

Start the OneView Monitor Service

To start the OneView Monitor service

1. Make sure the IPC port numbers are available.

   The OneView Monitor uses the following port numbers to communicate with the Policy Server processes:

   • Monitoring Agent: 44449
   • Monitor: 44450

   To see which port numbers are unavailable, open a Command Window and enter:

   netstat -an
   

   Note: For more information on changing the port numbers, see the Policy Server Administration Guide.

2. Using the Status tab of the Policy Server Management Console, start the Monitor service.

Access the OneView Monitor GUI

To access the OneView Monitor GUI

Enter the following URL in a browser:

http://server:<portnumber>/sitemindermonitor

server

Specifies the Web Server’s IP Address

portnumber

Specifies the port number.

Monitor a Policy Server Cluster

The OneView Monitor can be configured to monitor a Policy Server cluster when one Policy Server is set up as a centralized monitor for other Policy Servers in a cluster.

Note: More information about using the OneView Monitor exists in the Policy Server Administration Guide.