deploy/TaskHeapDemo

Generated tools (running local deployment required):

Deployment Configuration Editor (using local config.xml)
Runtime Control Panel
SandUI editor (using local TaskHeapDemoSandUI.xml)
localhost TaskHeap webapp user interface

The TaskHeapDemo deployment consists a web server, a central calculator, and a database, running on separate servers. This demonstrates how an application can be distributed for increased load handling, and how layered firewalls can be integrated into the application for increased security. The greyed out nodes show how a standalone TaskHeap client application could be integrated.

The same deployment can be "collapsed" to run on a single server without recompilation, which is what happens during development. TaskHeap can also alternately be deployed as a single .war file by changing packagers.

Dotted lines are used for asynchronous communications (send/subscribe), solid lines for synchronous (query/receive). See the configuration for message configuration details.

For a smooth startup, nodes are launched from the back-end towards the front-end:

DBMgr goes first so that data integrity is verified before anything else is attempted.
UsersDB is started to allow for AuthUser lookups.
CacheMgr is started so that cache notification will be available.
AuthDB is started to complete the launch of the dbserver nodes.
AuthCalc is the first of the calcserver nodes to start, to allow for communication from the calcserver nodes to the rest of the system at startup.
UsersCalc is started next, since it needs to look up a user for internal comms before being able to support the Authorizer in processing outbound messages.
UpdateMgr goes next so that subsequent updates go through the business logic.
ExtSync is needed for PlanCalculator processing, so it is brought up next.
PlanCalc is brought up, which verifies access to ExtSync and DBMgr. This completes launching of the calcserver nodes.
AuthWeb is the first of the webserver nodes to start, to allow for communication from the webserver nodes to the rest of the system at startup.
UsersWeb is next, to provide for caching of users in support of user authorization processing.
Finally TaskHeapUI is brought up to complete the system.