Skip Navigation Links | |
Exit Print View | |
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide |
1. High Availability in GlassFish Server
2. Setting Up SSH for Centralized Administration
3. Administering GlassFish Server Nodes
4. Administering GlassFish Server Clusters
5. Administering GlassFish Server Instances
6. Administering Named Configurations
7. Configuring Web Servers for HTTP Load Balancing
Supported Operating Systems and Web Servers
Configuring Oracle iPlanet Web Server
To Set up the HTTP Load Balancer in SSL Mode for Oracle iPlanet Web Server 7
Configuring Apache HTTP Server
Configuring Apache Before Installing the GlassFish Loadbalancer Plug-In
To Build and Install Apache With SSL Support
To Create a Security Certificate for Apache
Configuring Apache After Installing the GlassFish Loadbalancer Plug-In
Configuring Security Files to Work With the Load Balancer
Providing Access Permissions to Apache User
Loadbalancer Plug-In Initialization
Modifying Directory Access Permissions to Enable Auto Apply
Starting Apache on Solaris and Linux
Microsoft IIS 7.5+ Post-Install Configuration Steps
To Configure Microsoft IIS 7.5+ After Installing the GlassFish Loadbalancer Plug-In
Automatically Configured sun-passthrough Properties
Configuring Oracle HTTP Server
To Configure Oracle HTTP Server to Use the Loadbalancer Plug-In
To Enable the Load Balancer Auto Apply Feature
Installing the Loadbalancer Plug-In
To Install the Loadbalancer Plug-In
Verifying Loadbalancer Plug-In Configuration
To Verify the Loadbalancer Plug-In Configuration
8. Configuring HTTP Load Balancing
9. Upgrading Applications Without Loss of Availability
10. Configuring High Availability Session Persistence and Failover
11. Configuring Java Message Service High Availability
The GlassFish Loadbalancer Configurator automatically performs the necessary configurations for the Oracle iPlanet Web Server. The Loadbalancer Plug-In supports Oracle iPlanet Web Server 7.0 Update 9+.
The manual configuration procedure in this section is only required if you plan on using the load balancer Auto Apply feature. The Auto Apply feature enables changes made to a configuration through the GlassFish Server Administration Console or from the command line with the apply-http-lb-changes(1) subcommand to be automatically sent over the wire to the web server configuration directory. To use the Auto Apply feature, you must configure the web server for SSL mode. This SSL configuration must be performed on the web server prior to installing the Loadbalancer Plug-In. If you will not be using the load balancer Auto Apply feature, you can skip this SSL configuration procedure.
Before You Begin
The Loadbalancer Plug-In does not support iPlanet Web Server administration passwords that are less than 8 characters in length. Ensure that the administration password you use for your iPlanet Web server configuration is eight or more characters long.
webserver-install-dir/bin/certutil -N -d webserver-install-dir/admin-server/config-store/config-name/config
When prompted, provide the NSS database password.
The command for starting the Admin Server depends on your operating system. For example, on Windows systems:
webserver-install-dir\admin-server\bin\startserv.bat
The name of the directory in which the web server is installed.
Enter the following command on a single line:
webserver-install-dir/bin/wadm create-selfsigned-cert --user= admin-user --server-name=host-name --nickname=ServerCert --token=internal --config=config-name
Refer to your web server documentation for complete instructions on the wadm command.
Enter the following command on a single line:
webserver-install-dir/bin/wadm create-http-listener --user=admin-user --server-name=host-name --default-virtual-server-name=default-virtual-server-name --listener-port=8090 --config=config-name http-listener-ssl
Enter the following command on a single line:
webserver-install-dir/bin/wadm set-ssl-prop --user=admin-user --http-listener=http-listener-ssl --config=config-name enabled=true server-cert-nickname=ServerCert
webserver-install-dir/bin/wadm deploy-config config-name
The wadm commands operate on the central configuration, so the web server will not use the changes until they are deployed.