WebSphere eXtreme Scale Monitoring console embedded in WebSphere Application Server requires an extra security setup step

Technote (troubleshooting)


Problem(Abstract)

The monitoring console is not able to successfully connect to the catalog service domain when running WebSphere eXtreme Scale with WebSphere Application Server and security is enabled.

Diagnosing the problem

A first failure data capture is recorded in the log file:

FFDC Exception:java.lang.NullPointerException SourceId:com.ibm.ISecurityUtilityImpl.StdinLoginPrompt.run
Problem Id:176 java.lang.NullPointerException
at com.ibm.ISecurityUtilityImpl.StdinLoginPrompt.getPassword(StdinLoginPrompt.java:153)
at com.ibm.ISecurityUtilityImpl.StdinLoginPrompt.run(StdinLoginPrompt.java:201)
at java.lang.Thread.run(Thread.java:770)


Resolving the problem

  1. Stop the WebSphere eXtreme Scale monitoring console using the stopConsoleServer command.
  2. Locate the properties/sas.client.properties file from your WebSphere Application Server profile directory. For WebSphere Application Server Network Deployment, this location is WAS_HOME/profiles/Dmgr/properties.
  3. Edit the file by setting these properties: com.ibm.CORBA.loginSource, com.ibm.CORBA.loginUserid, and com.ibm.CORBA.loginPassword
  4. Set loginSource to properties.
  5. Use the WebSphere Application Server administrator user ID and password for the loginUserid and loginPassword properties.
  6. Start the monitoring console using the startConsoleServer command.

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere eXtreme Scale

Software version:

8.6

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows, i5/OS, z/OS

Reference #:

1618653

Modified date:

2012-11-28

Translate my page

Machine Translation

Content navigation