The validate-config-values script, known as a validate for short, will check your product configuration for accuracy. Running the validate script is required after any property files are edited before the deploy or update-config scripts can be executed.
This article covers the items that a validate script reviews and how to run the script.
What does the validate-config-values script check?
The follow properties are verified during a validate:
- File separator (UNIX only)
- Leading and trailing spaces
- File descriptors (UNIX only)
- Java version and location
- Unique multicast settings
- Configuration override
- Multicast port prefix
- Multicast address
- JDBC driver
- Database connection and permissions
- Bulk loading
- Existence of super user
- Existence of super user group
- Existence of super user in super user group
- LDAP query time
- WildFly home path
- WildFly encryption salt
- Login for wsadmin utility
- WebSphere topology
- Application server status
- WebSphere application security
- Infogix product license
Running the validate-config-values script
For WebSphere and WildFly deployments, your JVM must be online for the validate script to execute. For JBoss deployments, the JVM must be offline.
- Navigate to the following directory:
- Run the validate script based on the syntax and examples below.
The general syntax of the script is:
validate-config-values.(bat|sh) [-c <JVM Name>] <product ID>
<product ID>is one of the following values:
-c <JVM Name>is the name of your JVM configuration within your installation. This is required if you specified a custom JVM configuration during your initial product installation. If you are using the
defaultconfiguration, then omit this parameter. If you are unsure whether you have a JVM configuration check, review our How to check your JVM configuration name article.
Windows example with Assure via default configuration:
Linux example with Insight and a configuration name of
./validate-config-values.sh -c JVM1 II