Process of validating a will
The business layer stores configuration data in the Config schema, and working data and results in the Results schema.When passing data to and from the client application, the business layer behaves in a manner common to most traditional Java Web Applications.The business layer makes small database transactions and sends small volumes of information to the front-end using the HTTP connection.This is somewhat unusual in that the application front-ends are mostly rich GUIs rather than browsers.Since it is an extensible system, it can be extended to add further user applications when installed to work for a particular use case.For example, Oracle Watchlist Screening extends to add a user application for screening data against watchlists.Note: Many of the client applications are available either separately (for dedicated use) or within another application.For example, the Configuration Analysis, Match Review and Issue Manager applications are also available in Director.
These directories are created when you install EDQ.
EDQ provides integrated data quality in customer relationship management and other applications.
Following are the key features of EDQ: EDQ is a Java Web Application that uses a Java Servlet Engine, a Java Web Start graphical user interface, and a Structured Query Language (SQL) relational database management system (RDBMS) system for data storage. It is comprised of several client applications that are Graphical User Interfaces (GUIs), a data repository, and a business layer.
Note: Each EDQ server must have its own Config and Results schemas.
If multiple servers are deployed in a High Availability architecture, then the configuration cannot be shared by pointing both servers to the same schemas.