The following sections detail common problems you may experience with the OneView Monitor during installation and the proposed solutions.
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:
Init fn="ServletExecInit" ServExec_instance_name.instances="IP_address:port_number"
Specifies the name of your SerlvetExec instance.
Specifies the IP address of the system to which ServletExec is installed.
Specifies the port number for the SerlvetExec instance.
Note: The Policy Server Configuration Wizard added the correct entry at the end 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
<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">
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
The Virtual Directory Wizard opens.
Note: You can specify any name for the alias as sitemindermonitor is an example
Allow Execute Access
Copyright © 2013 CA.
All rights reserved.
|
|