Common Issues with the IBM Installation Manager and WebSphere Application Server Installations
Resolving The Problem
This article describes common Issues with the IBM Installation Manager and WebSphere® Application Server Installations.
This topic contains errors and/or problems you may encounter when using the IBM Installation Manager
Why do I get the following "SWT Library" load error when attempting to start the IBM Installation Manager GUI (Graphical User Interface) ?
00:00.88 ERROR [main] com.ibm.cic.agent.internal.ui.AgentUI reportStatus
Could not load SWT library. Reasons:
0509-022 Cannot load module /opt/tws/IBM/InstallationManager/eclipse/configuration/org.eclipse.osgi/bundles/465/1/.cp/liblibswt-pi-gtk-4237.a.so.
0509-026 System error: A file or directory in the path name does not exist.
swt-pi-gtk (Not found in java.library.path)
0509-022 Cannot load module /.swt/lib/aix/ppc/liblibswt-pi-gtk-4237.a.so.
0509-026 System error: A file or directory in the path name does not exist.
- This problem is documented here in the Technote Required gtk libraries for IBM Installation Manager on AIX.
IBM Installation Manager is an Eclipse Rich Client Program application based on the open source project found at http://www.eclipse.org. Eclipse changed the window system requirement from motif to gtk on UNIX operating systems. For AIX, this Eclipse window system change requires the gtk libraries to be installed to support the GUI.
To resolve the issue with using the GUI, the gtk+ RPM files and dependencies must be installed onto the AIX operating system. See the technote referenced above link for the required gtk RPM files and required versions.
What are some of the symptoms I can encounter with the IBM Installation Manager if the required graphical libraries are not installed and/or installed at the correct versions ?
This problem is documented in the Technote Installation Manager graphical environment issues on Solaris, Linux, AIX.
If the required operating system graphical libraries are not installed, you can still use the IBM Installation Manager in console mode, command-line mode, or silent mode using a response file.
Problems with the IBM Installation Manager Graphical User Interface (GUI) include startup issues, broken icons, PangoLayout errors, JVM crash, and JVM hang issues.
For these common problems and resolutions with the IBM Installation Manager GUI see the technote referenced above.
Why do I get the following CRIMA1137W warning message when installing the WebSphere Application Server product using the IBM Installation Manager ?
|CRIMA1137W WARNING: The following packages do not support the 64-bit version of Installation Manager that you are using: |
IBM WebSphere Application Server Network Deployment version 126.96.36.199.
If you continue, you might have issues with installation and deployment.
For information about 64-bit mode support for a package, see the package documentation.
The reason this message occurs is because the 64-bit version of Installation Manager checks each package for 64-bit support. If a package does not support the 64-bit version, you receive a warning.
The existence of the CRIMA1137W warning will depend on each IBM package/product being installed. The above Technote references RAD but this message can also be displayed when installing other products such as WebSphere Application Server.
If the IBM package/product being installed has dependencies on the 32 bit Installation Manager (loading 32 bit shared objects, accessing a specific 32 bit program on the computer, ...) then the package will have a problem installing, updating or uninstalling.
WebSphere Application Server Version 188.8.131.52 and later can be installed with the 64-bit version of IBM Installation Manager. If you receive the CRIMA1137W warning when installing 184.108.40.206 or later then the warning message can safely be ignored.
Can I change my installed WebSphere Application Server instace from 32-bit to 64-bit ?
This problem is documented in dW Answers: How can I convert my 32 bit WebSphere v8 Installation to a 64 bit installation?
There is not a way to convert or upgrade a 32-bit installation of WebSphere Application Server from 32-bit to 64-bit or vice versa. The only way to achieve this is to uninstall the 32-bit WebSphere product and re-install the 64-bit version of the product. However, you can retain the profile configuration by backing up the 32-bit profile configuration and restoring it to the newly installed 64-bit instance of WebSphere Application Server:
- Use backupconfig to create a backup of each profile.
- Uninstall the 32-bit version of WebSphere and delete the remaining WebSphere directory structure.
- Install the 64-bit version of WebSphere into the same directory structure as before ensuring all paths remain the same as in the 32-bit install.
- Create the same profiles on the newly installed 64-bit instance of WebSphere as existed in the 32-bit instance.
- Recreate the deployment manager profile using the same cellname, nodename and servername as before.
- Recreate all other node profiles using the same cellname, nodename and servername as before and federate them to the deployment manager.
- Use restoreconfig to restore the 32-bit profile configuration into the 64-bit instance of WebSphere Application Server.
- Once all profiles have been successfully restored, the 64-bit server instances can be started.
See the dW Answers link above for details and steps needed to perform the procedure.
Why does the IBM Installation Manager GUI hang when installing WebSphere on RedHat Enterprise Linux / RHEL ?
This problem is documented in dW Answers: IBM Installation Manager GUI hangs when Installing WebSphere on RHEL
This is a known problem that is caused by an Eclipse bug: Bug 215234 - gtk_enumerate_printers blocks Printer#getDefaultPrinterData() (UI hangs)
To resolve the issue you can perform one of the following options:
- To the end of the <Installation_Mananger_Home>/eclipse/IBMIM.ini file, add the following line:
- Update the IBM Installation Manager to v1.8 or later which can be downloaded from: Installation Manager and Packaging Utility download documents
Why am I unable to install a second instance of WebSphere Application Server onto the same operating system but into a different location ?
The IBM Installation Manager displays the first instance of WebSphere but will not allow a second instance to be installed.
This problem is documented in dW Answers: Can multiple installs of WebSphere exist on the same machine, Installation Manager states already installed
- You can install multiple instances of WebSphere Application Server onto a single operating system using the same user id.
- When installing WebSphere, each installation is assigned a "Package Group".
- To install another instance of WebSphere you need to assign it a unique "Package Group" name.
- If you are using the Installation Manager GUI, it will inform you that another version is already installed, but will allow you to hit "Continue" to install a second instance.
- The "Package Group" name of the second installation instance of WebSphere will be assigned an "_number". Example:
- You can use the imcl command from <Installation_Manager_Home>/eclipse/tools to see the "Package Group" for each install:
- If you are using a silent method like imcl and/or a response file, installing additional instances of WebSphere will increment the "Package Group" automatically for each additional installation of the same product.
|If the first installation instance of WebSphere has a "Package Group" name of "IBM WebSphere Application Server v85", then the second installation instance of WebSphere will have a "Package Group" name of "IBM WebSphere Application Server v85_1"|
|imcl listInstalledPackages -verbose|
imcl listInstallationDirectories -long
Why is IBM Installation Manager 220.127.116.11 failing my virus scan with messages similar to the following?
|Not scanned (The file is encrypted) C:\IBM Rational\IM18.104.22.168\agent.installer.aix.gtk.ppc_1.8.4001.20160217_1716.zip |
Not scanned (The file is encrypted) C:\IBM Rational\IM22.214.171.124\agent.installer.linux.gtk.s390x_1.8.4001.20160217_1716.zip
Not scanned (The file is encrypted) C:\IBM Rational\IM126.96.36.199\agent.installer.linux.gtk.x86_1.8.4001.20160217_1716.zip
Not scanned (The file is encrypted) C:\IBM Rational\IM188.8.131.52\agent.installer.linux.gtk.x86_64_1.8.4001.20160217_1716.zip
Not scanned (The file is encrypted) C:\IBM Rational\IM184.108.40.206\Test\plugins\com.ibm.cic.agent.core_1.7.11.v20160129_1848.jar
This is a known issue with IBM Installation Manager 220.127.116.11. The com.ibm.cic.agent.core_1.7.11.v20160129_1848.jar file listed above contains some encrypted zip files under the win32 directory. These encrypted zip files were unintentionally included in the plugin and have since been fixed in IBM Installation Manager 1.8.5.
15 June 2018