Data Director Implementation Guide

Data Director Implementation Guide

Validation, Application State and Deployment

Validation, Application State and Deployment

The following persisted parameters determine how and whether an IDD application is deployed.
Parameter
Description
valid_ind
Contains the most recent validation status for the application. The validation status is a single value that represents the highest (most severe) error that has been found.
active_ind
Managed directly by the user to reflect the intention for deployment of the application.

Validation

An IDD application configuration is loosely coupled with the metadata in an MDM-RE System. The configuration contains references to objects in an MDM-RE System. Changes to an MDM-RE System (the addition, modification, or removal of Identity Tables, Searches, and so on) are not automatically reflected in the IDD configuration. For this reason, the IDD validation process is necessary and must be repeated periodically.
Validation is run in the following circumstances:
  • when requested by the user in the IDD Configuration Manager
  • when importing an IDD configuration
  • before deploying an application when the application server is started up
The following validation levels are available.
valid_ind
Validation Level
Description
-1
Not Validated
The IDD application has not been validated.
0
No Error
No errors or warnings were found during validation.
1
Information
Provides information to the user. No configuration changes are required.
2
Warning
A configuration might need to be changed, but should cause no run-time problems.
3
Error
A configuration error must be fixed. Run-time problems can be expected.
4
Critical Error
Same as Error, but indicates a problem that requires even more urgent attention.
5
Fatal Error
An error that prevents the IDD application from running at all. The application will not be deployed before the error has been addressed.

Application State

The application state is controlled by the user in the IDD Configuration Manager. It stores the intended deployment for the IDD application.
An IDD application can be deployed even if the configuration contains errors. Only fatal errors (described in the previous section) will prevent an IDD application from being deployed. It can be useful to deploy an IDD application that contains errors when building an application, allowing the implementer to test parts of the configuration while other parts are incomplete.
active_ind
Name
Description
-1
Not Deployed
IDD application is not deployed. Useful when the application is in development. Changes can be made and saved without the additional overhead of deploying the application.
0
Limited Deployment
IDD application is deployed, but the application will not be displayed in the list of available applications. You must access the application using its full URL (
http://<hostname>[:<port>]/bdd?bdd_name=name
).
1
Full Deployment
IDD application is deployed for full use. It is displayed in the list of applications and users can run the application.

Deployment

Deployment is the process of taking an IDD configuration and making it available as an application. An application is not deployed if
active_ind
is
-1
for that application.
Deployment occurs in response to the following events:
Event
Description
Application Server Startup
All IDD applications with
active_ind
that is not -1 are first validated. If the validation level is not Fatal Error, then the IDD application is deployed. At this time, only a partial validation is run to check for fatal errors.
Import / Save
Any time an IDD application is imported or saved, it is also deployed unless its
active_ind
is -1.
Re-deployment
User re-deploys an IDD application.

0 COMMENTS

We’d like to hear from you!