Introduction to the Verj.io Server
Documentation
home
See also: Starting and Stopping the Server, Server File System, Server Configuration
The Verj.io Server is the runtime component of the Verj.io
system. The server is a Java servlet application that can run under any J2EE
application server, and on almost any OS platform including Windows, Linux,
Unix, Mac and others. The system is distributed with the Apache Tomcat
application server and this is recommended for all server instances unless your
installation is already using an alternative application server.
The server is highly scalable and can be clustered to
support high transaction volumes.
What is the server used for?
The server’s main functions are to:
- Run
Forms (web applications)
- Run
published REST web services
- Run
published SOAP web services (these are known as Integration Services)
- Run the
Workflow Engine to execute Workflow Processes
- Run
the background scheduler
When used for testing with the Verj.io Studio the server
provides some more functions:
- Testing
Forms
- Testing
REST web services
- Testing
SOAP web services (Integration Services)
- Testing
Workflow Processes
- Testing
System Services
- Importing
database metadata (table/view layouts etc) to create Resources
- Displaying
the Execution Log (View >
Execution Log from the menu at the top of the studio window)
- Loading
any web resource files in the Form Editor which are sourced from the
server (all web resource files can optionally be configured to be loaded
from the application server)
Server Types
There are two main types of server:
- Embedded Test Server: this server
is distributed with the Verj.io Studio and is the default server type for
use with the studio. It’s a cut down instance of Apache Tomcat and is
fully integrated with the studio. Mostly this server looks after itself
and does not need to be manually started or stopped. It can be managed
using the Manage Server icon in the top right hand corner of the studio
window.
- External Server: all other servers
are “external” meaning that they are distinct processes that can be
started and stopped. This is the only server type that can be used to run
a production system. It can also be used for test systems or in
conjunction with the Verj.io Studio as an alternative to the embedded
server. When used with the studio, both the studio and server components
must be configured to point to the same workspace.
The studio can be
configured to use either server type and this choice is specified using the Test Server
tab of Studio Preferences.