axoniq.axonserver.name - unique node name of the Axon Server node is taken from the hostname of the server.
axoniq.axonserver.hostname - hostname of the Axon Server node, as returned to clients, is taken from the hostname of the server.
axoniq.axonserver.port - gRPC port for clients to connect is set to 8124 by default
server.port - HTTP port for REST clients to connect is set to 8024 by default
AxonServer stores all Events and Snapshot Events in segmented files on disk. By default, these files are stored in the ./data directory.
The following settings define an alternative storage location:
axoniq.axonserver.event.storage - path where (regular) events are stored
axoniq.axonserver.snapshot.storage - path where Snapshot Events are stored
By default each Axon Server node will create its own H2 database in a file axonserver-controldb in the data directory. To change this, set the property:
axoniq.axonserver.controldb-path - path to controlDB
Logging is by default set to WARN level for all packages. To change the logging levels for specific packages or classes add logging level properties to the axonserver.properties file, for example:
Log messages are written to stdout by default. To change this add the properties logging.file and/or logging.path to the axonserver.properties file.
# write log entries to file called messaging.loglogging.file=messaging.log# create logfiles in directory /var/loglogging.path=/var/log
Flow control is the process of managing the rate of data transmission between two nodes to prevent a fast sender from overwhelming a slow receiver.
In the messaging platform flow control is possible both between the messaging platform and the message handlers, and between the nodes in the messaging platform cluster.
Messaging platform - message handler:
The client needs to set the following properties to configure flow control:
axon.axonserver.initial-nr-of-permits  - number of messages that the server can initially send to client.
axon.axonserver.nr-of-new-permits  - additional number of messages that the server can send to client.
axon.axonserver.new-permits-threshold  - when client reaches this threshold in remaining messages, it sends a request with additional number of messages to receive.
Axon Server nodes:
Set the following properties to set flow control on the synchronization between nodes in an Axon Server cluster:
axoniq.axonserver.commandFlowControl.initial-nr-of-permits  - number of messages that the master can initially send to replica.
axoniq.axonserver.commandFlowControl.nr-of-new-permits  - additional number of messages that the master can send to replica.
axoniq.axonserver.commandFlowControl.new-permits-threshold  - when replica reaches this threshold in remaining messages, it sends a request with additional number of messages to receive.
axoniq.axonserver.queryFlowControl.initial-nr-of-permits  - number of messages that the master can initially send to replica.
axoniq.axonserver.queryFlowControl.nr-of-new-permits  - additional number of messages that the master can send to replica.
axoniq.axonserver.queryFlowControl.new-permits-threshold  - when replica reaches this threshold in remaining messages, it sends a request with additional number of messages to receive.
Requires private key and public certificate. The same certificate is used to connect to all event store servers.
For gRPC communication add file locations to the
axoniq.axonserver.ssl.cert-chain-file - location of the public certificate file
axoniq.axonserver.ssl.private-key-file - location of the private key file
For HTTPs configuration the certificate and key need to be installed in a p12 keystore. To install the keys use the following command:
$ openssl pkcs12 -export -in [public-cert-file] -inkey [private-key-file] -out [keystore-file] -name [alias]
Configure the Messaging Platform server to use HTTPs by adding the following properties to the axonserver.properties file:
The Axon Server package contains a migration tool to migrate from an already existing RDBMS event store to a new Axon Server instance. The tool reads events and snapshots from the existing store and pushes them to the Axon Server server.
The migration tool maintains the state of its migration, so it can be run multiple times.
Set the following properties to define the existing event store and the target Axon Server server:
axoniq.axonserver.servers - comma separated list of hostnames and ports for the Axon Server cluster.
axoniq.datasource.eventstore.url - url of the JDBC data store containing the existing event store
axoniq.datasource.eventstore.username - username to connect to the JDBC data store containing the existing event store
axoniq.datasource.eventstore.password - password to connect to the JDBC data store containing the existing event store
The default settings expect the data in the current event store to be serialized using the
XstreamSerializer. When the data is serialized using the JacksonSerializer add the following property:
To run the migration tool create a file
application.properties, containing the properties mentioned above, e.g.
Run the command
When the source event store is requiring a specific JDBC driver, you should put the required JDBC driver jar files in the libs directory.
Note that the migration tool only migrates the event store data to Axon Server. It does not update the tracking token values in token_entry tables. Tracking tokens are highly dependent on the implementation of the actual event store used. Migrating them is case specific and error prone. Our recommendation is to reset the tracking processors after the migration.