Websphere for Linux on Iseries: Implementation Guide

Chapter 2: Installation and Configuration

Figure 2-1: The VNC Viewer icon

Figure 2-2: Entering the host name and the session ID

Figure 2-3: Click Install the product on the LaunchPad

Figure 2-4: Accepting the Open SSL license

Figure 2-5: Accepting the software license agreement

Figure 2-6: Selecting the Full setup type

Figure 2-7: Selecting the specific features on the Custom window

Figure 2-8: Setting the installation directories

Figure 2-9: Setting the node name and host name

Figure 2-10: Verifying the selected features

Figure 2-11: Uncheck the register option

Figure 2-12: Finishing the installation wizard

Figure 2-13: Starting the server in the First Steps Window

Figure 2-14: Messages in verifying installation

Figure 2-15: Verify the server status

Figure 2-16: Verifying the server status and starting the application server

Figure 2-17: Snoop— Access through the embedded Web server

Figure 2-18: Logging in to the Administrative Console

Figure 2-19: Access the Administrative Console through the embedded HTTP Server

Figure 2-20: Application Servers— server1

Figure 2-21: Access WebSphere Application Server through IBM HTTP Server

Figure 2-22: Verifying the status of IBM HTTP Server

Figure 2-23: Putting your host name on /opt/IBMHttpServer/conf/httpd.conf

Figure 2-24: Typing —wq to save your IBM HTTP Server configuration

Figure 2-25: Snoop— Accessing through your Web server

Figure 2-26: Verifying the connectivity using the sample application

Figure 2-27: Click Run to run the Pet Store application

Figure 2-28: Click "enter the store" to start the PetStore application

Figure 2-29: The PetStore application

Figure 2-30: Click Virtual Hosts after expanding Environment

Figure 2-31: Click Host Aliases

Figure 2-32: Click * in the row of port 80

Figure 2-33: Set the Host Name (*) and the port number (50001)

Figure 2-34: Click Save after changing your configuration

Figure 2-35: Click Save to save your changes to the master confutation

Figure 2-36: Accessing the Update Web server plugin

Figure 2-37: The confirmation message after saving the configuration

Figure 2-38: Confirming Virtual host Name 80 → 50001

Figure 2-39: Adding the line Listen 50001

Figure 2-40: Successful connection with the specific port number

Figure 2-41: Click "Install the product" on the LaunchPad

Figure 2-42: Selecting the features to install

Figure 2-43: Set the installation directory

Figure 2-44: Setting the node, host, and cell names

Figure 2-45: Verify the installed features

Figure 2-46: Uncheck the register option

Figure 2-47: Finishing the installation wizard

Figure 2-48: Start the Deployment Manager on the First Steps window

Figure 2-49: Messages regarding starting the Deployment Manager

Figure 2-50: Message verifying successful installation

Figure 2-51: Administrative console— ND

Figure 2-52: Changing the port number on the server.xml file

Figure 2-53: Changing the port number on the virtualhosts.xml file

Figure 2-54: Administrative console— ND

Figure 2-55: Our Cluster environment

Figure 2-56: Setting the node information

Figure 2-57: Adding the node successfully

Figure 2-58: Starting the remote application server

Figure 2-59: Added remote node shows up successfully

Figure 2-60: Cell nodes list from Administrative Console

Figure 2-61: Setting the New Cluster information

Figure 2-62: Setting the New Clustered Servers information (linux)

Figure 2-63: Setting the New Clustered Servers (linux02)

Figure 2-64: Cluster started successfully

Figure 2-65: Mapping modules to application servers

Figure 2-66: Successful installation message

Figure 2-67: Starting the Hello application

Figure 2-68: Dispatched the application to WLM_Server1

Figure 2-69: Dispatched the application to WLM_Server2

Figure 2-70: Clicking Install the product on the LaunchPad window

Figure 2-71: Selecting the existing base product to install Enterprise

Figure 2-72: Selecting the Typical setup type

Figure 2-73: Selecting the specific features

Figure 2-74: Setting the installation directory

Figure 2-75: Verifying the installed features— Typical

Figure 2-76: Uncheck the register option

Figure 2-77: Finishing the installation wizard

Figure 2-78: Administrative console— Enterprise

Figure 2-79: Click Remove Node to remove node— linux

Chapter 3: Connectivity with OS/400 Resources

Figure 3-1: Overview of MyBankCMP sample application

Figure 3-2: iSeries Navigator— Creating a new Library

Figure 3-3: iSeries Navigator— Running SQL statements

Figure 3-4: iSeries Navigator— Creating a journal

Figure 3-5: iSeries Navigator— Journal parameters

Figure 3-6: iSeries Navigator— Start journaling ACCOUNT table

Figure 3-7: FTP— Copy jt400.jar to Linux file system

Figure 3-8: WebSphere console— Creating a WebSphere variable

Figure 3-9: WebSphere console— Creating variables/configuration

Figure 3-10: WebSphere console— Save message

Figure 3-11: WebSphere Console - Saving on master configuration

Figure 3-12: WebSphere console— Resources/JDBC providers

Figure 3-13: WebSphere console— Selecting DB2 JBDC driver

Figure 3-14: WebSphere console— Configuration properties for JDBC provider

Figure 3-15: WebSphere console— JDBC provider created

Figure 3-16: WebSphere console— JDBC additional properties/data sources

Figure 3-17: WebSphere console— General properties for the datasource

Figure 3-18: WebSphere console— Update additional properties

Figure 3-19: J2C Authentication Data Entries option

Figure 3-20: J2C Authentication data entry

Figure 3-21: Defining user and password for used by J2C security

Figure 3-22: Shortcut to MyBankDS

Figure 3-23: Select Custom properties

Figure 3-24: serverName option in the custom properties menu

Figure 3-25: Configuring the serverName

Figure 3-26: Database option in Custom properties menu

Figure 3-27: Configuring the database name

Figure 3-28: Libraries option in Custom properties menu

Figure 3-29: Configuring the Library name

Figure 3-30: Assign MyBankAlias to Datasource

Figure 3-31: WebSphere console— Installing a new application

Figure 3-32: Importing .EAR file to WebSphere Application Server environment

Figure 3-33: Defining the path where the EAR files resides

Figure 3-34: Installing application— Connection factory bindings

Figure 3-35: Installation wizard— Step 1

Figure 3-36: Installation wizard— Step 2

Figure 3-37: Installation wizard— Step 3

Figure 3-38: Installation wizard— Step 4

Figure 3-39: Installation wizard— Step 5

Figure 3-40: Installation wizard— Step 5

Figure 3-41: Installation wizard— Step 6

Figure 3-42: Installation wizard— Step 7

Figure 3-43: Installation wizard— Step 8

Figure 3-44: installation Wizard - Step 10

Figure 3-45: Executing the application installation wizard

Figure 3-46: Finishing installation— Saving in master configuration

Figure 3-47: Updating Web server plugin

Figure 3-48: Acknowledge updating Web server plugin

Figure 3-49: plugin-cfg.xml file after upgrading Web server plugin

Figure 3-50: Starting the MyBankCMP application

Figure 3-51: MyBankCMP start page

Figure 3-52: Create a new account

Figure 3-53: Bank account created

Figure 3-54: Transfer funds

Figure 3-55: Transfer successful

Figure 3-56: Loan Application Entry display

Figure 3-57: Structure of the Loan Service application

Figure 3-58: Structure of web.xml file

Figure 3-59: CallRPGweb.pcml

Figure 3-60: RPG program— /QSYS.LIB/ITSDOWS.LIB/APPL01.PGM

Figure 3-61: Preparing for the application installation— Path and Context Root

Figure 3-62: Preparing for the application installation— Virtual host

Figure 3-63: Install New Application AppDeployment Options

Figure 3-64: Start Enterprise Application

Figure 3-65: Loan Service Input Form

Figure 3-66: Loan Service Result Form

Figure 3-67: USER1 on APPLPF.file

Chapter 4: Tips and Techniques

Figure 4-1: Troubleshooting— Server.xml file

Figure 4-2: Nodes Synchronization status

Figure 4-3: Logs and Trace

Figure 4-4: Log and trace— Choosing a server

Figure 4-5: JVM logs— Runtime tag

Figure 4-6: Specifying the product directory to apply the fix

Figure 4-7: Select Install fixes

Figure 4-8: Specifying the directory where the fix is located

Figure 4-9: Selecting the fix to install

Figure 4-10: Confirming the summary

Figure 4-11: Finishing the update wizard

Figure 4-12: Removing the suse_addmodule.conf line

Figure 4-13: Removing the libperl.so line

Figure 4-14: Adding the statements to load the plugin modules

Figure 4-15: Adding the mod_app_server_http.c line