Get desktop application:
View/edit binary Protocol Buffers messages
Service describing operations for connecting to the AxonServer platform. Clients are expected to use this service on any of the Platform's Admin nodes to obtain connection information of the node that it should set up the actual connection with. On that second node, the clients should open an instruction stream (see OpenStream), so that AxonServer and the client application can exchange information and instructions.
Obtains connection information for the Server that a Client should use for its connections.
Message containing connection information of the node to Connect with
The connection details of the node the client should connect with
Flag indicating that the connection may be reused to connect. When true, the client _may_ reuse the connection established for the GetPlatformServer request for subsequent requests.
Opens an instruction stream to the Platform, allowing AxonServer to provide management instructions to the application
An instruction from Application Node to the AxonServer platform
The actual instruction to send
Information about the client being connected. This information is used by AxonServer to monitor the topology of connected applications.
Information about Processors defined in the application. This information is used by Axon Server to monitor the progress of Event Processors across instances.
This heartbeat is used by AxonServer in order to check if the connection is still alive
Acknowledgement of previously sent instruction via outbound stream
The result of the execution of an instruction
Subscribe to topology changes in the AxonServer cluster. This allows the client to receive updates about changes in the cluster, such as handler additions or removals.
Unsubscribe from topology changes in the AxonServer cluster.
Instruction identifier. If this identifier is set, this instruction will be acknowledged via outbound stream
An instruction or information from the AxonServer Platform to the Application Node
The actual instruction or information
Information provided by AxonServer which provides information about the AxonServer node the application is connected with
A request from AxonServer to the Application to migrate its connection to another node. Clients SHOULD honor this request by closing their current connection, and using the GetPlatformServer RPC to request a new destination.
Instruction from AxonServer to Pause a Streaming Event Processor.
Instruction from AxonServer to Start a Streaming Event Processor.
Instruction from AxonServer to Release a specific segment in a Streaming Event Processor
A request from AxonServer for status information of a specific Streaming Event Processor
Instruction to split a Segment in a Streaming Event Processor
Instruction to merge two Segments in a Streaming Event Processor
This heartbeat is used by AxonFramework in order to check if the connection is still alive
Acknowledgement of previously sent instruction via inbound stream
Notification of a change in the topology of the AxonServer cluster. This is used to inform clients about changes in the cluster, such as handler additions or removals.
Instruction identifier. If this identifier is set, this instruction will be acknowledged via inbound stream
Message containing details about the Client Application
Used as request type in: PlatformService.GetPlatformServer
Used as field type in:
A unique identifier for this client instance. Is used to distinguish different instances of the same component
The name of the component. Several instances of the same component should share this name
Any tags associated with the client, which may provide hints and preferences for setting up connections
Axon framework version used by the client application instance
Used in:
The subscription ID to add or remove
The load factor for the subscription
Message containing information about the status of an Event Processor
Used in: ,
The logical name of this processor.
The mode in which this processor is reading Events, for example: 'Tracking' or 'Subscribing'
The number of threads currently actively processing Events
Flag indicating whether the processor is running
Flag indicating whether the processor, when stopped, did so because of an irrecoverable Error
Status details of each of the Segments for which Events are being processed. This is only provided by Streaming Event Processors.
The number of threads the processor has available to assign to Segments. Will report 0 if all threads are assigned a Segment.
The Token Store Identifier if available. This is only provided by Streaming Event Processors.
Flag indicating whether the processor is a Streaming Event Processor. This dictates whether streaming operations, like split and merge, are supported by this processor.
current load balancing strategy name for the event processor
Message containing information about the status of a Segment of a Streaming Event Processor
Used in:
The ID of the Segment for which the status is reported
Indicates whether the Segment has "Caught Up" with the Head of the Event Stream
Indicates whether the Segment is "Replaying" historic events after a Reset.
The fraction this segment processes. A fraction of 2 means 1/2, 4 means 1/4, etc.
The approximate position of the token in the stream.
Information about the error state of the Segment, if applicable.
Message providing reference to an Event Processor
Used in:
The name of the Event Processor
Message providing reference to a Segment of an Event Processor
Used in:
The name of the Event Processor
The identifier of the Segment
Used in: ,
(message has no fields)
Message containing connection information for an AxonServer Node
Used in: ,
The host name to use when connecting to this node
The port number for gRPC connections
The port number for HTTP connections
The version identifier of the API
The unique name of the node to connect with, for purpose of debugging
Used in:
The subscription ID to add or remove
Message send when AxonServer requests the client to re-establish its connection with the Platform
Used in:
(message has no fields)
Message to subscribe to topology changes within the control channel's context
Used in:
(message has no fields)
Used in:
The client ID of the component requesting the update
The client ID of the component requesting the update
The name of the component requesting the update
The subscription ID to add or remove
The processor name to add or remove
Message to unsubscribe from topology changes within the control channel's context
Used in:
(message has no fields)
Used in:
a new command handler has been added
a command handler has been removed
a new query handler has been added
a query handler has been removed
reset all information in the client, new information will be sent