WebSphere configuration problem messages displayed in the administrative console
 Technote (troubleshooting)
 
Problem(Abstract)
At the bottom of the IBM® WebSphere® Application Server administrative console there is a section where potential configuration problems are displayed. This document explains what these messages mean and how to adjust the level of validation.
 
Resolving the problem
In the "WebSphere Status" frame at the bottom of the administrative console is a section entitled "WebSphere Configuration Problems". This displays the number of workspace files and potential problems with the administrative configuration for the current user ID. These administrative configuration messages are check warnings (CHKW) and are displayed when the tool detects something that is different from the templates.
There are different settings for the "Configuration Document Validation":
  • Maximum: Validate all documents

  • High: Validate extracted, parent, and local sibling documents

  • Medium: Validate extracted and parent documents

  • Low: Validate extracted documents

  • None: Do not validate documents

Different messages will appear based on the validation level setting.

Every login will default to the validation setting of "low" unless you change it. To modify the level, select the number beside the "Total Configuration Problems" and then choose the "Configuration Document Validation" radio button setting you want to change for the login preference.

Looking at the "Configuration Problems" and "Scope", you can determine if the message is important or not. The "Scope" will help you determine which xml file the tool detected and the configuration problem that exists.

Examples of less important messages:

CHKW2010E: The configuration repository of an administrative service is absent.

If the application server does not have audit repository updates to the log files enabled, and you add the following directive to the server.xml file:
<configRepository xmi:id="RepositoryService_1"/>
you will see the above error. This directive is only needed if you want that application server to log all audit repository updates. If you do not want this set, you will always see this error in the "WebSphere Configuration Problems".

CHKW2061E: The executable target kind of a Java™ process definition is absent.

CHKW2062E: The executable target of a Java process definition is absent.

If the servers have the Java Virtual Machine (JVM™) flag for executable arguments in the server.xml file (<executableArguments></executableArguments>) but nothing is set, then you will see the above two errors for this server. This is not a problem if you are not using any executable arguments, the tool is just reporting that you have blank flags in the server.xml file.

For more information concerning WebSphere Application Server Configuration Problems, visit the Information Center.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1152735
IBM Group: Software Group
Modified date: Jul 17, 2008