Starting eXtreme Scale Console server on 64-bit platforms

One of the new features available in version 7.1 of WebSphere eXtreme Scale is its new Console Server.

Make no mistake about new features in WebSphere product family. It's very reliable ... (once you manage to enable it). A screenshot below illustrates what you can get from the console.

XS Console - Grid Overview

The problem is starting console is not as straightforward on many 64-bit platforms.

Below is an excerpt of the output you will get when you run startConsole on 64-bit AIX machine.

wxs@wxshost01:/usr/IBM/WebSphere/eXtremeScale/ObjectGrid/bin> ./startConsoleServer.sh

[error]The WebSphere eXtreme Scale console server is only supported with 32-bit Java Runtime Environments (JRE). Set the JAVA_HOME environmental variable prior to starting the console server to reference a supported  32-bit JRE, or install the 32-bit version of WebSphere eXtreme Scale.

wxs@wxshost01:/usr/IBM/WebSphere/eXtremeScale/ObjectGrid/bin>

Out-of-the-box, WebSphere eXtreme Scale (WXS) ships 64-bit JRE on AIX. Unfortunately, the startConsoleServer.sh script also relies on this JVM. This clearly is a defect. Fortunately, the workaround is simple. Switch to another 32-bit JVM.
Switching the JVM is a piece-of-cake. Updating JAVA_HOME (located in the script itself) should solve the problem. Unfortunately, it is not. You are likely to get CWPZC0011E with UnsatisfiedLinkError being thrown.

wxs@wxshost01:/usr/IBM/WebSphere/eXtremeScale/ObjectGrid/bin> ./startConsoleServer.sh

CWPZC0011E: An unhandled error was caught; message: java.lang.UnsatisfiedLinkError: ZeroProcessManagement (A file or directory in the path name does not exist.)

wxs@wxshost01:/usr/IBM/WebSphere/eXtremeScale/ObjectGrid/bin>

The secret is you need to clear the cache that the underlying project zero engine resolves for the native path first. Just remove $OBJECTGRID_HOME/console/.zero/private/resolved.properties. Then, you should be able to successfully start the XS Console Server.

wxs@wxshost01:/usr/IBM/WebSphere/eXtremeScale/ObjectGrid/bin> ./startConsoleServer.sh

CWPZT0600I: Command resolve was successful
[info]Creating new XS database using schema version: 1.0.0.2
[info]Parsing file ./sql/derby/create-1.0.0.2.sql...
[info]Finished executing file ./sql/derby/create-1.0.0.2.sql.
[info]Creating acl tables
[info]Parsing file /usr/IBM/WebSphere/eXtremeScale/ObjectGrid/console/private/expanded/ibm/rainmaker.acl-1.0.0.2/sql/derby/create-1.0.0.0.sql...
[info]Finished executing file /usr/IBM/WebSphere/eXtremeScale/ObjectGrid/console/private/expanded/ibm/rainmaker.acl-1.0.0.2/sql/derby/create-1.0.0.0.sql.
removing cache for user because of an event user-role-added
CWZCO1005I: SMTP server has not been configured - email to  will not be sent.
removing cache for user because of an event user-role-added
removing cache for user because of an event user-role-added
removing cache for user because of an event user-role-added
removing cache for user because of an event user-role-added
Application started and servicing requests at http://localhost:7080/ https://localhost:7443/
CWPZT0600I: Command start was successful

wxs@wxshost01:/usr/IBM/WebSphere/eXtremeScale/ObjectGrid/bin>

The rest is enjoying your grid visibility from the browser. :-)

Acknowledgement: many thanks to the following engineers from IBM support center for the solution.

• Abraham Sweiss
• Kawsar Kamal
• Michael J. Smith

The solution is now published as a technote swg21502255.