Administration Guide
Checking the Status of Liquid Data Resources
This chapter describes the status page of the Liquid Data Administration console. It includes the following sections:
Status Administration Page
If a resource has a known configuration problem, the problem is highlighted on the summary page for each type of resource. You can then click on the status for a particular resource to find details about the problem.
Status Values
When you view the status for a given resource, one row is displayed for each managed server in a cluster. Table 21-1 shows the values for the status and their definitions. If there are any additional errors, those are also displayed in the status table.
Table 21-1 Resource Status Values
Value
|
Definition
|
UNKNOWN
|
The resource status checking has not occurred. The status will be checked the next tome the resource is accessed (for example, when a client request requires the resource or when an administrator refreshes the status on the Liquid Data Administration Console).
|
INVALID
|
The resource has been checked and failed the validation. A message describing the problem is logged and is available in the console status page for the resource.
|
WARNING
|
Indicates that the resource validation encountered some problems for part of the resource. This might indicate that certain functions are available but others are not. A message describing the problem is logged and is available in the console status page for the resource.
|
VALID
|
The validation check for the resource was successful.
|
To Check the Status of a Invalid Resources
The summary page for each resource (for example, the stored query page) includes a column displaying the resource status. If the column has a red icon for a given resource, that indicates a problem for that resource. Click the red icon to see the details for the resource status.
What Determines the Status of a Resource
The status of a resource is validated at server startup and when a configuration is created or modified. Table 21-2 shows the logic used during resource validation to determine the status for different resources.
Table 21-2 Validation logic for resources
Liquid Data Resource
|
Validation Logic
|
Application Views and Web Services
|
Until the resource is accessed the first time, the status is UNKNOWN. After it has been accessed, if no functions are loaded, then it is marked INVALID. If one or more functions are loaded but one or more functions do not load, then the data source status is WARNING. Otherwise, it is VALID.
|
Custom Functions
|
Attempts to load the functions specified in the CFLD file. If no functions are loaded, then it is marked INVALID. If one or more functions are loaded but one or more functions do not load, then the data source status is WARNING. Otherwise, it is VALID.
|
SQL Calls and Relational Databases
|
Connects to the database to get the schema information for the data source. If any errors occur during this process, then the data source is marked INVALID. Otherwise it is VALID.
|
Delimited Files
|
If a schema is specified, check the schema file to see if it is a valid XML schema. If the schema is invalid, the status of the data source is INVALID.
If there is no schema file, check the first row of the delimited file to infer the schema. If there are errors and the schema cannot be inferred, then the status of the data source is INVALID, otherwise it is VALID.
|
Stored Queries, XML Files, and Complex Parameter Types
|
Checks the schema file to see if it is a valid XML schema. If the schema is valid, the status of the data source is VALID, otherwise the status is INVALID.
|
Note: Even if the status of a resource is VALID, it does not guarantee that the resource will be available. There could be problems in the underlying systems or in other parameters that the Liquid Data server does not detect. The system is designed to highlight problems that the server is aware of, not to exhaustively check for problems.