Previous Topic: OneView Monitor Troubleshooting

Next Topic: Windows/IIS Virtual Path to /sitemindermonitor Does Not Exist

Fix Modified UNIX/Sun Java System Web Server Configuration Files

As mentioned in the procedure for installing the ServletExec/AS on a UNIX/Sun Java System, we advise not allowing ServletExec to modify the Sun Java System Web server's configuration files (obj.conf and magnus.conf). However, if ServletExec did modify these files during installation, the Web server instance fails after you configure the FSS Administrative UI and OneView Monitor GUI using the Policy Server installer/wizard. The ServletExec installer puts entries in these files that conflict with those from the Policy Server.

To keep the Web server instance from failing, remove the conflicting entries from the Sun Java System Web Server instance's obj.conf and magnus.conf files.

  1. Open /<sunjavasystem_home>/servers/https-<web_server_instance_name>.domain.com/config/magnus.conf, and remove the first line:
    Init fn="ServletExecInit" <ServExec_instance_name>.instances="<IP_address>:<portnumber> "
    

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

  2. Open /<sunjavasystem_home>/servers/https-<web_server_instance_name>.domain.com/config/obj.conf, and remove lines four and five 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
    name="se-<ServExec_instance_name>" entries in lines two and three since these were added by the Policy Server Configuration Wizard.

  3. In the same obj.conf file, remove the second to the last <Object name="<ServExec_instance_name>"> 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
    <Object name="se-<ServExec_instance_name>"> entry since this one was added by the Policy Server Configuration Wizard.

  4. After saving these files, you should be able to start the Web server instance from the Sun Java System Web Server Administration Server page.


Copyright © 2010 CA. All rights reserved. Email CA about this topic