Mirror Modes in Federated Repositories
Choose bidirectional, receiving-only, or transmitter mode to control Federation artifact flow.
Federated repositories support two synchronization modes that determine how artifacts and metadata flow between Federation members: bidirectional (default) and receiving-only (unidirectional).
| Mode | Sends | Receives | Configuration |
|---|---|---|---|
| Bidirectional (default) | Yes | Yes | Default mode for all members |
| Receiving-only | No | Yes | Set when creating or updating a Federated repository |
| Transmitter | Yes | No | Set automatically on the counterpart member when receiving-only mode is configured |
Bidirectional Mode
In bidirectional mode, all Federation members both send and receive artifacts and metadata events. Changes made to an artifact on one member are replicated asynchronously to the other members, and vice versa.
For example, if Federated repository A in "JPD A" and Federated repository B in "JPD B" are members of the same Federation:
- Deploying a file to Federated repository A in "JPD A" triggers a copy of the file to Federated repository B in "JPD B".
- Deploying a file to Federated repository B in "JPD B" triggers a copy of the file to Federated repository A in "JPD A".
If both members receive conflicting changes to the same artifact, see Synchronization and Conflict Resolution for how the Federation resolves them.
Receiving-Only Mode
When a Federation member is set to receiving-only mode, the repository receives events and binaries from other Federation members but can't send. This option maintains a central source of truth while enabling access to artifacts in distributed environments.
Receiving-only mode can be configured when creating a new Federated repository or by updating an existing one.
Best practice: keep receiving-only members read-only
Receiving-only mode stops the member from sending events, but it doesn't block local artifact changes on that JPD. Because a receiving-only member never sends events, any local upload or deletion stays on that member only and causes the target to diverge from the source. Perform all artifact changes on the sending member. For more information, see Best Practice: Keep Receiving-Only Members Read-Only.
Transmitter Mode
When a Federation member is set to transmitter mode, the repository sends events and binaries to other Federation members but doesn't receive. Transmitter mode is the complement of receiving-only mode and is set automatically on the counterpart member when receiving-only mode is configured.
Note
Transmitter mode isn't directly user-configurable in the Platform UI. It is assigned internally when the counterpart member is set to receiving-only mode.
Related Topics
Updated 1 day ago