Production Configuration

To create a production configuration of AMPS, you configure the instance to meet the needs of the application (or applications) that will use the instance.

An overview of the most commonly used features is available in the Introduction to AMPS guide. This guide, the AMPS User Guide provides detailed descriptions of those features, including the required and optional configurations for each.

Typically, all instances of AMPS will configure:

• The instance Name (this is required).

• The Admin interface for the instance, to make monitoring available. This typically includes setting a path to persist the instance statistics database.

• Logging for the instance (at a minimum of info level for production instances, typically at trace level for development, testing, or UAT instances).

• One or more Transports to allow incoming connections to the AMPS server.

• Administrative actions to create a scheduled maintenance plan for the statistics database and the logs.

The ampServer binary will produce a minimal sample configuration to stdout if it is run with the --sample-config flag that shows a minimum configuration. Options that require site-specific information (for example, the path to the statistics database or log files) are commented out in the sample.

Instances of AMPS may then add configuration to take advantage of advanced messaging features (such as the State of the World (SOW), Aggregation and Analytics, the ability to Record and Replay Messages, and so on), to add resiliency by Replicating Messages Between Instances (typically required for Highly Available AMPS Installations), and so on.