Deploying State Bundles

To deploy custom-state bundles, make the files available to Brand Mobiliser at runtime, and configure the states to start automatically.

1. Copy the bundle .jar files to BRAND_HOME/bundle/application.

   This directory contains all the bundles that are deployed to the Brand Mobiliser runtime environment.

   Note: Brand Mobiliser system bundles are installed in BRAND_HOME/bundle.
2. Edit the BRAND_HOME/conf/config.properties file to add the new custom-state file to the list of bundles that are started automatically.

   felix.auto.start.15 = ${aims.app.dir}/customState-1.0-SNAPSHOT.jar

   All state bundles are listed in the config.properties file. Brand Mobiliser reinitializes its bundle cache each time it starts.

3. Restart the Brand Mobiliser server.
   To verify that no errors occurred, check these log files:

   • brand.log
   • felix.log
   • spring.log
   • persist.log

   If there are errors, check the Spring configuration and the import/private/dynamic package specifications.

• Verifying Deployment Using Telnet
  Use Telnet to verify that custom-state bundles resolve and start. The Telnet interface listens only on the localhost port, which ensures runtime environment security.
• Verifying Deployment Using the AIMS Web Console
  In a development environment, you can use the AIMS System Web console to verify that custom-state bundles resolve and start. To ensure runtime environment security, the console restricts access, based on a list of allowable IP addresses. By default, only localhost is accessible.