What we can do is look for message in /var/log/messages
cat messages |
We see a line something like the one highlighted below
Feb 17 03:03:20 localhost /etc/gdm/Xsession: 00:00.70 ERROR [main] org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory safeLogged Feb 17 03:03:20 localhost /etc/gdm/Xsession: Could not load SWT library. Reasons: Feb 17 03:03:20 localhost /etc/gdm/Xsession: /home/stever/.eclipse/870893307/configuration/org.eclipse.osgi/bundles/268/1/.cp/libswt-pi-gtk-4234.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) Feb 17 03:03:20 localhost /etc/gdm/Xsession: swt-pi-gtk (Not found in java.library.path) Feb 17 03:03:20 localhost /etc/gdm/Xsession: /home/stever/.swt/lib/linux/x86/libswt-pi-gtk-4234.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) Feb 17 03:03:20 localhost /etc/gdm/Xsession: /home/stever/.swt/lib/linux/x86/libswt-pi-gtk.so (/home/stever/.swt/lib/linux/x86/liblibswt-pi-gtk.so.so: cannot open shared object file: No such file or directory) Feb 17 03:03:20 localhost /etc/gdm/Xsession: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: Feb 17 03:03:20 localhost /etc/gdm/Xsession: /home/stever/.eclipse/870893307/configuration/org.eclipse.osgi/bundles/268/1/.cp/libswt-pi-gtk-4234.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) Feb 17 03:03:20 localhost /etc/gdm/Xsession: swt-pi-gtk (Not found in java.library.path) Feb 17 03:03:20 localhost /etc/gdm/Xsession: /home/stever/.swt/lib/linux/x86/libswt-pi-gtk-4234.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) Feb 17 03:03:20 localhost /etc/gdm/Xsession: /home/stever/.swt/lib/linux/x86/libswt-pi-gtk.so (/home/stever/.swt/lib/linux/x86/liblibswt-pi-gtk.so.so: cannot open shared object file: No such file or directory) Feb 17 03:03:20 localhost /etc/gdm/Xsession: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: Feb 17 03:03:20 localhost /etc/gdm/Xsession: /home/stever/.eclipse/870893307/configuration/org.eclipse.osgi/bundles/268/1/.cp/libswt-pi-gtk-4234.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) Feb 17 03:03:20 localhost /etc/gdm/Xsession: swt-pi-gtk (Not found in java.library.path) Feb 17 03:03:20 localhost /etc/gdm/Xsession: /home/stever/.swt/lib/linux/x86/libswt-pi-gtk-4234.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) Feb 17 03:03:20 localhost /etc/gdm/Xsession: /home/stever/.swt/lib/linux/x86/libswt-pi-gtk.so (/home/stever/.swt/lib/linux/x86/liblibswt-pi-gtk.so.so: cannot open shared object file: No such file or directory) Feb 17 03:03:20 localhost /etc/gdm/Xsession: at org.eclipse.swt.internal.Library.loadLibrary(Library.java:331) Feb 17 03:03:20 localhost /etc/gdm/Xsession: at org.eclipse.swt.internal.Library.loadLibrary(Library.java:240) Feb 17 03:03:20 localhost /etc/gdm/Xsession: at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:22) Feb 17 03:03:20 localhost /etc/gdm/Xsession: at java.lang.J9VMInternals.initializeImpl(Native Method) Feb 17 03:03:20 localhost /etc/gdm/Xsession: … Feb 17 03:03:20 localhost /etc/gdm/Xsession: The displayed failed to initialize. See the log /home/stever/.eclipse/870893307/configuration/1424142197941.log for details. |
Opening this file we get the following message
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: /opt/IBM/IntegrationToolkit90/configuration/org.eclipse.osgi/bundles/5918/1/.cp/libswt-pi-gtk-3659.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) swt-pi-gtk (Not found in java.library.path) /tmp/swtlib-32/libswt-pi-gtk-3659.so (libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory) /tmp/swtlib-32/libswt-pi-gtk.so (/tmp/swtlib-32/liblibswt-pi-gtk.so.so: cannot open shared object file: No such file or directory)
at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source) at org.eclipse.swt.internal.gtk.OS.<clinit>(Unknown Source) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source) at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(Unknown Source) at org.eclipse.ui.internal.Workbench.createDisplay(Unknown Source) at org.eclipse.ui.PlatformUI.createDisplay(Unknown Source) at org.eclipse.ui.internal.ide.application.I
DEApplication.createDisplay(Unknown Source) at org.eclipse.ui.internal.ide.application.IDEApplication.start(Unknown Source) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source) at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source) at org.eclipse.equinox.launcher.Main.run(Unknown Source) at org.eclipse.equinox.launcher.Main.main(Unknown Source) |
Solution
We did not look at the dependencies required for IIB 9.0 to run on a supported platform. Below is a quick fix, however it is recommended that when you use a non-certified platform that you look up on the IIB site to find the nearest operating system that matches for example If Using CentOS 7.x then look for Redhat Enterprise Linux Enterprise (RHEL) 7. If 7 is not available then go to the next lowest OS version i.e. RHEL 6.x
Note: Here is a link to the IBM Knowledge Centre for example: http://www-01.ibm.com/support/knowledgecenter/
You can drill down the link index to find to the Integration Broker 9.0 landing page as seen in the screen capture below.
It can be hard to find a list of dependencies as IBM are certifying platforms and you have chosen to install on a non-supported platform. Though this is true, there are often many blogs on solutions and also the IBM forums can help. But let’s not deceive ourselves, it can take some time to find a solution and you have to be prepared to try and try again. Unless you have [paid for support. then blood sweat and of course hands-on experience is required.
Note: Most of the GUI issues such as when the IBM Installation Manager fails to load is because Installation Manager is a 32-bit application and requires 32-bit versions of OS system libraries. These libraries are not installed on RHEL 6.0/6.1 x86_64 (64-bit) by default. You must install these 32-bit libraries on your system before you run Installation Manager.
- Install dependencies
yum install gtk2.i686 gtk2-engines.i686 PackageKit-gtk-module.i686 PackageKit-gtk-module.x86_64 libcanberra-gtk2.x86_64 libcanberra-gtk2.i686 |