# Metadata mapping for aggregated files

## Aggregated file metadata

Metadata appearing in the aggregated file depends on the aggregation strategy configured in the [message processing rule](/data-mover-1.21/transfer-protocols-and-connectors/jms-connector/message-processing-rules.md): **many to one** or **one to one.**

### Aggregating multiple JMS messages into a single file

When the aggregation strategy is set to **many to one**, only the queue name will appear in the **Additional Metadata** section of the **Metadata information** window. No specific actions must be taken to have metadata displayed.

This is the **Metadata information** window appearing when the **many to one** aggregation strategy is set:

<figure><img src="/files/xwmSLib3EXqfxKZZ2T75" alt="" width="563"><figcaption></figcaption></figure>

### Aggregating each JMS message to one file

When the aggregation strategy is set to **one to one**, all metadata message headers and properties will appear automatically in the **Additional Metadata** section of the **Metadata information** window. No specific actions must be taken to have metadata displayed.

The **Metadata information** window appears going to **Monitoring → Search file in all Virtual File Systems → View Metadata** entry appearing when clicking the 3 dots button.

This is the **Metadata information** window appearing when the **one to one** aggregation strategy is set:

<figure><img src="/files/OJ6ahidLj6YHaITt2mOd" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.primeur.com/data-mover-1.21/transfer-protocols-and-connectors/jms-connector/aggregate-jms-messages-into-files/metadata-mapping-for-aggregated-files.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.