Exporting Profiles from the Command Line |
DEVELOPER |
 |
|
Exporting Profiles from the Command Line |
DEVELOPER |
|
The Profile Export Command Line facility provides a simple way for you to transfer PROIV operators and projects between machines from the Operating System command line. Refer JSON Export and Character Encodings other than UTF-8 for additional information.
When you run the Export utility from the command line, the selected PROIV objects such as Operators and/or Projects are extracted.
The extracted data is written to file in the format of JSON(JavaScript Object Notation). You can use the exported files as a backup or import to a different machine. The Import utility (regardless of the method used to export) can be used to read the object definitions and data from an exported file.
You can create the following User Profile export files:
· PROIV Operators, these files will have a .p4op extension and will contain all operator related data.
· PROIV Projects, these files will have a .p4pr extension and contain all project related data.
To export, simply execute the runproiv script in UNIX with the following parameters:
./runproiv.sh /proivhome/config/decvt100.properties %%% %%% projects myexportedresults.txt /proivhome/boots/Jsonexport mydevproject1 mydevproject2 export 2>&1 > runproiv.log
|
Field |
Description |
|
Config File |
The location of the configuration file you will use to launch the PROIV session. Command line execution must use a non gui character based terminal type. |
|
PROIV Company Division |
Must be %%% to successfully execute this functionality. This operator is included as part of the standard distribution. |
|
PROIV Operator |
Must be %%% to successfully execute this functionality. This operator is included as part of the standard distribution. |
|
Profile Type |
This will be "operators" or "projects". |
|
Results File |
Output of the results (including any exceptions). This file will reside in the boots folder if no path is specified |
|
Export Folder Location |
This is the folder where the individual json files (.p4op/.p4pr) will reside. |
|
Selection From |
In the example of a project export, this will be the PROIV project name. For an operator export, this will be the PROIV operator. |
|
Selection To |
In the example of a project export, this will be the PROIV project name. For an operator export, this will be the PROIV operator. |
|
Action Type |
For exports, this must be "export". |
1. Reserved PROIV operator %%%% must be present in your PROIV environment.
Topic ID: 500802