WebSphere Application Server V3.5 install

The IBM WebSphere Application Server V3.5.1, Advanced Edition GUI

installation, executed via ./install, will not work for iPlanet Web Server V4.1SP7 due to a prerequisite check failure. For this reason, we edited the

prereq.properties file, which is in the same directory as the install program. We changed the line:

prereq_checker=1 to:

prereq_checker=0

in order to turn off prerequisite checking.

To install WebSphere Application Server, complete the following steps: 1. Start a Solaris Console window and log in as user root.

2. We downloaded and used the WebSphere Application Server Version 3.5.1. 3. Edit the prereq.properties file to remove the prerequisite check.

4. Start the WebSphere Application Server V3.5 install program by typing the following:

# /<install_directory>/install.sh 5. Click Next on the welcome window.

6. When the Install Options window appears, select Custom Installation. Otherwise, the Quick install option will use InstantDB and we want to use our Oracle for the WebSphere repository database. Click Next.

7. When the Choose Application Server Components window appears, select the following as shown in Figure 3-12:

– Server Runtime

– Administrative Console – Samples (optional)

– Configure Default Server and Application – WebServer Plugins

Figure 3-12 We will install everything except the IBM HTTP Server, because we have already installed an HTTP server

8. When the second Choose Application Server Components window appears, select to install the plug-in for:

– Netscape V4.0 plug-in

– Netscape V4.0 Security plug-in Click Next. See Figure 3-13.

Figure 3-13 We will install and configure the WebSphere Application Server plug-in for both iPlanet servers, with and without SSL

9. When the Location of Configuration files window appears, enter the path for each Web server. The paths are normally in the form:

/usr/netscape/server4/<name_of_HTTP_server>/config

Figure 3-14 shows the paths we used for our example installation on Solaris. Click Next.

Figure 3-14 The directory name where the configuration files are stored varies with the name of your iPlanet server

10.When the Database Options window appears enter the following information: – Database Type: Oracle

– Database Name: was

– DB Home: /opt/oracle8/u01/app/oracle/product/8.1.7

– DB URL: jdbc:oracle:thin@<hostname>:<server_port>:<db_SID> For example: jdbc:oracle:thin@sun2:1521:was

– Database User ID: ejsadmin

– Database Password: <your_password> – Confirm Password: <your_password>

Note: The WebSphere Application Server repository database name is user

defined and can be different from the name was. Within the context of Oracle, a WebSphere Application Server database is the equivalent of a tablespace within the Oracle database.

Figure 3-15 shows an example. Click Next.

Figure 3-15 Fill all the details of your database connection

11.When the Security Information window appears enter root as the user ID and fill in the password fields. This password won’t be kept. It’s just for the installation process. Choose Use dummy key ring file as shown in Figure 3-16. Click Next.

Figure 3-16 The WebSphere Application Server installation program needs the root password

12.When the Select Destination Directory window appears, accept the default /opt/WebSphere/AppServer and click Next.

13.When the Install Options Selected window appears, revise the options. Use the Back button if you need to change something. If everything is OK, click

Next.

14.Click Yes to begin the installation of files.

Confirm changes to iPlanet configuration files

The next time you open the administration console of iPlanet, it will complain about manual edits not bing loaded. These are the changes the WebSphere Application Server installation program has done. They have to be done separately to both HTTP servers, the SSL and the non-SSL.

To apply the changes follow this steps:

1. Click Apply at the upper right of the iPlanet administration console, as shown in Figure 3-17.

Figure 3-17 Apply iPlanet configuration updates for WebSphere Application Server 2. Click Load Configuration Files as shown in Figure 3-18.

Figure 3-18 Click Load Configuration Files

3. After a success message confirms that all the changes found in the

configuration files are consistent, a new window appears where you can apply the changes found. Click Apply Changes as shown in Figure 3-19.

Figure 3-19 Click the Apply Changes button

4. If you are applying the changes, you must provide the password to the certificate database before proceeding.

The HTTP servers have to be restarted for these changes to take effect.

WebSphere Application Server configuration for Oracle8i

Prior to starting the WebSphere Application Server, we need to complete the following configuration steps:

1. Start a Solaris Console window and log in as root. 2. Change to the WebSphere Application Server directory

/opt/WebSphere/AppServer/bin.

a. Search for the following:

DB_INSTANCE_HOME=fully_qualified_path_to_your_Oracle_home_directory export DB_INSTANCE_HOME

If the path ends in a slash (..../.), remove it from the path. b. Search for the following:

if ["${DB_TYPE}"!="DB2"] then { LD_LIBRARY_PATH=$WAS_HOME/lib/odbc/lib:$WAS_HOME/bin: $WAS_HOME/lib:$JAVA_HOME/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH ${JAVA_EXE?}\ -classpath $CLASSPATH \ -DDER_DRIVER_PATH=$DER_DRIVER_PATH \ com.ibm.ejs.sm.util.process.Nanny admin.config }

c. Change this section as shown below. New parts are indicated in bold text. if ["${DB_TYPE}"!="DB2"] then { ORACLE_HOME=Oracle_home_directory export ORACLE_HOME LD_LIBRARY_PATH=$WAS_HOME/lib/odbc/lib:$WAS_HOME/bin: $WAS_HOME/lib:$JAVA_HOME/lib:$LD_LIBRARY_PATH LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH LIBPATH=$LD_LIBRARY_PATH export LIBPATH NLS_LANG=AMERICAN_AMERICA.UTF8 export NLS_LANG ${JAVA_EXE?}\ -classpath $CLASSPATH \ -DDER_DRIVER_PATH=$DER_DRIVER_PATH \ com.ibm.ejs.sm.util.process.Nanny admin.config }

Where Oracle_home_directory is the fully qualified path to your Oracle home directory. For example,

/opt/oracle8/u01/app/oracle/product/8.1.7 . d. Save your changes.

Configuring the WebSphere Application Server

This section includes some general configuration steps for the WebSphere Application Server.

Start the WebSphere Application Server

To start the WebSphere Application Server, complete the following steps: 1. Start a Solaris Console window and log in as user root.

2. Start WebSphere Application Server. # cd /opt/WebSphere/AppServer/bin # ./startupServer.sh

3. View the tracefile log as follows: # cd /opt/WebSphere/AppServer/logs # tail -f tracefile

Look for the following message if successfully started: AdminServer A Initializing WebSphere Administration server AdminServer A WebSphere Administration server open for e-business

Install WebSphere Payment Manager

1. Before installing WebSphere Payment Manager, review the hardware and software prerequisites detailed in the IBM WebSphere Payment Manager for Multiplatforms Install Guide Version 2.2. If you have used the install

instructions for the prerequisite products described in this chapter, then you will already meet the Payment Manager requirements.

2. Insert the Payment Manager for Solaris CD-ROM, and mount the CD-ROM file system, if necessary. Run the Install command.

3. In the Payment Manager Install window, click Next. 4. Accept the license agreement and click Next.

5. Accept the default destination directory or enter another directory. Do not include blanks or spaces in the destination directory name. Figure 3-20 shows an example using the default Payment Manager install directory. Click

Next.

Note: Ensure the resolution on your display is set to 800 by 600 pixels or

higher to best view the Payment Manager installation program.

The database, the HTTP server and WebSphere Application Server must be running during the installation.

Figure 3-20 Payment Manager install directory

6. If your Web server is already installed, you will be asked for the location of the publish directory. If the location displayed is correct, click Next. If not, enter the correct location and click Next. The publish directory is the directory out of which your Web server serves documents. Figure 3-21 shows an example using the default publish directory the iPlanet Web Server.

Figure 3-21 iPlanet publish directory for Payment Manager install

7. If WebSphere Application Server is already installed and the installation program cannot determine which JDK WebSphere Application Server is using, you will be asked to enter the location of the JDK directory.

8. Select which database you will use with Payment Manager: UDB or Oracle. We selected Oracle 8.0/8i as shown in Figure 3-22.

Figure 3-22 Payment Manager install using Oracle database

9. The install then attempts to find JDBC driver information for your database. As we have not yet specified the correct location of the JDBC classes, the JDBC Driver Information window will advise that the JDBC driver class could not be loaded. This is shown in Figure 3-23.

Figure 3-23 Load failure for JDBC driver class

10., Enter the name of the file where the JDBC classes can be found and click

Next. The location of the JDBC classes for Oracle 8.1.7 is

$ORACLE_HOME/jdbc/lib/classes12.zip where the default value of $ORACLE_HOME is /opt/oracle8/u01/app/oracle/product/8.1.7

Figure 3-24 shows an example of this. Note that no entry is required for the JDBC shared load library path.

Figure 3-24 Location of ORacle JDBC driver classes

11.In the Payment Manager Database Access Information window, enter your values for the database owner user ID, administrator’s user ID, administrator’s password, Payment Manager database name, and the DB2 instance name. See Figure 3-25 for an example. Click Next.

Figure 3-25 Payment Manager database information

12.In the Payment Manager Configuration Information window, take the default of 8611 for the Payment API port number or enter a new value if another application on your system uses this TCP port. Click Next.

13.In the Payment Manager WebSphere Configuration Information window, enter your WebSphere Administrative Node Name and click Next.

14.In the Installation Summary window, review the chosen parameters. Click

Next to continue the installation.

15.Note: The progress bar will move during installation, although at times it may appear to have stopped. Do not terminate the install, which is continuing. The progress bar will resume moving when system resources permit.

After the installation is complete you can verify that WebSphere Payment Manager has been correctly installed by taking the following steps: 1. Start the Payment Engine:

a. Change to the Payment Manager install directory cd /opt/PaymentManager

b. Enter ./IBMPayServer

server use the WebSphere Administrative Console to check that the virtual hosts entries for the default host still have aliases that include the SSL port 443, because these aliases may be removed by the Payment Manager install. 3. Launch the Payment Manager user interface in a Web browser using the

URL:

http://<hostname>/webapp/PaymentManager/PaymentServletUI/Start 4. Check that you can log on to Payment Manager using the default