Running Ebase Xi Out of the Box
Starting
the Ebase Xi Designer
Running
the server as a service under Windows
Apache
Derby JDBC Configuration
Using
external tools to view/modify the Ebase Xi database
See also: Ebase Security, Introduction to the Ebase Designer
This document describes how to start
and stop the Ebase Xi Server and Designer components. The Ebase Xi root
installation directory is referred to as EBASE_HOME throughout this document
The Ebase Xi Server can be started from Windows Explorer
follows:
The Ebase Xi Server can be started from the command line as
follows:
The Ebase Xi Designer can be started from Windows Explorer
follows:
The Ebase Xi Designer can be started from the command line
as follows:
In both cases, the start_ebase_designer
script will launch the Ebase Designer
client. You will first be presented with the login screen. Please consult your
system administrator to find out what your username and password is.
When using Ebase Xi for the first time, the basic
installation is provided with a default user:
(Note that for systems upgraded from a release prior to V3.4.0, this will be ufsuser/ufsuser.)
It is strongly recommended to remove this user or change the
password once you have entered the system. (See Ebase
Security for more information)
If you have trouble starting the Ebase Server, make sure
there are no instances of Tomcat already running. In addition, the
supplied system uses port 3030 for web connections. Make sure you do not have
any other applications already using this port.
Ebase can be stopped from Windows Explorer as follows.
Ebase can be stopped from the command line as follows.
In both cases, the stop_ebase_server
script will cleanly shutdown the Ebase Server.
It is recommended always to shutdown the server in this way.
Note: The server may be restarted without restarting the
Ebase Designer and vice versa.
This information is available as a technical note. Please
contact Ebase Technology support.
Ebase maintains a log of information about all forms which
have been run. This is useful for troubleshooting.
The Ebase Server will by default log
to the system console and the file
EBASE_HOME/UfsServer/Tomcat/logs/ufsserver.log. Logging to a file can be
configured in the UFSSetup.properties
file by setting the following properties:
Designer logs
Logs for forms executed via the designer can be viewed
through Ebase Designer's view menu (View --> Execution log)
Note: The Ebase Designer execution log is cleared
each time the server is restarted. The log can also be cleared manually using
the Clear button on the execution log window.
Ebase is shipped with Apache Derby database. This database
is an embedded database and starts up when the Ebase Xi Server is started. It
is a fully relational database implemented in 100% Java. For more information
about derby see http://db.apache.org/derby/
Apache Derby is the default database when running Ebase Xi
out of the box. There is no additional configuration required when starting
Ebase Xi for the first time.
The physical database is stored in the following directory –
<ebase-install-directory>/UFSServer/DB/UFS
The JDBC Connection URL should be configured as follows:
jdbc:derby:UFS;create=false
The UFS part of the JDBC URL can be changed to an absolute
location of a database e.g
jdbc:derby:c:/mydatabase/UFS;create=false
To create the database if it does not exist (useful for
creating your own database separate from Ebase Xi), substitute the create=false with create=true
There are several client tools that you can use to
view/modify the Ebase Xi data or configure a new database.
Note: you cannot connect to the database while the Ebase Xi Server is
running as only one client can attach to the database at any one time in
embedded mode.