3 Installing and Configuring WebSphere 8.5 and 8.5.5

Beginning with JD Edwards EnterpriseOne Tools Release 9.1 Update 2.3, the IBM WebSphere Application Server Release 8.5 is supported.

Beginning with JD Edwards EnterpriseOne Tools Release 9.1 Update 3.3, the IBM WebSphere Application Server Release 8.5.5 is supported. This fix pack can be installed as a new installation or an update.

Relative to WebSphere 7.0, with IBM WebSphere 8.5 the installation procedure has changed dramatically. You will now use the IBM Installation Manager as a central hub to manage the installation process. The IBM Installation Manager is designed to make the installation procedure much simpler and easier than in prior releases.

Additionally IBM WebSphere Application Server 8.5 supports SDK 1.6 as the basic configuration but with SDK 1.7 as an optional configuration.For JD Edwards EnterpriseOne, the implementation requires SDK 1.7 as the default run-time configuration for WebSphere Application Server 8.5. Therefore, after WebSphere Application Server is installed with the basic configuration, you MUST change the default SDK to 1.7.

There are several different methods that you can install WebSphere Application Server 8.5 on IBM i operating system:

  • Response files

  • Command line

  • iRemoteInstall Command

This document focuses on both the Command Line and iRemoteInstall Command methods.

This chapter describes these tasks:

3.1 Before You Begin

Before you begin the installation of WebSphere 8.5 on IBM i systems, you should perform the steps in this section.

  • All editions of WebSphere Application Server V8.5 use the Installation Manager 1.5.3 to install and maintain the product.

  • Review the installation checklist at the below link and apply any requested PTFs:

    http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%2Fcom.ibm.websphere.installation.nd.iseries.doc%2Fae%2Ftins_is_check.html

  • Download all the required software from the JD Edwards Update Center.

  • Install the required IBM WebSphere SDK Java Technology Edition 7.0. This JDK is available in these versions depending on the bitness of your system:

    • IBM WebSphere SDK 7.0 32 bit (5761-JV1 option 14), PTF SI46212

    • IBM WebSphere SDK 7.0 64 bit (5761-JV1 option 15), PTF SI46211

      Surrounding text describes java_bitness.gif.

  • The following table lists the IBM i Group PTFs that are included in the WebSphere Application Server Group PTF, along with the versions, that were tested with WebSphere Application Server V85 for IBM i.

Area Group PTF Number Group PTF Level Tested


WebSphere 8.5 WebSphere 8.5.5
Database SF99701 #12 #24
Java SF99572 #7 #14
IBM HTTP Server SF99368 #11 #21

3.2 Installing WebSphere Products using Command Line

This section discusses these topics:

3.2.1 Installing the IBM Installation Manager using the Command Line

Use this procedure to install the IBM Installation Manager using the command line.

  1. Download and expand the Installation Manager assembly (zip file) to your IBM i system. For example:

    /home/was85/im

  2. Run these commands from Qshell:

    $ cd /home/was85/im
                        $ umask 022
$ installc -acceptLicense -log ../im.install_log.txt

    The IBM Installation Manager is installed to this directory on your IBM i system:

    /QIBM/ProdData/InstallataioManager

3.2.2 Installing WebSphere Express or Network Deployment using the Command Line

Caution:

Before you perform this procedure, you must have previously installed the IBM Installation Manager as described in the previous section of this guide entitled: Section 3.2.1, "Installing the IBM Installation Manager using the Command Line".

Fix Pack 8.5.5 can be installed as a new installation or an update. For purposes of this procedure, all references are to release 8.5, but you can substitute 8.5.5 where applicable

Use this procedure to install WebSphere Express or Network Deployment using the command line.

  1. Expand the WebSphere Application Server zip file into a common directory. After all files are unzipped to a single directory, the directory should look similar to the following:

    Surrounding text describes was_unzipped.gif.

  2. Start Qshell:

    $ STRQSH

  3. Change directory to the location to the tools folder of the Installation Manager. For example:

    $ cd /QIBM/ProdData/InstallManager/eclipse/tools

  4. Enter the following command based on the product you want to install (where the bolded section is the variable that specifies the product):

    ND Installations

    $ imcl install com.ibm.websphere.ND.v85 -repositories /home/was85 -installationDirectory /QIBM/ProdData/WebSphere/AppServer/V85/ND -sharedResourcesDirectory /QIBM/UserData/InstallationManager/IMShared -acceptLicense -showProgress

    BASE Installations

    $ imcl install com.ibm.websphere.BASE.v85 -repositories /home/was85 -installationDirectory /QIBM/ProdData/WebSphere/AppServer/V85/BASE -sharedResourcesDirectory /QIBM/UserData/InstallationManager/IMShared -acceptLicense -showProgress

    EXPRESS Installations

    $ imcl install com.ibm.websphere.EXPRESS.v85 -repositories /home/was85 -installationDirectory /QIBM/ProdData/WebSphere/AppServer/V85/EXPRESS  -sharedResourcesDirectory /QIBM/UserData/InstallationManager/IMShared -acceptLicense -showProgress

    Upon completion, the IBM i system indicates the product is installed, as shown in the following example for a ND installation:

    Surrounding text describes install_nd_example.gif.

  5. Enter the following command to review the installed products:

    imcl listInstalledPackages -long

    The below example shows returned results for an IBM i system with WebSphere Express and ND installed.

    WebSphere 8.5

    Surrounding text describes install_nd_example2.gif.

    WebSphere 8.5.5

    Surrounding text describes install_nd_ex_was855.gif.

3.3 Installing WebSphere Products using iRemoteInstall Command

This section discusses these topics:

3.3.1 Understanding the iRemoteInstall Command

The iRemoteInstall.bat program is located in this folder in either the ND or Supplement images:

/Remote_Installation_Tool_for_IBM_I

The syntax of the iRemoteInstall command is shown below:

Surrounding text describes iremote_command_syntax.gif.

3.3.2 Installing the IBM Installation Manager using the iRemoteInstall Command

Fix Pack 8.5.5 can be installed as a new installation or an update. For purposes of this procedure, all references are to release 8.5, but you can substitute 8.5.5 where applicable.

Use this procedure to install the IBM Installation Manager using the iRemoteInstall command.

Note:

This procedure must be performed from a Microsoft Windows machine.

  1. On a Microsoft Windows machine, download this Installation Manager zip file:

    InstMgr_IBM_I_WAS_8.5.zip

    Note:

    You do not need to unzip this file.

  2. Download these WebSphere Application Server for Network Deployment (ND) zip files:

    WAS_ND_V8.5_1 of 3.zip

    WAS_ND_V8.5_2 of 3.zip

    WAS_ND_V8.5_3 of 3.zip

  3. Unzip the above downloaded files.

  4. Locate the iRemoteInstall.bat file from the WebSphere product directory. For example:

    Z:\software\ND\Remote_Installation_Tool_for IBM_i

  5. Open a Microsoft Windows command line window As Administrator.

  6. Enter this command to install the IBM Installation Manager:

    iRemoteInstall.bat -hostname <your_host> -username <userid> -password <password> -iminstkit <location of the Installation Manager zip file>

    The following example shows an example of the command and the results of its execution.

    Surrounding text describes iremote_command_example.gif.

3.3.3 Installing WebSphere Express or Network Deployment using the iRemoteInstall Command

Use this procedure to install WebSphere Express or Network Deployment using the the iRemoteInstall command.

  1. On a Microsoft Windows machine, download these WebSphere Application Server zip files:

    WAS_ND_V8.5_1 of 3.zip

    WAS_ND_V8.5_2 of 3.zip

    WAS_ND_V8.5_3 of 3.zip

  2. Unzip the above downloaded files.

  3. Locate the iRemoteInstall.bat file from the WebSphere product directory. For example:

    Z:\software\ND\Remote_Installation_Tool_for IBM_i

  4. Open a Microsoft Windows command line window As Administrator.

  5. Enter this command to install the WebSphere Application Server:

    iRemoteInstall.bat -hostname <your_host> -username <userid> -password <password> -wasoid ND -wasrepoloc Z:\Software\was85\ND -wasinstloc /QIBM/ProdData/WebSphere/AppServer/V85/ND

    The following example shows an example of the command and the results of its execution.

    Surrounding text describes iremote_command_example2.gif.

3.3.4 Verify the Installation

You can view the installed products using this command:

./imcl listInstalledPackages -long

You can also verify the installation thru Work with License Program. For example, that program returns results similar to those shown in this example:

Surrounding text describes license_program_results.gif.

3.4 Installing and Configuring the IBM HTTP server

The IBM HTTP Server is installed under the license program 5770DG1. You should apply the required group PTF as listed in the following table:

Area Group PTF Number Group PTF Level Tested
IBM HTTP Server SF99368 #11

3.5 Applying Updates to the WebSphere Application Server 8.5

This section discusses these topics:

3.5.1 Applying Updates from the Command Line

After you have installed WebSphere Application Server, you should verify if any updates or iFixes are required.

Product fix packs contain bundled service to bring WebSphere Application Server up to a new product level. Interim fixes provide corrective service for specific known problems. You can use the IBM Installation Manager command-line function to update the product with the fixes that are available for your service level of WebSphere Application Server version 8.5.

Note:

You cannot use the iRemoteInstall command to install a fix pack.

Use this procedure to apply updates to the WebSphere Application Server:

  1. Download a file that contains the fix pack from Fix Central, and use local updating.

  2. Transfer the compressed fix file in binary format to the IBM i systems on which it will be installed.

  3. Extract the compressed repository file to a directory on your system.

  4. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.

  5. Stop all servers and applications on the WebSphere Application Server installation that is being updated.

  6. On a CL command line, run the STRQSH commands to start the Qshell command shell.

  7. Make suer that the umask is set to 022.

  8. Change to this directory:

    <Installation_manager>/eclipse/tools

  9. Install the fix pack using this command:

    ./imcl install <offering_ID_offering_version -repositories <location_of_expanded_files> -installationDirectory <product_installation_locatin> -acceptLicense

  10. Verify by installation by using this command to list all installed packages:

    ./imcl listInstalledPackages -log

3.5.2 Applying Updates using the iGSC WebSphere8xScripts Utility

Use this procedure to apply updates to WebSphere Application Server using the iGSC WebSphere8xScripts Utility.

Note:

This utility can also update the IBM Installation Manager

Caution:

In order to install the fix pack updates, you must have the fix pack group PTF loaded on the system.

  1. Download the iGSC WebSphere8xScripts utility as described below:

    1. Create this directory on your system:

      /Websphere8xScripts

    2. Navigate to this IBM download location:

      http://public.dhe.ibm.com/services/us/igsc/cta/websphere/

    3. Save the Websphere8xScripts.zip file into the directory /Websphere8xScripts you created in the first step of this procedure.

    4. Within the directory that you placed the downloaded .zip file for the scripts, unzip the files using this command:

      jar -xvf Websphere8xScripts.zip

    5. Execute this shell script:

      WasInstallMenu.sh

    Surrounding text describes wasinstallmenu.gif.

  2. On WebSphere Application Server Install/Uninstall/Fix Pack Menu, enter the number of the task to perform.

3.6 Verifying SDK 7.0 on WebSphere Application Server 8.5

JD Edwards EnterpriseOne supports WebSphere Application Server 8.5 running with SDK 7.0 only. You must switch the java level after the installation is completed.

Starting with WebSphere Application Server 8.5, SDK 7.0 is supported as an optional feature. The java 1.6 is still the default installation.

Use this procedure to verify the java level:

  1. Locate the managesdk command which is located in the bin directory of your profile. For example:

    /QIBM/ProdData/WebSphere/AppServer/V85/ND

  2. Use this command to view the available Java products:

    managesdk -listAvailable

    Below is an example of the returned results from this command:

    Surrounding text describes installed_products_command.gif.

    Note:

    SDK 1.6 is always installed.

  3. Use this command to view the available Java products with details information:

    managesdk -listAvailable -verbose

    Below is an example of the returned results from this command:

    Surrounding text describes installed_products_command2.gif.

    Note:

    SDK 1.6 is always installed.

The following examples demonstrate correct syntax when you run the managesdk command:

managesdk -listAvailable [-verbose]

managesdk -listEnabledProfile -profileName AppSrv01 [-verbose]

managesdk -listEnabledProfileAll [-verbose]

managesdk -enableProfile -profileName AppSrv01 -sdkname 1.7_64 -enableServers

managesdk -enableProfileAll -sdkname 1.7_64 -enableServers

managesdk -getNewProfileDefault [-verbose]

managesdk -setNewProfileDefault -sdkname 1.7_64

managesdk -getCommandDefault [-verbose]

managesdk -setCommandDefault -sdkname 1.7_64

3.7 Switching to SDK 7.0 on WebSphere Application Server 8.5

The section provides examples that demonstrate the sequence of commands to use to:

3.7.1 List Available SDKs

Issue this command to view a list of available SDK names for the product installation:

./managesdk -listAvailable

The following is an example of the returned results from this command:

Surrounding text describes installed_sdks.gif.

3.7.2 Change the Default SDK to Version 7.0 SDK

Issue this command to change the default SDK to Version 7.0 SDK:

./managesdk -setCommandDefault -sdkname 1.7_64

The following is an example of the returned results from this command:

Surrounding text describes set_sdk_version.gif.

3.7.3 Set New Profile Default to Version 7.0 SDK

Issue this command to change the set the default for new profiles to Version 7.0 SDK:

./managesdk -setNewProfileDefault -sdkname 1.7_64

The following is an example of the returned results from this command:

Surrounding text describes set_new_profiles_default.gif.

3.7.4 Set Existing Profile Default to Version 7.0 SDK

Issue this command to change the set the default for existing profiles to Version 7.0 SDK:

./managesdk -enableProfileAll -sdkname 1.7_64 -enableServers

The following is an example of the returned results from this command:

Surrounding text describes set_exist_profiles_default.gif.

3.7.5 Modify the JD Edwards EnterpriseOne Server Manager Agent with JRE 1.7.0

Use this procedure to modify the Server Manager Agent with JRE 1.7.0:

  1. Stop the JD Edwards EnterpriseOne Server Manager Agent.

  2. Edit the runAgent file to include the location of the jdk70 as specified by the JAVA_HOME setting. For example:

    JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk70/64bit

  3. Save the runAgent file.

  4. Start the JD Edwards EnterpriseOne Server Manager Agent.

3.8 Creating a New Profile for the WebSphere Application Server

Use this procedure to create a new profile for the WebSphere Application Server:

  1. On a CL command line, run the STRQSH commands to start the Qshell command shell.

  2. Change to this directory:

    /QIBM/ProdData/WebSphere/AppServer/V85/ND/bin

  3. Use the following command to create a profile:

    ./manageprofiles -create -templatePath /QIBM/ProdData/WebSphere/AppServer/V85/ND/profileTemplates/default

3.9 Manually Generating a Plug-in

Note:

Federated (Clustered) Web Servers. If you are using WebSphere Application Server and running JD Edwards EnterpriseOne as part of a federated (or clustered) web server, you may need to regenerate the WebSphere global plugin configuration after deploying the newest tools release. This is required when new servlets have been added to the tools release you are deploying.

To update (regenerate) plugins, refer to the following procedure.

To update (regenerate) and propagate the global web server plugin configuration:

  1. Log on to the Deployment Manager Administration Console using the Dmgr01 profile.

    Surrounding text describes was_update_global_plugins.gif.

  2. Expand the Environment node and select Update global Web server plug-in configuration.

  3. Review the content in the right-hand pane and note the location of the plug-in file in the description. For example, the description might say:

    The global plugin-cfg.xml file is placed in the %was_profile_home%/config/cells directory.

  4. Click the OK button.