<html><title>Managing Perforce Server Sources</title>
<h1>Managing Perforce Server Sources</h1>
This tab enables you to specify details about the Perforce servers that you are
integrating with external defect trackers.
<p><b>To add a Perforce Server source:</b>
<ol>
<li>Click <b>New</b>. The <b>Add Perforce Server Source</b> dialog is displayed.</li>
<li>Enter the server connection details (see below).</li>
<li>Click <b>Check connection and jobspec.</b> If you have correctly specified
valid values, the dialog displays a success message in the <b>Server status</b>
field. If a connection error is displayed, correct your entries and again
click <b>Check connection and jobspec</b>. P4DTG retrieves and displays reference
field data for the specified Perforce server. If the <b>Server status</b>
field says that the server is not configured, you must add the required fields
to the Perforce job specification. For details, see the <i>Perforce Defect
Tracking Gateway User's Guide</i>.</li>
<li>Click <b>OK</b> to save your entries and dismiss the dialog.</li>
</ol>
Your newly-defined Perforce server source is now displayed in <b>Defined Perforce
Server Sources</b>.
<p> <b> Server Connection Details</b>
<p>
<ul>
<li><b>Name:</b> an alias for the Perforce server and its associated connection
information. </li>
<li><b>Server:</b> the name of the Perforce server host machine and the port
on which it is running. Specify as <i>hostname</i>:<i>port</i>; for example
<tt>p4host:1667</tt>. </li>
<li><b>User name:</b> the user name to be used to connect to the Perforce
server when data is read or written. </li>
<li><b>Password:</b> password for the specified user, if required.</li>
<li><b>Reference fields</b>: The data required to replicate issues and jobs.
The references fields are:
<ul>
<li><b>Modified Date:</b> the date that the job was last updated</li>
<li>
<p><b>Modified By:</b> the Perforce user who last updated the job.
<p></li>
</ul>
</li>
</ul>
<p><b>Important</b>: To ensure that you can distinguish jobs modified by the gateway,
create a dedicated Perforce user to be used only by the gateway. The user
name must be used only for defect replication. Do not use this user name for
any other purpose. Ensure that the user name is neither a prefix nor a suffix
of any other user name. For example, if you already have a Perforce user named
“admin-logger,” do not assign “admin” or “logger”
as the user name.
<p><b>To edit a Perforce server source:</b> click the source in the <b> Perforce
server sources</b> list, then click <b>Edit.</b>
<p>To configure filtering of selected defects to replicate them to differing defect
trackers or SCM systems, define <a href="segments.html">segments</a>.
<p><b>To delete a Perforce server source:</b> click the source in the <b>Perforce
server sources</b> list, then click <b>Delete.</b> The source is marked for
deletion. To delete the source permanently, click <b>Apply </b>or<b> OK</b>.
To undelete a marked source, click the source that is marked for deletion, then
click <b>Undelete</b>.
<hr>
<a href="about.html">About</a><br>
<a href="index.html">Contents</a><br>
<i><font size="-1">p4tab.html</font></i> </html>