Validation Results
The FTL server validates the realm configuration. A GUI page reports configuration errors and warnings detected.
Validation
The FTL server configuration interface validates modifications as you make them (that is, at every save and automatic save operation). The FTL server also validates when you deploy.
See Also:
Columns
| Column | Description |
|---|---|
| Severity |
Error,
Warning, or
Info
For more information, see the following section, Severity of Validation Issues. |
| Component | The type of configuration definition which triggered a validation exception.
This value is also a link to the GUI page where you can reconfigure the problematic definition. |
| Name | The name of the problematic definition. |
| Field | The problematic parameter of the definition. |
| Description | A brief description of the issue that triggered the validation exception. |
Severity of Validation Issues
The FTL server detects configuration issues and categorizes them by severity:
- Error The definition is not deployable.
For example, required parameters of a definition are missing, invalid, or undefined, as in an endpoint that lacks a transport.
- Warning The definition is deployable, but inconsistent, and could result in a run-time issue.
For example, a dynamic TCP transport listen end is defined, without a corresponding connect end.
- Info The definition is deployable, but could be misconfigured.
For example, a format definition without any fields, or a persistence store without any static durables nor dynamic durable templates.