Connecting To Primavera Database
Connecting To Primavera Database
Connecting To Primavera Database
Table of Contents
1.1.1 Overview
Primavera Risk Analysis can read in project data from a P3 project file, XER files, a P6 EPPM database and
a P6 Professional database. It is also possible to connect via Web Services ('Using Web Services to
connect' in the on-line documentation) using v8.0 and 8.1.
The primary purpose of this interface is to enable Primavera P6 users to risk analyze their projects using
Primavera Risk Analysis's risk tools.
XER files
XER files can be created from the Primavera P6 desktop client using the File | Export command.
Having created an XER file it can be read directly by Primavera Risk Analysis using the File |
Primavera | Open Primavera XER file.
There is no need to have any Primavera P6 software installed. You can open a .xer file that has been
sent to you.
Disadvantages of XER compared with the "Direct connection" shown above
- Always imports project resources individually as there is no option to import as only costs
summarized as Labor, Non-Labor, Material and Expense.
- Cannot be used to update the Primavera P6 database.
See Opening a Primavera XER project file ('Primavera P6 - Opening a Primavera P6 XER
project file' in the on-line documentation)
MPP files
Primavera P6 can create MPP files. This format is not recommended as it is designed to support
projects created and saved in MS Project. The format is limited in the way that Primavera P6 can store
data.
The Primavera Connection Wizard will help you set up the connection between Primavera Risk Analysis
and a Primavera P6 project database.
Security
All Primavera Risk Analysis connections to a Primavera P6 project database use Primavera's security. This
allows users to login with their Primavera user name and password giving the user access to only the
projects they have permission to view.
If this is the first time you are connecting to a Primavera P6 Database using the API or you receive an
error while trying to connect using the API, please perform the steps detailed in Opening Primavera
Risk Analysis From Primavera P6 Professional (on-line documentation).
This will perform the necessary API connection steps for integration between Primavera P6 and
Primavera Risk Analysis.
Oracle recommends using a Secured Socket Layer (SSL) connection where available.
Batch Size: For API and Native connections. This option does not normally need to be adjusted.
Primavera recommend a batch size of 1024 for Primavera v6.0 and v7.0.
Connection Timeout: For API and Native connections. Increase this value if you are experiencing
"Server Busy" messages during the import. Primavera P6 reports the server as being busy if this timeout
setting is exceeded during an import, e.g. the network connection is slow, the project contains a lot of
data.
Always display import log: A log of the import will always be displayed even if there are no errors.
Use these connection settings for all Primavera Risk Analysis users: This will populate the
PrimaveraRiskAnalysis.ini file in the Primavera Risk Analysis installation folder with the Primavera
connection settings. Primavera Risk Analysis will always use these settings when they are available rather
than the user's own registry settings.
The Primavera Integration API contains components that allow Primavera Risk Analysis to access your
Primavera P6 project database.
The API method can be used when connecting to the following Primavera applications:
P6 v6
P6 v7
P6 Professional database R8.1 or higher
Requirements
- Primavera P6 installed using Oracle or SQL / MSDE installation. The Interbase installation is not
supported.
- Primavera Integration API installed.
HTTP(S) Port:
Only enabled when either HTTP or HTTPS modes are selected, this is the port number the application
server is configured to listen for HTTP or HTTPS requests.
Batch Size:
Usually does not need changing. For remote connections if the time taken to display a large EPS is
great then increasing this value to 1024 may help.
Connection Timeout (Seconds):
This option allows the amount of time Primavera Risk Analysis tries to connect to Primavera P6 to be
increased. This should only be increased if connections to the Primavera P6 database are timing out
even though the connection is correctly configured. Usually only required for large Primavera P6
database implementations.
If the connection is timing out the following "Server Busy" message is displayed:
"This action cannot be completed because the other program is busy. Choose 'Switch To' to
activate the busy program and correct the problem".
PDF Documentation
Some of the on-line help (e.g. tutorials) can be found in the Documentation folder that is created when
the Primavera Risk Analysis software is installed. The documentation is saved in the Adobe PDF format.
The default installation folder for the documentation is:
C:\Program Files\Oracle\Primavera Risk Analysis\Documentation