Welcome to the Perforce Knowledge Base

The Perforce Knowledge Base (KB) is the repository of Perforce's technical articles. If you have suggestions for articles, or have comments and questions, please let us know.

Featured Articles

Perforce Metadata and Archive Replication
This article provides answers to common questions that arise when setting up and implementing replication using 'p4 pull'.

Jan 17, 2012

Getting Started with Eclipse and P4Eclipse
P4Eclipse, the Perforce Plug-in for Eclipse, enables you to access Perforce from within the Eclipse IDE. This article takes you through the step-by-step set up of P4Eclipse, including installation and configuring preferences.

Sep 30, 2011

Securing Your Perforce Server
This article details some basic security considerations involved with setting up and using a Perforce Server, including using passwords, security levels, and protections. It also serves as a reminder that strong operating system and network security are an essential part of securing your Perforce system.

Jul 11, 2011

Unicode File Type Handling Changes In 2009.2
In the 2009.2 release of the Perforce Server, users can no longer submit files of type "unicode" to a non-unicode server. This article discusses a workaround if corruption has occurred to any unicode files as a result of the bug fix in 2009.2, as well as how this change affects utf16 files.

Aug 9, 2010

Installing A New License File
How do you install a new server license? This article describes three methods. Did you know that as of 2008.1 you can use the P4V Administration Tool? Read on for more details.

Jun 7, 2010

Self Serve Tools
Diagnosing slow server performance can be tricky. The Perforce Server Log Analyzer will allow you to examine possible usage problems by parsing your server log file and displaying commands that may have affected your server's performance. Results will be kept on our server for a period of 10 days and can be accessed any time by using your email address and access key. Log files will be automatically purged from our system upon expiration.

Dec 10, 2009