Download Exsys CORVID System Requirements

yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Clusterpoint wikipedia , lookup

Semantic Web wikipedia , lookup

Versant Object Database wikipedia , lookup

Web analytics wikipedia , lookup

Java ConcurrentMap wikipedia , lookup

Runtime verification wikipedia , lookup

Exsys CORVID System Requirements
Development System Requirements:
Microsoft Windows Vista, XP, 2000, 2003
Microsoft Internet Explorer ver. 5 or higher
150 MB Free Disk Space
Minimum Screen Resolution: 1024 x 768 with standard fonts or 1156 x 864 with large fonts
Development Server Requirements:
For CORVID Applet Runtime, any machine and operating system capable of serving HTML
pages. (Applet tags are part of the system page and the applet JAR file is served without
server-side processing)
For CORVID Servlet Runtime, any machine and operating system that supports Java Servlets
with a Servlet engine such as Tomcat or equivalent. Also, the ability to serve standard HTML
pages for images and links referenced in the system using standard URLs.
End User Requirements:
For CORVID Applet Runtime, any machine and operating system with a Browser that supports
Java applets (requires only Java JVM 1.1)
For CORVID Servlet Runtime, any machine and operating system with a Browser that supports
HTML forms
For standalone delivery, any machine and operating system with a Java JVM 1.1 or higher
Exsys CORVID Development Environment
Exsys CORVID is designed to enable domain experts to quickly and easily develop decision support
systems using everyday language without having to learn complex, arcane programming syntax.
Developed applications can be delivered via the Web using the Exsys CORVID Servlet and Applet
Runtimes or run as a standalone Java application.
CORVID Servlet Runtime
The CORVID Servlet is a Java program that is run via a servlet engine such as Tomcat on the server.
With the CORVID Servlet Runtime, all processing is done on the server with only dynamically built
HTML pages sent to the client machine. The servlet engine automatically handles multiple users.
When the servlet engine needs to communicate with the user to ask a question or display results, it
builds a customized HTML page using a template file that is part of the system, combined with
session specific data and variables. This page is sent to the user's browser as an HTML form.
Since the CORVID servlet engine is already running, starting a new session is very quick and the user
does not have to wait for an applet and knowledge base to download. In addition, the full power of
HTML (and any extensions supported by the browser such as XML, JavaScript, etc) can be used to
design the user interface screens. This allows for far more complex and sophisticated interfaces to
be built than can be done using the CORVID applet approach. The exact look-and-feel of a Web site
can be matched, and the expert systems can be transparently integrated into Web sites. Since the
servlet is running on the server, there is both increased security for the system and easier
interfacing to other server programs. For example, in the applet version, obtaining information from
a database requires a separate call back to the server, with appropriate security to obtain the data,
which is then sent back to the applet. In the servlet version, the CORVID Servlet Runtime can simply
access the database directly.
CORVID Applet Runtime
When delivered with the CORVID applet runtime, a system is run using a Java applet that is part of a
Web page. All knowledge base files, and the applet to run them, are simply served to the client
machine. All the processing is done on the client machine, with no additional load on the server.
Fielding systems can be done from any Web server. In addition, systems can be run locally simply by
opening the associated HTML page in a browser.
Standalone Application Delivery
Systems can also be fielded as Java applications. This is not a Web based delivery, but allows the
program to be integrated into non-Web architectures. This is also especially effective for background
processing of data streams and those situations that call for running the expert system in a non-Web
Exsys CORVID can generate reports in many ways depending on the requirements of the system. The
reports can be generated and displayed:
In the CORVID Applet Runtime window. Such reports can be formatted with CORVID screen
commands to add formatting, images and HTML links.
In a separate browser window, displayed by the CORVID Applet Runtime. This requires
calling a server-side program to dynamically build a report page that can be displayed in a
browser window. The report can be in HTML, text, RTF, PDF or any other format supported
by the browser. The server-side program that is called is provided as a servlet, CGI
program, and PERL script, depending on system configuration and preference, though the
servlet approach is the recommended option.
Using the CORVID Servlet Runtime, reports can be created and displayed using only the
Servlet Runtime program. The report can be in HTML, text, RTF, PDF or any other format
supported by the browser. The reports can be displayed in the normal sequence of pages in
a system, or from a link to optionally display the report if the user chooses.
The CORVID Servlet Runtime can also generate reports that are automatically emailed to the
user, or others. These reports can be in any format supported by the email reader (typically
HTML, RTF or text).
In standalone mode, files can be directly written to the local machine. This allows report
files to be created and then opened by calling a local program. This can be done using
HTML, text, RTF or PDF formats and calling the appropriate local program (browser, MS
Word, Acrobat, etc)
Calling Databases
Databases can be directly accessed from both the Servlet and Applet runtimes using the functions
provided with CORVID. Any ODBC or JDBC complaint database can be used, with the interface via
standard SQL commands. Database security is provided by having CORVID only be able to access
specific commands stored on the server. The command list and associated parameters is created in
the CORVID development environment. The database interface can be used to obtain data needed
by the system, store intermediate or final results, or provide text strings used within the system
when the same system must run in more than 5 languages.
Interfacing with Other Programs
There are also ways to call other programs. Any executable program on the same server can be
directly called, with parameters passed on the command line. Any program that can be called via a
URL can be called using GET or POST to send data. This allows any other Servlet, CGI program, PERL
script, among many others, to be called. This opens up a wide range of interface possibilities.
Custom Functions
The Exsys CORVID Runtime supports an option allowing the developer to add custom commands and
functionality to the underlying inference engine. This is a very rarely needed option, but it is
available should some very special interface or function be required. Such functionality is
implemented by creating a custom Java class that implements the functionality and using it to
replace the default class provided with CORVID.
Building and adding the class requires knowledge of Java programming and a Java development
environment. However, once the functionality has been added it can be called and used by system
developers with no Java knowledge. The custom class can access and write system data through a
set of Java API commands that can be called from within the custom class.
For additional information contact:
EXSYS Inc, 2155 Louisiana Blvd. NE, Suite 3100, Albuquerque, NM 87110 U.S.A.
Email: [email protected]
Tel: +1.505.888.9494 Fax: +1.505.888.9509