Installation guide

Chapter 16. Configuring the NSAPI connector on Solaris

The following tasks describe how to configure the NSAPI connector to use a JBoss Enterprise Platform

as a worker node for a Sun Java System Web Server (SJWS) master node. Sun Java System Web

Server has been renamed to the Oracle iPlanet Web Server. The old name is used throughout this guide

for clarity.

In this section, all of the server instances are on the same machine. T o use different machines for each

instance, use the -b switch to bind your instance of JBoss Enterprise Platform to a public IP address.

Remember to edit the workers.properties file on the SJWS machine to reflect these changes in IP

address.

16.1. Prerequisites and configuration assumptions

Worker nodes are already installed with a JBoss Enterprise Platform 5.1 or later. The Native

components are not a requirement of the NSAPI connector. Refer to the Installation Guide for

assistance with this prerequisite.

The master node is already installed with one of the following technology combinations, and the

appropriate Native binary for its operating system and architecture. Refer to the Installation Guide for

assistance with this installation prerequisite.

Solaris 9 x86 with Sun Java System Web Server 6.1 SP12

Solaris 9 SPARC 64 with Sun Java System Web Server 6.1 SP12

Solaris 10 x86 with Sun Java System Web Server 7.0 U8

Solaris 10 SPARC 64 with Sun Java System Web Server 7.0 U8

16.2. Configure server instance as a worker node

Task: Configure a JBoss Enterprise Applica tion Pla tform Worker Node

Follow this task to correctly configure a JBoss Enterprise Application Platform instance as a SJWS

worker node.

Prerequisit es

Section 16.1, “Prerequisites and configuration assumptions”

1. Creat e a se rve r profile for each worker node

Make a copy of the server profile that you wish to configure as a worker node. (This procedure

uses the default server profile.)

[user@workstation jboss-ep-5.1]$ cd jboss-as/server

[user@workstation server]$ cp -r default/ default-01

[user@workstation server]$ cp -r default/ default-02

2. Give each inst a nce a unique na me

Edit the following line in the deploy/jbossweb.sar/server.xml file of each new worker

instance:

Add a unique jvmRoute value, as shown. This value is the identifier for this node in the cluster.

For the default-01 server profile:

For the default-02 server profile:

3. Enable session handling

Uncomment the following line in the deployers/jbossweb.deployer/META-INF/war-

deployers-jboss-beans.xml file of each worker node:

<property name="useJK">false</property>

This property controls whether special session handling is used to coordinate with mod_jk and

other connector variants. Set this property to true in both worker nodes:

4. Start your worker node s

Start each worker node in a separate command line interface. Ensure that each node is bound to

JBoss Enterprise Application Platform 5 HTTP Connectors Load Balancing Guide 61