Message Types
This tag defines the message types supported by the AMPS instance. A single AMPS instance can support multiple message types.
For more information on AMPS message types, see the Message Types section in the AMPS User Guide.
MessageType
definitions for fix
, nvfix
, xml
, json
, bflat
, msgpack
, bson
, and binary
are automatically loaded by AMPS. You only need to define a new MessageType
for these types if the settings for the message type need to be changed (for example, to create a custom FIX-based type that changes the FieldSeparator
of the message).
The MessageTypes
tag can contain multiple MessageType
definitions. To add more than one message type to the message types that are loaded by default, include multiple MessageType
tags.
AMPS loads the capability to use Google protocol buffer (protobuf
) messages by default. To use protocol buffer messages, you configure one or more message types that use the protobuf
module and load the .proto
files that define the format of the messages you will be processing with AMPS.
AMPS also supports the ability to create a composite message type by combining a number of existing message types. Composite message types are defined using the MessageType
configuration element.
Name | Description |
| This element defines the name for the message type. The name is used to specify By default, AMPS loads message types for |
| The element specifies the name of the module that will be loaded for this message type. By default, AMPS loads the modules that implement the following message types: AMPS supports creating composite message types out of existing message types using the composite-global and composite-local modules, which are loaded by default. |
| Sets the version compatibility for FIX messages that AMPS sends to the /AMPS/SOWStats topic. AMPS accepts three values for this option:
Default:
For message types other than FIX, there is no difference between For most cases, you can leave this option set to the default. If you are using a system that requires consistent FIX tags across messages, set this parameter to |
| Options to pass to a custom message type module. AMPS does not specify the format or type of the elements within an Options element. AMPS simply parses the XML and then sends the XML to the module. If you are configuring a custom message type, see the documentation for that message type module for details. |
| Option: Applies to Sequence of characters used to separate field items in a FIX message. Note: this field is the ASCII value of the char sequence. |
| Option: Applies to Sequence of characters used to separate the header from the body in a FIX message. Note: this field is the ASCII value of the char sequence. |
| Option: Applies to Sequence of characters used to separate message items in the body in a FIX message. Note: this field is the ASCII value of the char sequence. |
| Option: Applies to the By default, AMPS includes an optimization to allow the server to only partially parse JSON messages. This may result in unexpected behavior for some messages. For example, given a message such as When set to Default: |
| Applies to message types that use the protobuf module. The name of the type within the .proto file to use for this message type. The name must be package-qualified (for example, my.package. Message would load the type Message within the package my.package). Obsolete usage - A previous meaning of this element was made obsolete in AMPS 4.0 and later versions. That usage was replaced by the Module directive. |
| Applies to message types that use the For composite message types, the See the AMPS User Guide section on Composite Messages for more information. |
ProtoPath (required) | Applies to message types that use the The path in which to search for The A configuration may omit the alias, and simply provide the path. For example, to use the path or The following AMPS uses the aliases provided in this configuration item when processing import statements within the loaded will load for the file at will load the file at If no Unless your existing definitions use an aliasing scheme, it is most convenient to set the empty alias. You may specify any number of |
| Applies to message types that use Google protocol buffers. The name of the |
For example, message types could be described as follows:
Last updated