Configuring P4 Server

Client-side environment variables

On the client-side several environment variables are used to configure P4 Server under Perforce IPLM:

P4PORT

P4PORT points to the server and port of the P4 Server to use to build a workspace.  

syntax:
 
P4PORT = <servername>:<perforce port> 
example:
 
P4PORT = centralcommit1:666

The server:port value in the P4PORT environment variable is used to build the initial workspace, this value is then stored in the file named by P4CONFIG, and that value is used for subsequent perforce operations in the workspace.

Note that in a replicated environment P4PORT should be set to the address of either the central commit server or the local replica server (edge, forwarding replica, etc) that is closest to the user.

P4IGNORE

The P4IGNORE variable points to a file containing a list of files/directories to ignore when adding files to the depot or reconciling workspaces.

More information on P4IGNORE, including examples, can be found here.

P4CONFIG

The P4CONFIG variable points to a file that contains the configuration information for a given workspace.  This file will automatically be created in each Perforce IPLM workspace and the values in it will be used to configure perforce.

syntax:
 
P4CONFIG = <p4config file> 
example:
 
P4CONFIG = .p4config
 
in the workspace:
> cat .p4config
P4PORT=tau-deploy-test-c6:1666
P4CLIENT=ws:testserver:testsite:mdx:tutorial.tutorial:e4bde0aa

The value of P4PORT in the P4CONFIG file will be taken from the value of the P4PORT environment variable at the time the workspace was created.

The value of the P4CLIENT will be created by Perforce IPLM. 

Server Side Perforce Configurables

On the server the configuration mechanism is via the 'p4 configure' command:

syntax:
 
> p4 configure set <servername>#<configuration variable>=<value> 
> p4 configure show allservers
 
example:
 
> p4 configure set testserver#net.parallel.max=21
 
> p4 configure show all servers
any: net.parallel.max = 21
any: net.parallel.min = 1000
any: net.parallel.minsize = 500M
any: net.parallel.submit.min = 1000
any: net.parallel.submit.threads = 21
any: net.parallel.threads = 21
testserver: P4LOG = /usr/share/mdx/repos/p4/logs/testserver.log
testserver: P4TICKETS = /usr/share/mdx/repos/p4/.p4tickets
testserver: journalPrefix = /usr/share/mdx/repos/backup/p4d_backup_testserver
testserver: lbr.bufsize = 64k
testserver: net.tcpsize = 512k
testserver: server.depot.root = /usr/share/mdx/repos/p4/depots

More discussion on configuring P4 Server can be found at Important P4 Server Configuration Variables.

Configuring replication servers is discussed at P4 Server Replication.