Sun Java System Access Manager 7.1 Postinstallation Guide

Chapter 7 Installing and Configuring Third-Party Web Containers

Sun Java^TM System Access Manager 7.1 supports the following third-party web containers:

BEA WebLogic Server

http://www.bea.com/products/weblogic/server/
IBM WebSphere Application Server

http://www-306.ibm.com/software/webservers/appserv/was/support/

This chapter includes these topics:

Requirements For Using a Third-Party Web Container

The requirements to use either BEA WebLogic Server or IBM WebSphere Application Server as the web container include:

WebLogic Server and WebSphere Application Server are not part of the Sun Java Enterprise System (Java ES). Therefore, you must obtain the web container software from BEA or IBM and then install and configure them independently of the Java ES installer.
You should be familiar with administration tasks for the web container, including configuring, starting, and stopping an instance.

When you configure Access Manager by running the amconfig script (or amconfig.bat on Windows systems), the web container must be installed, configured, and running.
Access Manager requires Sun Java System Directory Server. Either install a new Directory Server using the Java ES installer or specify an existing Directory Server.

General Steps For Using a Third-Party Web Container

To use a third-party web container, follow these general steps:

If necessary, install Sun Java System Directory Server.
Install and configure the web container by following the BEA or IBM documentation.
Install Access Manager by running the Java ES installer with the Configure Later option.
Start the web container.
Configure Access Manager for the web container by running the amconfig script with configuration parameters specified in the amsamplesilent file (or a copy of the file). On Windows systems, run amconfig.bat with configuration parameters specified in the AMConfigurator.properties file (or a copy of the file).
Restart the web container.

Installing and Configuring BEA WebLogic Server 8.1 SP4

To install and configure BEA WebLogic Server 8.1 SP4, and to start and stop instances, follow the BEA documentation:

http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/

During installation and configuration, save the information to set the configuration variables shown in WebLogic Application Server 8.1 SP4 Configuration Variables when you run the Access Manager amconfig script (or amconfig.bat on Windows systems).

To Install and Configure BEA WebLogic Application Server 8.1 SP4

Install WebLogic Application Server 8.1 SP4 and any required patches.

Configure WebLogic Application Server using either the Administration Console or command-line interface.

Start WebLogic Application Server using either the Administration Console or command-line interface.

WebLogic Application Server 8.1 SP4 Configuration Variables

The following table describes the configuration variables that you set in the amsamplesilent file (or copy of the file) when you run the amconfig script to configure Access Manager with BEA WebLogic Server 8.1 SP4 as the web container.

On Windows systems, On Windows systems, run amconfig.bat with configuration parameters specified in the AMConfigurator.properties file (or a copy of the file).

Table 7–1 BEA WebLogic Server 8.1 SP4 Configuration Variables


Configuration Variable	Description
`WEB_CONTAINER`	Web container variable. Set to `WL8`.
`WL8_HOME`	WebLogic Server home directory. Default: `/usr/local/bea`
`WL8_PROJECT_DIR`	WebLogic Server project directory. Default: `user_projects`
`WL8_DOMAIN`	WebLogic Server domain name. Default: `mydomain`
`WL8_CONFIG_LOCATION`	Parent directory of the location of the WebLogic Server start script.
`WL8_SERVER`	WebLogic Server server name. Default: `myserver`
`WL8_INSTANCE`	WebLogic Server instance name. Default: `/usr/local/bea/weblogic81 ($WL8_HOME/weblogic81)`
`WL8_PROTOCOL`	WebLogic Server protocol. Default: `http`
`WL8_HOST`	WebLogic Server host name. Default: Host name of the server
`WL8_PORT`	WebLogic Server port. Default: 7001
`WL8_SSLPORT`	WebLogic Server SSL port. Default: 7002
`WL8_ADMIN`	WebLogic Server administrator. Default: `"weblogic"`
`WL8_PASSWORD`	WebLogic Server administrator password.
`WL8_JDK_HOME`	WebLogic Server JDK home directory. Default: `/usr/local/bea/jdk142_04 ($WL8_HOME/jdk142_04)`

Installing and Configuring IBM WebSphere Application Server 5.1.1.6

To install and configure IBM WebSphere Application Server 5.1.1.6, and to start and stop instances, follow the IBM documentation:

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1/index.jsp

During installation and configuration, save the information to set the configuration variables shown in IBM WebSphere Application Server Configuration Variables when you run the Access Manager amconfig script.

To Install and Configure IBM WebSphere Application Server

Install WebSphere Application Server and any required patches.

Verify that the WebSphere Application Server installation was successful.
1. Make sure the server.xml file exists in the following directory:
```
/opt/WebSphere/AppServer/config/cells/cell-name/noes/node-name/servers/server1
```
2. Start the server with the startServer.sh utility. For example:
```
# /opt/WebSphere/AppServer/bin/startServer.sh server1
```
3. In a Web browser, use the following URL to view the sample Web application:
```
http://fqdn:port/snoop
```
  Where fqdn and port specify the server name and port number.

After you have verified a successful installation, stop the server using the stopServer.sh utility. For example:
```
# /opt/WebSphere/AppServer/bin/stopServer.sh server1
```

Install any required patches using the updateWizard.sh utility.

Restart WebSphere Application Server using the startServer.sh utility.

IBM WebSphere Application Server Configuration Variables

On Windows systems, On Windows systems, run amconfig.bat with configuration parameters specified in the AMConfigurator.properties file (or a copy of the file).

Table 7–2 IBM WebSphere Application Server 5.1 Configuration Variables


Variable	Description
`WEB_CONTAINER`	Web container variable. Set to `WAS5`.
`WAS51_HOME`	WebSphere home directory. Default: `/opt/WebSphere/AppServer`
`WAS51_JDK_HOME`	WebSphere JDK home directory. Default: `/opt/WebSphere/AppServer/java`
`WAS51_CELL`	WebSphere cell. Default: host-name value
`WAS51_NODE`	WebSphere node name. Default: host name of the server where WebSphere is installed. Default: hostname value
`WAS51_INSTANCE`	WebSphere instance name. Default: `server1`
`WAS51_PROTOCOL`	WebSphere protocol. Default: `http`
`WAS51_HOST`	WebSphere host name. Default: Hostname of the server
`WAS51_PORT`	WebSphere port. Default: 9080
`WAS51_SSLPORT`	WebSphere SSL port. Default: 9081
`WAS51_ADMIN`	WebSphere administrator. Default: `"admin"`
`WAS51_ADMINPORT`	WebSphere administrator port. Default: 9090

Installing Access Manager and Other Java ES Components

Run the Java ES installer to install these components:

Sun Java System Directory Server. Either install a new Directory Server or use an existing Directory Server, if you prefer.
Access Manager 7.1 with the Configure Later option.
Other Java ES components as needed. For example, if you are planning to configure Access Manager for session failover, install Sun Java System Message Queue.

For information about running the installer, see Sun Java Enterprise System 5 Installation Guide for UNIX or the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

Configuring Access Manager Using the `amconfig` Script

On Windows systems, run amconfig.bat with configuration parameters specified in the AMConfigurator.properties file (or a copy of the file).

To configure or reconfigure an Access Manager for a third-party web container, set variables in a copy of the amsamplesilent file and run the amconfig script.

To Configure Access Manager Using the `amconfig` Script

Copy the amsamplesilent file and rename the file to describe the new instance you want to configure.

For example, if you plan to configure an Access Manager instance for WebLogic Application Server, you might name the file as am_weblogic_server.

Set the variables in the am_weblogic_server file to configure (or reconfigure) the Access Manager instance. For example:
```
AM_REALM=enabled
DEPLOY_LEVEL=1
NEW_INSTANCE=false
WEB_CONTAINER=WAS5 # WebLogic Application Server is the web container
DIRECTORY_MODE=4  # Directory Server is provisioned with user data
AM_ENC_PW=password-encryption-key-value
...
```
Caution –
In a multiple server deployment that shares the same Directory Server, all Access Manager instances must use the same value for the password encryption key. Before you run the amconfig script, set the AM_ENC_PWD variable in the copy of the amsamplesilent file with the same encryption key value used for other instances.

Run the amconfig script.

For example, on Solaris systems with Access Manager installed in the default directory, run amconfig using the new am_weblogic_server file as the configuration input file:
```
# cd /opt/SUNWam/bin/
# ./amconfig -s ./am_weblogic_server
```
The amconfigscript reads the variables in the am_weblogic_server file and then runs in silent mode (-s option) to configure Access Manager for the WebLogic Application Server web container.

For more information about the amsamplesilent file and running the amconfig script, see Chapter 2, Running the Access Manager amconfig ScriptChapter 2.

Restart the web container.

Next Steps

In case you might need to reconfigure or uninstall this instance later, save the new am_weblogic_server file.