Developing Custom Application States

Custom state development using the State SDK is a Java development task you can perform with or without a development IDE, such as Eclipse or NetBeans. After you develop and deploy custom states, you can use them to develop applications.

Before proceeding with custom state development, verify that:

The development environment meets system requirements in the Brand Mobiliser Release Bulletin.
Brand Mobiliser is installed on the development machine. Brand Mobiliser is required to access State SDK bundles for custom state development, and to deploy and test custom states through the development process.

Third-party software mechanisms that custom states can use include:

Spring Framework – for application context and dependency injection.
Spring Dynamic Modules (Spring DM) – for abstracting OSGi mechanisms.
OSGi Services – for software-service publication and consumption.
OSGi Configuration Admin – for container-based configuration of services and components.

Application Life Cycle
Applications run in the Brand Mobiliser Processing Engine (processing engine) runtime container and are managed by the processing engine. Once deployed to the runtime container, applications can be invoked by either incoming messages or events. Events can be generated by the system, a scheduled time, or a call from an external Web service.
Developing and Deploying Custom States
Develop and deploy custom states to extend the functionality of Brand Mobiliser, and to meet client-specific requirements.
Custom State Samples
Custom state samples illustrate how to implement a service state, a standalone state, and a menu state.
State SDK Core Components
You can use State SDK core components when developing custom states. Each component is an OSGi bundle. These components are deployed with Brand Mobiliser, so you need not redeploy them with custom-state components.