Photo of the cover of WebSphere Application Server Administration Using Jython

Official companion web site

Configuration Validation (Part 1)
Most recently modified on 2011-09-25
This article supplements the following sections of our book:
Chapter 8: The AdminConfig Object
Configuration Verification/Validation
page 162 and 163
You can buy our book from
Back to home pageBack to table of contents pageBack to interesting articles page

It is convenient to think of WAS configuration as a giant DOM tree. The main trunk of that tree is IBM proprietary and very thin. The major sections of that DOM tree show up as XML files in the configuration repository. Many of those XML files have schemas. Thus, there is a grammar that can be used to decide if the configuration entries are grammatically correct.

Validation options:

getValidationLevel setValidationLevel

Defualt value is HIGHEST. Probably should not be changed.
getCrossDocumentValidationEnabled setCrossDocumentValidationEnabled

Default value is true. Probably should not be changed.
getValidationOutput setValidationOutput

Can be set to any fully qualified file name as long as WAS has permission to write there.

With the possible exception of the name of the file that holds the validation results, you will probably never change these settings. You can also change these settings by editing wsadmin.properties

See also these related articles:
AdminConfig SyntaxThe WAS Configuration TreeConfiguration TypesConfiguration IDsShow and Tell (Part 1)Show and Tell (Part 2)Show and Tell (Part 3)Preserving ChangesModifyCreateConfiguration Validation (Part 1)Configuration Validation (Part 2)Almost Never Used Commands (Part 1)Almost Never Used Commands (Part 2)
Click here to schedule a speaker at your locationClick here to inquire about consulting for your companyClick here to inquire about training for your company.