Introduction to Using the Ebase Xi Server

The Ebase Xi Server is the runtime component of the Ebase Xi 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
Run Integration Services (in response to web service calls)
Run the Workflow Engine to execute Workflow Processes
Run the background scheduler

The server provides additional functionality when used in conjunction with the Ebase Xi Designer:

Testing Forms
Testing Integration Services
Testing Workflow Processes
Testing System Services
Importing resources using Database Connections
Displaying the Execution Log (View > Execution Log from the menu at the top of the designer 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)

Designer/Server configuration options?

There are two main options and this choice is configured in Designer Preferences:

Use the Integrated Local Test Server: this is the default and the system is distributed with this option enabled. The Integrated Local Test Server is a cut down instance of Apache Tomcat which is fully integrated with the designer and does not need to be manually started or stopped.

Use an External Server: with this option you connect to a full instance of an application server. Use this option when you are connecting a designer to an existing production or other standalone system. Both the designer and the server must be configured to use the same workspace.

Server Configuration

Most server configuration is performed using the Server Administration Application. Most of the configuration options are saved in files in the ebaseConf folder within each web application on the server.