Release Notes for the Perforce Defect Tracking Gateway General Release 2007.1 May 3, 2007 Introduction These notes include release-specific information about the Perforce Defect Tracking Gateway. For details about installing, configuring and using this product, consult the Defect Tracking Gateway Guide, which is included in the distribution zip file. The file name for the user guide is p4dtg.pdf. The Perforce Defect Tracking Gateway integrates Perforce with third- party defect tracking systems. The Mercury Quality Center 9.0 plugin supports the Windows platform, with any of MSDE, SQL Server or Oracle as the underlying database. The Perforce Defect Tracking Gateway requires the 2006.2 Perforce server. This version of the Perforce Defect Tracking Gateway does not support Windows Vista. Installing the Perforce Defect Tracking Gateway To install the Perforce Defect Tracking Gateway, download and run the installer from the Perforce web site. To test the basic operation of the system with the p4dtg-test.exe executable, issue the following commands (commands indicated by ">", output consists of "Loading module" and "Module loaded" messages: C:> p4dtg-test.exe > LL plugins\p4jobs.dll Loading module: [plugins\p4jobs.dll] Module loaded: plugins\p4jobs.dll > LT Module tests passed > LF Module freed > LL plugins\qc90dtg Loading module: [plugins\qc90dtg] Module loaded: plugins\qc90dtg > LT Module tests passed > Q Usage Notes - The replication engine runs as a process that is spawned by a Windows service. The configuration tool automatically installs the service when you start replication for the first time. The service is deleted when you delete the associated mapping. After installation, use the configuration tool to start and stop replication for specific mappings. To ensure that the replication engine restarts when the machine is rebooted, use the system Service control panel to set the replication service to Automatic. If you configure the replication engine as an Automatic service, you must run the replication engine on a machine other than the machine where Perforce and Quality Center are running, because you cannot control the order in which Windows starts services. - Configuration files created by the 2006.2 Beta release of this product are not compatible with configuration files used in the production release. If you participated in the Beta, you must run the configuration tool to rebuild all of your configuration files. Configuration files created by the 2006.2 release of this product are compatible with this release. - If Quality Center is configured to support a strict workflow, do not mirror any fields used to enforce that workflow. Because the Perforce jobs subsystem does not provide support for workflow rules, updates to Mercury Quality Center fields that are used in workflow enforcement might violate those rules, causing the transaction to be rejected. - If a change on the Perforce side is rejected by Mercury Quality Center, the Perforce job is marked as being in an error state, and further attempts to replicate it cease until the error is corrected. Error states are recorded in the DTG_ERROR field of the affected job. - Quality Center reports errors using a "Dispatch Error" format. For more detailed information about these error conditions, check the log file that is generated by the replication engine. - The most common cause of replication failures is caused by updates that are made using the username that the replication engine uses to update Perforce jobs. The engine does not replicate transactions that were submitted using its own username. To avoid this problem, ensure that this username is employed only by the replication engine. -------------------------------------------------------------------------------- Changes since Release 7.1 May 3, 2007: #148124 Support for P4TICKETS. To use tickets, leave the password field blank for the Perforce Data Source. A valid ticket must be obtained prior to running the configuration tool - if the ticket expires, replication will cease. After setting the ticket(s), copy the p4tickets.txt file into the 'C:\Documents and Settings\LocalService' directory so that the replication server service can find the ticket file. (Bug #28464) Changes since Release 2006.2 January 15, 2007: #122074 DTS Source Creation requires a Project to be selected before enabling the "OK" button to save the new source. (Bug #24481) #122074 p4dtg-test will reject calls to Perforce only extensions for non-perforce plugins. (Bug #24647) #122074 p4dtg-test help text now states that the SD method may require a connection to a specific project in order to function. Quality Center plugin has this requirement. (Bug #24648) #122074 p4dtg-test help text now states that the DE method requires the date to be formated according to the plugin being tested. (Bug #24649) #122074 p4jobs plugin will now put single line field values on the same line as the field name. (Bug #24652) #119397 Prevent configuration tool from crashing when connecting to a non-p4d server using the p4jobs plugin. (Bug #24256) #119387 Prevent replication engine from being run when the Defect Tracking Source is not providing a "Last Modified Date" field. (Bug #24242) #119387 Correct non-enabling of possible select values when all select value mappings are deleted using UNMAP ALL. (Bug #24226) #118987 Prevent running the replication engine on an empty mapping description. (Bug #24206) #118866 Correct check for incomplete select mappings to not consider deleted mappings. (Bug #24198) #118864 Prevent changing of nicknames once they have been established. (Bug #24200) #118864 Prevent deletion of Data Sources which are used in mappings. (Bug #24194) #118755 Prevent invoking replication on a mappings marked for deletion (Bug #24190) #118383 To ensure that all new Mercury issues are properly replicated, the Quality Center plugin subtracts 30 seconds from the timestamp used used to detect new or changed issues. (Bug #24153) #117382 Enable the Perforce server and the Defect Tracking server to run in different time zones. (Bug #23792) #117101 Enable the configuration tool to display long project names. (Bug #23954) #117035 P4DTG now supports the following Mercury date formats: DMY - Day Month Year - dd/mm/yyyy MDY - Month Day Year - mm/dd/yyyy YMD - Year Month Day - yyyy/mm/dd 24 hr - hh:mm:ss 12 hr - hh:mm:ss AM|PM Other formats are not supported. (Bug #23916) #116366 The replication engine no longer crashes if the Defect Tracking System returns a NULL value for a defect's LastModifiedDate field. (Bug #23855) #115643 Support running the replication engine using Windows services. (Bug #23050)