> For the complete documentation index, see [llms.txt](https://docs.rumi.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rumi.systems/rumi-core/guides/developing-applications/configuring-the-runtime.md).

# Configuring the Runtime

This section covers **development-time configuration** of the Rumi runtime environment. These are settings you specify in your DDL (configuration XML), annotations, and system properties during development, before deployment.

## Scope of This Section

**Development-Time Configuration** includes:

* DDL parameters that control runtime behavior
* Settings specified in your `config.xml` during development
* Annotation-driven configuration in your code
* System properties that affect runtime operation

This is distinct from **runtime operations** covered in [Operating Applications](/rumi-core/guides/operating-applications.md), which focuses on administering, monitoring, and troubleshooting deployed microservices.

## Configuration Topics

### Message Flow

* [**Message Flow**](/rumi-core/guides/developing-applications/configuring-the-runtime/message-flow.md) - Configure message flow behavior
  * [Duplicate Detection](/rumi-core/guides/developing-applications/configuring-the-runtime/message-flow/duplicate-detection.md) - Configure duplicate message detection

### Runtime Behavior

* [**Configuring Adaptive Batching**](/rumi-core/guides/developing-applications/configuring-the-runtime/transactions/adaptive-batching.md) - Configure transaction batching for throughput optimization

### Threading and Performance

* [**Configuring Threading**](/rumi-core/guides/developing-applications/configuring-the-runtime/threading.md) - Configure disruptors, thread affinitization, and NUMA optimization

### Administration and Monitoring

* [**Configuring Administration**](/rumi-core/guides/developing-applications/configuring-the-runtime/administration.md) - Configure Admin over SMA for remote administration
* [**Configuring Monitoring**](/rumi-core/guides/developing-applications/configuring-the-runtime/monitoring.md) - Configure heartbeats, statistics collection, and telemetry

### Logging

* **Configuring Logging** - Configure trace logging and log levels (see [Trace Logging](/rumi-core/guides/operating-applications/analysis-and-troubleshooting/trace-logging.md))

## Development vs Operations

| Development-Time (This Section)               | Runtime Operations                                   |
| --------------------------------------------- | ---------------------------------------------------- |
| **When**: During development, in DDL/code     | **When**: After deployment, with running services    |
| **How**: DDL XML, annotations, properties     | **How**: Admin tools, viewing output, analyzing logs |
| **Example**: Configure heartbeat interval     | **Example**: View heartbeat statistics               |
| **Example**: Enable transaction latency stats | **Example**: Analyze transaction performance         |
| **Example**: Set up Admin over SMA            | **Example**: Use admin tool to manage services       |

## Related Topics

* [Operating Applications](/rumi-core/guides/operating-applications.md) - Runtime administration, monitoring, and troubleshooting
* [Operating Model](/rumi-core/concepts/operating-model.md) - Conceptual overview of operations architecture
* [Configuration Reference](/rumi-core/reference/configuration.md) - Complete DDL elements and global properties reference

## Next Steps

1. Review the configuration topics relevant to your use case
2. Add configuration to your `config.xml` during development
3. Deploy your microservice
4. Use [Operating Applications](/rumi-core/guides/operating-applications.md) to manage and monitor at runtime


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rumi.systems/rumi-core/guides/developing-applications/configuring-the-runtime.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.