com.smartgwt.client.docs

Interface Server_properties

public interface Server_properties

server.properties file

The server.properties file is a configuration file read by the Smart GWT server - see the file itself for more information and default or sample settings.

Note that this is a standard Java Properties file, except it allows variable substitution from other properties defined earlier in the file.

It's loaded from the CLASSPATH, so it can be anywhere in the CLASSPATH, but is typically either in the projects java "src" directory or in WEB-INF/classes.

Server side code can access and modify the properties specified in this file via the com.isomorphic.base.Config class.

When modifying server.properties developers should restart the servlet engine after changing this file to pick up changes.

The following settings are used by Smart GWT server features.
Note that this is not intended to be an exhaustive list:

• project.datasources specifies the location for server-backed DataSource configuration files (*.ds.xml files) as well as server-backed SimpleType declarations (*.type.xml files)
• project.ui specifies the location for XML Screen definitions (*.ui.xml files)
• project.project specifies the location for XML Project definitions (*.project.xml files)
• project.apps specifies the location for Application declarations (*.app.xml files)
• modulesDir specifies the location for modules files if using the loadISC or loadModules jsp tags.
• authentication.defaultRequired can be used to require authentication for all dataSources by default
• authentication.superuserRole can be used to identify a user role as the super user role.
• This file can contain DataBase configuration settings for SQL DataSources. Note that the Admin Console tool provides an interface for adding database configuration blocks to server.properties without the need to edit the file by hand.
• This file can contain SQL Connection pooling settings for SQL DataSources.
• This file can contain various configuration properties used for JpaIntegration
• This file can contain SMTP configuration settings for the OperationBinding.mail feature.
• This file can contain configuration settings for the optional RealTimeMessaging module.
• enabledBuiltins can be used to configure access to methods provided by the server side BuiltInRPC class. (See server side JavaDoc for that class as well as the tools deployment overview for more information).
• domainSync.disabled and domainSync.baseDomains can be used to configure domain synching behavior.