Overview of deploying and managing query applications
Typically, query application deployments script the start up and management of all Apama query application components outside of the Apama's development environment in Software AG Designer. Apama recommends the use of the Ant export facility of Software AG Designer to aid in this.
Queries can also be run from Software AG Designer. However, Software AG Designer can run only a single correlator deployment. Use Apama macros for Ant to deploy multiple correlator deployments.
Queries can be deployed on a single node, but typically would be deployed across multiple nodes, forming a cluster. While involving more components, a cluster provides:
Scale out across multiple hosts
Resiliency against failures
Continued availability if some nodes fail
Using a cluster will involve the following:
Some number of correlators that are executing queries
A BigMemory distributed cache for storing event history
A JMS bus for distributing events to correlators
There are likely to also be adapters or a message bus to deliver events generated by queries, and possibly adapters connected to each correlator. See
Deploying and Configuring Adapters.
Queries use the store name "ApamaQueriesStore". If you want to use BigMemory, you need to configure the BigMemory driver to use that as the store name, else an in-process only memory store will be used. See
Configuring BigMemory driver.