# Camel Runners

All Camel configurations are applicable, and can be passed on to these runners using global runner elements.

## Camel Event Runner

CamelEventRunner(*com.rierino.runner.camel.CamelEventRunner*) provides a variety of integration options, all of which can be used as input and output streams for use cases that require channels beyond what Spring and Samza runners support.

This event runner can consume message from all input streams mapped to it, with a camelRoute property and produce to any output system with a camelRoute setting. All input messages are converted to Json first and then to the message class defined for the input stream before processing as an event/journal/command, etc. All outputs are converted to an instance of the class required by the output endpoint.

{% embed url="<https://camel.apache.org/>" %}
Apache Camel
{% endembed %}


---

# Agent Instructions: 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:

```
GET https://docs.rierino.com/devops/microservices/service-runners/deploying-runners/camel-runners.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.