Running the VPLMPosImport Batch

This section explains how to run the VPLMPosImport batch tool.

You need to have VPLM administrator rights to be authorized to run the VPLMPosImport batch tool.

Keep in mind that you must specify using the -context parameter a security context referencing the VPLMAdmin role, for example VPLMAdmin.MyCompany.Default.

On Windows

Go the installation folder:

INSTALL_PATH\server\win_b64\code\command

then run the following command with the appropriate command-line parameters:

VPLMPosImport.bat

On UNIX

Go the installation folder:

INSTALL_PATH/server/scripts

then run the following command with the appropriate command-line parameters:

VPLMPosImport.sh

Command-Line Parameters

This is the full list of command-line parameters:

Parameter Description
-user userid P&O user identifier to be used in order to connect to the ENOVIA V6 repository (mandatory); this parameter should only be specified when executing VPLMPosImport as a Java batch
-password password User password to be used in order to connect to the ENOVIA V6 repository (mandatory); this parameter should only be specified when executing VPLMPosImport as a Java batch
-context contextid P&O context identifier to be used to connect to the ENOVIA V6 repository (optional; the default is VPLMAdmin.MyCompany.Default)
-server url

URL of the ENOVIA V6 server (mandatory), for example:

http://localhost:7023/ematrix

This parameter should only be specified when executing VPLMPosImport as a Java batch.
-file importfile Full path and name of the input import file (mandatory)
-no-abort-on-error Have the import engine resume execution upon error (optional; the default behavior is to abort the execution as soon as an error is encountered).

Note: Disabling an “abort on error” feature may prove dangerous, since ignoring errors may result in the definition of an incomplete security policy in the P&O and Security database.
-report reportfile Full path and name of the output report file (optional); if specified, the execution status of all import commands is written to the report file
-transaction-mode

Indicates how modifications should be committed to the database. Possible values are:


  • global: changes are committed once at the end of execution
  • intermediate: changes are committed every Nth command, as specified by option -transaction-size
  • local: all changes are committed individually
-transaction-size Indicates the size of transaction when -transaction-mode is set to intermediate. The default size is 50
-syntax Display help on import syntax (optional); requires -h
-h Display help (optional)

Best Practices

Once users have been created using the VPLMPosImport command, the application server needs to be restarted otherwise the Publish/Subscribe function will not work.

Furthermore, when you use the VPLMPosImport batch tool to delete a user and create the same user again, and try to reconnect using the same user, user connection and searching for all persons will not work unless you reload the server cache.

Before running the import tools just after an installation, please make sure all installed JPO have been well recompiled, otherwise the batch tool will fail. We recommend that you force the JPO compilation via MQL. Please refer to the MQL Administration Guide for further information.

To perform massive data imports, the administrator should check the import file content. All the data ID defined within the file should be unique otherwise a unique constraint violation will be raised by the system and the batch will fail with no consistent error messages.