Skip to content

Latest commit

 

History

History
 
 

sag-apama-correlator

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 

Apama Correlator

The current template provisions an Apama installation, creates an Apama correlator instance and deploys a simple Apama application.

This template demonstrates in detail all possible Apama correlator configurations that can be applied using a product template. Use this template as a reference when provisioning Apama correlator instances.

Requirements

Supported Software AG releases

  • Apama 10.2 and higher
  • Command Central 10.4
  • Command Central 10.2 and 10.3 with limitations When applying the template and Digital Event Service is not configured, it reports status UNKNOWN which causes template job to time out.

Supported platforms

All supported Windows and UNIX platforms.

Supported use cases

  • Provisioning new environments of version 10.2 and higher
  • Installing latest fixes
  • Creating an Apama correlator instance and deploying a simple EPL application to it
  • Configuration of:
    • License
    • Ports
    • Logging
    • Persistence
    • All other supported correlator configuration items

Running as a composite template

When importing the composite template to Command Central, you will have to attach the simple 'HelloWorld' application. Add the template.yaml and HelloWorld.zip into a single zip file and import that file using the Command Central CLI with the following command:

sagcc exec templates composite import -i template.zip

For more information about applying templates, see Applying template using Command Central CLI.

To provision a default instance of an Apama 10.2 correlator with all the latest fixes, listening on port 15904:

sagcc exec templates composite apply sag-apama-correlator nodes=sag1 \
  repo.product=products-10.2 \
  repo.fix=fixes-10.2 \
  os.platform=LNXAMD64 \
  --sync-job --wait 360

Adding as a runtime layer to a stack

Once imported, this template can also be used as a runtime layer for stacks, using either the Command Central CLI, or the Command Central web user interface.

For more information about using stacks and layers, see Creating a stack using Command Central Web UI.