CA SiteMinder ® Web Agent Installation Guide r12.
This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for your informational purposes only and are subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA.
CA Product References This document references the following CA products: ■ CA SiteMinder® ■ CA Identity Manager ■ CA SOA Security Manager Contact CA Contact Technical Support For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At http://ca.
Contents Chapter 1: Preparation 11 How to Prepare for a Web Agent Installation ..................................................... 11 Supported Operating Systems and Web Servers ................................................. 12 How to Prepare a Windows System for a Web Agent Installation .............................. 12 How to Prepare a UNIX System for a Web Agent Installation .................................. 14 AIX Requirements .....................................................................
Installation and Configuration Log Files ...................................................... 41 Modify the SmHost.conf File (Windows) ...................................................... 42 Re-register a Trusted Host Using the Registration Tool (Windows) ............................. 44 Register Multiple Trusted Hosts on One System (Windows) ....................................... 47 Registration Services Installed Files (Windows) ..................................................
Add the Agent ISAPI Filter to Additional Web Sites that you want to Protect with SiteMinder ............................................................................................ 89 How to Configure a SiteMinder Web Agent on IIS 6.0 ............................................. 91 Assign Read Permissions to Samples and Error Files Directories ............................... 92 Allow IIS to Execute the Agent ISAPI and CGI Extensions ..................................... 93 IIS 6.
Chapter 8: Configure a Domino Web Agent 135 Configure a Domino Web Agent on Windows Systems ........................................... 135 Add the Domino Web Agent DLL (Windows) ................................................. 136 Run the Configuration Wizard for a Domino Web Agent on Windows .......................... 137 (Optional) Configure the CGI Directory and CGI URL Path Settings ...........................
Uninstall a Web Agent from a UNIX System ..................................................... 164 Uninstall Documentation from UNIX Systems ................................................ 165 Chapter 13: Troubleshooting 167 Agent Start-Up/Shutdown Issues (Framework Agents Only) ..................................... 167 Agent Won‘t Start Because LLAWP is Already Running or Log Messages not Written to the Correct Log Files ...........................................................................
Register a Trusted Host ........................................................................ 182 Identify Policy Servers for Trusted Host Registration ............................................ 183 Specify the Host Configuration File ............................................................. 183 Select a Web Server for Configuration .......................................................... 184 WEB_SERVER_INFO Variables ..............................................................
Chapter 1: Preparation This section contains the following topics: How to Prepare for a Web Agent Installation (see page 11) Supported Operating Systems and Web Servers (see page 12) General Preparations for All Web Agents (see page 19) Policy Server Requirements (see page 20) Prepare for Password Services (see page 23) Prepare for Registration Services (Optional) (see page 25) How to Prepare for a Web Agent Installation To prepare for a Web Agent installation, use the following process: 1.
Supported Operating Systems and Web Servers Supported Operating Systems and Web Servers Before you install a Web Agent, make sure you are using a supported operating system and web server configuration. For a list of SiteMinder Web Agents and supported web server platforms, go to Technical Support, and search for the SiteMinder r12.0 SP2 Platform Matrix.
Supported Operating Systems and Web Servers The actual tools and steps involved in editing the Metabase depend on the version of IIS you are using. For example, if you are using an r12.0 SP2 SiteMinder Web Agent, on IIS 6.0, you would edit the Metabase using the following process: Note: For more information, see your Microsoft documentation, or go to http://support.microsoft.com/ 1. Download and install the Metabase Explorer from Microsoft by doing the following: a. Go to the Microsoft Downloads website.
Supported Operating Systems and Web Servers 10. Close the Metabase Explorer. 11. Run the Configuration Wizard to reconfigure your IIS Web Agent. 12. Repeat Steps 3 through 10, but change the number 1 back to the original identifier from in Step 2. 13. Restart the IIS web server. Install an Apache Web Server on Windows as a Service for All Users The Web Agent Configuration Wizard will not detect a valid Apache installation if the Apache web server is installed for an individual user.
Supported Operating Systems and Web Servers Required Solaris Patches Before installing a Web Agent on a Solaris machine, you must install the following patches: Solaris 9 Requires patch 111711-16. Solaris 10 Requires patch 119963-08. You can check on patch versions by logging in as root and executing the following command: showrev -p | grep patch_id To locate Solaris patches, go to Sun Microsystems Solution Center. Solaris Settings for Certain Apache 1.3 Type Web Servers Certain versions of Apache 1.
Supported Operating Systems and Web Servers HP-UX Release Patch HP-UX 11i v1 ■ PHSS_26560 ld and linker cumulative patch AIX Requirements SiteMinder Web Agents running on AIX systems require the following patches: ■ For Apache 1.
Supported Operating Systems and Web Servers Required Linux Libraries When installing a Red Hat Enterprise Linux version of a Web Agent, the following are required libraries: ■ On Red Hat Enterprise Linux 2.1, if using the "linux" kit (the kit built with GCC 2.96), there are no libraries required that are not part of a basic installation. ■ On Red Hat Enterprise Linux 3.0, use the "linux" kit (the kit built with GCC 3.2), and there are no libraries required that are not part of a basic installation.
Supported Operating Systems and Web Servers IBM Hot Fix Required for Domino 6.5.2 IBM hot fix SPR #NORK632KQA is required for a Web Agent to run on a Domino 6.5.2 server. This hotfix applies to Windows and UNIX platforms. Miscellaneous Web Server Preparations The following sections discuss installation preparations for various web servers.
General Preparations for All Web Agents General Preparations for All Web Agents The following sections describe general preparations for all Web Agents. Gather information Needed to Complete the Agent Installation You must have the following information before installing the Web Agent: ■ Name of the SiteMinder Administrator allowed to install Agents ■ Name of the Host Configuration Object. This defines the trusted host configuration.
Policy Server Requirements For details on supported web server and operating system versions, go to Technical Support, and then search for the SiteMinder r12.0 SP2 Platform Support Matrix. Policy Server Requirements Before you install the Web Agent, the Policy Server must be installed, configured and able to communicate with the system where you plan to install the Web Agent. Note: For more information, see the Policy Server documentation.
Policy Server Requirements Agent Configuration Parameters Required by All Agents All Agents must have a value set for the following parameter: DefaultAgentName Defines a name that the Web Agent uses when it receives a request on an IP address or interface for which there is no agent name specified in the AgentName parameter. If you are using virtual servers, you can set up your SiteMinder environment quickly by using a DefaultAgentName instead of defining a separate Web Agent for each virtual server.
Policy Server Requirements Agent Configuration Parameters Required for Domino Web Agents In addition to the parameters required by all Agents, Domino Web Agents must also have values set for the following parameters: DominoDefaultUser Specifies the name by which the Domino Web Agent identifies the users that SiteMinder has previously authenticated against another directory to the Domino server. Important! This parameter must be encrypted if it is stored in a local configuration file.
Prepare for Password Services Agent Configuration Parameters Required for IIS Web Agents In addition to the parameters required by all Agents, IIS Web Agents may need to have values set for the following parameters in certain circumstances: DefaultUsername Specifies the name of a Windows user that is used to access IIS resources as a proxy user. When users want to access resources on an IIS web server protected by SiteMinder, they may not have the necessary server access privileges.
Prepare for Password Services Repair ServletExec’s CLASSPATH for JSP Password Services (Windows) If you install JSP-based Password Services on a Windows system and get an error message that a servlet is not found when you access an existing servlet or Password Services .jsp, verify that the ServletExec classpath is correct. If your classpath appears correct and the error still occurs, you may need to repair your classpath.pref file. To repair the ServletExec classpath 1.
Prepare for Registration Services (Optional) Prepare for Registration Services (Optional) The following sections discuss prerequisites and guidelines for registration services. Use Registration Services The SiteMinder Web Agent includes Registration Services. Registration Services is a subset of the DMS product, but you can use it without a DMS license. Note: For more information, see the Policy Server documentation. To continue using your existing DMS application with r12.
Prepare for Registration Services (Optional) Use Active Directory for Registration Services (Windows Only) If you want to use Active Directory with Registration Services, check that: ■ Windows 2000, including Active Directory, is operational ■ Microsoft‘s Certificate Server is configured for Active Directory ■ Active Directory‘s Root Certificate is accessible from a browser Note: For information about configuring Active Directory, see the DMS 2.01 Release Notes.
Prepare for Registration Services (Optional) Modify the DMS Admin Password for Registration Services The DMS Administrator is a SiteMinder administrator with Manage User privileges.
Prepare for Registration Services (Optional) Modify the ServletExecAS Startup Script to Run Registration Services with ServletExecAS (UNIX only) If you are using Registration Services with ServletExecAS you must modify the StartServletExec script. To modify the StartServletExec script 1. Open the StartServletExec script with a text editor. See the ServletExecAS documentation for the exact location of this script. Note: You can access the ServletExec documentation on the New Atlanta Web site. 2.
Prepare for Registration Services (Optional) Operating System Path Variable Solaris LD_LIBRARY_PATH HP-UX SHLIB_PATH LINUX LD_LIBRARY_PATH AIX LIBPATH Chapter 1: Preparation 29
Chapter 2: Install a Web Agent on a Windows System This section contains the following topics: Run a GUI Mode Installation on Windows (see page 32) Unattended Installations on Windows (see page 34) Reinstall the Web Agent on Windows (see page 36) Installation History Log File (see page 37) Register Your System as a Trusted Host on Windows (see page 38) Register Multiple Trusted Hosts on One System (Windows) (see page 47) Registration Services Installed Files (Windows) (see page 48) Fix the ServletExec CLASS
Run a GUI Mode Installation on Windows Run a GUI Mode Installation on Windows To install an Agent, you must be logged into the system where the web server is installed. 1. Exit all applications that are running and stop the web server. 2. Download the installation file from Technical Support. 3. Navigate to the win folder then run the executable file for your operating system: ca-wa-version-winprocessor_type.
Run a GUI Mode Installation on Windows If the installation program detects that there are locked Agent files, it will prompt you to restart your system instead of reconfiguring it. Select whether to restart the system automatically or later on your own. For Web Agents installed on IIS 6.0 servers, reboot your system after installation; it is not sufficient to restart the IIS service. Important! If you are configuring an Agent on an IIS web server, do not configure the Agent immediately after installation.
Unattended Installations on Windows Unattended Installations on Windows After you have installed the Web Agent on one system, you can automate installations on other web servers using the Agent‘s unattended installation feature. An unattended installation lets you install or uninstall the Web Agent without any user interaction. An unattended installation uses a properties file that is initially configured with values from the initial GUI or console mode Web Agent installation.
Unattended Installations on Windows Run an Unattended Installation on Windows You should have completed an initial Web Agent installation and, if necessary, modified the ca-wa-installer.properties file. Now, you can use the file to run subsequent Web Agent installations. To run an unattended Web Agent installation 1. From a system where the Web Agent is already installed, copy the following files to a local directory: a. ca-wa-version-win32.exe (Agent executable) from where it resides on your system. b.
Reinstall the Web Agent on Windows More Information How to Configure a SiteMinder Web Agent on IIS 6.0 (see page 91) How to Configure Any Web Agent in Unattended Mode (see page 145) How to Stop an Unattended Installation in Progress on Windows To manually stop an unattended installation on Windows systems, use the following process: 1. Open the Windows Task Manager. 2. Stop the following processes: ■ ca-wa-version-win.exe ■ wa_install.
Installation History Log File Installation History Log File The installer creates a log file with following information: ■ The product name ■ The installed location ■ The complete (full) version number This file is created in the following location: Windows C:\Program Files\CA\install-info\ca-install-history.log UNIX /opt/ca/install-info/ca-install-history.
Register Your System as a Trusted Host on Windows Register Your System as a Trusted Host on Windows A trusted host is a client computer where one or more SiteMinder Web Agents can be installed. The term trusted host refers to the physical system. To establish a connection between the trusted host and the Policy Server, you need to register the host with the Policy Server. After registration is complete, the registration tool creates the SmHost.conf file.
Register Your System as a Trusted Host on Windows This administrator should already be defined at the Policy Server and have the permission Register Trusted Hosts set. The default administrator is SiteMinder. ■ Admin Password—enter the administrator‘s password. ■ Confirm Admin Password—re-enter the password. ■ Enabled Shared Secret Rollover—check this box to periodically change the shared secret used to encrypt communication between the trusted host and the Policy Server.
Register Your System as a Trusted Host on Windows policyserver="ip_address,5555,5555,5555" b. Click Add. You can add more than one Policy Sever; however, for host registration, only the first server in the list will be used. If multiple Policy Servers are specified, the Agent uses them as bootstrap servers. When the Agent starts up, the Web Agent has several Policy Servers to which it can connect to retrieve its Host Configuration Object.
Register Your System as a Trusted Host on Windows The host is registered and a host configuration file, SmHost.conf, is created in web_agent_home/config. You can modify this file. web_agent_home Indicates the directory where the Web Agent is installed. Default (Windows installations): C:\Program Files\CA\webagent Default (UNIX installations): /opt/ca/webagent 10. Click Continue. 11.
Register Your System as a Trusted Host on Windows Modify the SmHost.conf File (Windows) Web Agents and custom Agents act as trusted hosts by using the information in the SmHost.conf file to locate and make initial connections to a Policy Server. Once the Agent connects to the Policy Server, the initial connections are closed. Any further communication between the Agent and the Policy Server is based on settings in the Host Configuration Object that is located on the Policy Server.
Register Your System as a Trusted Host on Windows Important: If an Agent is configured on a multi-process web server, specifying multiple Policy Server entries is recommended to ensure that any child process can establish a connection to the secondary Policy Server if the primary Policy Server fails. Each time a new child process is started, it will not be able to initialize the Web Agent if only one Policy Server is listed in the file and that Policy Server is unreachable.
Register Your System as a Trusted Host on Windows Re-register a Trusted Host Using the Registration Tool (Windows) When you install a Web Agent on a server for the first time, you are prompted to register that server as a trusted host. After the trusted host is registered, you do not have to re-register with subsequent Agent installations.
Register Your System as a Trusted Host on Windows The following arguments are used with the smreghost command: -i policy_server_IP_ address:port Indicates the IP address of the Policy Server where you are registering this host. Specify the port of the authentication server only if you are not using the default port.
Register Your System as a Trusted Host on Windows -f path_to_host_config_file (Optional) Indicates the full path to the file that contains the registration data. The default file is SmHost.conf. If you do not specify a path, the file is installed in the location where you are running the smreghost tool. If you use the same name as an existing host configuration file, the tool backups up the original and adds a .bk extension to the backup file name.
Register Multiple Trusted Hosts on One System (Windows) Default: ETPKI -cd crypto_provider_DLL_or_configuration_file_path (Required for PKCS11 encryption) Indicates the full path to the PKCS11 DLL or configuration file. -ct crypto_provider_token_label (Optional for PKCS11 encryption) Indicates the token label for the hardware token. Only use this argument if there is a token label. -o Overwrites an existing trusted host.
Registration Services Installed Files (Windows) To register multiple trusted hosts, use one of the following methods: ■ Registering with the Configuration Wizard: To register additional servers as trusted hosts, go through the registration process again; however, when prompted to specify a location for the SmHost.conf file, enter a unique path. Do not register a new host and use an existing web server‘s SmHost.conf file or that file will be overwritten. You can use the name SmHost.
Registration Services Installed Files (Windows) Physical Directories The Web Agent installation puts the Registration Services sub-directories in: ■ web_agent_home\samples Contains files used by Registration Services that you can customize. ■ web_agent_home\samples_default Contains backup files for Registration Services. Do not modify these files.
Fix the ServletExec CLASSPATH for DMS Fix the ServletExec CLASSPATH for DMS If you install DMS on a Windows system and get ‗servlet DMS not found‘ errors when you access a DMS page, verify that the ServletExec classpath is correct. If your classpath appears correct and the error still occurs, you may need to repair your classpath.pref file. To repair the ServletExec classpath 1. Use the ServletExec Administrative Interface to define the Classpath for the Java Virtual Machine.
Chapter 3: Install a Web Agent on a UNIX System This section contains the following topics: Install the Web Agent Documentation on UNIX Systems (see page 52) Install the Web Agent on a UNIX System (see page 53) Set the Web Agent Environment Variables After Installation (see page 60) Set Web Agent Variables when using apachectl Script (see page 61) Installation History Log File (see page 61) Reinstall a Web Agent on UNIX (see page 62) Register Your System as a Trusted Host on UNIX (see page 62) Register a Tr
Install the Web Agent Documentation on UNIX Systems Install the Web Agent Documentation on UNIX Systems You install the Web Agent documentation independently from the Web Agent—it is not installed by default. We recommend that you install the documentation before installing the Web Agent so you can specify the install location.
Install the Web Agent on a UNIX System Install the Web Agent on a UNIX System There are several types of Web Agent installations on a UNIX system: Note: Installing a Web Agent on a 64-bit Suse Linux 10 system requires additional preparations. ■ Installing from a graphical user interface ■ Installing from a console window responding to command-line prompts ■ Installing installation file, unattended by an administrator and requiring no user interaction.
Install the Web Agent on a UNIX System Run a GUI Mode Installation on UNIX To install an Agent, you must be logged into the account where the web server is installed. Note: If you are upgrading an existing r12 Web Agent to r12 SP1, you must login as the root user. If you are installing a new r12 SP1 Web Agent, root privileges are not required. To run a GUI mode installation on UNIX: 1.
Install the Web Agent on a UNIX System The installation program prepares the files. 9. In the Introduction dialog box, read the information then click Next. 10. Read the License Agreement then select the radio button to accept the agreement. Click Next. If you do not accept the agreement, the installation terminates. 11. Read the notes in the Important Information dialog box, then click Next. 12.
Install the Web Agent on a UNIX System Run a Console Mode Installation on UNIX You can install the SiteMinder Web Agent on a UNIX system using the console mode. Note: If you are upgrading an existing r12 Web Agent to r12 SP1, you must login as the root user. If you are installing a new r12 SP1 Web Agent, root privileges are not required. To run a console mode installation on UNIX 1. Exit all applications that are running and stop the web server. 2.
Install the Web Agent on a UNIX System 12. In the Choose Install Location section, specify the location where the installation should place the Agent files. To accept the default location, press Enter. If you specify a path, it must contain the word "webagent." If it does not, the installation program will create this folder and append it to the path. For example, if you specify export/ca/wa, the path becomes export/ca/wa/webagent.
Install the Web Agent on a UNIX System Prepare an Unattended Installation on UNIX Unattended installation uses the ca-wa-installer.properties file to propagate the Web Agent installation set up to all Agents in your network. In this properties file, you define installation parameters, then copy the file and the Web Agent executable file to any web server in your network to run an unattended installation. The ca-wa-installer.
Install the Web Agent on a UNIX System Run an Unattended Installation on UNIX You should have completed an initial Web Agent installation and, if necessary, modified the ca-wa-installer.properties file. Now, you can use the file to run subsequent Web Agent installations. To run an unattended Web Agent installation 1. From a system where the Web Agent is already installed, copy the following files to a local directory: a. ca-wa-version-operating_system.
Set the Web Agent Environment Variables After Installation Set the Web Agent Environment Variables After Installation You can set the Web Agent environment variables after installing the Web Agent using the ca_wa_env.sh script Running the script for Web Agents installed on most UNIX platforms ensures that the Web Agent and web server can work together. The script sets environment variables required by the Web Agent. The ca_wa_env.
Set Web Agent Variables when using apachectl Script Set Web Agent Variables when using apachectl Script If you run your Apache server using the apachectl script (such as when running an Apache web server on POSIX), add a line to the apachectl script to set the environment variables for the SiteMinder Web Agent. To set the web agent variables when using apachectl script on Apache servers 1. Locate a line resembling the following example: # Source /etc/sysconfig/httpd for $HTTPD setting, etc 2.
Reinstall a Web Agent on UNIX Reinstall a Web Agent on UNIX You can reinstall a Web Agent to restore missing application files. For this procedure, you do not need to uninstall the existing Web Agent; simply perform a reinstall over the existing Web Agent files by repeating the installation procedure. To reinstall the Web Agent on UNIX, use the following process: 1. Make copies of your Web Agent configuration settings to have as a back up. 2.
Register a Trusted Host in GUI or Console Mode Register a Trusted Host in GUI or Console Mode These instructions are for GUI and Console Mode registration. The steps for the two modes are the same, with the following exceptions for Console mode: ■ You may be instructed to select an option by entering a corresponding number for that option. ■ You press Enter after each step to proceed through the process. The prompts should guide you through the process.
Register a Trusted Host in GUI or Console Mode ■ Admin Password—enter the administrator‘s password. ■ Confirm Admin Password—re-enter the password. ■ Enabled Shared Secret Rollover—check this box to periodically change the shared secret used to encrypt communication between the trusted host and the Policy Server. Key rollover must be enabled at the Policy Server for this feature to work.
Register a Trusted Host in GUI or Console Mode Note also that if you specify a non-default port, that port is used for the Policy Server‘s authentication, authorization, and accounting ports; however, the unified server responds to any Agent request on any port. The entry in the SmHost.conf file will resemble: policyserver="ip_address,5555,5555,5555" b. Click Add. You can add more than one Policy Sever; however, for host registration, only the first server in the list will be used.
Register a Trusted Host in GUI or Console Mode 9. Accept the default location of the host configuration file, SmHost.conf or click Choose to select a different location. Click Next. If you select a non-default location then want to revert to the default directory, click Restore Default Folder. The host is registered and a host configuration file, SmHost.conf, is created in web_agent_home/config. You can modify this file. 10. Configure your Web Agent.
Register a Trusted Host in GUI or Console Mode Modify the SmHost.conf File (UNIX) Web Agents and custom Agents act as trusted hosts by using the information in the SmHost.conf file to locate and make initial connections to a Policy Server. Once the Agent connects to the Policy Server, the initial connections are closed. Any further communication between the Agent and the Policy Server is based on settings in the Host Configuration Object that is located on the Policy Server.
Register a Trusted Host in GUI or Console Mode Important: If an Agent is configured on a multi-process web server, specifying multiple Policy Server entries is recommended to ensure that any child process can establish a connection to the secondary Policy Server if the primary Policy Server fails. Each time a new child process is started, it will not be able to initialize the Web Agent if only one Policy Server is listed in the file and that Policy Server is unreachable.
Register a Trusted Host in GUI or Console Mode Re-register a Trusted Host Using the Registration Tool (UNIX) When you install a Web Agent on a server for the first time, you are prompted to register that server as a trusted host. After the trusted host is registered, you do not have to re-register with subsequent Agent installations.
Register a Trusted Host in GUI or Console Mode HP-UX SHLIB_PATH LINUX LD_LIBRARY_PATH AIX LIBPATH 4. Enter the smreghost command using the following required arguments, as shown in the following example: smreghost -i policy_server_IP_address:[port] -u administrator_username -p Administrator_password -hn hostname_for_registration -hc host_configuration_ object Note: Separate each command argument from its value with a space. Surround any values that contain spaces with double quotes (").
Register a Trusted Host in GUI or Console Mode -p Administrator_password Indicates the password of the Administrator who is allowed to register a trusted host. -hn hostname_for_registration Indicates the name of the host to be registered. This can be any name that identifies the host, but it must be unique. After registration, this name is placed in the Trusted Host list in the Administrative UI. -hc host_config_object Indicates the name of the Host Configuration Object configured at the Policy Server.
Register a Trusted Host in GUI or Console Mode -f path_to_host_config_file (Optional) Indicates the full path to the file that contains the registration data. The default file is SmHost.conf. If you do not specify a path, the file is installed in the location where you are running the smreghost tool. If you use the same name as an existing host configuration file, the tool backups up the original and adds a .bk extension to the backup file name.
Register a Trusted Host in GUI or Console Mode Default: ETPKI -cd crypto_provider_DLL_or_configuration_file_path (Required for PKCS11 encryption) Indicates the full path to the PKCS11 DLL or configuration file. -ct crypto_provider_token_label (Optional for PKCS11 encryption) Indicates the token label for the hardware token. Only use this argument if there is a token label. -ck crypto_provider_token_pin (Required for PKCS11 encryption) Indicates the passphrase for the token.
Register Multiple Trusted Hosts on One System (UNIX) Register Multiple Trusted Hosts on One System (UNIX) You typically register only one trusted host for each machine where web servers and Agents are installed. However, you can register multiple trusted hosts on one computer to create distinct connections for each SiteMinder client. Using multiple trusted hosts ensures a unique shared secret and a secure connection for each client requiring communication with the Policy Server.
Files Installed for Registration Services (UNIX) Files Installed for Registration Services (UNIX) The Web Agent installation installs a number of virtual and physical directories for Registration Services: Virtual Directories ■ siteminderagent/dmspages ■ siteminderagent/dmsforms You can view these directories using the Internet Services Manager and looking at the Default website for your server.
Chapter 4: Upgrade a Web Agent to r12.0 SP2 This section contains the following topics: How to Prepare for a Web Agent Upgrade (see page 77) Upgrade a Web Agent to r12.0 SP2 on Windows Systems (see page 79) Upgrade a Web Agent to r12.0 SP2 on UNIX Systems (see page 81) How to Prepare for a Web Agent Upgrade You can prepare for upgrading a Web Agent using the following process: 1. Review the upgrade process in the SiteMinder Upgrade Guide. 2. Back up any customized files on your web server. 3.
How to Prepare for a Web Agent Upgrade Password Services and Forms Template Changes During Upgrades For Password Services and forms templates, the jpw_default, pw_default, and samples_default directories are upgraded. However the non-default versions of these directories (jpw, pw, and samples), which may contain customized files, will not be modified in any way.
Upgrade a Web Agent to r12.0 SP2 on Windows Systems Upgrade a Web Agent to r12.0 SP2 on Windows Systems The executable on the SiteMinder media upgrades your existing SiteMinder Web Agents to r12.0 SP2, provided the web server version has not changed since the last installation of the Web Agent. If you have upgraded the web server itself since you last installed the Web Agent, the Agent upgrade may not work.
Upgrade a Web Agent to r12.0 SP2 on Windows Systems 8. In the Confirm Upgrade dialog box, select one of the following options, and then click Next: ■ Continue with the upgrade—upgrades the Web Agent to r12.0 SP2. ■ Abort the upgrade—exits the upgrade procedure without upgrading the Web Agent. 9. In the Pre-installation Summary dialog box, confirm that the installation settings are correct, then click Install. The new Web Agent files are copied to the specified location.
Upgrade a Web Agent to r12.0 SP2 on UNIX Systems Upgrade a Web Agent to r12.0 SP2 on UNIX Systems The executable on the SiteMinder media upgrades your existing SiteMinder Web Agents to r12.0 SP2, provided the web server version has not changed since the last installation of the Web Agent. If you have upgraded the web server itself since you last installed the Web Agent, the Agent upgrade may not work.
Upgrade a Web Agent to r12.0 SP2 on UNIX Systems ■ Continue with the upgrade—upgrades the Web Agent to r12.0 SP2. ■ Abort the installation—exits the upgrade procedure without upgrading the Web Agent. 11. In the Pre-installation Summary dialog box, confirm that the installation settings are correct, then click Install. The new Web Agent files are copied to the specified location. 12. In the Install Complete dialog box, click Done. The Web Agent upgrade is complete. If the system with the 5.
Chapter 5: Configure an IIS Web Agent This section contains the following topics: How to Configure How to Configure How to Configure Access (see page a SiteMinder Web Agent on IIS 7.0 (see page 83) a SiteMinder Web Agent on IIS 6.0 (see page 91) a SiteMinder Web Agent to Protect Microsoft Outlook Web 100) How to Configure a SiteMinder Web Agent on IIS 7.0 To configure a SiteMinder Web Agent for an IIS 7.0 web server, use the following process: 1.
How to Configure a SiteMinder Web Agent on IIS 7.0 Add Role Services to your IIS 7 Web Server Before operating a SiteMinder Web Agent on an IIS 7 web server, you must configure the web server to use the role services that are required by the SiteMinder Web Agent. To add role services to your IIS 7 web server 1. On your Windows Server 2008 system, click Start, Administrative Tools, Server Manager. Note: If the User Account Control dialog appears, click Continue. The Server Manager opens. 2.
How to Configure a SiteMinder Web Agent on IIS 7.0 Run the Configuration Wizard for an IIS Web Agent Before you configure the Agent, you may want to register the system where the Agent is installed as a trusted host; however, you can do this at a later time. To configure an IIS Web Agent 1. If necessary, start the Web Agent Configuration Wizard. The default method is to select Start, Programs, SiteMinder, Web Agent Configuration Wizard.
How to Configure a SiteMinder Web Agent on IIS 7.0 a. Select a servlet engine to be configured for the web server. If you do not see your engine displayed, select Other Advanced server. Click Next. b. In the Self Registration Services Admin Account dialog box, identify the the DMS Administrator by provide values for the Admin User Name, Admin Password and Admin Confirm Password fields and click Next.
How to Configure a SiteMinder Web Agent on IIS 7.0 Add Handler Mappings to Additional Web Sites you want to Protect with SiteMinder Every additional web site (beyond the Default Web Site) in the IIS 7.0 web server that you want to protect with SiteMinder requires a handler mapping. Note: These settings are added to the Default Web Site of the IIS web server automatically by the Web Agent Configuration wizard.
How to Configure a SiteMinder Web Agent on IIS 7.0 To add a handler mapping to additional web sites 1. Open the Internet Information Services (IIS) Manager. Note: If the User Account Control dialog appears, click Continue. 2. In the Connections pane, expand the web server. The Sites folder appears. 3. Expand the Sites folder, and then click the icon of the additional web site that you want to protect with . 4. Under the IIS section, double-click the Handler Mappings icon.
How to Configure a SiteMinder Web Agent on IIS 7.0 Add the Agent ISAPI Filter to Additional Web Sites that you want to Protect with SiteMinder To run a SiteMinder Web Agent on an additional (not the default) web site on IIS 7.0, add a SiteMinder ISAPI filter to each additional web site you want to protect. This filter executes the Web Agent ISAPI scripts and other files. Note: These settings are added to the Default Web Site of the IIS web server automatically by the Web Agent Configuration wizard.
How to Configure a SiteMinder Web Agent on IIS 7.0 To add the agent ISAPI filter to additional web sites that you want to protect with SiteMinder 1. Open the Internet Information Services (IIS) Manager. Note: If the User Account Control dialog appears, click Continue. 2. In the Connections pane, expand the web server. The Sites folder appears. 3. Expand the Sites folder, and then click the icon of the additional web site that you want to protect with SiteMinder. 4.
How to Configure a SiteMinder Web Agent on IIS 6.0 How to Configure a SiteMinder Web Agent on IIS 6.0 Before you can use the Web Agent on an IIS 6.0 web server, you must complete the prerequisites using the following process: 1. Assign read permissions to samples and error files directories. 2. Allow IIS to execute Web Agent ISAPI and CGI extensions. 3. (Optional) Increase the Web Agent's size limit for uploaded files. 4. Gather the Web Agent information. 5.
How to Configure a SiteMinder Web Agent on IIS 6.0 Assign Read Permissions to Samples and Error Files Directories The Network Service account must have Read permissions to any directory where the Web Agent reads forms credential collector (FCC) files and to any directory where the Web Agent reads Web Agent custom error files. To Assign Read Permissions to the Samples and Error Files Directories 1.
How to Configure a SiteMinder Web Agent on IIS 6.0 Allow IIS to Execute the Agent ISAPI and CGI Extensions You must add certain ISAPI and CGI extentions to the IIS 6.0 web server and grant the server permission to execute them before configuring the SiteMinder Web Agent. These extensions will execute the Web Agent ISAPI and CGI scripts and other files. To add the extensions and permissions 1.
How to Configure a SiteMinder Web Agent on IIS 6.0 ■ web_agent_home/pw_default/smpwservicescgi.exe (suggested extension name: PW Default CGI) IIS 6.0 Web Agents and Third-Party Software on the Same Server The IIS 6.0 Web Agent consists of an ISAPI filter and an ISAPI extension. The majority of Web Agent processing occurs in the extension. When the Web Agent is installed on an IIS 6.
How to Configure a SiteMinder Web Agent on IIS 6.0 Increase the Agent's Size Limit for Uploaded Files The Web Agent installed on an IIS 6.0 web server has a size limit of 2.5 MB for uploading files. If you want to increase this size limit, you can add a new key to the Windows registry on your web server. To upload files that are larger than this limit 1. Open the registry editor. Note: For more information, see your Microsoft documentation, or go to http://support.microsoft.com/ 2.
How to Configure a SiteMinder Web Agent on IIS 6.0 Run the Configuration Wizard for an IIS Web Agent Before you configure the Agent, you may want to register the system where the Agent is installed as a trusted host; however, you can do this at a later time. To configure an IIS Web Agent 1. If necessary, start the Web Agent Configuration Wizard. The default method is to select Start, Programs, SiteMinder, Web Agent Configuration Wizard.
How to Configure a SiteMinder Web Agent on IIS 6.0 a. Select a servlet engine to be configured for the web server. If you do not see your engine displayed, select Other Advanced server. Click Next. b. In the Self Registration Services Admin Account dialog box, identify the the DMS Administrator by provide values for the Admin User Name, Admin Password and Admin Confirm Password fields and click Next.
How to Configure a SiteMinder Web Agent on IIS 6.0 Put the Agent Filter and Extension Before Other Third-Party Filters The IIS 6.0 Web Agent consists of an ISAPI filter and an ISAPI extension. The majority of Web Agent processing occurs in the extension. When the Web Agent is installed on an IIS 6.
How to Configure a SiteMinder Web Agent on IIS 6.0 a. Open the IIS Manager, and then expand the web server. b. Right-click the Default Web Site folder, and select Properties. c. Click the Home Directory tab, and then click Configuration. d. The following file should be at the top of the Wildcard application maps (order of implementation) field: web_agent_home\bin\ISAPI6WebAgent.dll web_agent_home Indicates the directory where the Web Agent is installed.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access To have a SiteMinder Web Agent protect a Microsoft Outlook Web Access web site, use the following process: Note: See the SiteMinder r12.0 SP2 Product Support Matrix at http://ca.com/support to determine which versions of this component are supported. 1. Install or configure the following prerequisites: a. Microsoft Exchange Server. b.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access 3. Repeat Steps 2a through 2g on the IIS web server that hosts your Microsoft Outlook Web Access Client. 4. Confirm that SiteMinder is protecting the Outlook Web Access web site.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access Confirm the SiteMinder ISAPI filter appears first in the list The IIS 6.0 Web Agent consists of an ISAPI filter and an ISAPI extension. The majority of Web Agent processing occurs in the extension. When the Web Agent is installed on an IIS 6.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access a. Open the IIS Manager, and then expand the web server. b. Right-click the Default Web Site folder, and select Properties. c. Click the Home Directory tab, and then click Configuration. d. The following file should be at the top of the Wildcard application maps (order of implementation) field: web_agent_home\bin\ISAPI6WebAgent.dll web_agent_home Indicates the directory where the Web Agent is installed.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access Set the Default Web Site Directory Location and Execute Permissions The Default Web Site of your IIS web server needs a specific directory location and execute permissions to integrate with Microsoft Outlook Web Access. To set the default web site directory location and execute permissions 1. Open the Internet Information Services (IIS) Manager. 2. Right-click the Default Web Site folder, and then select Properties.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access Add the ISAPI Extension to the Exchange Web Site The Microsoft Exchange web site on your IIS web server needs the SiteMinder ISAPI extension to operate with Microsoft Outlook Web Access. To add the ISAPI extension to the Exchange web site 1. Open the Internet Information Services (IIS) Manager, and then expand the Web Sites folder. A list of web sites appears. 2. Right-click the Exchange folder, and then select Properties.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access Set the Directory Security for the Exchange Web Site The Microsoft Exchange web site on your IIS web server needs certain directory security settings to operate with Microsoft Outlook Web Access. To set the directory security for the Exchange web site 1. Open the Internet Information Services (IIS) Manager, and then expand the Web Sites folder. A list of web sites appears. 2.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access Add the ISAPI Extension to the Exchweb Web Site The Microsoft Exchweb web site on your IIS web server needs the SiteMinder ISAPI extension to operate with Microsoft Outlook Web Access. To add the ISAPI extension to the Exchweb web site 1. Open the Internet Information Services (IIS) Manager, and then expand the Web Sites folder. A list of web sites appears. 2. Right-click the Exchweb folder, and then select Properties.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access Set the Directory Security for the Exchweb Web Site The Microsoft Exchweb web site on your IIS web server needs certain directory security settings to operate with Microsoft Outlook Web Access. To set the directory security for the Exchweb web site 1. Open the Internet Information Services (IIS) Manager, and then expand the Web Sites folder. A list of web sites appears. 2.
How to Configure a SiteMinder Web Agent to Protect Microsoft Outlook Web Access Confirm that SiteMinder is protecting the Outlook Web Access web site After configuring your Microsoft Exchange and Microsoft Outlook Web Access web sites, you can verify that the SiteMinder Web Agent is protecting them. Confirm that SiteMinder is protecting the Outlook Web Access web site 1. Enable the Web Agent. 2. Open the Outlook Web Access Inbox page. The following URL is an example: http://exchange_server_name.example.
Chapter 6: Configure a Sun Java System Web Agent This section contains the following topics: Run the Configuration Wizard on Windows (see page 112) Configure Sun Java System Web Agents Using GUI or Console Mode (see page 115) Manually Configure a Sun Java System Web Server (see page 119) Apply Changes to Sun Java System Web Server Files (see page 120) Chapter 6: Configure a Sun Java System Web Agent 111
Run the Configuration Wizard on Windows Run the Configuration Wizard on Windows To configure the Web Agent on an Sun Java System web server 1. If necessary, start the Web Agent Configuration Wizard. The default method is to select Start, Programs, SiteMinder, Web Agent Configuration Wizard. If you have placed the Wizard shortcut in a non-default location, the procedure will be different.
Run the Configuration Wizard on Windows ■ X509 Client Certificate—identifies a user based on X.509 V3 client certificates. Digital certificates act as a signature for a user. Certificate authentication uses SSL communication. ■ X509 Client Cert and HTTP Basic—combines X.509 Client Certificate and Basic authentication. The user‘s X.509 client certificate must be verified and he or she must provide a valid user name and password. ■ X509 Client Cert or HTTP Basic—combines X.
Run the Configuration Wizard on Windows The Web Agent files are installed and the Configuration Complete dialog box displays. 8. Click Done to exit the Configuration Wizard. 9. Enable the Web Agent: a. Open the WebAgent.conf file, located in: Sun_Java_System_server_home\servers\https-hostname\config b. Set the EnableWebAgent parameter to Yes. c. Save the file. 10. Apply changes to Sun Java System Web Server files. This is required for the Agent‘s configuration to take effect.
Configure Sun Java System Web Agents Using GUI or Console Mode Configure Sun Java System Web Agents Using GUI or Console Mode These instructions are for GUI and Console Mode configuration. The steps for the two modes are the same, with these exceptions for Console Mode: ■ You may be instructed to select an option by entering a corresponding number. For example, to select the Sun Java System Web Server, you enter a 3, which corresponds to this server.
Configure Sun Java System Web Agents Using GUI or Console Mode If you have already configured a server with a Web Agent and you are running the Configuration Wizard to configure additional web servers instances, the Wizard displays the Select One or More Instances to Overwrite dialog box. This dialog box lists the web servers that you have previously configured. a. Select one of the following: Overwrite—to overwrite the server instance configuration. Preserve—to preserve the web server's configuration.
Configure Sun Java System Web Agents Using GUI or Console Mode ■ X509 Client Cert and Form—The X.509 Client Certificate and HTML Forms authentication scheme combines the use of X.509 Client Certificates and the use of customized HTML forms to collect authentication information. Using this scheme, the user‘s X.509 client certificate must be verified and the user must provide the credentials requested by an HTML form. Note: For more information, see the Policy Server documentation. 8.
Configure Sun Java System Web Agents Using GUI or Console Mode More Information Apply Changes to Sun Java System Web Server Files (see page 120) 118 Web Agent Installation Guide
Manually Configure a Sun Java System Web Server Manually Configure a Sun Java System Web Server The SiteMinder Web Agent Configuration wizard only configures the default instance of your Sun Java System web server. If you want to configure a different instance of the Sun Java System web server to use SiteMinder, you need to manually edit the obj.conf file that is used by that server instance.
Apply Changes to Sun Java System Web Server Files 9. Remove the following line: NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Program Files/Sun/WebServer7/lib/icons" name="es-internal" 10. Locate the following line: ObjectType fn="force-type" type="text/plain" 11. Insert a new line below the previous one, and then add the following text: Service method="(GET|POST)" fn="SmAdvancedAuth" 12. Save the obj.conf file. The Sun Java System web server is manually configured.
Apply Changes to Sun Java System Web Server Files More Information Settings Added to the Sun Java System Server Configuration (see page 189) Tune the Shared Memory Segments (see page 152) Chapter 6: Configure a Sun Java System Web Agent 121
Chapter 7: Configure an Apache Web Agent This section contains the following topics: Configure an Apache Web Agent on Windows Systems (see page 124) Configuration Methods for Apache Web Agents on UNIX Systems (see page 126) Improve Server Performance with Optional httpd.conf File Changes (see page 130) Set the LD_PRELOAD Variable for Apache Agent Operation (see page 130) Set the LD_ASSUME_KERNEL for Apache Agent on SuSE Linux 9 for zSeries (see page 132) Enabling SHLIB Path for an Agent on Apache 2.
Configure an Apache Web Agent on Windows Systems Configure an Apache Web Agent on Windows Systems Before you configure the Agent, you may want to register the system where the Agent is installed as a trusted host; however, you can do this at a later time. To configure the Apache Web Agent 1. If necessary, start the Web Agent Configuration Wizard. The default method is to select Start, Programs, SiteMinder, Web Agent Configuration Wizard.
Configure an Apache Web Agent on Windows Systems 6. Select the web server instances that you want to configure with Web Agents. If you have already configured a server with a Web Agent and you are running the Configuration Wizard to configure additional web servers instances, the Wizard displays the Select One or More Instances to Overwrite dialog box. This dialog box lists the web servers that you have previously configured. a.
Configuration Methods for Apache Web Agents on UNIX Systems Apache_home\conf where Apache_home is the installed location of the Apache web server. b. Set the EnableWebAgent parameter to Yes. c. Save and close the file. 12. Restart the web server. When you run the Configuration Wizard for the Apache Web Agent, it makes changes to the Web Server‘s httpd.conf file and to the library path. For httpd.conf changes to take effect, you need to restart the web server.
Configuration Methods for Apache Web Agents on UNIX Systems Configure an Apache Web Agent Using GUI or Console Mode These instructions are for GUI and Console Mode configuration. The steps for the two modes are the same, with these exceptions for Console Mode: ■ You may be instructed to select an option by entering a corresponding number. For example, to select the Apache Web Server, you enter a 1, which corresponds to this server.
Configuration Methods for Apache Web Agents on UNIX Systems Select this option if you are using an Apache-based web server (such as IBM HTTP, HP Apache-based, or Oracle). You are prompted to enter the full configuration path to the web server root. ■ I don‘t have an Apache web server. Choose this option to skip Apache configuration and continue with the Agent configuration. Click Next. 5. Following the server root path, specify the version of Apache you are using.
Configuration Methods for Apache Web Agents on UNIX Systems The user name and password that you enter here must match the DMS Admin values you set at the Policy Server. The DMS Administrator account secures DMS requests that are performed outside of the scope of a DMS administrator, such as self-registration. The user name and encrypted password for the account are stored in the dms.properties file on the Web Agent. 9. In the Web Server Configuration Summary dialog box.
Improve Server Performance with Optional httpd.conf File Changes Improve Server Performance with Optional httpd.conf File Changes You can improve server performance by modifying the default configuration settings in the httpd.conf file; however, these changes are not required: To improve server performance with optional httpd.conf file changes 1. For Apache and Sun Java System servers, assign a higher priority level to your Apache20WebAgent.
Set the LD_PRELOAD Variable for Apache Agent Operation Set the LD_PRELOAD Variable for an Oracle 10G Web Server on Linux After you install the Web Agent r12.0 SP2 on an Oracle 10G web server running on a Linux platform, you must set the LD_PRELOAD environment variable in the apachectl script. If the LD_PRELOAD variable is not included in the apachectl script, the Oracle 10G web server may dump core upon shutdown and fail to restart. 1. Open the apachectl file. 2.
Set the LD_ASSUME_KERNEL for Apache Agent on SuSE Linux 9 for zSeries Set the LD_ASSUME_KERNEL for Apache Agent on SuSE Linux 9 for zSeries After you install the Web Agent on an Apache web server running on SuSE Linux 9 for zSeries, set the LD_ASSUME_KERNEL environment variable as follows: LD_ASSUME_KERNEL=2.4.21 export LD_ASSUME_KERNEL Important! You must set this variable to 2.4.21 because it represents the kernel release upon which the Web Agent libraries are built.
Enabling SHLIB Path for an Agent on Apache 2.0/HP-UX 11 Enabling SHLIB Path for an Agent on Apache 2.0/HP-UX 11 For the Web Agent to operate on an Apache 2.0 web server running HP-UX 11, be sure the SHLIB_PATH is enabled in the Apache executable. 1. Check if the SHLIB PATH is already enabled by executing the command chatr httpd. A partial sample of the output is shown below. Notice that SHLIB_PATH is disabled.
Configure Apache for Oracle 9.0.2/9.0.3 HTTP Server To configure the Apache Web Agent for Oracle HTTP Server, you must: 1. Optionally, Install a Server Certificate (Required for SSL Only). For SSL-enabled Oracle HTTP Servers, you must install a server certificate using the Oracle Wallet Manager application. For more information, see the documentation supplied with your Oracle HTTP Server. 2. Configure the Apache Web Agent for the Oracle Server 3. Restart the Web Server as follows: a.
Chapter 8: Configure a Domino Web Agent This section contains the following topics: Configure a Domino Web Agent on Windows Systems (see page 135) How to Configure a Domino Web Agent on UNIX Systems (see page 139) Configure a Domino Web Agent on Windows Systems To configure a Domino Web Agent on Windows systems, perform the following tasks: ■ Add the Domino Web Agent DLL ■ Run the Web Agent Configuration Wizard ■ (Optional) Configure the CGI directory and CGI URL Path Settings ■ (Optional) Configure
Configure a Domino Web Agent on Windows Systems Add the Domino Web Agent DLL (Windows) To make the Domino Web Agent operate properly, you must add the DOMINOWebAgent.dll file to the filter DLLs. The Web Agent DLL must be the first DLL in the list. To add the Domino Web Agent DLL 1. Open Lotus Notes. 2. Select File, Database, Open. 3. In the Server field, select the Domino Server where you installed the Web Agent. 4. In the Database scroll box, select the server‘s address book.
Configure a Domino Web Agent on Windows Systems Run the Configuration Wizard for a Domino Web Agent on Windows Before you configure the Agent, you may want to register the system where the Agent is installed as a trusted host; however, you can do this at a later time. web_agent_home Indicates the directory where the Web Agent is installed. Default (Windows installations): C:\Program Files\CA\webagent Default (UNIX installations): /opt/ca/webagent To configure a Domino Web Agent 1.
Configure a Domino Web Agent on Windows Systems Important! If you uncheck a previously configured server, the Web Agent will be removed from this server. b. Click Next. 6. In the Agent Configuration Object field, enter the name of the Agent Configuration Object for this Web server instance, then click Next. This name must match an Agent Configuration Object already defined at the Policy Server. For example, to use the default enter DominoDefaultSettings. 7.
How to Configure a Domino Web Agent on UNIX Systems (Optional) Configure Alias Settings to Enable Forms and Other HTML Authentication Schemes To configure the Domino Web Agent to support HTML Forms authentication schemes perform the following tasks: 1. Create a subdirectory named "siteminderagent" in the Domino document root (\domino\html\) directory. 2. Copy all the subdirectories of agent_home\samples to the siteminderagent directory you created in Step 1.
How to Configure a Domino Web Agent on UNIX Systems Add the Domino Web Agent DLL (UNIX) For the Domino Web Agent to operate properly, you must add the dominowebagent.so library to the filter DLLs. This library must be first in the list. web_agent_home Indicates the directory where the Web Agent is installed. Default (Windows installations): C:\Program Files\CA\webagent Default (UNIX installations): /opt/ca/webagent To add the Domino Web Agent DLL 1. Open Lotus Notes. 2. Select File, Database, Open. 3.
How to Configure a Domino Web Agent on UNIX Systems Configuration Methods for Domino Web Agents on UNIX Systems The following configuration methods are available for Web Agents on UNIX systems: ■ GUI mode ■ Console mode ■ Unattended mode More Information How to Configure Any Web Agent in Unattended Mode (see page 145) Register Your System as a Trusted Host on UNIX (see page 62) Chapter 8: Configure a Domino Web Agent 141
How to Configure a Domino Web Agent on UNIX Systems Configure Domino Web Agents in GUI or Console Mode These instructions are for GUI and Console Mode configuration. The steps for the two modes are the same, with these exceptions for Console Mode: ■ You may be instructed to select an option by entering a corresponding number. For example, to select the Apache Web Server, you enter a 1, which corresponds to this server.
How to Configure a Domino Web Agent on UNIX Systems Important! If you uncheck a previously configured server, the Web Agent will be removed from this server. b. Click Next. 6. In the Agent Configuration Object field, enter the name of the Agent Configuration Object for this web server instance. This name must match an Agent Configuration Object already defined at the Policy Server. For example, to use the default enter DominoDefaultSettings. 7. In the Web Server Configuration Summary dialog box.
How to Configure a Domino Web Agent on UNIX Systems (Optional) Configure Alias Settings to Enable Forms and Other HTML Authentication Schemes To configure the Domino Web Agent to support HTML Forms authentication schemes perform the following tasks: 1. Create a subdirectory named "siteminderagent" in the Domino document root (/domino/html) directory. 2. Copy all the subdirectories of agent_home/samples to the siteminderagent directory you created in Step 1.
Chapter 9: Configurations Available for All Web Agents This section contains the following topics: How to Configure Any Web Agent in Unattended Mode (see page 145) Check SmHost.
How to Configure Any Web Agent in Unattended Mode Prepare an Unattended Configuration Unattended configuration uses the ca-wa-installer.properties file to propagate the Web Agent configuration set up across all Agents in your network. For configuration, you define configuration parameters in the properties file, then copy the file to any web server in your network to run an unattended configuration. When you perform an initial Web Agent installation and configuration, the ca-wa-installer.
How to Configure Any Web Agent in Unattended Mode To run an unattended Web Agent configuration 1. From a system where the Web Agent is already installed, copy the ca-wa-installer.properties file from web_agent_home/install_config_info to a local directory on the system where you want to run an unattended configuration. 2. Open a console window and navigate to web_agent_home/install_config_info.
Check SmHost.conf File Permissions for Shared Secret Rollover Check SmHost.conf File Permissions for Shared Secret Rollover If you enable shared secret rollover, the user who owns the web server process must have permissions to write to the SmHost.conf file. If this file cannot be modified by this user, then the shared secret rollover cannot be updated. For example, for Sun Java System and Apache web servers, the person specified by the User directive needs write permission to the SmHost.conf file.
How to Set Up Additional Agent Components How to Set Up Additional Agent Components The Web Agent Configuration Wizard guides you through basic Agent configuration. However, there are other Agent components that you can configure without the wizard. All SiteMinder Web Agents can protect resources, act as forms credential collectors (FCC) and/or an SSL credential collectors (SCC), and serve as a cookie provider for single sign-on. The Web Agent can serve in one or more of these roles simultaneously.
Chapter 10: Operating System Tuning This section contains the following topics: Tune the Shared Memory Segments (see page 152) How to Tune the Solaris 10 Resource Controls (see page 154) Chapter 10: Operating System Tuning 151
Tune the Shared Memory Segments Tune the Shared Memory Segments If you install an Apache or Sun Java System Web Agent on Solaris or HP-UX systems, you must tune the operating system‘s shared memory settings for the Web Agent to function correctly. By increasing the operating system‘s shared memory segments, you improve the performance of the Web Agent. The variables that control shared memory segments are defined in the operating system‘s specification file.
Tune the Shared Memory Segments shmsys:shminfo_shmmni Specifies the maximum number of shared memory segments that can exist simultaneously, system-wide. Example: (except Apache 1.x/Solaris 9) N/A Example: (Apache 1.x/Solaris 9) 200 shmsys:shminfo_shmseg (Not required for Solaris 9) Specifies the maximum number of shared memory segments per process. Example: 24 semsys:seminfo_semmni Specifies the number of semaphore identifiers. Use 11 for every instance of the Agent that you run on the system.
How to Tune the Solaris 10 Resource Controls How to Tune the Solaris 10 Resource Controls You may want to tune the resource controls at the project level if you need to improve the performance of the Web Agent. Note: See your Solaris documentation for more information. Tuning the resource controls on Solaris 10 uses the following process: 1. Determine the project associated with the user account under which the Web Agent runs. 2.
Chapter 11: Password Services This section contains the following topics: Password Services Implementations (see page 155) How to Set Up Your Environment for JSP Password Services (see page 156) How to Configure the ServletExec Servlet Engine for JSP Password Services for an IIS Web Server (see page 157) How to Configure the ServletExec Servlet Engine for JSP Password Services on a Sun Java System Web Server in the UNIX Operating Environment (see page 158) Password Services Implementations SiteMinder Passw
How to Set Up Your Environment for JSP Password Services How to Set Up Your Environment for JSP Password Services To use Password Services with JSP forms, you must modify your web server and servlet engine using the following process: 1. Add the the following password-services JAR files to the servlet engine classpath: web_agent_home\jpw\jpw.jar web_agent_home\Java\servlet.jar web_agent_home\Java\jsafe.jar 2.
How to Configure the ServletExec Servlet Engine for JSP Password Services for an IIS Web Server How to Configure the ServletExec Servlet Engine for JSP Password Services for an IIS Web Server To configure the ServletExec Servlet Engine for SiteMinder JSP-based Password Services, use the following process: Note: You can access the ServletExec documentation on the New Atlanta Web site. 1. Open the ServletExec Administration interface. 2.
How to Configure the ServletExec Servlet Engine for JSP Password Services on a Sun Java System Web Server in the UNIX Operating Environment How to Configure the ServletExec Servlet Engine for JSP Password Services on a Sun Java System Web Server in the UNIX Operating Environment To configure the ServletExec Servlet Engine for JSP Password Services on a Sun Java System Web server in the UNIX operating environment, use the following process: 1.
How to Configure the ServletExec Servlet Engine for JSP Password Services on a Sun Java System Web Server in the UNIX Operating Environment 4. Start the ServletExec Servlet engine, and then use its Administrative interface to do the following: Note: You can access the ServletExec documentation on the New Atlanta Web site. a. Add the following servlets: ■ Servlet Name: PSWDChangeServlet ■ Servlet Class: PSWDChangeServlet b.
Chapter 12: Uninstall a Web Agent This section contains the following topics: Notes About Uninstalling Web Agents (see page 161) Set JRE in PATH Variable Before Uninstalling the Web Agent (see page 162) Uninstall a Web Agent from a Windows System (see page 163) Uninstall a Web Agent from a UNIX System (see page 164) Notes About Uninstalling Web Agents Be aware of the following: ■ All Web Agents for all installed web servers will be uninstalled.
Set JRE in PATH Variable Before Uninstalling the Web Agent Set JRE in PATH Variable Before Uninstalling the Web Agent On Windows and UNIX systems, when you are uninstalling the Web Agent, make sure the JRE is in the PATH variable or the uninstallation program stops and issues one of the following error messages: ■ ―Could not find a valid Java virtual machine to load. You need to reinstall a supported Java virtual machine.‖ ■ "No Java virtual machine could be found from your PATH environment variable.
Uninstall a Web Agent from a Windows System Uninstall a Web Agent from a Windows System Before you uninstall, you may want to make copies of your registry settings and Web Agent configuration settings to have as a back up. To uninstall a Web Agent from a Windows system 1. Stop the web server. 2. Click Start, Control Panel, Add/Remove Programs. The Add/Remove Programs dialog appears. 3. Scroll through the program list and select CA SiteMinder Web Agent version. 4. Click Change/Remove.
Uninstall a Web Agent from a UNIX System Uninstall a Web Agent from a UNIX System These instructions are for GUI and Console Mode uninstallation. Note: Removing a Web Agent from a 64-bit Suse Linux 10 system requires additional preparations. The steps for the two modes are the same, with these exceptions for Console Mode: ■ You may be instructed to select an option by entering a corresponding number.
Uninstall a Web Agent from a UNIX System 11. Restart the web server(s). Note: For Sun Java System web servers, the obj.conf, magnus.conf, and mime.types files are restored to its original settings prior to the Web Agent installation. Uninstall Documentation from UNIX Systems These instructions are for GUI and Console Mode uninstallation. The steps for the two modes are the same, with these exceptions for Console Mode: ■ You may be instructed to select an option by entering a corresponding number.
Chapter 13: Troubleshooting This section contains the following topics: Agent Start-Up/Shutdown Issues (Framework Agents Only) (see page 167) Connectivity and Trusted Host Registration Issues (see page 171) General Installation Issues (see page 172) Miscellaneous Issues (see page 176) Sun Java System Web Agent Issues (see page 177) Apache Web Agent Issues (see page 178) Domino Web Agent Issues (see page 180) Agent Start-Up/Shutdown Issues (Framework Agents Only) If the Web Agent does not start after instal
Agent Start-Up/Shutdown Issues (Framework Agents Only) Agent Won’t Start Because LLAWP is Already Running or Log Messages not Written to the Correct Log Files Valid on UNIX Symptom: I'm having one or more of the following problems: ■ My Web Agent won't start because the LLAWP process is already running. ■ My Web Agent starts, however the log messages are being written to the log files of a second agent instance.
Agent Start-Up/Shutdown Issues (Framework Agents Only) Shut Down LLAWP If the LLAWP process does not shut down properly when shutting down the web server, shut down the LLAWP from the command line. This shuts down the running worker process associated with a WebAgent.conf file. To shut down the LLAWP, use the command with this syntax: LLAWP path_to_WebAgent.conf -web_server_type -shutdown For example: LLAWP /usr/apache/conf/WebAgent.
Agent Start-Up/Shutdown Issues (Framework Agents Only) Stop LLAWP When Stopping IBM HTTP Server 2.0.47 The IBM HTTP Server 2.0.47 on Windows 2000 and 2003 crashes if the ibm_afpa_module and the Web Agent are enabled. If the ibm_afpa_module is loaded and a module registering an init function does not exit that function quickly, the apache.exe child process crashes with an access violation in LIBAPR.dll. To solve this issue for versions of IBM HTTP Server v2.0.x, if there is an
Connectivity and Trusted Host Registration Issues Connectivity and Trusted Host Registration Issues This section contains troubleshooting information related to trusted host registration. Trusted Host Registration Fails Symptom: I cannot register a trusted host. Solution: Check the following: ■ Make sure that the Policy Server is installed and configured on the target server, that the IP address for the server is correct, and that the Policy Server is running.
General Installation Issues No Connection From Trusted Host to Policy Server Symptom: Trusted host cannot make a connection to the Policy Server. Solution: Do the following: ■ Ensure that the EnableWebAgent parameter in the WebAgent.conf file is set to yes. ■ Check for the SmHost.conf file in web_agent_home/config. The presence of this file indicates a successful registration of the trusted host. web_agent_home Indicates the directory where the Web Agent is installed.
General Installation Issues More Information Fix the ServletExec CLASSPATH for DMS (see page 50) One Installation Hangs During Multiple Installations on the Same System Symptom: You are running multiple installations on the same system at the same time and an installation hangs. Solution: Try the following tasks in the order listed: 1. Reboot the system and try the installation again. 2. Rename the ZeroG registry file, then retry the installation.
General Installation Issues Attempt to Access DMS Page Returns Error Valid on Windows Symptom: On Windows systems, you receive a servlet DMS not found error when you access a DMS page. Solution: Check the ServletExec CLASSPATH and modify it if necessary.
General Installation Issues Error Message During Upgrade Valid on Windows, UNIX Symptom: You receive the following error during an upgrade: ComponentMoveData Error -115 Solution: Do the following: 1. Click OK to exit the error message. 2. Start the Policy Server Management Console. 3. From the console, stop the Policy Server. 4. Close the Management Console. 5. Run the upgrade or again and this error message should no longer appear.
Miscellaneous Issues Miscellaneous Issues This section contains troubleshooting information related to miscellaneous issues. Netscape Browser Won't Open PDFs Valid on UNIX Symptom: I cannot open PDF Files from the Online Manuals Index HTML page on a UNIX system using a Netscape browser. Solution: If a .pdf file does not open after you click a link on the doc_index.htm page, set Acrobat Reader as a helper application in Netscape Navigator.
Sun Java System Web Agent Issues Adobe Acrobat Reader Won't Install on a Windows System Valid on Windows Symptom: I cannot install Adobe Acrobat Reader on a Windows system. Solution: If the Acrobat Reader installation program hangs while the Policy Server is running, stop the server using the Policy Server Management Console, then the installation program should start. Sun Java System Web Agent Issues This section contains troubleshooting information related to Sun Java System Web Agents.
Apache Web Agent Issues Reconfigured Web Agent Won't Operate Valid on Sun Java System web servers Symptom: Web Agent configuration changes are not in the obj.conf file. The Web Agent cannot operate. Solution: The Sun Java System Administration console was used to make server modifications before the changes made by the Agent configuration to the obj.conf were applied. Re-configure the Web Agent. Sun Java System Web Server Fails at Runtime Symptom: Sun Java System web server is failing at run time.
Apache Web Agent Issues Apache Server Starts But Web Agent Is Not Enabled Symptom: The Apache Agent is not enabled even though the web server has started. Solution: Do the following tasks: ■ Open the WebAgent.conf file, and then set EnableWebAgent to yes. ■ Compile the Apache web server to include the mod_so Apache module . ■ Modify the httpd.conf file so it to loads the mod_sm SiteMinder Agent Module. ■ Modify the httpd.conf file to initialize the Agent, using the SmInitFile entry.
Domino Web Agent Issues Apache Web Agent Not Operating Symptom: The Apache Web Agent is not operating. Solution: Tune the Apache operating system shared memory. Domino Web Agent Issues This section contains troubleshooting information related to Domino Web Agents. Domino Web Agent Not Enabled but the Web Server has Started Valid on Domino Symptom: The Domino Web Agent is not enabled even though the web server has started. Solution: Do the following: ■ In the WebAgent.
Appendix A: Unattended Installation This section contains the following topics: ca-wa-installer.
Modify General Information Modify General Information In the General Information section of the properties file, you can modify the settings in the following table: Parameter Description and Sample Value USER_INSTALL_DIR The location where the unattended installation will place the Web Agent. For example: C:\\Program Files\\ca\\webagent USER_SHORTCUTS The location where the installation places a shortcut to the Configuration Wizard.
Identify Policy Servers for Trusted Host Registration Parameter Description and Sample Value The default is 0. Set this parameter to 1 to enable shared secret rollover.
Select a Web Server for Configuration Select a Web Server for Configuration In the Trusted Host Registration section of the properties file, you can modify the settings in the following table: Parameter Description and Sample Value APACHE_SELECTED Indicates which Apache web server you are configuring and that server‘s root directory.
Select a Web Server for Configuration More Information WEB_SERVER_INFO Variables (see page 185) WEB_SERVER_INFO Variables The WEB_SERVER_INFO variables and their values are as follows: server_instance Indicates the web server instance. Example: https-server1 web_server_config_dir Indicates the path to the web server's config directory.
Select a Web Server for Configuration web_agent_operating_system Indicates the type of operating system used by the Web Agent. Limits: Windows, Unix Example: Windows empty_string Indicates an empty string saved for future use. Example: +EMPTYSTR+ selected_web_server Indicates whether the selected web server should be configured with an Agent.
Select a Web Server for Configuration advanced_auth_scheme Specifies which advanced authentication scheme, if any, is being used. Choose one of the following options: ■ HTTP Basic over SSL ■ X509 Client Certificate ■ X509 Client Certificate and HTTP Basic ■ X509 Client Certificate or HTTP Basic ■ X509 Client Certificate or Form ■ X509 Client Certificate and Form ■ No advanced authentication agent_config_object Indicates which Agent Configuration Object to use.
Configure the Web Server to Restart (Windows Only) Configure the Web Server to Restart (Windows Only) In the section to list Policy Servers for trusted host registration, you can modify the setting in the following table: Parameter Description and Sample Value USER_REQUESTED_RESTA RT Allows the installation program to reboot the Windows machine, if required after the configuration process. Set to Yes to allow a reboot. Otherwise, set to No.
Appendix B: Settings Added to the Sun Java System Server Configuration This section contains the following topics: Additions for Sun Java System Server 6.0 (see page 189) magnus.conf File Additions for Windows Platforms (see page 190) Code Added to the magnus.conf File on UNIX Platforms (see page 190) obj.conf File Additions for Windows Platforms (see page 191) obj.conf File Additions for UNIX Platforms (see page 193) mime.
magnus.conf File Additions for Windows Platforms magnus.conf File Additions for Windows Platforms The following lines are added to the magnus.conf file on Windows platforms: Init fn="load-modules" shlib="C:/Program Files/ca/webagent/bin/SunOneWebAgent.dll" funcs="SmInitAgent,SmInitChild,SiteMinderAgent,SmRequireAuth,SmAdvancedAuth" Init fn=SmInitAgent config="C:/iPlanet/Servers/https-server1/config/WebAgent.conf" errortext="Error initializing Web Agent...
obj.conf File Additions for Windows Platforms obj.conf File Additions for Windows Platforms When a Web Agent is configured to support an advanced authentication scheme, the Web Agent adds settings to the Sun Java System‘s obj.conf file. SiteMinder does not remove these settings later if the Agent is reconfigured to support a different advanced authentication scheme. You must manually edit the obj.conf file to remove the settings that are no longer relevant.
obj.conf File Additions for Windows Platforms ■ The line that begins NameTrans fn="pfx2dir" from="/siteminderagent/certoptional" is added if you chose to configure a certificate based authentication scheme. ■ The line that reads PathCheck fn="SmRequireAuth" is added to any existing PathCheck lines in the default object. It verifies that the user is authorized to perform the requested action on the requested resource.
obj.conf File Additions for UNIX Platforms obj.conf File Additions for UNIX Platforms When a Web Agent is configured to support an advanced authentication scheme, the Web Agent adds settings to the Sun Java System‘s obj.conf file. SiteMinder does not remove these settings later if the Agent is reconfigured to support a different advanced authentication scheme. You must manually edit the obj.conf file to remove the settings that are no longer relevant.
mime.types File Additions for Windows and UNIX Platforms ■ Most of the lines that begin NameTrans fn="pfx2dir" add virtual directories and mappings for the Agent to support SiteMinder‘s Password Services (CGI and JSP versions). ■ The line that begins NameTrans fn="pfx2dir" from="/siteminderagent/certoptional" is added if you chose to configure a certificate based authentication scheme. ■ The line that reads PathCheck fn="SmRequireAuth" is added to any existing PathCheck lines in the default object.
Check Agent Start-up with LLAWP Check Agent Start-up with LLAWP You can see if the Web Agent is starting up properly by starting the LLAWP process. To start the LLAWP process 1. Ensure you have configured the Web Agent with the Configuration Wizard. 2. Open a console window and enter the following command: LLAWP path_to_WebAgent.conf -web_server_type web_server_type can be ISAPI60 or APACHE20 path_to_WebAgent.conf can be a full path or a relative path from the location where you are running LLAWP.
Appendix C: Configuration Changes to Web Servers with Apache Web Agent This appendix lists changes made automatically by running the Web Agent Configuration Wizard to configure an Apache Web Agent. These changes apply to all web servers that support the Apache Web Agent, including Apache 1.x, Apache 2.0, IBM HTTP Server, and the HP Apache web server.
Set Library Path and Path for Oracle 10g Web Server Running in Apache 2.x Mode Set Library Path and Path for Oracle 10g Web Server Running in Apache 2.x Mode For an Oracle 10g web server running in Apache 2.x mode, both the LD_LIBRARY_PATH and PATH variables need to be set in the apachectl script. The LD_LIBRARY_PATH is automatically added to the apachectl script. The location of the apachectl script varies according to your version of OHS: Apache 1.3.
Changes to the httpd.conf File Entries Added to DSO Support Section The following line(s) are added to the Dynamic Shared Object (DSO) Support configuration section, which precedes the Main server configuration section of the file.
Changes to the httpd.conf File LoadModule Entries Added The SiteMinder Agent requires one of the following modules in order to load: Apache 1.x (except servers running on HP-UX 11i) LoadModule sm_module web_agent_home/bin/mod_sm.so Apache 1.x running on HP-UX 11i LoadModule hpaCCso_module web_agent_home/bin/mod_hpaCCso.sl HPaCCLoadModule sm_module web_agent_home/bin/mod_sm.sl Note: HP-UX uses the extension .sl to refer to a shared library. If the operating system for the Web Agent is HP-UX, the .
Changes to the httpd.conf File Note: This module is only for Apache 1.3.27 web servers. It is not supported for proprietary versions of the Apache 1.3.x web server, such as IBM HTTP Server, or Oracle HTTP Server. The entry to load mod_smcertenv must come after the entry to load mod_sm. mod_sm.c Entry Added to ClearModuleList If the directive ClearModuleList exists in the DSO configuration section, the mod_sm.
Changes to the httpd.conf File Alias Entries Added In the Aliases section of the file, entries are added to enable SiteMinder features. Note the following: ■ The Alias /siteminderagent/ ―web_agent_home/samples/‖ entry must come after all other aliases in the Aliases section. ■ For SiteMinder to use Basic over SSL or X.509 certificate-based authentication schemes with an Apache Web Agent, SSL must be enabled by compiling the Apache server to include the mod_ssl module. To obtain this module, see www.
Changes to the httpd.conf File Allow from all X509 Client Cert or Basic authentication AliasMatch /siteminderagent/certoptional/[0-9]+/(.
Changes to the httpd.conf File AddHandler Entries Added for Traditional Agents For traditional Web Agents (versions before 5.x QMR 6, such as Agents installed on Apache 1.x web servers), the following entries are added to the AddHandler section of the file for SiteMinder features. Note: These entries do not apply to Framework Web Agents (versions including v5.x QMR 6 and all subsequent versions, such as Agents installed on Apache 2.0 web servers). These functions are now part of the Web Agent Framework.
Agent Parameter Added for SSL Connections Using Apache 1.
Appendix D: Environment Variables Added or Modified by the Web Agent Installation This section contains the following topics: Added or Modified Environment Variables (see page 207) Added or Modified Environment Variables The following environment variables are added or modified by the Web Agent installation: ■ NETE_WA_ROOT = $INSTALL_PATH$ ■ NETE_WA_PATH = $INSTALL_PATH$$/$bin Appendix D: Environment Variables Added or Modified by the Web Agent Installation 207
Index ( (Optional) Configure Alias Settings to Enable Forms and Other HTML Authentication Schemes • 139, 144 (Optional) Configure the CGI Directory and CGI URL Path Settings • 138, 143 A Add a Logs Subdirectory for Apache Web Agents • 18 Add Handler Mappings to Additional Web Sites you want to Protect with SiteMinder • 87 Add Role Services to your IIS 7 Web Server • 84 Add the Agent ISAPI Filter to Additional Web Sites that you want to Protect with SiteMinder • 89 Add the Domino Web Agent DLL (UNIX) • 140
using forms authentication • 149 X.509 client certificate and basic • 112, 115 X.509 client certificate and HTML Forms • 112, 115 X.509 client certificate or basic • 112, 115 X.509 client certificate or HTML Forms • 112, 115 X509 Client Certificate • 112, 115 B Back Up Customized Files • 77 boostrap servers, configuring • 42, 67 C CA Product References • iii ca-wa-installer.properties File • 181 Certificate Authentication Entries Added • 205 Changes to the httpd.
Entries Added to DSO Support Section • 199 Environment Variables Added or Modified by the Web Agent Installation • 207 Error Message During Upgrade • 175 F Files Installed for Registration Services (UNIX) • 75 Fix the ServletExec CLASSPATH for DMS • 50 forms authentication scheme credential collection • 149 G Gather information Needed to Complete the Agent Installation • 19 general information settings, unattended installation • 182 General Installation Issues • 172 General Preparations for All Web Agents
Install the Correct Agent for a Web Server • 19 Install the Web Agent Documentation on UNIX Systems • 52 Install the Web Agent on a UNIX System • 53 Installation and Configuration Log Files • 41, 55 Installation History Log File • 37, 61 installer.properties file description • 58 installer.
Prepare an Unattended Installation on Windows • 34 Prepare for Password Services • 23 Prepare for Registration Services (Optional) • 25 prerequisites for installation Web Agents, UNIX • 12 Preservation of Any WebAgentTrace.conf File Changes • 19 properties files dms.
Set the LD_PRELOAD Variable for SSL Configuration on an IBM HTTP Server 2.0.47/Linux AS 3.0 System • 131 Set the Web Agent Environment Variables After Installation • 60 Set Web Agent Variables when using apachectl Script • 61 Settings Added to the Sun Java System Server Configuration • 189 shared memory segments, tuning • 152 Shut Down LLAWP • 169 SiteMinder Administrator for registering hosts • 20 smget Error Message When Web Server Starts • 177 SmHost.
reinstalling a Web Agent • 62 Upgrade a Web Agent to r12.0 SP2 • 77 Upgrade a Web Agent to r12.0 SP2 on UNIX Systems • 81 Upgrade a Web Agent to r12.
