ServerID:

Read-only

A unique identifier for this server. This must match the contents of the server’s server.id file as defined by the p4 serverid command.

If the server type is identifier, the server id specifies the name of the cluster

Type:

Writable

Server executable type. One of the following:

Each type may offer one or more services. See next.

Services:

Writable

The server type server provides the following services:

The proxy type server provides a p4p caching proxy.

The broker type server provides the following services:

The services field for the identifier type server specifies the existence of the cluster, and has the value cluster. The name of the cluster is then drawn from the ServerID field.

The admin type server provides the following services:

Name:

Writable

The P4NAME associated with this server.

You can leave this blank or you can set it to the same value as the serverid.

Address:

Writable

The P4PORT used by this server.

ExternalAddress:

Writable

For an edge server, this optional field specifies the external address used for connections to a commit server. This field must be set for the edge server to enable parallel submits in a federated environment.

Description:

Writable

An optional description for this server.

User:

Writable

The service user name used by the server. For additional information about the use of this field, see the section "Service users" in the chapter "Perforce Replication" in Helix Versioning Engine Administrator Guide: Multi-site Deployment.

ClientDataFilter:

Writable

For a replica server, this optional field can contain one or more patterns describing how active client workspace metadata is to be filtered. Active client workspace data includes have lists, working records, and pending resolves.

To include client data, use the syntax:

//client-pattern/...

To exclude client data, use the syntax:

-//client-pattern/...

All patterns are specified in client syntax.

RevisionDataFilter:

Writable

For a replica server, this optional field can contain one or more patterns describing how submitted revision metadata is to be filtered. Submitted revision data includes revision records, integration records, label contents, and the files listed in submitted changelists.

To include depot data, use the syntax:

//depot/pattern/...

To exclude depot data, use the syntax:

-//depot/pattern/...

All patterns are specified in depot syntax.

ArchiveDataFilter:

Writable

For a replica server, this optional field can contain one or more patterns describing the policy for automatically scheduling the replication of file content. If this field is present, only those files described by the pattern are automatically transferred to the replica; other files are not transferred until they are referenced by a replica command that needs the file content.

Files specified in the ArchiveDataFilter: field are transferred to the replica regardless of whether any users of the replica have made requests for their content.

To automatically transfer files on submit, use the syntax:

//depot/pattern/...

To exclude files from automatic transfer, use the syntax:

-//depot/pattern/...

All patterns are specified in depot syntax.

DistributedConfig:

Writable

For an edge or commit server, this optional field, which is displayed only when you use the -l or -c option, shows configuration settings for this server.

If this field is present when invoked with -c, the configuration commands in this field are run on the current server using the scope of the server specified in the serverID field.

-c edge-server | commit-server

Set or change configuration values used to set up the distributed environment on an edge or commit server. The specified service dictates which configuration values can be set. Configuration fields are initially populated with the configured values if set, default values if unset, or unset for unset values with no default.

After exiting from the form, any configuration commands in this field will be run on the current server for the scope of the serverID. Because the commands apply only to the ServerID server, the server# prefix is not allowed.

For more information, see the section "Shortcuts to configuring the server" in Helix Versioning Engine Administrator Guide: Multi-site Deployment.

-d serverID

Delete the named server specification.

-g

Generate a new serverID as part of the form.

-i

Read a server specification from standard input.

You can combine this option with the -c option to generate and run configuration variables used to set up an edge or commit server. When used with -c, only the fields explicitly set in standard input from the DistributedConfig field will be configured.

-l

Use with -o flag to display the values of the configuration variables used to set up the current edge or commit server in a distributed environment. This option shows the configuration commands in the DistributedConfig field.

-o

Write the named server specification to standard output.

g-opts

See “Global Options”.

N/A

N/A

see discussion below

To change a server’s ID after creation

p4 serverid

To list all known servers

p4 servers