Sun Java System Access Manager Policy Agent 2.2 Guide for Sun Java System Web Server 6.1

Appendix B Troubleshooting a Web Agent Deployment

This appendix applies to Agent for Sun Java System Web Server 6.1. If a problem is discussed in this appendix, it either applies only to this agent or it applies to two or more agents with one of them being this agent. This appendix explains how you can resolve problems that you might encounter while deploying or using this web agent. Be sure to also check the Sun Java System Access Manager Policy Agent 2.2 Release Notes, to see if the problem that you encounter is a known limitation of the web agent. If workarounds are available for such problems, they will be provided in the release notes.

In this chapter, refer to the troubleshooting section applicable to your platform as follows:

Solaris Systems: Troubleshooting Symptoms in Agent for Sun Java System Web Server 6.1

This section includes various problems you might encounter on Solaris systems. The explanation of the problem is followed by possible solutions.

Solaris Systems: Troubleshooting Symptom 1

Symptom: Cannot install the web agent after a previous installation has been removed.

The following is an example message that is displayed when you run the web agent installation program:

Launching installer... Sun Java(tm) System; Access Manager Policy Agent for Sun ONE Web Server 6.0 and 6.1 is installed. Please refer to installation manual to configure this agent for another web server instance or uninstall it before installing another agent.

Possible Causes:

You might have an existing installation of the web agent.
You might have a previously-installed web agent and did not use the web agent’s uninstallation program to uninstall the agent.
The installation program’s productregistry file might be corrupted.

Possible Solutions: Performing the following troubleshooting activities might resolve the issue:

Check that you have uninstalled any existing installation of the web agent.
The productregistry file may be corrupted if there is no existing installation of the web agent. This file is used by the installation program to track installed products. It is found in /var/sadm/install directory.

Note –

Make a backup copy of productregistry file before you make changes.

Remove the web agent entry in this file. This entry starts with the following lines:

<compid>SUNWames6
        <compversion>2.2
                <uniquename>SUNWames6</uniquename>
                <vendor></vendor>
                <compinstance>1
                        <parent>Agent for Sun Java(tm) System Web Server 6.0 and 6.1
                                <instance>1
                                        <version>2.2</version>
                                </instance>
                        </parent>
                        <comptype>COMPONENT</comptype>
                        <location>/opt/webagent</location>
                        <dependent>
                                <compref>Agent for Sun Java(tm) System Web Server 6.0 and 6.1
                                        <instance>1
                                                <version>2.2</version>
                                        </instance>
                                 </compref>
                        </dependent>
                        <data>
                                <key>pkgs
                                    <value>SUNWames6</value>
                                </key>
                        </data>
                </compinstance>
        </compversion>
</compid>
<compid>Agent for Sun Java(tm) System Web Server 6.0 and 6.1
        <compversion>2.2
                <uniquename>Agent for Sun Java(tm) System Web Server 6.0 and 6.1</uniquename>
                <vendor></vendor>
                <compinstance>1
                        <parent>Sun Java(tm) System Access Manager Policy Agent
                               <instance>3
                                        <version>2.2</version>
                               </instance>
                        </parent>
                        <children>
                                 <compref>SUNWames6
                                        <instance>1
                                                <version>2.2</version>
                                        </instance>
                                 </compref>
                       </children>
                       <comptype>FEATURE</comptype>
                       <location>/opt/webagent</location>
                       <dependent>
                                <compref>Sun Java(tm) System Access Manager Policy Agent
                                        <instance>3
                                                <version>2.2</version>
                                        </instance>
                                </compref>
                       </dependent>
                       <required>
                                <compref>SUNWames6
                                        <instance>1
                                                <version>2.2</version>
                                        </instance>
                                </compref>
                        </required>
                </compinstance>
         </compversion>
</compid>

Solaris Systems: Troubleshooting Symptom 2

Symptom: The uninstallation program does not remove entries from the agent’s web container.

Possible Causes: Another instance of the web agent exists that was configured using the configuration script.

Possible Solution: Remove all the instances of the web agent using the unconfig script before running the uninstallation program.

Solaris Systems: Troubleshooting Symptom 3

Symptom: The browser goes into a loop for approximately a minute before displaying an access-denied page.

Possible Cause: The user tries to access a resource for which a policy with a time condition has been set and the time on the web agent host and the Access Manager host are not in sync.

Possible Solution: Login as root and run the command rdate hostname to synchronize the time on both the hosts.

Solaris Systems: Troubleshooting Symptom 4

Symptom: Instances of Agent for Sun Java System Web Server 6.1 are not effective after the modification of the Sun Java System Web Server 6.1 configuration using the Administration Console.

Possible Cause: Modifications to the configuration of the Web Server's configuration files (obj.conf, magnus.conf) might be overwritten by the server, which would disable the web agent completely.

Possible Solution: To ensure this does not occur, after installing the web agent, go to the Web Server’s administration console, and click Apply. You could either load the configuration or click Apply Changes to restart the server. If you encounter this problem, change to the bin directory where the unconfig script is located. Unconfigure the web agent and reconfigure it for this instance of the Web Server. After doing this, bring up the Administration Console of the Web Server and click Apply to save the configuration changes made by the web agent.

Solaris Systems: Troubleshooting Symptom 5

Symptom:When a user attempts to access a resource using Internet Explorer as the browser, access is denied.

Possible Cause: Internet Explorer overrides the port number of the web agent with the Access Manager port number. In such cases, the agent log file lists the URL that is being evaluated. The port number for that URL is incorrect.

Possible Solution: You can ensure this problem does not occur by setting the following property in the web agent AMAgent.properties configuration file to true as shown:

com.sun.am.policy.agents.config.override_port = true

Solaris Systems: Troubleshooting Symptom 6

Symptom: The agent issues a message stating that the web server is not recognized. This problem is specific to Agent for Sun Java System Web Server 6.1.

Possible Cause: Agent for Sun Java System Web Server 6.1 searches for the file WebServer.inf to verify the web server version number, but the file does not exist.

Possible Solution: Enable Agent for Sun Java System Web Server 6.1 to recognize the Sun Java System Web Server 6.1 instance by creating a file and adding text to that file that includes the version number of the Sun Java System Web Server instance as demonstrated in the task description that follows.

To Create a File To Allow Agent for Sun Java System Web Server 6.1 To Recognize the Web Server

Create a directory named WebServer in the following directory of the Sun Java System Web Server 6.1 instance:
```
WebServer-base/setup/
```
After you perform this step, the full path to this directory is as follows:
```
WebServer-base/setup/WebServer/
```

Create a filed named WebServer.inf in the WebServer directory.

After you perform this step, the full path to this file is as follows:
```
WebServer-base/setup/WebServer/WebServer.inf
```

Add the version information of Sun Java System Web Server 6.1 to the WebServer.inf file.

After you perform this step, the WebServer.inf file includes the following type of information:
[webcore] Version=6.1

Save the file.

Next Steps

Once you have properly created the WebServer.inf file, install Agent for Sun Java System Web Server 6.1.

Windows Systems: Troubleshooting Symptoms in Agent for Sun Java System Web Server 6.1

This section includes various problems you might encounter on Windows systems. The explanation of the problem is followed by possible solutions.

Windows Systems: Troubleshooting Symptom 1

Symptom: Cannot install the web agent after a previous installation has been removed.

Possible Causes:

You might have an existing installation of the web agent.
You might have a previously-installed web agent and did not use the web agent’s uninstallation program to uninstall the agent.
The installation program’s productregistry file might be corrupted.

Possible Solution: To resolve the issue, manually remove the web agent as explained in the following task description.

To Manually Remove Agent for Sun Java System Web Server 6.1

Stop all of the web sites.

Stop the web server instance.

Remove Agent for Sun Java System Web Server 6.1.
1. In the Start menu, select Control Panel->Add/Remove programs
2. Select Sun Java System Access Manager Policy Agent PolicyAgent-base.
3. Click Remove

Remove the PolicyAgent-base directory from the server.

where PolicyAgent-base represents the directory in which the web agent was originally installed.

Remove the following entries from the PATH variable:
- PolicyAgent-base\bin
- PolicyAgent-base\es6\bin

Restart the server.

Windows Systems: Troubleshooting Symptom 2

Symptom: Unable to uninstall the agent from a Windows system using the Add/Remove Program option in the Control Panel.

Possible Causes: Java’s class path might not be set correctly on the machine.

Possible Solution: Perform the following task.

To Uninstall a Web Agent on a Windows System When the GUI Uninstallation Fails

Open Command Prompt Window.

Change directories to PolicyAgent-base

Execute the following command:

java uninstall_Sun_Java_tm_System_Access_Manager_Policy_Agent

Windows Systems: Troubleshooting Symptom 3

Symptom: Instances of Agent for Sun Java System Web Server 6.1 are not effective after modification of the Sun Java System Web Server 6.1 configuration using the Administration Console

Possible Causes: The changes made by the agent installation to the server configuration files are overwritten by saving the changes in Administration Console.

Possible Solution: The right procedure when using the Administration Console is to load the configuration first (from disk file to memory), then to make modifications and save the changes (from memory to disk) by clicking the Apply button.

Windows Systems: Troubleshooting Symptom 4

Symptom:When a user attempts to access a resource using Internet Explorer as the browser, access is denied.

Possible Solution: You can ensure this problem does not occur by setting the following property in the web agent AMAgent.properties configuration file to true as shown:

com.sun.am.policy.agents.config.override_port = true

Windows Systems: Troubleshooting Symptom 5

Symptom: The agent issues a message stating that the web server is not recognized. This problem is specific to Agent for Sun Java System Web Server 6.1.

Possible Cause: Agent for Sun Java System Web Server 6.1 searches for the file WebServer.inf to verify the web server version number, but the file does not exist.

To Create a File To Allow Agent for Sun Java System Web Server 6.1 To Recognize the Web Server

Create a directory named WebServer in the following directory of the Sun Java System Web Server 6.1 instance:
```
WebServer-base/setup/
```
After you perform this step, the full path to this directory is as follows:
```
WebServer-base/setup/WebServer/
```

Create a filed named WebServer.inf in the WebServer directory.

After you perform this step, the full path to this file is as follows:
```
WebServer-base/setup/WebServer/WebServer.inf
```

Add the version information of Sun Java System Web Server 6.1 to the WebServer.inf file.

After you perform this step, the WebServer.inf file includes the following type of information:
[webcore] Version=6.1

Save the file.

Next Steps

Once you have properly created the WebServer.inf file, install Agent for Sun Java System Web Server 6.1.

Windows Systems: Troubleshooting Symptom 6

Symptom: After the agent is installed, the web server fails to start.

Possible Cause: Libraries that agents depend on for Windows systems are missing. Ensuring that the libraries msvcp70.dll and msvcr70.dll are available is a pre-installation step in this guide. If the libraries were not properly added, the web server might not start.

Possible Solution: Obtain the appropriate libraries as described in Preparing to Install Agent for Sun Java System Web Server 6.1 on Windows Systems.

Linux Systems: Troubleshooting Symptoms in Agent for Sun Java System Web Server 6.1

This section includes various problems you might encounter on Linux systems. The explanation of the problem is followed by possible solutions.

Linux Systems: Troubleshooting Symptom 1

Symptom:When a user attempts to access a resource using Internet Explorer as the browser, access is denied.

Possible Solution: You can ensure this problem does not occur by setting the following property in the web agent AMAgent.properties configuration file to true as shown:

com.sun.am.policy.agents.config.override_port = true

Linux Systems: Troubleshooting Symptom 2

Symptom: The agent issues a message stating that the web server is not recognized. This problem is specific to Agent for Sun Java System Web Server 6.1.

Possible Cause: Agent for Sun Java System Web Server 6.1 searches for the file WebServer.inf to verify the web server version number, but the file does not exist.

To Create a File To Allow Agent for Sun Java System Web Server 6.1 To Recognize the Web Server

Create a directory named WebServer in the following directory of the Sun Java System Web Server 6.1 instance:
```
WebServer-base/setup/
```
After you perform this step, the full path to this directory is as follows:
```
WebServer-base/setup/WebServer/
```

Create a filed named WebServer.inf in the WebServer directory.

After you perform this step, the full path to this file is as follows:
```
WebServer-base/setup/WebServer/WebServer.inf
```

Add the version information of Sun Java System Web Server 6.1 to the WebServer.inf file.

After you perform this step, the WebServer.inf file includes the following type of information:
[webcore] Version=6.1

Save the file.

Next Steps

Once you have properly created the WebServer.inf file, install Agent for Sun Java System Web Server 6.1.