Federated Topology
Federated repositories are easy to set up and support bi-directional synchronisation of local repositories without the need to set up complex topologies. These types of repositories are based on bidirectional replication, whereby artifact metadata is replicated constantly separately from the binary content.
As displayed in the following example, setting up mirroring across three sites using the traditional Replication feature, would have required setting up quite a complex mesh topology consisting of setting up multiple virtual repositories with a local repository and 3 remote repositories, whereas Federated repositories inherently support mirroring removing the need to create the mesh topology.
Get Started
To start working with Federated repositories, you will first need to set upcross-instance authentication (Circle-of-Trust)between the JPDs to allow the Platform Administrator to perform a set of CRUD (Create, Remove, Update and Delete) actions on the repositories based on their predefined set of permissions. All the actions performed on one of the Federated repositories will automatically be synchronized and reflected on all of the Federated members, including not just the repository content, but also certain configuration changes. For example, ifFederated repository Ain "JPD A" andFederated repository Bin "JPD B" are members of the same Federation, deploying a file toFederated Repository Ain "JPD A", will trigger a copy the file action to theFederated Repository B在“詹妮弗B”。同样,部署文件Federated Repository Bin "JPD B", will trigger a copy the file action to theFederated Repository Ain "JPD A". The configuration changes are also synchronized based on the latest update (e.g. latest update to the configuration is propagated to all members of Federation).
To start creating your first Federated repository, clickhere.
