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

Previous: Solaris Systems: Agent Installation for Sun Java System Web Proxy Server 4.0
Next: Linux Systems: Agent Installation for Sun Java System Web Proxy Server 4.0

Windows Systems: Agent Installation for Sun Java System Web Proxy Server 4.0

This section describes the installation of Agent for Sun Java System Web Proxy Server 4.0 on Windows systems.

Preparing to Install Agent for Sun Java System Web Proxy Server 4.0 on Windows Systems

Follow the specific steps outlined in this section before you install the agent to reduce the chance of complications occurring during and after the installation.

To Prepare to Install Agent for Sun Java System Web Proxy Server 4.0 on Windows Systems

Note –

You must have Java Runtime Environment (JRE) 1.3.1 or higher installed or available on a shared file system in order to run the graphical user interface (GUI) of the agent installation program. Currently, JRE 1.3.1 or any version higher is certified for use with the agent installation program.

Perform the following pre-installation tasks:

Ensure that Policy Agent 2.2 for Sun Java System Web Proxy Server 4.0 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for Sun Java System Web Proxy Server 4.0.

Install Sun Java System Web Proxy Server 4.0 if not already installed.

Refer to the Sun Java System Web Proxy Server 4.0 documentation for details on how best to install and configure this server. For example, you can refer to Sun Java System Web Proxy Server 4.0.2 2005Q4 Installation and Migration Guide.

Caution –
You should have a solid understanding of Sun Java System Web Proxy Server 4.0 to properly configure the server. Information provided in this guide about Sun Java System Web Proxy Server 4.0 does not serve as a substitute for the information available in the Sun Java System Web Proxy Server 4.0 product documentation.

Ensure that Sun Java System Web Proxy Server 4.0 has the latest patches available.

Set your JAVAHOME environment variable to a JDK version 1.3.1_04 or higher.

The installation requires that you set up your JAVAHOME variable correctly. However, if you have incorrectly set the JAVAHOME variable, the setup script will prompt you for supplying the correct JAVAHOME value:

Please enter JAVAHOME path to pick up java:

Ensure that required libraries are available on the Sun Java System Web Proxy Server 4.0 instance.

Depending on the Windows system you are using, the following libraries, msvcp70.dll and msvcr70.dll, might not be available. If these libraries are not available to the Sun Java System Web Proxy Server 4.0 instance upon which you are installing the agent, you must make them available as described in the following substeps.
1. Obtain these Windows libraries: msvcp70.dll and msvcr70.dll.
  
  These libraries come with certain Windows applications. You can also obtain them by contacting Sun technical support.
2. Place the libraries in the system32 subdirectory.
  
  The following path is an example of a conceivable path to this directory:
```
c:\WINDOWS\system32
```

Installing Agent for Sun Java System Web Proxy Server 4.0 on Windows Systems

The web agent installation program has one interface, the graphical user interface (GUI), for Windows systems. Use the following instructions to install Agent for Sun Java System Web Proxy Server 4.0 using the GUI on Windows systems.

GUI Installation of Agent for Sun Java System Web Proxy Server 4.0 on Windows Systems

You must have administrator privileges to run the installation program.

To Install Agent for Sun Java System Web Proxy Server 4.0 on Windows Systems Using the GUI

Unpack the product binaries.
unzip binaryname.zip
Note –
On Microsoft Windows 2003, the zip file is not automatically unpacked. Therefore, after you download the agents zip file, be sure to extract the zip file to a directory first and then execute setup.exe. To extract the zip file, right click on the zip file in the File Manager and select Extract. After extracting to a directory, double click setup.exe to execute it.

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

The Welcome page appears.

In the Welcome page, click Next.

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

Select the directory in which you would like to install the agent.

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

Enter the applicable information about the Sun Java System Web Proxy Server 4.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:

Host Name: Enter the fully qualified domain name (FQDN) of the system where the Sun Java System Web Proxy Server 4.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.

Proxy Server Instance Directory: Specify the Sun Java System Web Proxy Server 4.0 instance that this agent will protect. Enter the full path to the directory where the instance is located. For example: WebProxy-base\proxy-server-instance-name.
WebProxy-base
Represents the installation directory for Sun Java System Web Proxy Server 4.0. The following is an example of a conceivable Sun Java System Web Proxy Server 4.0 installation directory:
```
C:\Sun\ProxyServer40
```
proxy-server-instance-name
Represents the installation directory for Sun Java System Web Proxy Server 4.0. The following is an example of a conceivable Sun Java System Web Proxy Server 4.0 installation directory:
```
proxy-server1
```
Therefore, the following is an example of a full path to the proxy server instance directory:
```
C:\Sun\ProxyServer40\proxy-server1
```
Proxy Server Port: Enter the port number for the Sun Java System Web Proxy Server 4.0 instance that will be protected by the agent.

Proxy Server Protocol: If your Sun Java System Web Proxy Server 4.0 instance has been configured for SSL, then select HTTPS; otherwise select HTTP.

Agent Deployment URI: Enter a Universal Resource Identifier (URI) that will be used to access Agent for Sun Java System Web Proxy Server 4.0. The default value is /amagent.

Note –
The 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. Agent URI prefix is a configurable subset of Agent Deployment URI. It is important to set a valid URL for this property. Its value should be http://host.domain:port/web-proxy-deployment-uri where host, domain and port are FQDN and port number of the Sun Java System Web Proxy Server 4.0 instance where the agent is installed and web-proxy-deployment-uri is the URI where the Sun Java System Web Proxy Server 4.0 instance will look for web-proxy related HTML pages. Its default value is amagent.

The following is an example of an Agent Deployment URI:
```
http://host1.example.com:80/amagent
```

When you have entered all the information, click Next.

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 host2, the subdomain is eng, and the domain is example.com, then the Host Name in this case is host2.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.

After entering all the information, click Next.

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.

In the Ready to Install page, click Install Now.

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

Restart the Sun Java System Web Proxy Server 4.0 instance on which you just installed the agent.

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

After performing the applicable post-installation tasks described in Chapter 5, Post-Installation Configuration: Policy Agent 2.2 for Sun Java System Web Proxy Server 4.0, ensure that the installation was successful as described in All Systems: Verifying a Successful Installation on Policy Agent 2.2.