How to install WebSphereServer 7 on RHEL6x86-64

This document describes what it takes to perform a non-root installation of 64-bit IBM WebSphere Process Server (WPS) 7 with the 7.0.0.3 fixpack on Red Hat Enterprise Linux 6 x86-64.

Please note that Red Hat Enterprise Linux 6 is not a supported operating system by any available version of IBM WebSphere Process Server V7 to date (02/05/2011). Consult .

The installation instruction assumes that you're running a vanilla Red Hat Enterprise Linux 6 x86-64 with the Desktop group package installed.

[wps@rhel6 ~]$ uname -a Linux rhel6 2.6.32-71.14.1.el6.x86_64 #1 SMP Wed Jan 5 17:01:01 EST 2011 x86_64 x86_64 x86_64 GNU/Linux   [wps@rhel6 ~]$ lsb_release LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch   [wps@rhel6 ~]$ date Sun Feb 6 15:30:57 CET 2011   [wps@rhel6 ~]$ sudo yum update Loaded plugins: refresh-packagekit, rhnplugin rhel-x86_64-server-6 | 1.5 kB 00:00 Setting up Update Process No Packages marked for Update

Spis treści []

• 1 Executing launchpad.sh - /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

Executing launchpad.sh - /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

You start a WPS installation by executing launchpad.sh shell script. It runs a Firefox window where you click To install WebSphere process Server when the user does not have administrative or root privileges, click here or Nonadministrative or nonroot installation menu.

When in Nonadministrative or nonroot installation, click the Install WebSphere Application Server link to run the installation that eventually finishes with the following error:

In the console where you run launchpad.sh, you should notice another error message:

[wps@rhel6 wps7-install]$ ./launchpad.sh + firefox -P Profile_3574 -profile /tmp/IBM_LaunchPad_3574/Profile_3574 file:///media/psf/wps7-install/launchpad/Mozilla.html I Process Type: install I Install Type: nonOS400 I Install Mode: silentMode I #Received OPT Properties #Thu Feb 03 14:28:40 CET 2011 installType=installNew allowNonRootSilentInstall=true feature=samplesSelected;languagepack.console.all;languagepack.server.all disableNonBlockingPrereqChecking=true silentInstallLicenseAcceptance=true profileType=none installLocation=/home/wps/ibm/WebSphere/ProcServer disableOSPrereqChecking=true   Feb 3, 2011 2:28:42 PM java.util.prefs.FileSystemPreferences$2 run INFO: Created user preferences directory. none null $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.install.start) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.Features.samples) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.Features.consolelang) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.Features.serverlang) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.install.product,$W(identifyselectedproductaction$P(wsglobalinstallconstantsProductBean.currentNLSMessageKey)... $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summarypanel.Features.core) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.Features.samples) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.Features.consolelang) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.Features.serverlang) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.install.feature,$L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summarypanel.Features.core)... $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summarypanel.install.ifix,7.0.0.7-WS-WAS-LinuxX64-IFPK98944<br>7.0.0.X-WS-WASJavaSDK-LinuxX64-IFPM00452<br>) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.install.disksize,$W(calculatediskspaceInstallWizardBean.installRootSpaceRequired)) $L(com.ibm.ws.install.resourcebundle.WSResourceBundle,summaryPanel.install.end) $J(installSource)/setup.jar = 16746840 Total buffer 16746910 $J(installSource)/install = 12884 Total buffer 16759794 $J(installSource)/install.exe = 0 Total buffer 16759794 $J(installSource)/framework = 74264 Total buffer 16834058 $J(installSource)/lib = 2339244 Total buffer 19173302 $J(installSource)/version.txt = 0 Total buffer 19173302 $J(installSource)/panels/preSummary.xml = 10105 Total buffer 19183407 $J(installSource)/panels/uninstallPreSummaryControl.xml = 844 Total buffer 19184251 $J(installSource)/panels/uninstallWelcomePanel.xml = 927 Total buffer 19185178 $J(installSource)/panels/profileDeletionPanel.xml = 2142 Total buffer 19187320 $J(installSource)/panels/postSummary.xml = 10727 Total buffer 19198047 $J(installSource)/framework/pluginparamoverrides.xml.uninstall = 1665 Total buffer 19199712 /tmp/IBM_LaunchPad_3574/changeDirectory.sh: /media/psf/wps7-install/IM/userinst: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

The cryptic error message - /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory - is a means to tell you that you don't have 32-bit Linux binaries installed. In fact, you do not since it's a plain vanilla 64-bit Linux distribution. Besides, as it is pointed out in :

"By default, RHEL 5 only installs 64-bit runtime support on these platforms. However, various applications included with WebSphere Application Server Version 7.x products and packages also require the 32-bit runtime support. Therefore, you must install the 32-bit runtime support."

The error message pops up right before IBM Installation Manager (IBM IM or simply IM and I'll use it interchangeably) is supposed to show up. The IM has indeed been installed, but can't start (or draw to be precise) its GUI due to missing 32-bit packages. Although the WPS installer is for 64-bit version, its parts are still at 32-bit level and IM is unable to start.

[wps@rhel6 eclipse]$ file ./IBMIM ./IBMIM: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped

Installing 32-bit Linux packages It's really RTFM - Preparing Red Hat Enterprise Linux 5 for installation

You should start your WPS7 installation journey from the document . That's where the required 32-bit packages are listed. I had not read it before I started an installation and bad things happened for which losing time was the most painful.

The complete yum install command is as follows:

[root@rhel6 ~]# yum install glibc.i686 libstdc++.i686 compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 \ elfutils-libs.i686 elfutils-libs.x86_64 elfutils.x86_64 compat-db.i686 compat-db.x86_64 libXp.i686 libXp.x86_64 \ libXmu.i686 libXmu.x86_64 libXtst.i686 libXtst.x86_64 pam.i686 pam.x86_64 rpm-build.x86_64 \ libXft.i686 libXft.x86_64 elfutils.x86_64 compat-libstdc++-296.i686

Once you finish installing the 32-bit packages, run ldd to ensure that all the dynamic dependencies of IBMIM are resolved. Note the /lib/ld-linux.so.2 library at the bottom - that's why we're at it at all.

[wps@rhel6 eclipse]$ ldd ./IBMIM linux-gate.so.1 => (0x00202000) libpthread.so.0 => /lib/libpthread.so.0 (0x00e32000) libdl.so.2 => /lib/libdl.so.2 (0x00db1000) libc.so.6 => /lib/libc.so.6 (0x0050c000) /lib/ld-linux.so.2 (0x0048f000)

strace vs No such file or directory - installing gtk2.i686

Even though you might be thinking that the required 32-bit packages are in the system, the IM won't show up yet. That's where I came to use the strace utility that used to help enormously in such scenarios. Run it to find out what's missing, usually reflected by No such file or directory message.

[root@rhel6 eclipse]# pwd /home/wps/IBM/InstallationManager/eclipse [root@rhel6 eclipse]# strace ./IBMIM execve("./IBMIM", ["./IBMIM"], [/* 26 vars */]) = 0 [ Process PID=19818 runs in 32 bit mode. ] ... close(3) = 0 open("/lib/i686/libgdk_pixbuf-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory) open("/lib/libgdk_pixbuf-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib/libgdk_pixbuf-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory) munmap(0xf779e000, 60931) = 0 open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=60931, ...}) = 0 mmap2(NULL, 60931, PROT_READ, MAP_PRIVATE, 3, 0) = 0xfffffffff779e000 close(3) = 0 open("/lib/i686/libgtk-x11-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory) open("/lib/libgtk-x11-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/lib/libgtk-x11-2.0.so.0", O_RDONLY) = -1 ENOENT (No such file or directory) munmap(0xf779e000, 60931) = 0 shmctl(1638413, IPC_64|IPC_RMID, 0) = 0 munmap(0x773000, 38940) = 0 exit_group(13) = ?

A bit of Googling and it all boiled down to the gtk2.i686 package.

[root@rhel6 ~]# yum install gtk2.i686

All in all, you'll have to install a few more 32-bit packages. Here's the list.

[root@rhel6 ~]# yum list installed *.i686 Loaded plugins: refresh-packagekit, rhnplugin Installed Packages PackageKit-gtk-module.i686 0.5.8-13.el6 @rhel-x86_64-server-6 alsa-lib.i686 1.0.21-3.el6 @rhel-x86_64-server-6 atk.i686 1.28.0-2.el6 @rhel-x86_64-server-6 audit-libs.i686 2.0.4-1.el6 @rhel-x86_64-server-6 avahi-libs.i686 0.6.25-8.el6 @rhel-x86_64-server-6 bzip2-libs.i686 1.0.5-7.el6_0 @rhel-x86_64-server-6 cairo.i686 1.8.8-3.1.el6 @rhel-x86_64-server-6 compat-db.i686 4.6.21-15.el6 @rhel-x86_64-server-6 compat-db42.i686 4.2.52-15.el6 @rhel-x86_64-server-6 compat-db43.i686 4.3.29-15.el6 @rhel-x86_64-server-6 compat-libstdc++-296.i686 2.96-144.el6 @rhel-x86_64-server-6 compat-libstdc++-33.i686 3.2.3-69.el6 @rhel-x86_64-server-6 cracklib.i686 2.8.16-2.el6 @rhel-x86_64-server-6 cups-libs.i686 1:1.4.2-35.el6_0.1 @rhel-x86_64-server-6 db4.i686 4.7.25-16.el6 @rhel-x86_64-server-6 dbus-glib.i686 0.86-5.el6 @rhel-x86_64-server-6 dbus-libs.i686 1:1.2.24-3.el6 @rhel-x86_64-server-6 elfutils-libelf.i686 0.148-1.el6 @rhel-x86_64-server-6 elfutils-libs.i686 0.148-1.el6 @rhel-x86_64-server-6 expat.i686 2.0.1-9.1.el6 @rhel-x86_64-server-6 fontconfig.i686 2.8.0-3.el6 @rhel-x86_64-server-6 freetype.i686 2.3.11-6.el6_0.2 @rhel-x86_64-server-6 gamin.i686 0.1.10-9.el6 @rhel-x86_64-server-6 glib2.i686 2.22.5-5.el6 @rhel-x86_64-server-6 glibc.i686 2.12-1.7.el6_0.3 @rhel-x86_64-server-6 gnutls.i686 2.8.5-4.el6 @rhel-x86_64-server-6 gstreamer.i686 0.10.29-1.el6 @rhel-x86_64-server-6 gtk2.i686 2.18.9-4.el6 @rhel-x86_64-server-6 gtk2-engines.i686 2.18.4-5.el6 @rhel-x86_64-server-6 jasper-libs.i686 1.900.1-15.el6 @rhel-x86_64-server-6 keyutils-libs.i686 1.4-1.el6 @rhel-x86_64-server-6 krb5-libs.i686 1.8.2-3.el6_0.3 @rhel-x86_64-server-6 libICE.i686 1.0.6-1.el6 @rhel-x86_64-server-6 libSM.i686 1.1.0-7.1.el6 @rhel-x86_64-server-6 libX11.i686 1.3-2.el6 @rhel-x86_64-server-6 libXau.i686 1.0.5-1.el6 @rhel-x86_64-server-6 libXcomposite.i686 0.4.1-2.el6 @rhel-x86_64-server-6 libXcursor.i686 1.1.10-2.el6 @rhel-x86_64-server-6 libXdamage.i686 1.1.2-1.el6 @rhel-x86_64-server-6 libXext.i686 1.1-3.el6 @rhel-x86_64-server-6 libXfixes.i686 4.0.4-1.el6 @rhel-x86_64-server-6 libXft.i686 2.1.13-4.1.el6 @rhel-x86_64-server-6 libXi.i686 1.3-3.el6 @rhel-x86_64-server-6 libXinerama.i686 1.1-1.el6 @rhel-x86_64-server-6 libXmu.i686 1.0.5-1.el6 @rhel-x86_64-server-6 libXp.i686 1.0.0-15.1.el6 @rhel-x86_64-server-6 libXrandr.i686 1.3.0-4.el6 @rhel-x86_64-server-6 libXrender.i686 0.9.5-1.el6 @rhel-x86_64-server-6 libXt.i686 1.0.7-1.el6 @rhel-x86_64-server-6 libXtst.i686 1.0.99.2-3.el6 @rhel-x86_64-server-6 libasyncns.i686 0.8-1.1.el6 @rhel-x86_64-server-6 libcanberra.i686 0.22-1.el6 @rhel-x86_64-server-6 libcanberra-gtk2.i686 0.22-1.el6 @rhel-x86_64-server-6 libcom_err.i686 1.41.12-3.el6 @rhel-x86_64-server-6 libgcc.i686 4.4.4-13.el6 @rhel-x86_64-server-6 libgcrypt.i686 1.4.5-3.el6 @rhel-x86_64-server-6 libgpg-error.i686 1.7-3.el6 @rhel-x86_64-server-6 libjpeg.i686 6b-46.el6 @rhel-x86_64-server-6 libogg.i686 2:1.1.4-2.1.el6 @rhel-x86_64-server-6 libpng.i686 2:1.2.44-1.el6 @rhel-x86_64-server-6 libselinux.i686 2.0.94-2.el6 @rhel-x86_64-server-6 libsndfile.i686 1.0.20-3.el6 @rhel-x86_64-server-6 libstdc++.i686 4.4.4-13.el6 @rhel-x86_64-server-6 libtasn1.i686 2.3-3.el6 @rhel-x86_64-server-6 libtdb.i686 1.2.1-2.el6 @rhel-x86_64-server-6 libthai.i686 0.1.12-3.el6 @rhel-x86_64-server-6 libtiff.i686 3.9.4-1.el6 @rhel-x86_64-server-6 libtool-ltdl.i686 2.2.6-15.5.el6 @rhel-x86_64-server-6 libuuid.i686 2.17.2-6.el6 @rhel-x86_64-server-6 libvorbis.i686 1:1.2.3-4.el6 @rhel-x86_64-server-6 libxcb.i686 1.5-1.el6 @rhel-x86_64-server-6 libxml2.i686 2.7.6-1.el6 @rhel-x86_64-server-6 ncurses-libs.i686 5.7-3.20090208.el6 @rhel-x86_64-server-6 nss-softokn-freebl.i686 3.12.8-1.el6_0 @rhel-x86_64-server-6 pam.i686 1.1.1-4.el6_0.1 @rhel-x86_64-server-6 pango.i686 1.28.1-3.el6_0.3 @rhel-x86_64-server-6 pixman.i686 0.18.4-1.el6_0.1 @rhel-x86_64-server-6 pulseaudio-libs.i686 0.9.21-13.el6 @rhel-x86_64-server-6 readline.i686 6.0-3.el6 @rhel-x86_64-server-6 sqlite.i686 3.6.20-1.el6 @rhel-x86_64-server-6 tcp_wrappers-libs.i686 7.6-56.3.el6 @rhel-x86_64-server-6 xz-libs.i686 4.999.9-0.3.beta.20091007git.el6 @rhel-x86_64-server-6 zlib.i686 1.2.3-25.el6 @rhel-x86_64-server-6

First successful run of IBM Installation Manager

Once the 32-bit packages get installed, you may want to remove installed WAS and start over the installation. You don't have to. It's up to you to move on or start over and I believe both will end up fine. I started it over, i.e. I uninstalled all the installed packages - WAS and IM.

At the end of a successful installation you'll see the popup window:

The next step is to install WebSphere Process Server that will fire up the IBM Installation Manager. That's when you really know IM's happy with the environment and the necessary libraries are available.

It begins with checking out the repositories.

Back to...Installing 32-bit Linux packages Gtk-Message: Failed to load module

When IM runs, it spits the following warnings:

Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

That's a reincarnation of the missing 32-bit Linux packages problem and although it's harmless, it may get annoying.

You have to install additional packages - PackageKit-gtk-module.i686, PackageKit-gtk-module.x86_64, libcanberra-gtk2.x86_64 and libcanberra-gtk2.i686 - to get rid of the messages.

[root@rhel6 ~]# yum install PackageKit-gtk-module.i686 PackageKit-gtk-module.x86_64 libcanberra-gtk2.x86_64 libcanberra-gtk2.i686

Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks"

For getting rid of the warning Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks" you'll need to install gtk2-engines.i686.

[root@rhel6 ~]# yum install gtk2-engines.i686

ulimit -n 8192 or Too many open files

It's worth repeating that while not for the sake of installation itself, but for a proper run of WPS7, you should really set ulimit appropriately. Else you run into the issue with Too many open files:

[2/4/11 19:04:59:459 CET] 0000000e ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource jdbc/com.ibm.ws.sib/qnode.server1-BPC.qcell.Bus. The exception is: java.sql.SQLException: Meta-data for Container org.apache.derby.impl.store.raw.data.RAFContainer4@3d853d85 could not be accessed:java.sql.SQLException: Meta-data for Container org.apache.derby.impl.store.raw.data.RAFContainer4@3d853d85 could not be accessed:java.sql.SQLException: Java exception: '/home/wps/ibm/WebSphere/ProcServer/profiles/qwps/databases/BPEME/seg0/c191.dat (Too many open files): java.io.FileNotFoundException'.:java.io.FileNotFoundException: /home/wps/ibm/WebSphere/ProcServer/profiles/qwps/databases/BPEME/seg0/c191.dat (Too many open files)

Consult .

After the necessary changes, ulimit -a returns as follows.

[wps@rhel6 ~]$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 31558 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 8192 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 1024 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited

The Linux instance is finally ready for further installation steps.

Back to IBM Installation Manager Failure at installing IBM WebSphere Process Server 7.0.0.3 package

After getting rid of the last warnings, you may want to bounce IM or continue where you left out. I did bounce IM.

The IM will show the available up-to-date (while online) packages to install when you click Check for Other Versions, Fixes, and Extensions. You may also be asked to upgrade the IM itself to the latest 1.4.2 version. Do so as did I.

Press Next.

IM will guide you through the installation steps with its panels until you make it to the one about Red Hat Enterprise Linux 6 being not supported.

It's just a warning and unless you're picky, disregard it - press Next.

The installation will eventually stop at Error expanding installation packages due to missing dependencies for WPS 7.0.0.3.

It is because you can't install WPS 7.0.0.3 atop WAS 7.0.0.7 without upgrading to WPS 7.0.0.2 (WAS 7.0.0.7+ exactly) first. It has to be a two-step installation process.

Installing IBM WebSphere Process Server 7.0.0.2 package

You'll have to revert your installation to WPS 7.0.0.2 package. Cancel the current installation (the Cancel button) or use Back button to be presented with the Select packages to install panel.

Click the Check for Other Versions, Fixes, and Extensions button again and click the Show all versions checkbox.

Select the 7.0.0.2 package and its affiliates as depicted in the following screenshot.

Press Next.

Press Next until you're presented with the Review the summary information panel.

Confirm your selection by clicking the Install button.

After a while (it may take a longer while depending on your network connection speed), you should see The packages are installed panel.

Installing IBM WebSphere Process Server 7.0.0.3 package

With WPS 7.0.0.2 installed, you're ready for WPS 7.0.0.3 installation.

Press Next a couple of times until you hit the Validation Results panel.

These results tell you about the interim fixes which were installed during WPS 7.0.0.2 installation. Frankly, you could do nothing about it and they were installed, and you'll have to take steps to uninstall them for WPS 7.0.0.3 with the help of another installation tool - the IBM Update Installer for WebSphere.

Leave the IM where it is - you'll get back to it in a moment.

Installing IBM Update Installer V7.0.0.13 for WebSphere Software for Linux

Visit to download the 64-bit x86 AMD/Intel (tar.gz) package for the 64-bit Linux platform. Install it.

While installing you'll be told about your non-root privileges which is fine for our purposes - we do install the tool as a ordinary, non-root user.

Press Next a few times.

When you see the panel, make sure Launch IBM Update Installer for WebSphere Software on exit is checked and press Finish.

Uninstalling maintenance packages - 7.0.0.7-WS-WAS-LinuxX64-IFPK98944 and 7.0.0.x-SDKPM00452

Select a directory path for your WPS 7.0.0.2 installation.

Press Next.

Select the maintenance package to uninstall.

Press Next and finish the uninstallation.

Restart the IBM Update Installer for the other maintenance package.

Click Next to begin the uninstallation.

Close the tool.

Back to...Installing IBM WebSphere Process Server 7.0.0.3 package

Go back to IM you left before uninstalling the maintenance packages.

Press Recheck Status. It should display All prerequisites are met message.

You're ready to continue with WPS 7.0.0.3 installation.

Press Next.

Right before the final step in the WPS 7.0.0.3 installation (or the update I should say), you'll be presented with a list of features to be updated and/or removed.

Press Update to initiate the update.

After a few quarters you should see The packages are updated panel.

Press Finish.

It really finishes the installation efforts of yours. Congratulations!

Summary System menu for IBM Installation Manager and IBM WebSphere Application Server

The installation adds a menu for the IBM Installation Manager and the IBM WebSphere Application Server.

Installed Packages and Fixes in IBM Installation Manager

Run IM and use File > View Installed Packages to find out about the installed packages and fixes.

WSVR0001I: Server server1 open for e-business

Run the qwps profile with startServer.sh script.

[wps@rhel6 ~]$ cd ibm/WebSphere/ProcServer/profiles/qwps/ [wps@rhel6 qwps]$ ./bin/startServer.sh server1 ADMU0116I: Tool information is being logged in file /home/wps/ibm/WebSphere/ProcServer/profiles/qwps/logs/server1/startServer.log ADMU0128I: Starting tool with the qwps profile ADMU3100I: Reading configuration for server: server1 ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server server1 open for e-business; process id is 2392

Once the startup script for the qwps profile's server1 finishes, it prints out the following message in SystemOut.log:

[2/5/11 0:28:10:112 CET] 00000000 WsServerImpl A WSVR0001I: Server server1 open for e-business

Direct the browser of yours to to open up the Integrated Solutions Console for IBM WebSphere Process Server 7.0.0.3 (and IBM WebSphere Enterprise Service Bus 7.0.0.3, and IBM WebSphere Application Server 7.0.0.13).

I must admit that this is my first time when I successfully installed an IBM product as an ordinary, non-root user. This concludes the installation story.