ASAP XML Import and Export Jobs Do Not Conform to the Concurrent Threads Setting in the P6 Configuration (Doc ID 2229758.1)

Last updated on FEBRUARY 07, 2017

Applies to:

Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 15.2.0.0 to 15.2.12.0 [Release 15.2]
Primavera P6 Enterprise Project Portfolio Management - Version 15.2.0.0 to 15.2.12.0 [Release 15.2]
Information in this document applies to any platform.

Symptoms

ASAP/on-demand XML export or import jobs do not abide by the Concurrent Threads setting in the P6 Configuration.

 

EXAMPLE:

  1. Launch the P6 Administration application (<P6 EPPM home>\p6\adminpv.cmd or .sh).
  2. Enter the credentials for the privileged schema user (default privuser).
  3. Expand the P6 Configuration (NOTE: If a separate P6services.jar process has been set up, expand the configuration for that process).
  4. Expand Services > Import/Export Service.
  5. Set Concurrent Threads to '1'.
  6. Save the changes and exit the P6 Administration application.
  7. Login to P6 Web and initiate multiple ASAP XML import tasks.
  8. The exports will be processed concurrently, rather than one at a time per the Concurrent Threads setting.
- Even if the Concurrent Threads value is set to '0', multiple XML exports can run concurrently.
- This can cause performance issues if multiple users initiate large XML import/export jobs and all are simultaneously run by the the P6 Web JVM process.
- The Administrator of the P6 environment should have the ability to limit how many concurrent ASAP import/export jobs can run concurrently.
- The condition described in this document does not apply to scheduled XML import/export jobs, only on-demand jobs.

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms