Previous Topic: Import TransactionsNext Topic: Version Documents


pdm_kit Utility—Knowledge Import Tool

The pdm_kit utility imports data to the destination server according to the settings in the configuration file of a package.

Important! Before you execute the pdm_kit utility from the application server, ensure that the path (local or UNC) of the package is accessible by the background server. If the background server is not able to access this path, the package is not imported from the application server.
Important! The r11.0 import utility has been renamed to pdm_kit_txt.exe to allow importing r11.0 text files. This utility does not support any of the r12.9 import enhancements.

The referenced data previously referenced by the pdm_ket utility gets the real UUID or ID value of the destination server. When running pdm_kit utility a new userid parameter is applied. The pdm_kit utility works as follows:

  1. Imports documents by replacing the userid value (for contacts) or referenced name (for fields like asset) with appropriate UUID of the destination server.
  2. Imports images.
  3. Imports attachments.
  4. Uploads files from the local package folder to the remote repositories.

Note: If editing published documents is disabled, then the imported document is created as a rework version.

The utility is invoked as follows:

pdm_kit [-h] -f -u [-v]
-h

(Optional) Displays help for the utility on the interface.

-f

Specifies the path to the package.

-u

Specifies the default user.

-v

(Optional) Enables extensive logging (bop_logging) of program events. This option is commonly used for internal problem solving.

Note: For advanced availability configuration, you can execute the pdm_kit utility on background server. For Windows, you can also execute the pdm_kit utility on application server if the package resides in a UNC shared drive. For non-windows platform, you cannot execute pdm_kit utility on application server.

Example: Using pdm_kit to Import a Package

pdm_kit -f c:\package_path -u ServiceDesk