Sun Java System Access Manager Policy Agent 2.2 Guide for Microsoft Internet Information Services 5.0

Installation of Agent for Microsoft IIS 5.0

You must have administrator privileges to run the installation program.

ProcedureTo Install Agent for Microsoft IIS 5.0

  1. Unpack the product binaries using Windows zip utility or Winzip utility.

  2. Run the installation program by double-clicking setup.exe.

    The Welcome page appears.

  3. In the Welcome page, click Next.

  4. Read the License Agreement. Click Yes to accept the license agreement.

  5. Select the directory where you want to install the agent.

    The default directory is C:\Sun\Access_Manager\Agents\2.2.

    The directory you choose in which to install the web agent is referred to as the Policy Agent base directory, or PolicyAgent-base.

  6. Enter the applicable information about the Microsoft IIS 5.0 instance where this agent will be installed in the dialog box.

    The dialog box provides fields for entering the required information. You are prompted for information in the order shown as follows:

    Web Server Host Name: Enter the fully qualified domain name (FQDN) of the system where the Microsoft IIS 5.0 instance is installed.

    For example, if the host is host1, the subdomain is eng, and the domain is example.com, then the Host Name in this case is host1.eng.example.com.

    Web Server Instance Directory: Specify the Microsoft IIS 5.0 instance that this agent will protect. Enter the full path to the directory where the instance is located. For example: C:\inetpub\wwwroot.

    Web Server Port: Enter the port number for the Microsoft IIS 5.0 instance that will be protected by the agent.

    Web Server Protocol: If your Microsoft IIS 5.0 instance has been configured for SSL, then select HTTPS; otherwise select HTTP.

    Web Agent Deployment URI: Enter a Universal Resource Identifier (URI) that will be used to access Agent for Microsoft IIS 5.0. The default value is /amagent.


    Note –

    The web agent uses the value of the com.sun.am.policy.agents.config.agenturi.prefix property in the web agent AMAgent.properties configuration file to support some essential functions such as notification and POST data preservation. Web agent URI prefix is a configurable subset of Web Agent Deployment URI. It is important to set a valid URL for this property. Its value should be http://host.domain:port/web-agent-deployment-uri where host, domain and port are FQDN and port number of the Microsoft IIS 5.0 instance where the agent is installed and web-agent-deployment-uri is the URI where the Microsoft IIS 5.0 instance will look for web-agent related HTML pages. Its default value is amagent.

    The following is an example of an Agent Deployment URI:

    http://host1.example.com:80/amagent

  7. When you have entered all the information, click Next.

  8. Provide the following information about the Access Manager host:

    The deployment container will connect to this server.

    Primary Server Host: Enter the FQDN of the primary Access Manager host.

    For example, if the host is host3, the subdomain is eng, and the domain is example.com, then the Host Name in this case is host3.eng.example.com.

    Primary Server Port: Enter the port number for the primary Access Manager host.

    Primary Server Protocol: If the primary Access Manager host is SSL-enabled, select HTTPS. Otherwise select HTTP.

    Primary Server Deployment URI: Enter the location that was specified when Access Manager was installed. The default URI for Access Manager is /amserver.

    Primary Console Deployment URI: Enter the location that was specified when Access Manager console was installed. The default URI for Access Manager is /amconsole.

    Failover Server Host: Enter the FQDN of the secondary Access Manager host if the primary Access Manager host becomes unavailable. If no failover server host exists, then leave this field blank.

    Failover Server Port: Enter the port number of the secondary Access Manager host. If no failover server host exists, then leave this field blank.

    Failover Server Protocol: If the failover Access Manager host is SSL-enabled, select HTTPS. Otherwise select HTTP. If no failover server host exists, then leave this field blank.

    Failover Server Deployment URI: Enter the location that was specified when Access Manager was installed. The default URI for Access Manager is /amserver. If no failover server host exists, then leave this field blank.

    Failover Console Deployment URI: Enter the location that was specified when Access Manager Console was installed. The default URI for Access Manager is /amconsole. If no failover server host exists, then leave this field blank.

    Agent Access Manager Shared Secret:Enter the password for the Access Manager internal LDAP authentication user. This user is also referred to as amldapuser.

    For more information about the shared secret and its relationship with the Access Manager agent profile, see Chapter 4, The Relationship Between the Agent Profile and Web Agents in Policy Agent 2.2.

    Re-enter Shared Secret: Re-enter the password for the Access Manager internal LDAP authentication user (amldapuser).

    CDSSO Enabled: Check this box if you want to enable the CDSSO feature.

  9. After entering all the information, click Next.

  10. Review the installation summary to ensure that the information you have entered is correct.

    Note that it displays the CDCServlet URL if you have checked the CDSSO Enabled box in the previous panel.

    If you want to make changes, click Back. If all the information is correct, click Next.

  11. In the Ready to Install page, click Install Now.

  12. When the installation is complete, you can click Details to view details about the installation, or click Close to end the installation program.

  13. Restart the computer.

    Restarting your computer is necessary for the agent to work properly. The installation modifies the system path by appending to it the location of the agent libraries. This change takes effect only after your computer is restarted.

Next Steps

To ensure that the installation was successful, see Verifying a Successful Installation on Policy Agent 2.2.