IBM WebSphere Application Server 8.0 Administration Guide
上QQ阅读APP看书，第一时间看更新
上一章目录下一章

Graphical installation

For our first installation, we are going to use the new IBM Installation Manager (IIM) in graphical mode to install and configure WAS. We will install WAS in two parts. Part 1 will be installation of the base binaries and part 2 will be an installation of an application server profile. In each part, we will list the actions as a set of steps. Later in the chapter, we will cover command-line installs often called silent installs.

Part 1—Installing the base binaries

The WAS v8 installation GUI has been changed since WAS v7. IBM has updated many of its products to use a common Java-based installation tool called the IBM Installation Manager (IIM). A major benefit is that IIM provides a common installation interface for many products, with transferrable knowledge, allowing you to learn how to use IIM for one product and pick it up quickly in another. It also lends to a common approach to scripted installs for all products which incorporate IIM. Scripting installations save both time and expense and can dramatically reduce human error. Another important evolution of the WAS install process is that IIM uses installation repositories which employ a single set of downloads for all WAS versions and OS variants. Prior to the WAS 8 release, each OS version of WAS required separate downloads. Using a repository system now saves many hours of download and also disk space and simplifies the management of different installation packages.

Downloading WAS 8

Traditionally, installation media for WAS used to be obtained on CD; however, this is now a fading method due to organizations moving to Internet-based downloads often referred to as software by wire. IBM provides the official WAS software downloads using an online system called Passport Advantage. If your organization has a passport advantage account, then media CDs can still be requested to be delivered as part of your license agreement. For our WAS installation, we are going to use the IBM WebSphere Application Server for Developers Trial version 8; however, we need to first download the IBM installation manager, which will be used to install this particular version in WAS.

Downloading IBM Installation Manager

At the time of writing, the latest version of IIM (version 1.4.4) can be downloaded from IBM at the following location:

Note

If you would like to understand more about IIM you can consult the online documentation located at the following URL: http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.

Installing IIM

You should have downloaded one of the following files:

The following steps will help you run the installer:

  1. For Linux:
    • Copy the downloaded agent.installer.linux.gtk.x86_1.4.4000.20110525_1254.zip file to a suitable location on your Linux server and unzip it. Take note of this location for future reference.
    • Decompress the ZIP file.
    • Ensure you have an X Window System (X11 for short) session running.
    • Run the installer using the following command:

      ./install

  2. For Windows:
    • Copy the downloaded agent.installer.win32.win32.x86_1.4.4000.20110525_1254.zip file to a suitable location on your Windows server. Take note of this location for future reference.
    • Decompress the ZIP file.
    • Run the installer using the following command:

      install.exe

Once the installer is loaded, follow the steps mentioned next:

  1. The IIM installer will begin an installation wizard. The following screen is presented detailing the version of IIM that is going to be installed. You are also given an option to Check for other Versions, Fixes, and Extensions. If you choose this option, IIM will contact the IBM online repositories and scan for IIM updates. Click Next to continue:
  2. Read the license agreement, and then select the I accept the terms in the license agreement radio option, and click Next.
  3. In the following screen you will be given an option to change the location where the IBM Installation Manager will be installed. Either accept the default location or alter it as per your requirement. We will refer to this path as<iim_root>. Click Next to continue:

    Note

    The default installation path for IIM on Windows is: C:\Program Files (x86)\IBM\Installation Manager\eclipse.

  4. Review the installation summary information that is presented and click Install to perform the installation.
  5. Once the IIM installation has completed, click the Restart Installation Manager button to restart IIM.

Installing WAS using IBM Installation Manager

In this section, we detail the steps required to install WAS using the IIM:

  1. If IIM is not already running, launch IIM. You can use the following commands to launch IIM:
    • For Linux:

      <iim_root>/IBMIM

    • For Windows:

      <iim_root>\IBMIM.exe

  2. Once IIM is loaded, you will be presented with the workbench screen:
  3. Before we can install WAS, we need to set the repository location preferences. This will inform IIM where the WAS repository components are located. Using the File menu, select the Preferences option.

    Note

    In the Preferences page, you can select the location of your WAS binary repositories. If you have a Passport Advantage account, you can set the appropriate authentication settings for downloading the commercial versions of IBM products and install from a local repository.

  4. To add a repository location, click the Add Repository button located at the top right-hand corner of the preferences screen.
  5. In the Add a repository pop-up dialog, type the following URL in the Repository field: http://www.ibm.com/software/repositorymanager/V8WASDeveloperILAN.
  6. Click OK to add the URL to the Repositories list. You will be prompted by IIM to supply your IBM username and password (IBM ID). If you do not have an IBM ID, click the IBM ID and FAQ link to register. Once you have entered your IBM ID username and password, click OK. A new entry will appear in the Repositories list:
  7. Click OK again to close and return to the main workbench screen.
  8. From the main workbench screen, locate and click the Install button, as shown in the following screenshot:
  9. IIM will check online for the availability of the latest downloads and fix packs for the trial. Once the process has been completed, a list of installation packages will be presented.
  10. Ensure that all the installation packages are selected. Click the Check for other Versions, Fixes and Extensions button and IIM will re-verify the available downloads online. Once the verification is complete, click Next.
  11. In the following screen you will be presented with details of the actual WAS binaries and latest fixes that need to be downloaded from the online IBM repository. Click Next to continue.
  12. You will now be presented with another license screen, this time for WAS. Read the license agreement, then select the I accept the terms in the license agreement radio option, and click Next.
  13. On the next screen, you will be asked to fill out a questionnaire detailing your reason for evaluating WAS. Answer the questions as required and click Next to continue.
  14. The next screen defines where the IIM will create the WAS-shared resources folder. This folder contains the files that make up what is known as the installation repository. Accept the default location suggested by the IIM installer, or enter a different one. In the following example, we have used the default provided location /opt/IBM/IMShared. We will refer to the location as<iim_shared_resources>. Click Next to move on to the next screen where you will be asked to supply the location to install the WAS binaries:
  15. You will now be given an opportunity to decide where you want to install this instance of WAS. Once again, you can decide on a file path that is convenient to your needs. It may be useful to shorten the folder names, which will make it easier for administration later when we need to navigate through the WAS filesystems. For our purposes, we are going to accept the default location in the installation directory field as shown in the following screenshot. Take note of this path. Throughout the book it will be referred to as the<was_root> path:
  16. On the next page, select your preferred language, and click Next again, to move onto the features screen.
  17. Within the features screen, you will have the option to install the sample applications provided by IBM for testing JEE concepts and features of WAS. We will not be using the sample applications within this book, so this is an optional choice. You may wish to install the samples for later exploration. There are two other options, which we will leave checked:
    • EJBDeploy tool for pre-EJB 3.0 modules:

      Provided for backwards compatibility for generating EJB 2.0 deployment code.

    • Standalone clients and resource adapters:

      Provides a set of clients for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and others.

  18. Consult with your application development team to understand whether you need to incorporate these two options, or not.

    Tip

    Installing the sample applications will add extra logging information to your installation and clutter the admin console, so it is recommended not to install these applications until you need them. They can be installed using IIM at a later date.

  19. Also within the features screen, IIM will have already detected your Operating System (OS) architecture and pre-selected either the 32-bit or 64-bit IBM Software Development Kit option. Ensure this is correct for your OS. Click Next to continue.
  20. Click Next to proceed to the final summary screen and review the options you have chosen in the previous steps.
  21. Click the Install button to begin the actual WAS installation. Once the installation is complete, you will be given an option to run the Profile Management Tool (PMT) to create a WAS profile. At this stage, we do not want to launch the PMT tool. We will cover how to create profiles after we have verified the binaries have been installed.
  22. Select the option labeled None and exit the IBM Installation Manager.

Verifying the installed binaries

Previously, we chose to defer the running of the Profile Management Tool, so we could demonstrate the manual creation of a profile later on in the chapter. All we have installed at this point is the base binaries into the location we specified.

By looking at the files installed by the installer, you will see what makes up the base binaries. You will also notice that the folder permissions are rwxr-xr-x (755), which is a result of the 022 umask that we set before we ran the installation wizard.

Note

The presence of the Uninstall folder contains an uninstaller, which we can use to uninstall WAS.

We will now do a quick check to see if the base binaries have installed correctly by running the WAS command script versionInfo.sh (which is found in the<was_root>/bin folder). We can generate a report that will identify the state of the installation.

Note

From now on, we will refer to folders as relative to the base install folder; for example, using the syntax<was_root>/<folder_path> would refer to the WAS base installation folder, plus the path we are working with. Since you may have chosen not to follow the default WAS convention during installation, you can substitute the base folder with the appropriate naming convention.

Run the following command:

  1. For Linux:

    <was_root>/bin/versionInfo.sh

  2. For Windows:

    <was_root>\bin\versionInfo.bat

The result of running the previous command will be a report similar to the following screenshot:

Installation logs

The IIM logs events as it is installing the WAS product. If there is a problem with your installation, you can consult the logs. The IIM logs files are located at the following location:

  1. For Linux: 
    /var/logs
  2. For Windows non-administrator: 
    C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs
  3. For Windows administrator: 
    C:\Documents and Settings\<user id>\Application Data\IBM\Installation Manager\logs

Note

A really nice feature of the IIM logging style is that it produces a set of XML files that can opened in a web Brower. In the root of the IIM log location will be a file called index.xml. If you open this main index file in your favorite web browser, you can navigate through the logs as if they were web pages.

Log files are the life blood of WAS. They are used for problem solving and runtime status. We will delve more into server logging in

Agent data location

Previously in WAS 7 the installer stored application registry information in a file called vdp.properties (Vital Produt properfiles file), which is now no longer the case. IIM will store data in the agent data location, or appDataLocation, and it is this directory that IIM uses for data that is associated with an application. Associated data includes the state and history of operations that the Installation Manager completes.

Note

Changing the content, files, or directories in the agent data location directory or subdirectories is not supported. Changes to the content might prevent IIM from working.

There is a file called the cic.appDataLocation property, which is set in the config.ini file and can be located at:

  1. For Linux: 
    <iim_root>/eclipse/configuration
  2. For Windows: 
    <iim_root>\eclipse\configuration

By editing the cic.appDataLocation property within the config.ini file, you can choose the specific location where you want IIM to store the agent data location.

Part 2—Creating a WAS profile

By themselves, the base binaries serve no purpose. We must create a profile which is essentially an application server definition.

We use the Profile Management Tool (PMT) to create WAS profiles using a GUI. The tool is Java-based. To manually run it, type the following command:

  1. For Linux:

    <was_root>/bin/ProfileManagement/pmt.sh

  2. For Windows:

    <was_root>\bin\ProfileManagement\pmt.bat

  3. Once the PMT has loaded, the option to Create a profile will be available. Click the Create button to start the actual profile-creation wizard:
  4. In the environment screen you will be asked to either create a Management profile or an Application server profile. The two profile types are explained in the following table:
  5. Ensure the Application server option is selected and click Next to continue:
  6. In the Profile Creation options screen as shown in the following screenshot, select Advanced profile creation. Choosing this option allows for greater choice, flexibility, and control of our profile creation as opposed to using a default configuration. Default configurations are set by the wizard, and use naming conventions and settings that you may not wish to use, but are useful if you are needed to quickly build a test/development environment:
  7. On the next screen, we can see that the there are some optional choices. The Deploy the administrative console (recommend) option will install a special web application allowing an administrator to configure WAS using a web-based UI. Please ensure the Deploy the administrative console (recommend) option is selected before continuing.
  8. There is also an option to Deploy the default application. The default application contains some very useful testing features, which we will cover in
  9. In the Profile name and location screen we determine the actual name for our first profile and the location within the filesystem where it will be created. The profile will make up our application server definition. Enter appsrv01 in the Profile name field and<was_root>/profiles/appsrv01 in the Profile directory field, as shown in the following screenshot:

    Tip

    Using lowercase for all folder names prompted in a wizard makes it easier to remember especially when typing folder paths in Linux, as Linux is case-sensitive.

In the previous example, the Server runtime performance tuning option is set to Development, which speeds up server start-up. Since we will be starting and stopping the server many times during the course of our learning, it is recommended that we turn this option ON to save time when waiting for server restarts.

The following table describes the three runtime-performance options:

  1. Click Next to move on to the next screen.
  2. The next screen is the Node and Host Names screen. The Node name is an important part of the installation process. It is recommended to keep this name as short as possible. We will cover the administration of WAS nodes in later chapters. The Server name is the actual name of the application server's JVM. This name will be referred to in logging and configuration, which again we will address in later chapters. The Host name will automatically be taken from the OS host's file and can be changed in the wizard at this point to suit your requirements. You can use a hostname, or Fully Qualified Domain Name (FQDN). If you decide to change the hostname in the wizard, ensure that the change is reflected in your host file or DNS as required.

    Note

    If you use an FQDN, first test that it is resolvable. In our examples, we will be using a manually-derived hostname for simplicity. Our hostname will be node01 and our domain name is waslocal.com. The FQDN will be node01.waslocal.com. (This is not a real Internet domain.)

    We are running on a private network so we can call it whatever we like, as long as our OS host file is configured correctly.

  3. Enter the values listed in the following table into the fields on the Nodes and Host Names screen:
  4. You can see the application of these values in the following screenshot.
  5. Click Next to move on to the Administrative Security screen.
  6. In the Administrative Security screen, we will disable administrative security for now and re-enable it in

    Note

    We will deal with more on security later in Chapter 4,Security.

  7. The next screen is the Security Certificate (Part 1) screen. This is a new feature of the WAS installation wizard available since version 7. In previous versions of WAS, the security certificate screens were not available. The options available are: to use default certificates, use an existing keystore, or create one from another Certificate Authority (CA). For now, we will use the default keystore as generated by the installer. Certificates that are used for SSL are beyond the scope of this book. We will accept the default settings. Click Next to go to the Security Certificate (Part 2) screen.
  8. The next screen is the Security Certificate (Part 2) screen. When a browser connects to a page using SSL, it presents the hostname of the URL used to gain access to that page. If the SSL certificate within WAS doesn't match this hostname, then an exception will be displayed. The reason for this is that SSL provides a secure connection. If you connect to a host and the actual hostname doesn't match the hostname associated with the SSL certificate presented by the server, then you need to be informed whether to trust the site or not. The wizard will generate a self-signed certificate as part of the installation process. By updating the distinguished name of the self-signed certificate that WAS generates, we can stop browser exceptions.

    In the Issued to distinguished name field, type the following:

    cn=node01.waslocal.com,ou=Node01Cell,ou=node01,o=IBM,c=US

    In the Issued by distinguished name field type the following:

    cn=node01.waslocal.com,ou=RootCertificate,ou=Node01Cell,ou=node01,o=IBM,c=US

  9. Click Next to move on to the Port Value Assignment screen.
  10. WAS requires the use of several ports during runtime. It is wise to ensure that no other application is already using the ports that you wish to use. The wizard is quite clever and will detect port usage, even including older versions of WAS, and recommend free ports; however, it is good practice to use the Linux/Windows command netstat -an to ensure that no other processes are using these ports. Use the following steps to check for used ports:
    • Open a secure shell to your Linux server, or for Windows simply open a command prompt.
    • Type the following command:

      netstat –an

    • Within the report that is generated, you are looking to see if ports have already been used.

      The following table shows the default ports that WAS will use:

  11. Since this is our first WAS profile, we will use the defaults recommended by the wizard. If you see different ports than the default ones, then it means you must have other processes running on these ports, or another version of WAS is already installed.

    Note

    The administrative console port is very important. We will use this port to gain access to the administration console. Please take note of the Administrative console port (Default 9060), before you move on to the next step.

  12. Click Next to go to the next step of the installation, where we choose whether we want WAS to automatically restart on reboot. If you wish to have WAS automatically start up again when a server is rebooted, then you can enable this option. In our examples, we don't require WAS to start on reboot, so we will leave the Run the application server process as a Linux service checkbox unchecked.
    • Linux users: If enabled, the wizard will generate an automatic start and stop script in the init.d directories as required by the Linux run levels. We will not be discussing Linux run levels in this book; please consult your Linux distribution's documentation.
    • Windows users: For those of you who have chosen to install WAS on Windows, the equivalent screen will provide an option to install Windows service. You will require administrative privileges to ensure that the service can start and stop WAS correctly.

      Note

      Automatic start and stop scripts are recommended for production environments. However, Linux administrators may wish to craft their own start-up scripts. If you wish to learn how these start-up scripts work, then enable the creation of the Linux Service Definition to view the resulting script and it is also recommended that you consult how Linux run levels work.

      If you wish to add a service definition post-install and have appropriate access, you can run the WAS Linux command script<was_root>/bin/wasservice.sh or the Windows command script<was_root>\bin\wasservice.bat, which will create the appropriate start and stop scripts.

  13. Click Next to enter the Web Server Definition screen. We will be covering Web Server definitions in Chapter 9, Administrative Features. For now, we will skip this screen, leaving the Create a Web server definition checkbox unchecked. Click Next to move on to the Profile Creation Summary screen.
  14. The final step of the wizard is Profile Creation Summary. The wizard presents a summary of your configuration options. If you are not happy with your configuration, you can go back and change your settings. If your settings are correct, click Create, which will start the profile creation.

First steps console

Once the profile creation is complete, you can choose to run the First steps console, which offers a few checks that you can run to verify that the installation and profile creation was successful. To verify your GUI-based installation, it is best to ensure that you run all the checks within, and ensure that your installation and profile creation was successful and get quick proof that WAS is actually functional.

  1. Launch the First steps console by selecting the on-screen option labeled Launch the First steps console, and click Finish which will trigger the console to load. You can see the console in the following screenshot:
  2. Click on the Installation verification option in the First steps console as shown in the previous screenshot. If there were no problems with the installation, WAS will be started and a report similar to the following screenshot will be generated:
  3. Now that we have proven the application server was able to start, we can now stop the server by clicking on Stop the server. The First steps console should now report that server01 has stopped. This is shown in the following screenshot:
  4. You can now close down the First steps console window. When you exit the First steps console and return back to the Profile Management Tool, you will see that the new profile is listed in the profile list, as shown in the following screenshot:
  5. You have now successfully installed the WebSphere Application Server. You can close the PMT.

Profile Manager Tools (PMT) logs and files

Similar to the installation logs, the Profile Management Tool (PMT) also leaves a small footprint of logs detailing the profile creations.

Logs

During the creation of a profile, the PMT logs to a file called pmt.log in the<was_root>/logs/manageprofiles folder. This log file can be used to help diagnose causes of issues when a profile creation fails. This file most probably will not need to be consulted very often.

Files

After a profile is created, a useful file called AboutThisProfile.txt is created in the profile's logs folder; for example,<was_root>/profiles/appsrv01/logs.

This file can be useful to determine basic information about the profile-like ports and general settings.

Note

Also located in the logs folder is a file called ivtClient.log, which contains the logging information, reported previously in the First steps console..

上一章目录下一章