2.1 Planning

< Day Day Up >

This section provides the hardware and software requirements, and the pre-installation planning steps for the WebSphere Application Server V5.0 Base, Network Deployment, and Enterprise editions for Linux on iSeries.

2.1.1 Hardware and software requirements

The IBM WebSphere Application Server V5.0 Base, Network Deployment, and Enterprise editions for Linux on iSeries have the following hardware and software requirements.

Hardware requirements

Hardware requirements include:

iSeries Models that support LPAR (64-bit support only) with minimum of 450CPW in Linux partition
Minimum 16 GB free disk space for the OS/400 partition, and 2.5 GB minimum for the Linux partition
Minimum 256 MB of memory; 512 MB recommended for the OS/400 partition
Minimum 512 MB of memory for the Linux partition

For the most up-to-date hardware requirements, see:

http://www-3.ibm.com/software/webservers/appserv/doc/v50/prereqs/hardware502.htm

Software requirements

Software requirements for IBM WebSphere Application Server V5.0 Base, Network Deployment and Enterprise for Linux on iSeries include:

Supported Linux for iSeries operating systems:
- United Linux 1.0
  
  Note
  In terms of specific Linux distributions, SLES 8 (SUSE Linux Enterprise Server) supports WebSphere for Linux on iSeries.
Supported Web servers:
- Apache Server 1.3.26
- IBM HTTP Server 1.3.26.2
- IBM HTTP Server 2.0.42.2
- Internet Information Server 4.0 (on NT)
- Internet Information Server 5.0 (on W2K)
- Sun ONE Web Server, Enterprise Edition 6.0.4 or 6.0.5
- Lotus Domino® Enterprise Server 5.0.9a, 5.0.23 or 6.0.2
Note
IBM HTTP Server for iSeries is not supported for Websphere Application Server for Linux on iSeries.
Supported databases:
- Cloudscape™ 5.0.13 or 5.1.21
- DB2 for iSeries 5.1 or 5.2
- DB2 connect 8.1 FP2 or FP3
- DB2 Enterprise Server Edition 8.1 FP2 or FP3
- DB2 Workgroup Server Edition 8.1 FP2 or FP3

For the most up-to-date software requirements, see:

http://www-3.ibm.com/software/webservers/appserv/doc/v50/prereqs/prereq502.html/

Product installation directories

Table 2-1 lists the default installation components, directories, and variable names. We refer to these variables throughout the installation process.

Table 2-1: Product installation directories
Component	Default directory	Variable
WebSphere WebSphere Enterprise	/opt/WebSphere/AppServer	<WAS_HOME>
WebSphere Network Deployment	/opt/WebSphere/DeploymentManager	<ND_HOME>
IBM HTTP Server	/opt/IBMHTTPServer	<IHS_HOME>

2.1.2 Workstation requirements

Workstations on which you run IBM WebSphere Application ServerV5.0 Base, Network Deployment, and Enterprise editions for Linux on iSeries must have one of the following Web browsers installed:

Internet Explore 5.5 SP2® (on NT or W2K)
Internet Explore 6.0 SP2 (on NT or W2K)
Netscape Communication 4.79 (on AIX, NT, W2K, Sun or Linux)

2.1.3 Pre-installation tasks

Prior to installing the WebSphere Application Server V5 for Linux on iSeries, just a few pre-installation checks and tasks need to be completed:

Create the operation system groups and users needed for embedded messaging.
Check the ports that are unused.
Stop Web Server processes.

Creating the groups and users for embedded messaging

WebSphere Application Server supports asynchronous messaging based on the Java Message Service (JMS) of a JMS provider. WebSphere Application Server provides an internal JMS provider and administration objects for MQSeries® as the JMS provider. If you need the Java Message Service (JMS) function for your application and you have not installed WebSphere MQ 5.3 with the required MQ features, you need to select the embedded messaging features during the installation of WebSphere Application Server.

The features you need to select on the Base edition are Embedded Messaging (shown in Figure 2-7 on page 18) and the options that follow beneath it:

Server and Client
Client Only
Message-driven Bean Samples

The features you need to select on Enterprise edition are Embedded Messaging (shown in Figure 2-73 on page 74) and the options that follow beneath it:

Server and Client
Message-driven Bean Samples

Before you install the embedded messaging features, you need to create the mqm user and two groups, mqm and mqbrkrs. The user you run WebSphere Application Server with (in this case, the user is root) and the mqm user must be members of both groups. If you don't create them, the installation of WebSphere Application Server Embedded Messaging options fails with prerequisite check errors.

To create the user and groups:

Log in as root.
Create two new groups using the following commands: (In this book, the Linux commands start with "#".)
```
 # groupadd mqm # groupadd mqbrkrs 
```
Create a new user:
```
 # useradd -g users -m mqm 
```
Add the root user to the root, pkcs11, mqm, and mqbrkrs groups:
```
 # usermod -G root,pkcs11,mqm,mqbrkrs root 
```
Add the mqm user to the mqm and mqbrkrs groups:
```
 # usermod -G mqm,mqbrkrs mqm 
```
Log off and then log on again to get the new permissions:
```
 # su - root 
```

Checking the ports are unused

Check that no existing active services use the following IP ports on the server:

80 (IBM HTTP Server port)
2809 (Bootstrap port in Base edition)
5557 (JVM server security port)
5559 (JVM Server Direct Address)
5558 (JMS server queued address)
7277 (Cell Discovery Address)
7873 (DRS client address)
8008 (IBM HTTP Server Admin port)
8880 (SOAP Connector Address)
9443 (HTTPS Transport and Admini Console Secure port)
9080 (HTTP Transport port)
9090 (HTTP Admini Console port)
9100 (ORB Listener Port in Network Deployment edition
9808 (Bootstrap port in Network Deployment edition)

Use the following command to check the active services:

   # netstat -l

Stop Web Server processes

If you decide to use the Apache HTTP Server instead of the IBM HTTP Server, you need to install the Apache module plug-in. During the WebSphere Application Server installation, the installer updates the httpd.conf configuration files as part of the Web server plug-in component installation. Therefore, you need to stop the Apache HTTP server before processing.

Log in as root and start a terminal session.
Stop the Web server by entering the following command:
```
 # cd /usr/bin # ./apacheclt stop 
```
If you should decide to use the Apache HTTP Server instead of the IBM HTTP Server, select the following features as shown in Figure 2-7 on page 18:
1. Deselect IBM HTTP Server.
2. Select the Apache module plug-in instead of the IBM HTTP plug-in.
For how to configure the Apache HTTP Server, refer to "Apache HTTP Server configuration" on page 155.

< Day Day Up >