System Configuration Files

Brand Mobiliser Configuration Files

Brand Mobiliser configuration files are located in the BRAND_HOME/conf directory. config.properties and system.properties are required to start the server:

config.properties contains Advanced Interactive Message Server (AIMS) configurations that are based on the Apache Felix implementation. You need not change most of these settings, as they pertain to the Brand Mobiliser platform. You may need to make changes if you apply a patch; follow the step-by-step instructions provided with the patch.
system.properties contains subsystem configurations, such as logging, the Jetty HTTP server, and encryption settings. If you plan to encrypt configuration property values, enable encrypting in system.properties.

Brand Mobiliser Web UI

The user interface for Brand Mobiliser is configured in the service.brand_webapp.properties file.

AIMS System Web Console

During development, use the AIMS System Web console to inspect the OSGi container, deployed bundles, and register configurations. The Web console does not meet production standards, so to prevent unintended deployment to production, it is by default, disabled.

Jetty Servlet Container

The Jetty servlet container hosts Web applications, and is configured in the org.ops4j.pax.web.properties file. As described on the Apache Jakarta Web site, AJP13 is a connector component that communicates with a Web connector via the AJP protocol. AJP13 may be useful if you want to invisibly integrate Tomcat 4 (or Jetty) into an Apache installation, and you want Apache to handle the static content contained in the Web application, or to use Apache SSL processing. In many application environments, using an AJP13 component results in better overall performance than running your applications under Tomcat alone using the HTTP/1.1 connector. For details about the jetty.xml file, see http://www.eclipse.org/jetty/documentation/current/.

Log4j

Logging is controlled by the org.ops4j.pax.logging.properties file; the properties are dynamic and use the log4j configuration format. See http://logging.apache.org/log4j/1.2/manual.html .