IBM FileNet P8, Version 5.2.1             

GUI version of Configuration Manager starts and quickly exits

When you start the GUI version of Configuration Manager, the application starts and quickly exits.

Symptoms

If you start the GUI version of Configuration Manager (by invoking the configmgr executable file), the application starts and quickly exits. The following error appears in the application workspace log:

java.lang.UnsatisfiedLinkError: no swt-pi-gtk-3452 or swt-pi-gtk in swt.library.path, java.library.path or the jar file

This is usually related to missing library required by configuration manager to load the application.

Causes

The swt libraries that are packaged with Configuration Manager do not get loaded because of missing dependencies.

Environment

AIX, HPUX, HPUXi, Linux, Linux for System z, Oracle Solaris,

Diagnosing the problem

Navigate to the home directory of the user who starts configmgr, and then the .log file located under configmgr_workspace/.metadata.

The log file indicates the missing libraries and contains an entry similar to the following one:

java.lang.UnsatisfiedLinkError: no swt-pi-gtk-3452 or swt-pi-gtk in swt.library.path, java.library.path or the jar file
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:233)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:151)
at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:22)
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63)
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
at org.eclipse.swt.widgets.Display.<clinit>(OS.java:130)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:511)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
at com.ibm.ecm.configmgr.ui.rcp.Application.start(Application.java:73)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

Resolving the problem

To avoid the problem, you can run Configuration Manager in command mode. If you prefer to run Configuration Manager in GUI mode, you must complete the following steps before starting Configuration Manager:

  1. Navigate to the configuration manager plugins directory (for example, /opt/IBM/FileNet/ContentEngine/tools/configure/plugins):

    cd /opt/IBM/FileNet/ContentEngine/tools/configure/plugins
  2. Create a temporary directory in the plugins directory.

    mkdir temp
  3. Copy the appropriate Eclipse Standard Widget Toolkit (SWT) JAR file for your operating system, machine architecture, and Eclipse version into the temp directory, and unzip the JAR file. For example, if the operating system is Oracle Solaris, the machine architecture is SPARC, and the Eclipse version is 3.4.1:

    cp org.eclipse.swt.gtk.solaris.sparc_3.4.1.v3452b.jar temp
    cd temp
    unjar xvf org.eclipse.swt.gtk.solaris.sparc_3.4.1.v3452b.jar

    The following table contains some examples of Eclipse SWT JAR files:
    Table 1.
    Operating system Machine architecture Eclipse version Eclipse SWT JAR file
    Oracle Solaris SPARC 3.4.1 org.eclipse.swt.gtk.solaris.sparc_3.4.1.v3452b.jar
    Linux x86 3.5.2 org.eclipse.swt.gtk.linux.x86_3.5.2.v3557f.jar
    Linux S/390 3.5.2 org.eclipse.swt.gtk.linux.s.390_3.5.2.v35557g.jar
    Linux s390x 3.5.2 org.eclipse.swt.gtk.linux.s.390x_3.5.2.v35557g.jar
  4. In the list of libraries created by the unjar command, find the library that has the prefix libswt-pi-gtk and run the ldd command on that library. The ldd command finds all the required libraries and tells you which ones are missing.

    The following table shows examples of libraries with the prefix you are looking for:
    Table 2.
    Operating system Library Command to run
    Oracle Solaris libswt-pi-gtk-3452.so ldd libswt-pi-gtk-3452.so
    Linux libswt-pi-gtk-35557.so ldd libswt-pi-gtk-35557.so
    Note that the version number of the library you are looking for must match the version number in the log file. For example, the log file contains this entry:
    java.lang.UnsatisfiedLinkError: no swt-pi-gtk-3452 or swt-pi-gtk in swt.library.path, java.library.path or the jar file
    then you are looking for version 3452.
  5. Locate the missing libraries in the operating system installation media (or at the operating system vendor website) and install them.



Last updated: October 2015
p8pct034.htm

© Copyright IBM Corporation 2015.