Troubleshooting
Problem
WebSphere Application Server v8.0 and later can be installed into an iASP. The supported method to install WebSphere Application Server v8.0 and later into an iASP is to complete the installation on both the primary and backup system.
Resolving The Problem
WebSphere Application Server v8.0 and later can be installed into an iASP as long as the steps included in this document are followed. The installation must be performed on both the primary and backup system, leaving the product directory on SYSBASE and placing the profile directory on the iASP. This document explains the steps necessary steps.
Note: The same set of steps below apply to WebSphere Application Server v8.0, v8.5, and v9.0. Some commands may only show one version of WebSphere Application Server; however, either version of WebSphere Application Server can be used. WebSphere Application Server v8.0 will not function on IBM i V7R4 as Java Developer Kit (1.6) is not available.
Restrictions for running WebSphere under an iASP
To share the same UserData directory on an iASP, the following restrictions apply:
Installing WebSphere Application Server on the backup system
The steps below show how to perform the installation on the backup system. After performing these steps, you will have the product directory (ProdData) on SYSBAS and the profile directory (UserData) on the iASP:
Adding iASP group to WebSphere Application Server’s job description
WebSphere will not be able to see libraries and databases on the iASP unless the job description that WebSphere 8.x runs under is changed to set the iASP group. That can be done by issuing the following command:
CHGJOBD JOBD(<QWAS8|QWAS85|QWAS9>/QWASJOBD) INLASPGRP(<iASPname>)
Note: This must be done on both Primary and Backup systems.
Changing the Host Name in WebSphere Application Server
By default, when WebSphere Application Server is installed, it uses the system name is set the host name throughout the configuration files. That is not always the name we want WebSphere Application Server to use. In a high availability environment similar to what was created here, we want WebSphere Applicaiton Server to use theTakeover IP Address. By switching WebSphere Application Server to use the TakeOverIP Address, we are able to run WebSphere on either the backup or primary system and avoid any IP or naming issues when a switchover occurs. To change WebSphere’s host names, you should follow the instructions listed in the Information Center link below:
https://www.ibm.com/support/knowledgecenter/en/SSEQTP_8.5.5/com.ibm.websphere.base.iseries.doc/ae/tagt_hostname.html
Note: Because the profile directory resides on the iASP changing the host name only needs to be done one time.
Recommended cleanup after a switchover
When a switchover is done, it is recommended that WebSphere Application Server’s OSGi cache is cleaned up. This step could be added to an auto start or stop program and occur automatically when a switchover is done.
To clean up the OSGi cache, you should do the following:
1. Ensure the server is not running
2. cd /<iASPname>/Websphere_profile_dir/profiles/ProfileName/bin
3. Run: osgiCfgInit
Note: The same set of steps below apply to WebSphere Application Server v8.0, v8.5, and v9.0. Some commands may only show one version of WebSphere Application Server; however, either version of WebSphere Application Server can be used. WebSphere Application Server v8.0 will not function on IBM i V7R4 as Java Developer Kit (1.6) is not available.
Restrictions for running WebSphere under an iASP
To share the same UserData directory on an iASP, the following restrictions apply:
| 1. | The same prerequisite and optional software for WebSphere Application Server 8.x is installed on both the primary and secondary systems. |
| 2. | The names of the installation libraries for the WebSphere Application Server installations must be the same (in other words, WAS8A, WAS85B, and so on). |
| 3. | Maintenance of the WebSphere Application Server installations sharing the UserData directory is done such that they are kept at the same fix level. |
| 4. | The product default Java Virtual Machine (JVM) value must be the same for both primary and secondary installations. This should not be an issue if the primary and secondary systems have the same IBM Developer Kit for Java product options installed. |
The most practical method of achieving the second restriction is to ensure that the installation is the first WebSphere Application Server installation on each system. After installing, look in the <app_server_root>/properties/product.properties file to find the name of the installation library.
To determine the Java Virtual Machine the WebSphere Application Server product installation is enabled to use, you should preview the following files:
o <product_installation>/properties/sdk/cmdDefaultSDK.properties
o <product_installation>/properties/sdk/newProfileDefaultSDK.properties
Note: Java 6 is no longer supported. You will need to insure that the JVM begins with either 1.7 or 1.8
To determine the Java Virtual Machine the WebSphere Application Server product installation is enabled to use, you should preview the following files:
o <product_installation>/properties/sdk/cmdDefaultSDK.properties
o <product_installation>/properties/sdk/newProfileDefaultSDK.properties
Note: Java 6 is no longer supported. You will need to insure that the JVM begins with either 1.7 or 1.8
Use the managesdk command to change the product default JVM.
Installation Manager required to install WebSphere
Beginning with WebSphere 8.0, installing any WebSphere Application Server product requires Installation Manager (IM). Information about IM can be found at http://www-01.ibm.com/support/docview.wss?uid=swg27010911. To download Installation Manager, review http://www-947.ibm.com/support/entry/portal/all_download_links/software/rational/ibm_installation_manager.
Installing WebSphere Application Server on the primary system
The following steps show how to perform the installation on the primary system. After performing these steps, you will have the product directory (ProdData) on SYSBAS and the profile directory (UserData) on the iASP:
Installation Manager required to install WebSphere
Beginning with WebSphere 8.0, installing any WebSphere Application Server product requires Installation Manager (IM). Information about IM can be found at http://www-01.ibm.com/support/docview.wss?uid=swg27010911. To download Installation Manager, review http://www-947.ibm.com/support/entry/portal/all_download_links/software/rational/ibm_installation_manager.
Installing WebSphere Application Server on the primary system
The following steps show how to perform the installation on the primary system. After performing these steps, you will have the product directory (ProdData) on SYSBAS and the profile directory (UserData) on the iASP:
| 1. | Ensure you are logged into the 5250 session with a UserID that has explicit *SECADM and *ALLOBJ special authorities. |
| 2. | Install the IBM Installation Manager on the IBM i. Follow the steps outlined in the IBM Software Technical Document: "How to Download and Install/Upgrade the IBM Installation Manager (IM) product for the IBM i" to complete the installation. |
| 3. | Display the current value of QALWOBJRST and then change it to *ALL if needed. Execute the following CL command to display the current value of QALWOBJRST: DSPSYSVAL SYSVAL(QALWOBJRST) If the current value is NOT *ALL, record the current value (so that you remember what to change it back to) and then change the value to *ALL using the following CL command: CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL) |
| 4. | Execute the CHGOPTA EXTMEDFMT(*YES) CL command PRIOR TO loading the CD/DVD disc or image. |
| 5. | Execute the STRHOSTSVR *ALL CL command to ensure all of the IBM i Host Servers are started. |
| 6. | Start Qshell. STRQSH |
| 7. | Change directory to the Installation Manager directory in IFS: o cd /QIBM/ProdData/InstallationManager/eclipse/tools |
| 8. |
You will need to know the offering ID:
o If V8.0 Base then the offering ID is com.ibm.websphere.BASE.v80 o If V8.0 ND then the offering ID is com.ibm.websphere.ND.v80 o If V8.0 Express then the offering ID is com.ibm.websphere.EXPRESS.v80 o If V8.0 Web Enablement then the offering ID is com.ibm.websphere.WEBENAB.v80 o If V8.5 Base then the offering ID is com.ibm.websphere.BASE.v85 o If V8.5 ND then the offering ID is com.ibm.websphere.ND.v85 o If V8.5 Express then the offering ID is com.ibm.websphere.EXPRESS.v85 o If V8.5 Web Enablement then the offering ID is com.ibm.websphere.WEBENAB.v85 o If V9.0 Base then the offering ID is com.ibm.websphere.BASE.v90
o If V9.0 ND then the offering ID is com.ibm.websphere.ND.v90 o If V9.0 Web Enablement then the offering ID is com.ibm.websphere.WEBENAB.v90 |
| 9. | Determine whether the installation will be from a live repository or a local repository. If using the live repository, you must be registered with IBM Passport Advantage. The URL for the repository is http://www.ibm.com/software/repositorymanager/<offering_ID> where <offerring_ID> is defined from Step 2 above. If it is from a local repository (Disk or IFS), be sure to have the correct path. |
| 10. | Install WebSphere Application Server using imcl and the following parameters (with recommended values): o -repositories <live or local as determined from step 3> o -installationDirectory /QIBM/ProdData/WebSphere/AppServer/<V8|V85|V9>/<Base/Express/ND> o -properties was.install.os400.profile.location=/<iASPname>/QIBM/UserData/WebSphere/AppServer/<V8|V85|V9>/<Base/Express/ND> o -sharedResourcesDirectory /QIBM/UserData/IMShared o -log /home/was8xInstallLog.xml o -acceptLicense o -showProgress |
| For example, if you are installing V8.5 Base edition from the live repository on device iASP01, the complete command would be: ./imcl install com.ibm.websphere.BASE.v85 -repositories http://www.ibm.com/software/repositorymanager/com.ibm.websphere.BASE.v85 -installationDirectory /QIBM/ProdData/WebSphere/AppServer/V85/Base -properties was.install.os400.profile.location=/iASP01/QIBM/UserData/WebSphere/AppServer/V85/Base -sharedResourcesDirectory /QIBM/UserData/IMShared -log /home/was8xInstallLog.xml -acceptLicense -showProgress |
The steps below show how to perform the installation on the backup system. After performing these steps, you will have the product directory (ProdData) on SYSBAS and the profile directory (UserData) on the iASP:
| 1. | Ensure the iASP is available on to the backup system. |
| 2. | Ensure you are logged into the 5250 session with a UserID that has explicit *SECADM and *ALLOBJ special authorities. |
| 3. | Install the IBM Installation Manager on the IBM i. Follow the steps outlined in the IBM Software Technical Document: "How to Download and Install/Upgrade the IBM Installation Manager (IM) product for the IBM i" to complete the installation. |
| 4. | Display the current value of QALWOBJRST and then change it to *ALL if needed. Execute the following CL command to display the current value of QALWOBJRST: DSPSYSVAL SYSVAL(QALWOBJRST) If the current value is NOT *ALL, record the current value (so that you remember what to change it back to) and then change the value to *ALL using the following CL command: CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL) |
| 5. | Execute the CHGOPTA EXTMEDFMT(*YES) CL command PRIOR TO loading the CD/DVD disc or image. |
| 6. | Execute the STRHOSTSVR *ALL CL command to ensure all of the IBM i Host Servers are started. |
| 7. | Start Qshell. STRQSH |
| 2. | Change directory to the IM directory in IFS: o cd /QIBM/ProdData/InstallationManager/eclipse/tools |
| 3. | Install WebSphere Application Server using imcl and the following parameters (with recommended values) o -repositories <live or local repository as determined from step 3 of Installing WebSphere on the primary system above> o -installationDirectory /QIBM/ProdData/WebSphere/AppServer/<V8|V85|V9>/<Base/Express/ND> o -properties was.install.os400.profile.location=/<iASPname>/QIBM/UserData/WebSphere/AppServer/<V8|V85|V9>/<Base/Express/ND> o -sharedResourcesDirectory /QIBM/UserData/IMShared o -log /home/was8xInstallLog.xml o -acceptLicense o -showProgress |
Adding iASP group to WebSphere Application Server’s job description
WebSphere will not be able to see libraries and databases on the iASP unless the job description that WebSphere 8.x runs under is changed to set the iASP group. That can be done by issuing the following command:
CHGJOBD JOBD(<QWAS8|QWAS85|QWAS9>/QWASJOBD) INLASPGRP(<iASPname>)
Note: This must be done on both Primary and Backup systems.
Changing the Host Name in WebSphere Application Server
By default, when WebSphere Application Server is installed, it uses the system name is set the host name throughout the configuration files. That is not always the name we want WebSphere Application Server to use. In a high availability environment similar to what was created here, we want WebSphere Applicaiton Server to use theTakeover IP Address. By switching WebSphere Application Server to use the TakeOverIP Address, we are able to run WebSphere on either the backup or primary system and avoid any IP or naming issues when a switchover occurs. To change WebSphere’s host names, you should follow the instructions listed in the Information Center link below:
https://www.ibm.com/support/knowledgecenter/en/SSEQTP_8.5.5/com.ibm.websphere.base.iseries.doc/ae/tagt_hostname.html
Note: Because the profile directory resides on the iASP changing the host name only needs to be done one time.
Recommended cleanup after a switchover
When a switchover is done, it is recommended that WebSphere Application Server’s OSGi cache is cleaned up. This step could be added to an auto start or stop program and occur automatically when a switchover is done.
To clean up the OSGi cache, you should do the following:
1. Ensure the server is not running
2. cd /<iASPname>/Websphere_profile_dir/profiles/ProfileName/bin
3. Run: osgiCfgInit
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CHUAA2","label":"WebSphere Application Server"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0;7.2.0;7.3.0;7.4.0"}]
Historical Number
661197993
Was this topic helpful?
Document Information
Modified date:
15 August 2022
UID
nas8N1010511