Ebase Xi Property file UFSSetup.properties
This page documents the properties stored in file UFSSetup.properties in folder web application root/Web-inf/classes. This file contains properties for the Ebase Xi Server that should be rarely be changed. To implement changes, stop and restart the Ebase Xi server.
Almost all server properties are
saved in other files in the ebaseConf folder
of each web application, and are configured using the Server Administration Application.
The name of
the datasource in the J2EE application server for the
Ebase repository database. The default is UFSREPOSITORY.
The JDBC driver for the Ebase
repository database if JDBC connection pooling is not used (parameter Ufs.useConnectionPooling=false). Examples:
Ufs.dbDriver=org.gjt.mm.mysql.Driver
Ufs.dbDriver=oracle.jdbc.driver.OracleDriver
The password for the Ebase
repository database (parameter Ufs.useConnectionPooling=false).
The database URL for the Ebase repository
database if JDBC connection pooling is not used (parameter Ufs.useConnectionPooling=false).
Examples:
Ufs.dbURL= jdbc:mysql://localhost/ufs?autoReconnect=true
Ufs.dbURL= jdbc:oracle:thin:@ebt009:1521:ORCL
The User ID for the Ebase
repository database (parameter Ufs.useConnectionPooling=false).
The prefix to
insert before the datasource name when performing a
lookup using the naming service. This parameter is only required if the application
server uses a non-standard naming convention. (See How Ebase Accesses Database for
more information)
The prefix to
insert before the datasource name when performing a
lookup using the naming service. This parameter is only required if the
application server uses a non-standard naming convention. (See How Ebase Accesses Database for
more information)
The name used to look up a JTA UserTransaction from the application server’s naming service. The default is "java:comp/UserTransaction". This parameter is only required if the application server uses a non-standard naming convention.
Specifies
whether or not to use JDBC2 connection pooling. This should be set to true in all but exceptional circumstances.
This parameter acts as the master switch to initiate
an automatic upgrade between Ebase versions. Set to true
to initiate the upgrade. Otherwise set to false.