File-based Configuration

Top  Previous  Next

File-based configuration should be used if AggreGate Server fails to start and other configuration methods are not available. The default configuration file is server.xml. An alternative filename can be specified using the  '-f <filename>' command line option.

note_further-wt

It is important to note that AggreGate Server not only loads configuration file at startup, but also saves its settings during shutdown. Manual changes made in the file while AggreGate Server is running will be overwritten.

The configuration file is in XML (eXtensible Markup Language) format. Here is an excerpt:

<config>

 <firstLaunch>false</firstLaunch>

 <previousVersion>31001</previousVersion>

 <locale>ru</locale>

 <deviceServerPort>6450</deviceServerPort>

 <deviceServerSslPort>6455</deviceServerSslPort>

 <usersSelfRegistration>true</usersSelfRegistration>

 <configGuiMode>auto</configGuiMode>

 <netAdminPort>6440</netAdminPort>

 <netAdminEnabled>true</netAdminEnabled>

 <databaseDriver>org.hsqldb.jdbcDriver</databaseDriver>

 <databaseUrl>jdbc:hsqldb:file:db/AggreGate Server</databaseUrl>

 ...

</config>

The file is generated automatically by AggreGate Server, and there's no need to manually add options to it.  When troubleshooting, you might have to change the value of some settings.

You can find detailed description of available settings under Global configuration.