GUI Installation of Agent for Sun Java System Web Proxy Server 4.0 on Linux Systems (Sun Java System Access Manager Policy Agent 2.2 Guide for Sun Java System Web Proxy Server 4.0)

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

Previous: Preparing to Install Agent for Sun Java System Web Proxy Server 4.0 on Linux Systems
Next: Command Line Installation of Agent for Sun Java System Web Proxy Server 4.0 on Linux Systems

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

Use the following instructions to install Agent for Sun Java System Web Proxy Server 4.0 using the GUI on Linux systems.

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

You must have root permissions when you run the agent installation program.

Unpack the product binaries.

Unpack the product binary in the directory of your choice using the following command:

# gunzip -dc binaryname.tar.gz| tar -xvof -

From the directory in which you unpack the binaries, issue the following command:

# ./setup

The Welcome page appears.

In the Welcome page, click Next.

Read the License Agreement. Click Yes to agree to the license terms.

To search for the directory where you would like to install the agent, click Browse. To accept the default, click Next.

Click Next and provide the following information about the Sun Java System Web Proxy Server 4.0 instance this agent will protect:

Install Sun Java System Access Manager Policy Agent in this directory: Enter the full path to the directory where you want this agent to be installed, and then click Next.

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

Proxy Server Host Name: Enter the FQDN of the machine 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:
```
/opt/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:
```
/opt/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 the Sun Java System Web Proxy Server 4.0 instance has been configured for SSL, choose HTTPS; otherwise choose 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.

Enter information about the Access Manager host.

The agent will connect to this server.

Primary Server Host: Enter the fully qualified domain name (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 host exists, then leave this field blank.

Failover Server Port: Enter the port number of the secondary Access Manager host. If no failover 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 host exists, then leave this field blank.

Failover Console Deployment URI: Enter the location that was specified when console was installed. The default URI for Access Manager is /amconsole. If no failover 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 CDSSO feature.

After entering all the information, click Next.

Review the installation summary to ensure that the information you’ve 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 close the installation program.

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

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.