This page last changed on Feb 26, 2006 by vmassol.

Explanation

A Configuration specifies how the container is configured (logging, security, data sources, location where to put deployables, etc).

Configuration != Installation

The notion of Configuration is different from the notion of Installation. When you install a container, it is usually configured by default too to start and deploy files from where it is installed. However all containers support customizing the configuration and even possibly use a different location where the configuration resides.


(view as slideshow)
   
  Configuration inheritance tree
 


There are 2 main types of Configurations:

Configuration features

  • Configuration propertiesProperties to configure a container (request port, shutdown port, logging level, threads, etc)
  • Local ConfigurationA configuration for a container that is running on the local machine where Cargo is executing
  • Runtime ConfigurationA configuration for a container that is already started

Custom configuration

The Cargo Java API allows you to plug your own custom configuration implementation. You can register your configuration against the DefaultConfigurationFactory class. It's optional and only required if you want to let users use the DefaultConfigurationFactory class to instantiate your configuration. For example you could write:

ConfigurationFactory factory = new DefaultConfigurationFactory();
factory.registerConfiguration("containerIdOfAssociatedContainer", ConfigurationType.STANDALONE, MyCustomConfiguration.class);

If you're using a Cargo extension then refer to the extension documentation to check if it supports custom configurations.


Document generated by Confluence on Mar 22, 2006 15:28