eClient 101 Customization and Integration

Chapter 3. Installing eClient in a WebSphere Network Deployment environment 55

10.Accept the license agreement and click Next.

11.The installation will verify that your system has the required prerequisites.

12.Select Custom for the installation type and click Next to continue.

13.On the next window, a list of features to install is displayed. Since we will

install and run only HTTP Web server on this machine (cm01), select the

following entries from the list:

– IBM HTTP Server Version 1.3.26

– Web Server Plugin for IBM HTTP Server

14.Select Next to continue.

15.Enter the directories to be used for the IBM HTTP Server and Web server

plug-in installation. In our scenario, it is C:\IBMHttpServer. The WebSphere

installation directory is used to hold the Web server plug-in and the

installation log files.

16.Click Next to continue.

17.If you choose to install the HTTP server as a Windows service, you are

prompted to provide a user ID and password for starting and stopping the

HTTP Server service.

18.Click Next.

19.Review the information in the Summary window.

20.Click Next to begin copying the files.

21.Register the product.

22.Click Finish to complete the installation.

Verification

To verify if the installation has completed successfully, follow these steps:

1. Start IBM HTTP Administration 1.3.26 and IBM HTTP Server 1.3.26 services

in the Windows Control Panel.

2. Open a browser and enter http://localhost.

3. If the IBM HTTP Server home page is displayed, your installation is

successful.

3.3 Installing WebSphere Network Deployment

A Network Deployment configuration includes support for multiple nodes, each

with a node agent process and several application servers, all coordinated within

an administrative cell by the Deployment Manager process. Clusters of

56 eClient 101 Customization and Integration

load-balanced application servers can be configured within a Network

Deployment cell.

The configuration and application binaries of all components in the cell are

managed by the Deployment Manager and synchronized out to local copies on

each of the nodes.

A cell is a group of nodes in a single administrative domain. Each node is

identified by a logical name for configuration purposes. The configuration and

application binaries of all nodes in the cell are centralized in a cell master

configuration repository. This centralized repository is managed by the

Deployment Manager process and synchronized out to local copies held on each

of the nodes.

3.3.1 Installing WebSphere Application Server

A Network Deployment environment consists of multiple WebSphere Application

Server V5 nodes grouped into a single administrative domain. On each node in

the cell, you need to install WebSphere Application Server.

Follow the normal installation procedure (the same instruction that is used if the

Network Deployment configuration is not involved) to install WebSphere

Application Server on each node. This should be done for each node in the cell

before you start installing the WebSphere Application Server Network

Deployment.

Since the system will be quite complicated after everything is installed and

configured, you should consider doing verification after each installation. This

helps you to isolate and catch any problems in the early stages.

Follow these steps to verify the WebSphere installation:

1. Open a command window.

2. Run the command cd C:\WebSphere\ApServer\bin.

3. Run the command serverStatus -all to check the server’s running status.

4. Run the command startServer server1 to start it if server1 is not running.

5. Open a browser and enter http://localhost/snoop.

6. If you fail to display the servlet page, you should refer to the WebSphere

troubleshooting procedure to fix the problem.

For our scenario, we have two nodes in the cell. One of them resides on machine

cm02. The other one is on cm04.