Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Server Administration Documentation | 2025.2

# Global settings

The following settings apply to all operations you specify for the broker.

Setting | Meaning | Example
--- | --- | ---
`target` | The default P4 Server (P4D) to which commands are sent unless overridden by other settings in the configuration file. | `target = [protocol:]host:port;`
`listen` | The address on which the P4 Broker listens for commands from P4 Server client applications. Requires restarting p4d for change to take effect. | `listen = [protocol:][host:]port;`
`server.id` | (Optional) The unique ID associated with the Broker. | `server.id = brokerSvrID;`
`directory` | The home directory for the P4 Broker. Other paths specified in the broker configuration file must be relative to this location. Requires restarting p4d for change to take effect. | `directory = path`;
`logfile` | Path to the P4 Broker logfile. | `logfile = path;`
`debug-level` | Level of debugging output to log. Overrides the value specified by the `-v` option and `P4DEBUG`. You can specify the value for one or more flags. Requires restarting p4d for change to take effect. | `debug-level = server=1, time=1, rpl=3;`
`admin-name` | The name of your P4 Server Administrator. This is displayed in certain error messages. | `admin-name = "P4 Admin";`
`admin-email` | An email address where users can contact their P4 Server Administrator. This address is displayed to users when broker configuration problems occur. | `admin-email = admin@example.com;`
`admin-phone` | The telephone number of the P4 Server Administrator. | `admin-phone = nnnnnnn;`
`redirection` | The redirection mode to use: `selective` or `pedantic`. In `selective` mode, redirection is permitted within a session until one command has been executed against the default (target) server. From then on, all commands within that session run against the default server and are not redirected. In `pedantic` mode, all requests for redirection are honored. The default mode is `selective`. | `redirection = selective;`
`service-user` | An optional user account by which the broker authenticates itself when communicating with a target server. The broker configuration does not include a setting for specifying a password as this is considered insecure. Use the `p4 -u service-user login -p` command to generate a ticket. Store the displayed ticket value in a file, and then set the `ticket-file` setting to the path of that file. The default ticket timeout is 12 hours, but the ticket for a service user defaults to `unlimited` in 2025.2 and later. For 2025.1 and earlier: include the `service-user` in a group that has `unlimited` as its `Timeout` setting . | `service-user = svcbroker;`
`ticket-file` | An optional alternate location for `P4TICKETS` files. | `ticket-file = /home/p4broker/.p4tickets;`
`compress` | Compress connection between broker and server. Over a slow link such as a WAN, compression can increase performance. If the broker and the server are near to each other (and especially if they reside on the same physical machine), then bandwidth is not an issue, and compression should be disabled to spare CPU cycles. | `compress = false;`
`altserver` | An optional alternate server to help reduce the load on the target server. The `name` assigned to the alternate server is used in command handler specifications. See Alternate server definitions. The syntax is: altserver: name { target=[protocol:]host:port; } Multiple `altserver` settings might appear in the broker configuration file, one for each alternate server. For example:
    altserver: rep_18310 { target=10.5.10.118:18310; }
    altserver: rep_18320 { target=10.5.10.118:18320; }
    altserver: rep_18330 { target=10.5.10.118:18330; }

## Next step

Command handler specifications

Your search for returned results