Previous Topic: Policy Store TroubleshootingNext Topic: Administrative UI Troubleshooting


OneView Monitor Troubleshooting

The following sections detail common problems you may experience with the OneView Monitor during installation and the proposed solutions.

Fix Modified UNIX/Sun Java System Web Server Configuration Files

If the ServletExec installation modified the Oracle iPlanet web server configuration files, the web server instance fails after you configure the OneView Monitor UI. The ServletExec installer added entries in these files that conflict with entries from the Policy Server.

Follow these steps:

  1. Open the following configuration file: /sunjavasystem_home/servers/https-web_server_instance_name.domain.com/config/magnus.conf.
  2. Remove the first line:
    Init fn="ServletExecInit" ServExec_instance_name.instances="IP_address:port_number"
    
    ServExec_instance_name

    Specifies the name of your SerlvetExec instance.

    IP_address

    Specifies the IP address of the system to which ServletExec is installed.

    port_number

    Specifies the port number for the SerlvetExec instance.

    Note: The Policy Server Configuration Wizard added the correct entry at the end of the file.

  3. Open the following configuration file: /sunjavasystem_home/servers/https-web_server_instance_name.domain.com/config/obj.conf.
  4. Complete the following steps:
    1. Remove fourth and fifth lines from the top of the file:
      NameTrans fn="assign-name" from="/servlet/*"
      name="<ServExec_instance_name>"
      NameTrans fn="assign-name" from="*.jsp*"
      name="<ServExec_instance_name>"
      

      Important! Do not remove the following entry from the second and third lines. The Policy Server Configuration Wizard added this entry.

      name=se-ServExec_instance_name
      
    2. Remove the second to the last section from the end of the file:
      <Object name="ServExec_instance_name"
      Service fn="ServletExecService" group="ServExec_instance_name"
      </Object>
      

      Important! Do not remove the following entry. The Policy Server Configuration Wizard added this entry.

      <Object name="se-ServExec_instance_name">
      
  5. Save the configuration files and start the web server instance.
Windows/IIS Virtual Path to /sitemindermonitor Does Not Exist

Valid on Windows

Symptom:

The virtual path to the /sitemindermonitor does not exist under Default Web Site in the IIS Microsoft Management Console.

Solution:

Create the virtual path.

To create the virtual path

  1. From the Start menu, go to: Programs, Administrative Tools, Internet Service Manager.
  2. Select Default Web Site.
  3. From the Action menu, select New, Virtual Directory.

    The Virtual Directory Wizard opens.

  4. Specify the name (alias) of the virtual directory. For example:
    sitemindermonitor

    Note: You can specify any name for the alias as sitemindermonitor is an example

  5. Click Next.
  6. Specify the path to <siteminder_installation>\monitor\.
  7. Click Next.
  8. Select the following permission:
    Allow Execute Access
    
  9. Click Finish.