Import
The Import Drivefile option on the Activity menu reads the control file created by the split process and imports a document that has already been split. Once you have split your document, you can execute the import command at a command line. The Perl script to import is PCMImport.pl and is located in the Contenta_home/encaps/di directory.
Use the command line for the import activity to:
- execute the import activity for a document that has been split into components
- create a script to import a batch of documents, for example, as a system scheduled event
Configure digui.cfg file before issuing the PCMImport.pl command. The command line syntax is:
perl directory_path/PCMImport.pl arguments
The required syntax and arguments for PCMImport.pl are:
| Syntax/Argument | Description |
|---|---|
| perl | Perl executable. If Perl is not included in your PATH variable, specify the complete path to the Perl program. |
| directory_path/PCMImport.pl | Specify the directory path (directory_path) for the file (PCMImport.pl) to execute. |
| -file drivefile.xml | The full path of the XML DriveFile (drivefile.xml) generated by the split activity. |
The optional arguments for PCMImport.pl are:
| Argument | Description |
|---|---|
-api servername | The API server name (servername); the API service or process. |
-cookie string | Cookie string (string). |
-socket number | Socket number (number); used with cookie only. If not specified, defaults to the socket number specified in the DriveFile. |
-dbase name | The name of the Contenta database. If not specified, defaults to the database name specified in the DriveFile. |
-node nodename | The Contenta server’s node name. If not specified, defaults to the Contenta node specified in the DriveFile. |
-logsub function | The name of a custom logging or error reporting function. |
-config filename | Use to specify an alternate or custom Dynamic Import configuration file to use where filename is the name of the file (only; no path). The custom configuration file must be located in the Contenta_home/encaps/di directory. The custom configuration file must satisfy the required contents of the DI configuration file. It is recommended that you start your custom modifications with a copy of the delivered configuration file. If the |
-custom package | Use to specify an alternate custom callback (CustomCallbacks.pm) module where package is the case-sensitive name of the module that replaces CustomCallbacks.pm—for example, DITACustomCallbacks.pm or FrameBookCustomCallbacks.pm. The custom callback module must be located in the Contenta_home/encaps/di/custom directory. If not specified, the default is CustomCallbacks.pm |
-idmlog filename | Use to specify the log file in which to save information about what is being stored in AppData. Changes in the data stored in the map file may be made for editor tool compatibility. Only valid if AppData (in digui.cfg) is set to Yes. |