Overview of the Resin configuration: resin.properties for most common properties and resin.xml for full customization.

Most common Resin properties are configured by resin.properties. The resin.properties variables are used by the main resin.xml configuration file.

Full Resin customization is configured by the resin.xml. The resin.xml overview describes resources, clustering, HTTP hosts and URL dispatching, and custom CanDI configuration.

Resin's configuration uses a powerful, general dependency injection system (CanDI) to configure servlets, Resin resources, databases, application components, third-party libraries and drivers. By understanding a few rules matching the XML to the configured resources, an administrator can have full control over the application server behavior.

Because of the importance of verifying and debugging configuration, Resin's configuration is stateless, meaning that the XML files fully describe the configuration of the system. Resin avoids hidden state by avoiding deployment tools and internal, hidden database configuration.

Resin configuration can directly access Resin-IoC/WebBeans-configured beans and variables using EL expressions in the configuration files. Predefined variables include webApp, host, and resin variables.

Resin will keep its operational data in a directory named resin-data. By default directory resin-data is located under Resin Root.

All data in resin-data directory is managed internally by Resin.

For each server in cluster Resin creates a dedicated directory where operational data for that server is stored: e.g.resin-data/app-0, resin-data/app-1

Operational data for an individual server include two important directories:

A directory for deployed applications named .git
A directory for sessions and distributed cache named distcache

Deleting .git directory will result in all deployed applications be deleted from the server.

Deleting directory distcache will result in session data being deleted.