This guide tells you how to install and configure P4DTG, the Helix Defect Tracking Gateway. It is intended for anyone using P4DTG to replicate data between Helix Core Server and a defect tracker. For details about this release, refer to the P4DTG Release Notes.
Multiple search terms find topics with one or more of the terms, and each term gets a different highlight color: |
![]()
|
For an exact multi-word search, enclose the set of terms within quotes to form a single string: |
![]()
|
For an exact single-word search, use quotes:
|
|
You can search for any string on a page with |
Browse to the next or previous heading with arrow buttons: |
![]() |
See the top of any page to knows its location within the book: |
![]() |
Use the links to resources at the footer of each page: |
![]() |
Resize the Content pane as needed: |
![]() |
When sharing URLs, you can ignore the extra characters at the end of each page's URL because standard URLs do work. For example:
https://www.perforce.com/perforce/doc.current/manuals/cmdref/#CmdRef/p4_add.htm
or
https://www.perforce.com/perforce/doc.current/manuals/cmdref/#CmdRef/configurables.configurables.html#auth.default.method
How can we improve this manual? Email us at manual@perforce.com.
See https://www.perforce.com/support/self-service-resources/documentation.
Helix documentation uses the following syntax conventions to describe command line syntax.
Notation | Meaning |
---|---|
literal
|
Must be used in the command exactly as shown. |
italics | A parameter for which you must supply specific information. For example, for a serverid parameter, supply the ID of the server. |
[-f ] |
The enclosed elements are optional. Omit the brackets when you compose the command. |
... |
|
element1 | element2 | Either element1 or element2 is required. |