Open topic with navigation
The Helix Broker (P4Broker) enables you to implement local policies in your Helix Core environment by allowing you to restrict the commands that can be executed, or redirect specific commands to alternate (replica or edge) Helix servers.
The Helix Broker is a server process that mediates between Helix Core client applications and Helix server, including proxy servers. For example, Helix Core client applications can connect to a proxy server that connects to the broker, which then connects to a Helix server. Or, Helix Core client applications can connect to a broker configured to redirect reporting-related commands to a read-only replica server, while passing other commands through to a master server. You can use a broker to solve load-balancing, security, or other issues that can be resolved by sorting requests directed to one or more Helix servers.
The work needed to install and configure a broker is minimal: the administrator needs to configure the broker and configure the users to access the Helix server through the broker. Broker configuration involves the use of a configuration file that contains rules for specifying which commands individual users can execute and how commands are to be redirected to the appropriate Perforce service. You do not need to backup the broker. In case of failure, you just need to restart it and make sure that its configuration file has not been corrupted.
From the perspective of the end user, the broker is transparent: users connect to a Helix Broker just as they would connect to any other Helix Versioning Engine.