Configure Orchestrate Transaction Sender
Follow these steps to configure and connect to Orchestrate Transaction Sender dependencies:
- Configure Apache Kafka (mandatory)
- Configure Redis (optional). Use a persistent cache (recommended).
- Configure monitoring (optional). Improve the development experience and debugging.
- Configure Multi-tenancy (optional). Use Orchestrate with multiple tenants.
In addition to the dependencies, Orchestrate Transaction Sender needs to be configured to connect to the other microservices and to define how the service should be exposed.
tip
Configure each microservice using microservice-specific environment variables. Command line options are also available and take precedence over environment variables.
Configuration
| Environment Variable | Command line option | Description | Default |
|---|---|---|---|
API_URL | api-url | URL of the Gateway API HTTP endpoint. | localhost:8081 |
API_METRICS_URL | (only ENV var) | URL of the Gateway API HTTP metrics endpoint. | localhost:8082 |
KEY_MANAGER_URL | key-manager-url | URL of the Key Manager HTTP endpoint. | |
NONCE_MAX_RECOVERY | nonce-max-recovery | Maximum number of tries to recover a transaction with invalid nonce before returning an error. | 5 |
NONCE_MANAGER_TYPE | nonce-manager-type | Type of the nonce manager cache. Can be in-memory or redis | redis |
CLI options
See the complete list of command line options for the Orchestrate Transaction Sender:
{!cmd/tx-sender-run.txt!}