P6 EPPM Installation and Configuration Guide
16 R1
April 2016
Contents
About Installing and Configuring P6 EPPM ........................................................
6
Prerequisites for P6 EPPM Configuration
.......................................................... 8
Minimum
Hard Disk Space ..............................................................................
8
JDK
Installation
..........................................................................................
8
Setting
an Environment Variable for Java .....................................................
9 Installing
WebLogic
....................................................................................
10
Installing
a Database
..................................................................................
11 Grant
Privileges to the SYSTEM User
................................................................ 12 Content
Repository Installation and Configuration
............................................... 13 BI Publisher Installation
...............................................................................
13
Workflows
Repository Installation
................................................................... 14
Installing
the Oracle MDS Schema for BPM
.................................................. 14
Modifying
the P6 Environment for BPM
...................................................... 15
Installing
IAIK-JCE
.....................................................................................
16
Setting
an Environment Variable for IAIK-JCE ..............................................
17
About the P6 EPPM Installation Wizard
........................................................... 18
Your
P6 EPPM Suite
....................................................................................
19
Where
to Go From Here - Pre Configuration
Wizard.............................................. 21
Using
the P6 EPPM Configuration Wizard To Configure P6 EPPM .........................
21
Manually
Configuring Your Applications .....................................................
21
About the P6 EPPM Configuration Wizard
........................................................ 22
Configuring
Your Database
........................................................................... 22
Using
the Database Configuration Screen
................................................... 23
Using
the Database Type & Connection Screen
............................................ 24
Using
the Create Users Screen ................................................................
25
Configuring
Your WebLogic Server with P6 EPPM
................................................. 26
Using
the P6 Configuration Settings Screen
................................................. 26 Using the Application
Server Configuration Screen ........................................ 27
Using
the Configure WebLogic Screen
....................................................... 27
Using
the Configure Component Schema Screen
........................................... 28
Connecting
Applications to P6 EPPM
................................................................ 28
Using
the Content Repository Selection Screen
............................................ 29 Using the Content
Repository Configuration Screen for Oracle Webcenter
Content
Core Capabilities ....................................................... 30
Using
the Content Repository Configuration Screen for CMIS .............. 31
Using
the BI Publisher Screen .................................................................
32
Using
the BPM Workflows Screen
............................................................. 33
Using
the BPM Configuration Screen ........................................... 34
Completing
Your P6 EPPM Installation
.............................................................. 34
Using
the Configuration Review
Screen...................................................... 34 Using
the Configuration Progress Screen ....................................................
35 Using
the Configuration Complete
Screen................................................... 35 Default
Locations Created by the Wizard
................................................... 36
Default
Java Heap Settings Created by the Wizard
........................................ 37
Database Administration
............................................................................ 38
Implementing
Transparent Data Encryption on the P6 EPPM Database ........................ 38 Background
Processes and Clean Up in P6 EPPM
.................................................. 39 PX Tables Clean Up
Procedure
....................................................................... 40 RDBMS
Scheduler Configuration .....................................................................
41 Database
Settings Table
..............................................................................
42
Reading
Setting Values
................................................................................
43
Using
Code to Read Setting Values for Oracle
.............................................. 43
Using
Code to Read Setting Values for Microsoft SQL Server
............................. 43
Writing
Setting Values ................................................................................
44
Using
Code to Write Setting Values for Oracle
............................................. 44
Using
Code to Write Setting Values for Microsoft SQL Server
............................ 44
Tracking
Background Job Execution
................................................................ 45
High
Level Status Settings
..................................................................... 45
The
BGPLOG Table..............................................................................
46
SYMON
(System Monitor) Procedures
............................................................... 46
OBSPROJ_PROCESS_QUEUE
Procedure ....................................................... 47
USESSION_CLEANUP_EXPIRED
Procedure .................................................... 48
Tracking
Concurrent Usage of P6 EPPM ........................................ 50
DAMON
(Data Monitor) Procedures
.................................................................. 51
BGPLOG_CLEANUP
Procedure ................................................................. 52
REFRDEL_CLEANUP
Procedure ................................................................ 53 REFRDEL
Bypass Procedure ....................................................................
54 CLEANUP_PRMQUEUE
Procedure .............................................................. 55 USESSION_CLEAR_LOGICAL_DELETES
Procedure ........................................... 56 CLEANUP_LOGICAL_DELETES
Procedure ..................................................... 56 PRMAUDIT_CLEANUP
Procedure .............................................................. 58 CLEANUP_USESSAUD
Procedure ............................................................... 59
USER_DEFINED_BACKGROUND
Procedure .................................................... 61 Oracle
Database Performance
....................................................................... 61
Safe
Deletes ............................................................................................
61
Turning
Off Safe Deletes
....................................................................... 62
PRMAUDIT
Auditing ....................................................................................
62
Auditing
Level Configuration
.................................................................. 63 About Installing and Configuring P6 EPPM
Simple
Configuration ...........................................................................
63
Detailed
Configuration
......................................................................... 64 Auditing
Status .................................................................... 64
Options
Setting .................................................................... 65
SETTINGS_WRITE_STRING
Procedure ........................................... 66 The
Audit Table
.................................................................................
67 Session
Auditing .................................................................................
68
Column
Audit Data
..............................................................................
68
Using
the Data Pump Utility ..........................................................................
69
Running
a Schema Validation on the Database
............................................. 70
Running
the Data Pump Utility Using the Wizard
.......................................... 71
Running
the Data Pump Utility From the Command Line .................................
72
Where To Go From Here - Post Configuration Wizard
......................................... 73
Launching
Your P6 EPPM Applications ..............................................................
74
Starting
and Stopping Managed Servers
..................................................... 75 Starting
a Managed or Clustered Server ....................................... 76
Stopping
a Managed or Clustered Server ...................................... 77 Settings
You Must Configure in P6 Before You Begin
............................................. 77
Installing
Additional Applications
................................................................... 78
For More Information
................................................................................
79
Where
to Get Documentation
........................................................................ 79 Documentation
Accessibility .........................................................................
79 Where
to Get Training
................................................................................
79
Where
to Get Support
.................................................................................
80
Legal Notices
..........................................................................................
82
About Installing and
Configuring P6 EPPM
This guide tells you how to automatically
install and configure your applications. Before you begin, read the Prerequisites
for P6 EPPM Configuration (on page 7).
Installing P6 EPPM
You will use the setup.exe (for Windows) ./runinstaller
(for Linux or UNIX) in the Primavera P6 Enterprise Project Portfolio Management
physical media or download to install the following P6 EPPM applications:
Note: You do not have to install all
applications; you can pick and choose what you install. However, you must install
P6 to run the other P6 EPPM applications.
4 P6 (and its help and tutorials)
4 P6 Team Member Interfaces (includes P6 Team Member Web, E-mail
Statusing Service, and the server-side components for P6 mobile)
Notes:
- You will need to configure E-mail Statusing Service separately. See
the P6 EPPM System Administration Guide. - P6 for iOS supports SSL (https) or HTTP only when it has a
certificate signed by a trusted authority. - P6 for Android requires SSL (https) when you are not using SSO
authentication. If you are using SSO authentication, you can use HTTP or HTTPs
protocols. HTTPS requires a valid certificate from an Android trusted
certifying authority.
4
P6 Professional Cloud Connect
Select the P6 Professional
Cloud Connect install option if you plan to
use P6 Professional with an EPPM Oracle database by connecting to a
remote service. The wizard sets up a remote method of access to connect to the
EPPM database and the P6 APIs. For more details on establishing the P6
Professional Cloud Connect database connection in P6 Professional, see the P6 Professional Installation and
Configuration Guide (P6 EPPM).
Notes:
- When you choose to install P6 Professional Cloud Connect, the wizard
will also install P6 Integration API (in remote mode) by default. - P6 Professional Cloud Connect does not apply to Microsoft SQL Server
database users.
4 P6 Integration API
About Installing and Configuring P6 EPPM
Note: The wizard installs the remote P6
Integration API. If you want to use the local-mode P6 Integration API, see the P6 EPPM Integration API Configuration Guide.
4
P6 EPPM Web Services
Configuring P6 EPPM
Use the P6 EPPM Configuration Wizard for
your initial configuration of P6 EPPM. The P6 EPPM Configuration Wizard is a
wizard that you can use to create a P6 configuration in Primavera P6
Administrator and to configure:
4 A connection to an Oracle or Microsoft
SQL Server database
4
A WebLogic domain
4
Connections to optional enabling technologies, such as
a content repository (Oracle Webcenter Content Core Capabilities (WCCC),
Microsoft Sharepoint, or CMIS-compliant repositories), BIP, and or BPM
By default, the P6 EPPM Configuration
Wizard runs automatically after you install your P6 EPPM applications. If you
need to manually launch the P6 EPPM Configuration Wizard, use eppmconfig.cmd (for Windows) eppmconfig (for Linux) from the P6
EPPM installation folder at
C:\P6EPPM_1\p6.
After you use the P6 EPPM
Configuration Wizard, use Primavera P6 Administrator to configure P6 EPPM
administration settings. For more information about Primavera P6 Administrator,
see the P6 EPPM System Administration
Guide.
Prerequisites for P6 EPPM
Configuration
Review and
complete the prerequisites before configuring any P6 EPPM applications.
Minimum Hard Disk Space
Installing the
entire P6 EPPM suite requires 1GB of hard disk space. If you configure the WebLogic
domain, that will require 1.75GB of hard disk space; it also requires 4GB of
available system memory.
Note: These numbers do not include the
space the database requires because that is dependent on how you configure it.
JDK Installation
WebLogic Server requires
that you have a Java Development Kit (JDK) installed on your machine. You must
manually download and install the required JDK. For a list of supported JDK
versions for P6 EPPM, see the Tested
Configurations document. As new releases of the software become available,
you can find them at
http://www.oracle.com/technetwork/java/archive-139210.html.
Setting an Environment Variable
for Java
After installing the JDK, you must set the
following environment variables to ensure the P6 EPPM installation scripts can
locate your Java libraries:
4
JAVA_HOME
4
PATH
Setting the Environment Variables in Microsoft Windows
To set the JAVA_HOME and PATH environment
variables in Microsoft Windows:
1)
Click Start, Control Panel, System, and then Advanced system settings.
2)
In the System Properties dialog box, on the Advanced tab, click Environment Variables.
3)
Add the JAVA_HOME environment variable:
- In the System Variables section, click New.
- In the Variable name field, enter JAVA_HOME.
- In the Variable value field, enter the location where the JDK software is
installed (for example, C:\Program Files\Java\<java_version>) - Click OK.
4)
Update the PATH environment
variable to include the location of the Java executable files:
- In the System Variables section, select the PATH variable, and click Edit.
- In the Variable value field, insert %JAVA_HOME%\bin; in front of all the existing directories. Do not delete any
existing entries; otherwise, some existing applications may not run. - Click OK.
5)
Exit the Control Panel.
Setting the Environment Variables with Unix or Linux
To set the
JAVA_HOME and PATH environment variables with Unix or Linux:
1)
Set the JAVA_HOME environment variable by typing the following command:
export
JAVA_HOME=<JDK_installation_path>
2)
Set the PATH environment
variable by typing the following command:
export PATH=$PATH:$JAVA_HOME/bin
Installing
WebLogic
You will need to
install WebLogic to deploy P6 EPPM. For supported versions, see the Tested
Configurations document.
For more information about how to install WebLogic, see the following URL:
http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html
Note: Oracle recommends that you install
Oracle Access Manager on a new WebLogic Middleware home.
If existing Middleware
applications are installed into the Middleware home (for example, BI Publisher
or Identity Management), Access Manager will fail to deploy.
Tips
After you finish
installing WebLogic, ensure you can run the startNodeManager.cmd (with Windows)
startNodeManager.sh (with UNIX or Linux) before installing P6 EPPM. If you
cannot run this file, contact your WebLogic administrator for help.
Installing
a Database
You can use either Oracle or Microsoft SQL
Server on your database server for P6 EPPM deployments. For more information
about supported database versions, refer to Tested
Configurations. You must install the database server before you can create
the P6 EPPM database.
If you are using an Oracle Database, you
must make sure to create a database with the Oracle Text option enabled. Oracle
Text supports the Oracle Database content repository by using standard SQL to
index, search, and analyze text and documents stored in the database, in files
and on the web. For more details, refer to the Oracle Database documentation.
If you are using
a Microsoft SQL Server Database, you must make sure that you enable FILESTREAM
before attempting your P6 EPPM installation or upgrade. For information about
how to enable FILESTREAM, refer to the Microsoft SQL Server documentation for
your version.
Notes:
- If you attempt to create a database using Oracle Database 12c, the
option to create a container database is enabled by default. If you do not want
to create a container database, deselect the Create As Container Database check box during the database creation
process. If you create a container database, you must also create a pluggable
database on which to install your P6 EPPM instance. - When using an Oracle database, you must install Oracle Multimedia,
along with these supporting components: Oracle JVM, Oracle XML DB (XDB), and
XML Developer's Kit (XDK). Unless you specify otherwise, all these components
automatically get installed with the latest versions of an Oracle database (11g
and later). If you chose not to install these components, you will need to
install them before you install P6 EPPM. See the Oracle Multimedia's User's Guide on the Oracle Technology Network
(OTN) for information on how to install these components. - Oracle Text is enabled by default.
- jobsvc.job_data_x is used to store XML data for XML import processes
using the Varbinary(Max) datatype. In order to support the Varbinary(Max)
datatype, you must enable FILESTREAM.
Grant
Privileges to the SYSTEM User
Before installing P6 EPPM, execute the
following steps:
1)
Navigate to the following
location, open the designated script in a text editor, and modify the schema
user reference to match your actual schema user name:
\scripts\install\PM_<release level>\manual_script_before_install.sql
You must apply grant
options to the SYSTEM schema user or a custom user associated with the Oracle
DBA role. If you plan to use a custom schema user, other than SYSTEM, to
execute steps which require a DBA role, then you must update the references to
SYSTEM in the script with the new custom schema user associated with the DBA
role.
2)
From the command line, execute:
sqlplus
sys/password@<db_tns_names_entry> as sysdba
3)
Go to
p6suite\database\scripts\install\PM_<release_level>, and execute manual_script_before_install.sql.
This script grants SELECT and EXECUTE
privileges with grant option to SYSTEM, or a custom DBA username if you prefer
to use one, for the following sys objects:
SELECT
4
sys.DBA_VIEWS
EXECUTE
4
sys.DBMS_DBMS_REPUTIL
4
sys.DBMS_DBMS_LOB
4
sys.DBMS_SQL
4
sys.DBMS_JOB
4
sys.DBMS_RANDOM
4 sys.V_$TRANSACTION
Note: For more information about the
listed sys objects, refer to the Oracle Database documentation.
Content
Repository Installation and Configuration
The Content
Repository allows users to collaboratively share and manage documents in P6.
For P6 EPPM users to utilize the enhanced document management functionality,
you must install either Oracle Webcenter Content Core Capabilities (WCCC) or a
CMIS-compliant content repository. Refer to the documentation included with
those applications for installation instructions.
Note: P6 supports clustering of the
Content Repository only when using WebLogic for the application server.
After you install the Content Repository
application and P6, perform the following tasks to complete the Content
Repository setup:
4
Configure the Content Repository server based on your
organization’s needs.
4
See Configuring WCCC to Work with P6
4
If you are using another CMIS-compliant repository, see
the installation instructions included with your content repository.
4
Enter the appropriate Database/Instance/Content
Repository Primavera P6 Administrator settings. You can use the P6 EPPM
Configuration Wizard to enter your settings. See Using the Content Repository
Selection Screen (on page 29) for detailed information about these
settings.
For more
information about installing and configuring a content repository for P6 EPPM,
refer to the P6 EPPM Content Repository
Configuration Guide.
BI Publisher Installation
Consult BI
Publisher documentation for installation instructions. For complete overview
information about BI Publisher, go to the following web site:
http://www.oracle.com/technetwork/middleware/bi-publisher/documentation/index.html.
Workflows
Repository Installation
The Workflows
Repository helps users to keep track of project initiations in P6. For P6 users
to utilize the project initiation functionality, you must install the supported
Workflows Repository application, BPM. Refer to the documentation included with
the Oracle BPM application for installation instructions.
Installing the Oracle MDS Schema for
BPM
If you are using
BPM, you must install the Oracle MDS
schema using the Repository Creation
Unit (RCU) on a separate database instance. See the Tested Configurations document for supported versions.
Modifying the P6 Environment for
BPM
To configure BPM with P6:
1) Create a new
directory on the host where P6 is running. For example, P6BPMConnector/P6 and P6BPMConnector/BPM.
In the P6 media pack Tools\BPM
Connector\12c subfolder, locate the prm-bpm-connector-12c-v1.0.jar
1)
Copy the connector file listed
above to the P6BPMConnector/P6
folder you created.
Determine the location of the BPM
installation that you are using to integrate with P6. If you have multiple SOA
Suite installations, ensure that you determine the location of the specific
installation that you are integrating with P6.
2)
Copy all the supporting jars
from the BPM installation that you are using to integrate with P6 to the P6BPMConnector/BPM folder you created.
Their default locations are listed: 4 <Oracle_Home>\soa\soa\modules\oracle.soa.fabric_11.x.x\bpm-infra.j
ar
4
<Oracle_Home>\soa\soa\modules\oracle.soa.workflow_11.x.x\bpm-servi
ces.jar 4
<Oracle_Home>\soa\soa\modules\oracle.soa.fabric_11.x.x\fabric-runt
ime.jar
4
<Oracle_Home>\oracle_common\modules\oracle.jmx_12.x.x\jmxframework
.jar
4
<Oracle_Home>\oracle_common\modules\oracle.jmx_12.x.x\jmxspi.jar
4
<Oracle_Home>\soa\bpm\modules\oracle.bpm.mgmt_11.x.x\oracle.bpm.bp
mn-em-tools.jar
4
<Oracle_Home>\soa\soa\modules\oracle.soa.mgmt_11.x.x\soa-infra-mgm
t.jar
4
<Oracle_Home>\wlserver\server\lib\wlclient.jar
4
<Oracle_Home>\oracle_common\modules\oracle.xdk_12.x.x\xml.jar
4
<Oracle_Home>\oracle_common\modules\oracle.xdk_12.x.x\xmlparserv2.
jar
4
<Oracle_Home>\soa\soa\modules\oracle.soa.fabric_11.x.x\tracking-ap
i.jar
4 <Oracle_Home>\soa\soa\modules\oracle.rules_11.x.x\rulesdk2.jar
Note: The jars must be from the same BPM
installation that will be integrated with P6.
3) Edit the weblogic.policy file:
- Locate the weblogic.policy file
in one of the following locations:
In Windows: <Oracle_Home>/wlserver/server/lib In Linux: <Oracle_Home>/wlserver/server/lib
- Add the following information in weblogic.policy file and restart
the P6 application server.
grant
codeBase "file:<full path to BPM support JAR directory>/*"
{ permission java.security.AllPermission;
};
For example :
grant codeBase
"file:C:/oracle/bpm12XX/*" { permission java.security.AllPermission;
};
or
grant codeBase
"file:/home/oracle/bpm12XX/*" { permission
java.security.AllPermission;
};
- Save and close the file.
- Restart the P6 application
server.
Installing IAIK-JCE
IAIK-JCE is a Java Cryptography Extension
that has a set of APIs and can implement cryptographic functionality. It is
used for supporting additional security functionalities to the JDK. IAIK-JCE
libraries can be used to support higher level of encryption while
storing/transmitting sensitive information (for example, passwords) in P6 EPPM.
IAIK-JCE is installed when
you install P6 EPPM. To allow the P6 EPPM installer to recognize and install
IAIK-JCE, you must modify your existing java.security settings and copy the iaik_jce.jar file to the correct location in <Java_Home>.
To prepare IAIK-JCE for installation:
1)
Navigate to the following
URL:
http://jce.iaik.tugraz.at/sic/Products/Core-Crypto-Toolkits/JCA_JCE
2)
Download and extract iaik_jce.zip locally. See Tested Configurations for the supported versions of
IAIK-JCE.
3)
Navigate to the lib-signed
folder and then copy iaik_jce.jar to <Java_Home>/jre/lib/ext.
4)
Navigate to <Java_Home>/jre/lib/security
and then add the following to java.security.
security.provider.11=iaik.security.provider.IAIK
Note: If the number '11' is being used
by another entry, use the next available number.
5)
Save and then close the file.
6)
Complete the instructions in
the following topic:
Setting an Environment Variable for IAIK-JCE (on page 17)
Setting an Environment Variable for
IAIK-JCE
Setting the Environment Variables in Microsoft Windows
To set the JAVA_TOOL_OPTIONS
environment variables in Microsoft Windows:
1)
Click Start, Control Panel, System, and then Advanced system settings.
2)
In the System Properties dialog
box, on the Advanced tab, click Environment
Variables.
3)
Add the JAVA_TOOL_OPTIONS environment variable:
- In the System Variables
section, click New. - In the Variable name field,
type JAVA_TOOL_OPTIONS. - In the Variable value field,
type the following:
-Dprimavera.encryptor.provider="IAIK"
- Click OK.
4)
Exit the Control Panel.
Setting the Environment Variables with Unix or Linux
To set the
JAVA_TOOL_OPTIONS environment variables with Unix or
Linux:
1) Set
the JAVA_TOOL_OPTIONS environment variable
by typing the following command: export
JAVA_TOOL_OPTIONS=-Dprimavera.encryptor.provider="IAIK"
About the P6 EPPM Installation
Wizard
Before you run the installation wizard,
ensure that you have read the Prerequisites for P6 EPPM Configuration
(on page 7).
You can install the following with the
installation wizard:
4 P6
4 P6 Professional Cloud Connect (to connect to an EPPM Oracle database
and P6 APIs using a remote method of access)
Note: When you choose to install Cloud
Connect, the wizard will also install P6 Integration API (in remote mode) by
default.
4 P6 Integration API (remote mode only)
4 P6 EPPM Web Services
4
P6 Team Member (includes P6 Team Member Web and E-mail
Statusing Service)
Once you have completed
your installation, the P6 EPPM Configuration Wizard will appear. When the
configuration wizard appears, you will have the choice to configure your
database, WebLogic server, and extra application settings.
In This Section
Installing Your
P6 EPPM Suite
................................................................................
18
Where to Go From
Here - Pre Configuration Wizard ...............................................
21
About the P6 EPPM Installation Wizard
Your P6 EPPM
Suite
To install your P6 EPPM applications:
1)
Download the Primavera P6 Enterprise Project Portfolio
Management <release_level> for <platform> folder and extract
the contents.
2)
Go to the location where you
extracted the contents and run one of the following depending on your system
type:
4 If you are
installing on a Microsoft Windows system, navigate to the
P6_R<release_level>\Disk1\install
directory, and then double-click on the setup.exe file.
4
If you are installing on a non-Microsoft Windows
system, type the following command:
cd
P6_R<release_level>/Disk1/install chmod
755 runInstaller chmod
755 unzip
./runInstaller
3)
On the Welcome screen, click Next.
Note: Click Next on each wizard screen to advance
to the next step.
4)
On the Specify Home Details screen, complete the following:
- In the Name field, enter a name for the installation.
- In the Path field, browse to the location of the P6 EPPM home folder (for
example, C:\P6EPPM_1).
5)
On the Available Product Components screen, select each component you want
to install. Alternatively, if you are reinstalling your P6 EPPM applications
for an upgrade, select the components that have Reinstall as the value in the Install Status column.
Note: You can choose Select All if you
want to install all P6 EPPM applications.
- If you are installing P6, select
P6. - If you are connecting P6
Professional with an P6 EPPM Oracle database, select P6 Professional Cloud Connect. This installation option is
applicable to only Oracle database users. The wizard will also install P6
Integration API (in remote mode) by default.
Note: After running the P6 EPPM Configuration wizard, the Configuration
Complete screen will display the default URL generated for P6
Professional Cloud Connect. This
URL (case-sensitive) must be provided to P6 Professional users to enable them
to setup and configure a new database connection to the P6 Pro Cloud Connect
server in the P6 Professional database configuration utility.
For more details on establishing the
P6 Pro cloud connect database connection in P6 Professional, see the P6 Professional Installation and
Configuration Guide (P6 EPPM).
- If you are installing P6
Integration API, select P6 Integration
API.
Notes:
- The wizard will install the remote version of P6 Integration API.
- If you need to install the local version of P6 Integration API or
want to install the client-side packages (which include libraries and
documentation for remote mode), see the
P6 EPPM and P6 Professional Integration API Programming Guide.
- If you are installing P6 EPPM
Web Services, select P6 Web Services.
The wizard will also install the demo applications for P6 EPPM Web Services. - If you are installing P6 Team
Member, select P6 Team Member. This
will install the files necessary for P6 Team Member Web, E-mail Statusing
Service, and the server components for P6 mobile.
Notes:
- If you want to use E-mail Statusing Service, see the P6 EPPM System Administration Guide when
you have completed installing and configuring your other applications. - P6 for iOS supports SSL (https) or HTTP only when it has a
certificate signed by a trusted authority. - P6 for Android requires SSL (https) when you are not using SSO
authentication. If you are using SSO authentication, you can use HTTP or HTTPs
protocols. HTTPS requires a valid certificate from an Android trusted
certifying authority.
6)
On the Specify JDK Home screen, type or browse to the location where JDK
is installed.
7)
On the Summary screen:
- Verify that all of the
components that you want to install are listed. b. Click Install.
Note: Ignore the Configuration Assistants screen when it appears. It will close
itself.
8)
On the End of Installation screen, click Exit.
Note: The P6 EPPM Configuration Wizard
will appear if the installation was successful.
9)
In the Exit dialog box, click Yes.
10) If you want to use the P6 EPPM Configuration Wizard to configure
your P6 EPPM, WebLogic, and other applications, continue to About
the P6 EPPM Configuration Wizard (on page 21). If you want to configure
your applications manually, click Cancel
to exit the configuration wizard. See Where to Go From Here - Pre Configuration
Wizard to see what guides you will need to configure your applications
manually.
About the P6 EPPM Installation Wizard
Where to Go From
Here - Pre Configuration Wizard
The configuration
process provides you with several options to configure your applications to
work with P6 EPPM. The following sections describe your options.
Using the P6 EPPM Configuration
Wizard To Configure P6 EPPM
Oracle recommends
you use the P6 EPPM Configuration Wizard to configure P6 EPPM, its
applications, and WebLogic. With this option, you can install or upgrade your
database, deploy your P6 EPPM applications in WebLogic, and configure a content
repository, BI Publisher, and BPM to work with P6. Continue to About
the P6 EPPM Configuration Wizard (on page 21) to use this option.
Manually Configuring Your
Applications
Database
You can manually install
or upgrade your database. If you want to install or upgrade your database
manually, you can still use the wizard to deploy your P6 EPPM applications in
WebLogic and configure a content repository, BI Publisher, and BPM to work with
P6.
If you want to install or upgrade your
database manually, see the P6 EPPM
Installation and Configuration Guide for your database.
P6 EPPM Applications
You can manually deploy your P6 EPPM
applications in WebLogic. Depending on which applications you are using, use
the following:
4 P6 Server Configuration Guide
4 P6 EPPM Team Member Configuration Guide
4 P6 EPPM Web Services Configuration Guide
4 P6 EPPM Integration API Configuration Guide
Additional Applications
You can also use the Primavera P6
Administrator to connect additional applications to P6. Depending on your
application, use the following:
4 P6 EPPM BI Publisher Configuration Guide
4 P6 EPPM BPM Configuration Guide
4 P6 EPPM Content Repository Configuration Guide
4 P6 EPPM Oracle Identity Manager Configuration Guide
4 Primavera Oracle Access Manager Configuration Guide
4 Primavera Oracle Enterprise Manager Configuration
Guide
About the P6 EPPM Configuration
Wizard
The P6 EPPM Configuration Wizard will allow
you to:
4 Install or upgrade your database.
4
Deploy your P6 EPPM applications in WebLogic and setup
managed servers.
4
Configure BI Publisher, BPM, and your content
repository (WCCC or CMIS) with P6.
Use the P6 EPPM Configuration Wizard to
configure your suite. Before running the configuration wizard, consider the
following:
4 You must be on an Oracle server or
Microsoft SQL Server.
4 You must have a JDK installed. See the Tested Configurations document for information on supported
versions.
Note: To manually launch the P6 EPPM
Configuration Wizard, use eppmconfig.cmd
(for Windows) eppmconfig.sh (for
UNIX / Linux) from the P6 EPPM installation folder at <P6
EPPM_home>\P6EPPM_1\p6.
On the Welcome
screen, click Next if you want
to use the wizard to configure your suite. Click Cancel if you want to configure your applications manually.
In This Section
Configuring Your
Database .....................................................................................
22
Configuring Your
WebLogic Server with P6 EPPM ..................................................
26
Connecting
Applications to P6 EPPM ......................................................................
28
Completing Your
P6 EPPM Installation
................................................................... 34
Configuring Your Database
You must either
install or upgrade your database or already have the latest database installed
to use this wizard. If you want to manually install or upgrade your database,
leave the P6 EPPM Configuration Wizard open and go to the Manually Installing the P6 EPPM Database or Manually Upgrading the P6 EPPM Database guides. If you want to
automatically install or upgrade your database, continue to the next section.
Using the Database Configuration
Screen
On the Database Configuration screen:
1)
Choose one of the following:
4
Select Create a
new P6 EPPM database if you are creating a new database.
Select the Install Sample Projects option if you want to include sample
project data in a non-production database. If you do not select the Install
Sample Projects option, the P6 EPPM database loads empty data in a secure state
and includes only the most basic information needed to run.
4
Select Upgrade
an existing P6 EPPM database if you are upgrading your database.
4 Select Connect to an existing
P6 EPPM <release_level> database if you already installed a database
and want to configure your applications with it.
Note: Before you install sample data,
you should ensure sample data will not be audited. To disable Unified
Auditing:
- Open command prompt (if
Windows) or terminal (if UNIX) and connect to your database using the following
command:
sqlplus sys/password@dbservicename as sysdba
- Execute the following commands
in the same window:
noaudit policy ORA_SECURECONFIG; noaudit policy ORA_LOGON FAILURES;
- Close the window.
2)
Click Next.
Using the Database Type &
Connection Screen
On the Database Type & Connection screen:
1)
For the Database Type option, choose one of the following:
4 Oracle
4 Microsoft SQL Server.
2)
In the Database Host Address field, enter the server machine name or IP
address where you installed the database.
3)
In the Database Host Port field, enter or verify the port number for your
database.
The default for Oracle is 1521.
The default for Microsoft SQL Server is
1433.
4)
In the DBA (when installing or upgrading) or Public (when connecting to an upgraded database) Username field, enter or verify your
user name.
The default username for Oracle is
'system'.
The default username for Microsoft SQL
Server is 'sa'.
The default public username is 'pubuser'.
5)
In the DBA (when installing or upgrading) or Public (when connecting to an upgraded database) Password field, enter the password to
log in to the database.
6)
In the Database Name field:
- Enter the name of your
database. - Select SID (for example, orcl) or Service
(for example, orcl.us.oracle.com) based on the database you installed.
7)
Click Next.
Using the Create Users Screen
On the Create
Users screen:
1)
In the Database Users section, specify the user names and passwords for
these users:
-
Administrative (Oracle only) is the
schema owner for all P6 EPPM data. -
Privileged has read and write access to
most P6 EPPM data. -
Public has restricted access to the
database. -
Background (Oracle only) executes
background processes. -
Reporting is the PX Reporting user who owns tables and views for reporting
data.
Caution: Use a unique name for all your
user names; do not use duplicate names. For example, do not enter privuser as
the administrative user name or pubuser as your PX reporting user name.
Repeating user names will cause conflicts.
Notes:
- A red X will appear if the Password
and Confirm Password fields do not
match. A green check will appear when the two fields match. - P6 EPPM does not support passwords with multi-byte characters.
- Oracle recommends using strong passwords. Strong passwords in P6
EPPM contain between 8 and 20 characters and at least one numeric and one alpha
character. To further strengthen the password, use a mixture of upper and lower
case letters. - Do not use special characters in the database name, privileged user,
public user, or PX reporting user name, for example: { } [ ] : ; < > , .
? ! @ # $ % ^ & * ( ) - _ | / \ ~ `
2)
In the Application User section, enter the P6 EPPM application
administrative user name and password. By default, the application
administrative user will receive Admin Superuser access rights to all
applications.
Notes:
- A red X will appear if the Password
and Confirm Password fields do not
match. A green check will appear when the two fields match. - Oracle recommends using strong passwords. Strong passwords in P6
EPPM contain between 8 and 20 characters and at least one numeric and one alpha
character. To further strengthen the password, use a mixture of upper and lower
case letters.
3)
Click Next.
Configuring
Your WebLogic Server with P6 EPPM
In this section,
you will configure the P6 EPPM applications you installed with the installation
wizard. The P6 EPPM Configuration Wizard will set up managed servers and deploy
your P6 EPPM applications in the WebLogic domain that you installed.
Using the P6 Configuration Settings
Screen
On the P6 Configuration Settings screen:
1)
Do one of the following:
4
If a P6 configuration does not exist, in the Create a new configuration field, enter
your new configuration name.
4 If you already created a configuration, choose it from the Use an existing configuration option,
or create a new configuration.
Note:
- If you are upgrading from a previous version of P6 against the same
database, choose the option to create a new configuration. This is necessary to
accommodate new configuration settings. See the P6 EPPM System Administration Guide for more information about
configurations and the Primavera P6 Administrator. - You can edit the settings for this configuration through the
Primavera P6 Administrator.
2)
Click Next.
Using the Application Server
Configuration Screen
On the Application Server Configuration screen:
1)
Select the Configure WebLogic option.
Notes:
§ If
you do not want to configure WebLogic right now, ensure the Configure WebLogic option is clear and
click Next to continue to the next
screen. If you want to configure WebLogic manually, refer to the P6 Server Configuration Guide.
2)
Choose one of the following:
4
Create a new
WebLogic domain if you are creating a new domain.
4 Use an existing WebLogic domain if you already have a WebLogic domain.
Note: This is the domain where the
wizard will create your managed servers for each application.
3)
(Optional) Select Deploy Oracle WSM Policy Manager if you
are integrating with BPM and or select Configure
WSM Policy for P6WebServices if you are configuring OWSM authentication for
P6 EPPM Web Services. For more information, refer to the P6 EPPM Web Services Programming Guide.
Note: By default, the configuration
wizard deploys P6 EPPM Web Services with the oracle/wss_username_token_server_policy
OWSM policy. This policy does not contain message protection and encryption and
needs additional configuration to enable either. Refer to Adding Additional Policies to Oracle Web Services Manager in the P6 EPPM System Administration Guide for
details on configuring additional OWSM policies.
4)
Click Next.
Using the Configure WebLogic Screen
On the Configure WebLogic screen:
1)
In the WebLogic Server Home field, verify or choose the location of your
WebLogic home. For example, C:\Oracle\Middleware\Oracle_Home.
2)
In the Domain Home field, enter or verify your WebLogic domain home name.
3)
In the Port field, enter or verify the port number that your WebLogic
domain is using. The default port is 7001.
4)
In the Administration Username field, create or verify your administrative
user name for the WebLogic domain you defined on the previous screen.
5)
In the Password and Confirm
Password fields, enter the password for your administrative username.
6)
Click Next.
Using the Configure Component
Schema Screen
On the Configure Component Schema screen:
Notes:
- This screen will only appear if you selected the Deploy Oracle WSM
Policy Manager option above. If you did not select the option, the wizard will
skip this screen. - You must create the required schema for BPM before you deploy the P6
EPPM Configuration Wizard. For more information about the schema required for
BPM, see the Oracle Fusion Middleware
Installing and Configuring Oracle SOA Suite and Business Process Management
guide.
On the Component Schema screen:
1)
For the Configure Component Schema Connection option, choose Oracle or Microsoft SQL Server.
- If you are using Oracle
Database, select SID or Service.
2)
Do the following for the schema
in the Component Schema fields:
- In the Host Name field, enter the server machine name or IP address where
you installed the database. - In the Port field, enter or verify the port number for your database.
The default for Oracle is 1521.
The default for Microsoft SQL Server is
1433.
- In the Schema Owner field, enter or verify the name of the schema owner.
- In the Password field, enter the password to log into the database.
- In the SID/Service field, enter the SID (for Oracle 11g) or Service (for
Oracle 12c) based on the database you installed.
3)
Click Next.
Connecting Applications to P6
EPPM
If you installed
a content repository, BI Publisher, or BPM, you can use the P6 EPPM
Configuration
Wizard to configure these applications to work with P6 EPPM. The settings in
this wizard correspond to the settings in the Primavera P6 Administrator.
Notes:
- You can configure the settings for these applications later in the
Primavera P6 Administrator. See Manually Configuring Your Applications
(on page 21) for the guides you will need. - If you are using an existing P6 configuration, the wizard will skip
the content repository, BI Publisher, and BPM screens.
About the P6 EPPM Configuration Wizard
Using the Content Repository Selection
Screen
On the Content Repository Selection screen:
1)
Select the Connect to a Content Repository option.
Note: If you would rather configure your
content repository manually or do not have a content repository installed,
ensure the Connect to a Content
Repository option is clear and click Next.
See the P6 EPPM Content Repository
Configuration Guide for more information.
2)
Choose Oracle Webcenter Content Core Capabilities, CMIS, or Oracle Database.
Notes:
- If you select Oracle Database, you will not need to configure your
database as a content repository in the P6 EPPM Configuration Wizard. - If you want to configure Microsoft SharePoint with P6, you must
configure it with your CMIS-compliant content repository and then select CMIS for this step. See your
CMIS-client content repository documentation for information about how to
configure your CMIS-complient content repository with Microsoft SharePoint.
3)
Click Next.
Using the Content Repository
Configuration Screen for Oracle Webcenter Content Core Capabilities
On the Content Repository Configuration screen:
Note: Ensure the settings you entered in when you configured the content
repository match the settings you enter below.
1)
In the Host field, enter the machine name or IP address of the content
repository server.
2)
In the Port field, enter the IntradocServerPort number of the content
repository server. By default, this is 4444. To find the port number:
- Navigate to WCCC_Home\ucm\cs\config\.
- Open the config.cfg file.
- Find the IntradocServerPort
line, which contains the port number.
3)
In the Oracle Home field, enter the path to the P6 EPPM content repository
files on the content repository server, as specified when you configured your
content repository. This setting is required.
Example:
//Contribution Folders/Production/Oracle
Primavera/
4)
In the Oracle Security Group
field, enter the name of the Security Group assigned to the document folder
created in WebCenter for P6 EPPM documents, as specified when you configured
the content repository.
5)
In the Oracle Security Account field, enter the name of the Security
Account for P6 EPPM documents, as specified when you configured the content
repository.
If you did not enable security accounts,
leave this setting blank.
6)
In the Oracle Document Type field, enter the document type for P6 EPPM
documents, which can be either an existing document type or a new one, as
specified when you configured the content repository.
For example:
Enter the Document Type as Document.
7)
In the Metadata Prefix field, enter the prefix added to P6 EPPM metadata
fields, as specified when you configured the content repository.
8)
In the Admin User field, enter the user name with administrative
privileges, as specified when you configured the content repository. This
setting is required.
9)
In the Authentication Mode field, enter authentication mode used to access
the content repository server. P6 EPPM users cannot access content repository
functions if you do not configure this setting.
If you choose
"Multiple User", all P6 EPPM content repository-related user names
must match the equivalent content repository user name. For example, a P6 EPPM
user named "Joe" must have an equivalent user named "Joe"
in the content repository.If you choose "Single User", the
administrative user specified in the setting above must have access to all
appropriate Security Groups to browse to documents outside of the P6 EPPM home
folder. 10) Click Next.
About the P6 EPPM Configuration Wizard
Using the Content Repository
Configuration Screen for CMIS
On
the Content Repository Configuration
screen:
1)
In the Login Name field, enter the user name for your content repository.
2)
In the Password field, enter the password for the user name you entered
above.
3)
In the Authentication Mode
field, enter authentication mode used to access the content repository server.
P6 EPPM users cannot access content repository functions if you do not
configure this setting.
If you choose
"Multiple User", all P6 EPPM content repository-related user names
must match the equivalent content repository user name. For example, a P6 EPPM
user named "Joe" must have an equivalent user named "Joe"
in the content repository.
If you choose "Single User", the
administrative user specified in the setting above must have access to all
appropriate Security Groups to browse to documents outside of the P6 EPPM home
folder.
4)
In the Repository Name field, enter the name for your content repository.
5)
In the Document Home field, enter the location of your documentation home
where you want to store P6 documents.
6)
In the Web Service URL field, enter the URL for your web services
home.
Using the BI Publisher Screen
On the BI
Publisher screen:
1)
Select the Connect to BI Publisher option.
Note: If you would rather configure BI
Publisher manually or do not have BI Publisher installed, verify the Connect to BI Publisher option is clear
and click Next. See the P6 EPPM BI Publisher Configuration Guide
for more information.
2)
In the Server URL field, enter the URL used to connect to the BI Publisher
web service to P6. For example,
http://serverIP:port/xmlpserver/services/PublicReportService
3)
In the Version field, enter the version of BI Publisher that you want to
integrate with P6.
4)
In the Folder Paths field, enter the relative path to the BI Publisher P6
reports folder where P6 will search for reports.
Example format (the forward slash is
required):
/P6REPORTS
Notes:
- You can find the relative path (for example, /P6Reports) in the following folder:
- %weblogic_home%\user_projects\domains\bifoundation_
domain\config\bipublisher\repository\Reports
5)
In the Admin Username field, enter a BI Publisher web services user name
with administrative privileges (for example, PxRptUser).
6)
In the Password field, enter the password for the administrative user
name.
7)
In the Personal Folders field, select the option (true) to enable personal
folders per user. If you do not want to use personal folders, leave the option
clear. Users have their own personal folders where they can store their
objects. Only the user who created and saved the content in the folder can
access the folder.
8)
In the Scrub Username field, select the option (true) to enable the
setting or leave it clear (false) to ensure it is disabled.
This setting controls whether special
characters (non-alphanumeric) are removed from the user name when connecting to
BI Publisher. The default is 'false,' meaning special characters will not be
removed.
If you are using the P6 EPPM Extended
Schema for BI Publisher reporting, leave the setting as false.
If you are
using the P6 ODS Schema for BI Publisher reporting, change the setting to true.
Setting the value to true will allow the
user’s security context (user name) to format properly before it goes to BI
Publisher. This allows reporting queries to perform against the ODS tables.
9)
In the Cache Timeout field, enter how long cached report definitions
should appear. The default is 1d.
10)
Click Next.
About the P6 EPPM Configuration Wizard
Using the BPM Workflows Screen
On the BPM
Workflows screen:
1)
Select the Connect to BPM option.
Note: If you would rather configure BPM
manually or do not have BPM installed, ensure the Connect to BPM option is clear and click Next. For more information, see the 0P_ProdName_P6_Suite> BPM Configuration Guide.
2)
In the Connector file location field, enter the full path (including the
file name) where you copied the connector files. For example:
c:/Software/BPMJars/eppmjars/prm-bpm-connector-12c-v1.0.jar.
3)
In the BPM library path field enter the directory where you copied all the
jars.
Notes:
- To satisfy these requirements, this admin setting can contain
multiple path elements. You must separate multiple path elements with a
semicolon. For example: C:\Software\BPMJars;C:\Software\BPMJars - If the above settings are incorrect or the BPM jar files are
incomplete, you will see an error message when you try to configure BPM. Verify
that your settings and jar files are correct.
Using the BPM Configuration Screen
On the BPM
Configuration screen, add the following settings:
1)
In the bpm.user field, enter the BPM 11g user with administrative access
to BPM.
2)
In the bpm.password field, enter the password for the user.
3)
In the bpm.t3.url field, enter the T3 URL for your Oracle SOA
configuration. For example: t3://<host_name>:<port>/soa-infra
4)
In the bpm.security.realm field, enter the name of the security realm used
by BPM. This is jazn.com by
default.
5)
In the bpm.soap.url field, enter the URL for the SOAP services. Usually
this URL takes the form of http://<host_name>:<port>.
6)
In the bpm.workspace.url field, enter an address in the form of http://<host_name>:<port> that indicates where the BPM Workspace application is hosted.
Note: The host can be an IP address or a
host name such as a machine name.
7)
In the bpm.partition field, enter the name of the SOA partition containing
the BPM composite applications you would like to use in P6. The default
partition name is default.
8)
Click Next.
Completing Your P6 EPPM
Installation
Once you have finished
entering your configuration settings, you can verify all the applications you
configured. Once you click Configure,
the wizard will setup your P6 EPPM environment and start WebLogic. After the
wizard finishes, you will be able to login and use all of your applications.
Using the Configuration Review
Screen
On the Configuration Review screen:
1)
Verify all your configuration
settings are correct.
2)
Click Next.
3)
On the Acknowledgment dialog box, click OK to confirm you have read the information.
If you are upgrading from P6 8.2 or lower
version and have been using a content repository configured with P6, you will
need to run the Document Migration
Utility located in P6 home after the installation completes.
4)
On the Start Configuration? dialog box, click Yes to confirm you want the wizard to configure your applications.
Click No if you do not want to continue with
the configuration.
About the P6 EPPM Configuration Wizard
Using the Configuration Progress
Screen
On the Configuration
Progress screen, the wizard will let you know when each item is configured.
The configuration process will take several minutes. When the configuration is
done, all of your applications will have a green check next to them.
The configuration wizard will do any of the
following based on the selections you made in the previous screens:
4 Create your database.
4 Create or upgrade the Primavera
Configuration.
4 Create a WebLogic domain.
4
Create bootstrap files for your applications.
4 Create managed servers and deploy the
applications you installed into them.
4 Configure integrations with other
servers for the content repository, BI Publisher, and BPM.
4 Configure URLs to the P6 Help in the
Primavera P6 Administrator.
4 Create Start menu items for P6 EPPM
URLs and start/stop scripts.
4
Sets your parameters in WebLogic.
For example, it will set
your bootstrap variables and Java heap settings for you. This will connect P6
to your other P6 EPPM applications and ensure that your environment is set up
for optimal performance.
When the configuration wizard completes
this process:
1)
Note the location of the log
file. Use the log file to view what happened during setup and see what went
wrong if an error occurred.
2)
Click Next.
Using the Configuration Complete
Screen
On the Configuration Complete screen:
1) Click any link to go to the
default URL for each of your applications. 2) Click the Save Configuration button.
Note: The HTML file you save contains
the default URLs and other information for your P6 EPPM applications.
- Choose a location where you
want to store your HTML file (Oracle recommends using the P6 EPPM directory you
created when you installed your applications). - In the File Name field, verify or enter a name for your configuration HTML
file. c. Click Save.
d.
On the Configuration Saved Successfully
dialog box, click OK. 3) Click Finish.
Note: Once you click Finish, the wizard will start WebLogic
for you so you can begin using your applications instantly.
Default Locations Created by the
Wizard
The configuration wizard creates the
following defaults.
Oracle Primavera EPPM Home
4
C:\p6eppm_1\
4 Holds all your P6 EPPM applications
folders and files
Note:
- The local drive location is the default the wizard provides. If you
changed it, it will be noted in the HTML file you saved in Using the Configuration Complete
Screen (on page 35). - You will need to enter your IP address where it says 'server' in the
URLs below.
4 WebLogic Administration Console
Port: 7001
URL: http://server:7001/console
4 P6
Port: 8203
URL: http://server:8203/p6
4 P6 Integration API
Port: 8205
URL: http://server:8205/PrimaveraAPI
4 P6 EPPM Web Services
Port: 8206
URL: http://server:8206/p6ws/services
4
P6 mobile Port: 8207
URL:
http://server:8207/p6tmws
Note: This is the URL you will enter
when you sign into the P6 mobile app on your mobile device. The actual URL will
not work in a browser.
4 P6 Team Member Web
Port: 8207
URL: http://server:8207/p6tmweb
4 E-mail Statusing Service
File
Name: p6tm-email-service.zip
Default
Location: C:\P6EPPM_1\tmws or /usr/P6EPPM_1/tmws
Note: You will have to unzip the file and configure the email services
before you can update status through email. See the P6 EPPM System Administration Guide.
4 P6 Professional Cloud Connect
About the P6 EPPM Configuration Wizard
Port: 8208
URL:
http://server:8208/p6procloudconnect
Note: This URL (case-sensitive) must be
provided to P6 Professional users to enable them to setup and configure a new
database connection to the P6 Pro Cloud Connect service in the P6 Professional
database configuration utility.
For more details on establishing the
P6 Pro Cloud Connect connection in P6 Professional, see the P6 Professional Installation and Configuration Guide (P6 EPPM).
Default Java Heap Settings Created
by the Wizard
The Java Heap settings
will provide most environments with optimal performance. Do not change them
unless you know your environment requires different settings. Xms is the
initial heap size. Xmx is the maximum heap size.
4 WebLogic Administration Console Java Heap
-Xms512m -Xmx1024m
4 P6 Java Heap
-Xms512m -Xmx1024m
4 P6 ProfessionalCloud Connect
-Xms1024m -Xmx1024m
4 P6 Integration API Java Heap
-Xms256m -Xmx512m
4 P6 EPPM Web Services Java Heap
-Xms256m -Xmx512m
4 P6 mobile Java Heap
-Xms256m -Xmx512m
4 P6 Team Member Web Java Heap
-Xms256m -Xmx512m
Database Administration
Read this chapter to learn
how to configure the job scheduler supplied by your RDBMS, how to optimize
performance of your P6 EPPM database, and how to configure the PRMAUDIT feature
to monitor edits, deletions, and additions to the databases.
In This Section
Implementing
Transparent Data Encryption on the P6 EPPM Database ................. 38
Background
Processes and Clean Up in P6 EPPM
................................................. 39
PX Tables Clean
Up Procedure ...............................................................................
40
RDBMS Scheduler
Configuration
............................................................................ 41
Database Settings
Table .........................................................................................
42
Reading Setting
Values
...........................................................................................
43
Writing Setting
Values .............................................................................................
44
Tracking
Background Job Execution
....................................................................... 45
SYMON (System
Monitor) Procedures ....................................................................
46
DAMON (Data
Monitor) Procedures
........................................................................ 51
Oracle Database
Performance
................................................................................
61
Safe Deletes
............................................................................................................
61
PRMAUDIT Auditing
................................................................................................
62
Using the Data Pump Utility
.....................................................................................
69
Implementing Transparent Data
Encryption on the P6 EPPM Database
Transparent data
encryption (TDE) is an Oracle Advanced Security feature that is used for Oracle
Database encryption. TDE provides strong protection from malicious access to
database files by encrypting data before it is written to storage, decrypting
data when being read from storage, and offering built-in key management.
For more information about TDE, refer to
http://www.oracle.com/technetwork/database/options/advanced-security/index-099011.html.
For
TDE implementation instructions, refer to the readme.txt file in the P6 EPPM physical media or download at database\scripts\common\tde.
Database Administration
Background
Processes and Clean Up in P6 EPPM
Because clean up tasks can
be resource intensive and time consuming, in P6 EPPM, these tasks are initiated
by two background jobs that run on the database server using the background job
processes user name:
4
SYMON (System Monitor), responsible for running
procedures that take less than a few seconds to complete.
4
DAMON (Data Monitor), responsible for running
procedures that take longer than a few seconds to complete.
Both of these jobs are pre-configured with
default settings. Since the default settings are optimal for most environments,
you generally do not need to tune them. However, if you need to optimize your
background process further, you can use the background job processes user to
change the settings to tune the behavior of the background jobs for specific
environments.
The background process will:
4 Update the settings table with a record
each time a job runs.
4
Update the settings table with a HeartBeatTime record
for both the SYMON and DAMON processes. The background processes regularly
refresh the record to indicate that they are still running.
When you initiate background jobs:
4 Execute the stored procedure INITIALIZE_BACKGROUND_PROCS.
4 Locate the logs
of background process activity in BPLOGS
and SETTINGS tables within the Primavera
database.
PX Tables
Clean Up Procedure
To avoid operational problems for P6, PX
table entries are not automatically deleted when you delete data from P6
tables. You can use the following clean up procedure to clear the obsolete
entries in PX tables.
1) Run the
CLEAN_PX_DELETE stored procedure to purge obsolete entries in the PX tables:
For Oracle:
BEGIN
CLEAN_PX_DELETE();
END;
For a Microsoft SQL Server database:
USE [ddname]
GO
DECLARE @return_value int
EXEC @return_value =
[dbo].[CLEAN_PX_DELETE]
SELECT 'Return Value' = @return_value GO
where ddname is the is your admin user name
Note: You can run this procedure any time you want or you can run it as
a database background job and schedule a specific time for it to run.
2) To delete
batch size and max delete from each table in a single run, run the following
queries:
Note: You can specify the delete batch
size and max delete from each table in a single run. Delete batch size is the
number of rows deleted before a commit. Max delete is the max number of rows
that will be deleted from a table in a single run. They have default values if
you do not provide your own. They're used to avoid resource problems with the
P6 operations.
4
insert into settings (namespace, setting_name, setting_value)
values ('PxService.Cleanup','DeleteMaxSize','100000');
4
insert into settings (namespace, setting_name, setting_value)
values
('PxService.Cleanup','DeleteBatchSize','5000');
Database Administration
RDBMS Scheduler
Configuration
Since background jobs are initiated by the
job scheduler supplied by the RDBMS, you need to ensure that the scheduler for
your specific RDBMS is properly configured.
For
an Oracle Database: P6 EPPM uses DBMS_SCHEDULER to
schedule background jobs in Oracle. P6 EPPM 15 R2 does not need parameter
changes.
For a Microsoft SQL Server Database: P6
EPPM uses the SQL Agent service to automatically schedule background job
execution for Microsoft SQL Server. Background jobs handles the maintenance of
the utilities tables (for example, USESSION and REFRDEL). As part of background
jobs, the agent runs the SYMON and DAMON stored procedures at specific
intervals.
Database Settings Table
Settings Table Overview
The settings table contains name-value
pairs that configure the behavior of the background processes.
Namespace
The namespace component is a dot-notation
string representing a formal path to the parameter.
Setting Name
The setting name identifies the name of the
setting.
Value
Values in the SETTINGS table are
case-sensitive. The value portion of the pair can be:
4 String: The string data type is a free text value. The most common string
sub-type is interval which represents an interval of time by combining a
numeric portion with a unit portion as depicted in the table below.
|
Interval Subtype Table |
||||
|
Unit portion |
Example |
Meaning |
||
|
Numeric portion |
+ |
d |
‘30d’ |
Thirty day interval |
|
h |
‘2h’ |
Two hour interval |
||
|
m |
‘10m’ |
Ten minute interval |
||
|
s |
‘30s’ |
Thirty second interval |
||
4
Numeric: The numeric data type consists of any number.
4
Boolean: The Boolean data type can have one of two values: true or false,
where zero represents false and any non-zero number represents true. 4 Date: The date data type consists of dates.
Setting Example
The following is an example of a setting:
4 Namespace: database.cleanup.Usession
4
Setting Name: ExpiredSessionTimeout
4 Value: 2h (two hour
interval)
Database Administration
Reading
Setting Values
You can configure settings through the
Settings API Procedures. These procedures are similar to registry or INI file
procedure calls.
Reading Settings Values
Use the following SETTINGS_READ_*
procedures to determine the current value of specific settings:
4
SETTINGS_READ_STRING(ret_val,namespace,settings_name,default) 4
SETTINGS_READ_DATE(ret_val,namespace,settings_name,default)
4
SETTINGS_READ_NUMBER(ret_val,namespace,settings_name,default) 4
SETTINGS_READ_BOOL(ret_val,namespace,settings_name,default)
Using Code to Read Setting Values
for Oracle
The following code snippets for the Oracle
Database demonstrate how the SETTINGS_READ_* procedures read the setting
values.
To retrieve the value of the KeepInterval
setting in Oracle:
1) Use the following code:
SQL> variable vset varchar2(255)
SQL> exec
settings_read_string(:vset,'database.cleanup.Usession',
'ExpiredSessionTimeout');
2. The following message should appear:
PL/SQL procedure successfully completed. SQL> print vset
Using Code to Read Setting Values
for Microsoft SQL Server
The following code snippets for the
Microsoft SQL Server database demonstrate how the SETTINGS_READ_* procedures
read the setting values.
To retrieve the value of the KeepInterval
setting in SQL:
1)
Use the following code:
declare @vset varchar(255) exec settings_read_string @vset
OUTPUT,'database.cleanup.Usession','ExpiredSessionTimeout' print @vset
2)
The following message should
appear:
PL/SQL procedure successfully completed. SQL> print vset
Writing
Setting Values
Use the SETTINGS_WRITE_STRING procedure to
set the value of a specific setting:
SETTINGS_WRITE_STRING(new
value,namespace,settings_name);
Using Code to Write Setting Values
for Oracle
The following
code snippets for Oracle Database demonstrate how the
SETTINGS_WRITE_STRING procedure sets the
value of the ExpiredSessionTimeout setting to twelve hours.
To set the value of the
ExpiredSessionTimout setting to twelve hours in an Oracle Database:
1)
Log into SQL *Plus using
privuser as your user name.
2)
Run the following statement:
SQL > exec SETTINGS_WRITE_STRING
('12h','database.cleanup.Usession','ExpiredSessionTimeout');
Using Code to Write Setting Values
for Microsoft SQL Server
The following code snippets for Microsoft
SQL Server databases demonstrate how the SETTINGS_WRITE_STRING procedure sets
the value of the ExpiredSessionTimeout setting to twelve hours.
To set the value of the
ExpiredSessionTimeout setting to twelve hours in a Microsoft SQL Server
database:
1)
Open the Query Analyzer/SSMS
and connect as privuser.
2)
Select the P6 EPPM database,
then run the following statement (using 12 hours as an example):
exec SETTINGS_WRITE_STRING
'12h','database.cleanup.Usession', 'ExpiredSessionTimeout'
Tracking
Background Job Execution
You can track the
execution of background jobs by monitoring the high level status settings or by
inspecting the BGPLOG table.
High Level Status Settings
Each time a job
runs it will update the SETTINGS table for the setting_name = 'HeartBeatTime.'
The job can update this
value multiple times during the execution. You can monitor the maximum
difference between this time and the current date to ensure that the job is
running promptly. Refer to the High Level Status Settings table below for
information about the HeartBeatTime setting.
|
High Level Status Settings |
|
|
Last date and time |
|
|
Namespace |
database.background.Symon |
|
Setting Name |
HeartBeatTime |
|
Default Setting |
N/A |
|
Last date and time |
|
|
Namespace |
database.background.Damon |
|
Setting Name |
HeartBeatTime |
|
Default Setting |
N/A |
The BGPLOG Table
You can also
track the execution of background jobs by inspecting the BGPLOG table. The
BGPLOG table holds detailed entries from the background processes including
informational, elapsed time, and error entries. Refer to the BGPLOG Table
Descriptions for information about what this table contains.
|
BGPLOG Table Descriptions |
||
|
Column |
Description |
Value |
|
Log_time |
Time when background process made a log |
Datetime |
|
Source |
Program generating log entry |
"system_monitor", |
|
Type |
Type of message |
INFORMATION, ELAPSED TIME, ERROR |
|
Description |
Message from the background process |
A variable message followed by a number in |
SYMON (System Monitor)
Procedures
SYMON runs simple P6 EPPM tasks on a quick
schedule. By default, the job runs every minute; the tasks assigned to this job
should take only a few seconds to complete on each run. Do not change the
scheduled run time (every minute) for this procedure.
Procedures performed by SYMON
The procedures run by SYMON perform these
tasks:
4
Processing the PRMQUEUE entries for Project Security by
queuing OBSPROJ updates to the PRMQUEUE table.
4 Marking expired USESSION records as
logically deleted.
Note: You can manually run queries to
assist you with tracking concurrent usage of P6 EPPM.
OBSPROJ_PROCESS_QUEUE Procedure
OBSPROJ_PROCESS_QUEUE processes the
PRMQUEUE entries for Project Security. It defers processing of OBSPROJ updates
by queuing the updates to the PRMQUEUE table.
Refer to the following table for
information about the settings associated with the OBSPROJ_PROCESS_QUEUE
procedure.
OBSPROJ_PROCESS_QUEUE Settings
|
Setting Description: Maximum project-level queue records to |
|
|
Namespace |
database.obsproj.queue |
|
Setting Name |
MaxProjectUpdates |
|
Default Setting |
1000 |
|
Type |
Numeric |
|
Setting Description: Maximum EPS-level queue records to process on |
|
|
Namespace |
database.obsproj.queue |
|
Setting Name |
MaxEpsUpdate |
|
Default Setting |
25 |
|
Type |
Numeric |
|
Setting Description: |
|
|
Namespace |
database.obsproj.queue |
|
Setting Name |
MaxRetries |
|
Default Setting |
50 |
|
Type |
Numeric |
USESSION_CLEANUP_EXPIRED
Procedure
USESSION_CLEANUP_EXPIRED logically deletes
USESSION records that have not updated their last_active_time based on the
Expired Session settings. Marking expired USESSION records as logically deleted
maximizes the number of module access logins that are available. Since it is
not cleaning up the underlying data (physically deleting rows), the task
completes quickly.
Values in the SETTINGS table control the
clean up of expired sessions. By default, although the clean up of expired
sessions occurs every two hours, the SETTINGS table does not contain a value
for this setting. Use the SETTINGS_WRITE_STRING (value, namespace, setting) stored procedure to change the
default clean up value.
For example,
setting the value to "2d" deletes expired sessions older than two
days.
Note: Oracle recommends that you set the
ExpiredLongSessionTimeout sessions to at least one hour longer than your
longest job. For example, if your longest job is a summarizer job that usually
takes 12 hours, you should set the value in the SETTINGS table to at least 13.
Refer to the table below for information
about the USESSION_CLEANUP_EXPIRED Settings.
USESSION_CLEANUP_EXPIRED Settings
|
Setting |
|
|
Namespace |
database.cleanup.Usession |
|
Setting Name |
ExpiredSessionTimeout |
|
Default Setting |
2h |
|
Type |
Interval |
|
Setting 4 Scheduling 4 Leveling 4 Apply Actuals 4 Update Progress 4 Copy/Paste Project 4 Create Project from Template 4 Maintain Baselines (create new baseline) 4 Approve Timesheets 4 Summarize 4 PX Publish 4 Export 4 Import |
|
|
Namespace |
database.cleanup.Usession |
|
Setting Name |
ExpiredLongSessionTimeout |
|
Default Setting |
12h |
|
Type |
Interval |
Tracking Concurrent Usage of P6
EPPM
To track
concurrent usage of P6 EPPM, you can run queries against the USESSION and
USESSAUD tables to perform self-audits. See sample queries below.
Note: See DAMON (Data Monitor) Procedures (on page 51) for information on how to
set up the USESSAUD procedure. To ensure accuracy of these queries, run them
before physically deleting remaining USESSION records and cleaning up the
USESSAUD table.
4
Against the USESSION table, run the following query to
determine how many users are logged in at a given time:
select count(*) from usession where
delete_session_id is null
4
Against the USESSION table, run the following query to
determine how many users are logged into a specific P6 EPPM product at a given
time:
select count (*) from usession where
delete_session_id is null and app_name='P6 EPPM product name' where P6 EPPM product name
is the application abbreviation.
Note: You can view all available application abbreviations by running
the following query as an administrative database user: select
distinct(db_engine_type) from usereng
4
Against the USESSAUD table, run a query similar to the
following to determine how many users logged into P6 EPPM on a specific date
during a specified time range. You can alter the date, time range, and P6 EPPM
product as needed. The following example will search for all users who logged
into P6 Professional on February 17, 2010 between 9am and 10am: For an Oracle
database:
select * from usessaud where login_date
between to_date('17-FEB-10 09:00:00','DD-MON-YY HH:MI:SS') and
to_date('17-FEB-10
10:00:00','DD-MON-YY HH:MI:SS') and
app_name='Project Management'
For a Microsoft SQL Server database:
select * from usessaud where login_date
between
'2010-02-17 09:00' and '2011-02-17
10:00' and app_name='Project Management'
Tips
See
"Counting Users" in the P6 EPPM
System Administration Guide for information on counting users and how to
view the total number of licenses assigned for each module.
DAMON (Data Monitor) Procedures
The second database job is
the DAMON data monitor job. The DAMON job runs the majority of the background
processing and is responsible for running background clean up processes
required by the application that can potentially take a relatively long time to
run.
Oracle and DAMON
By default, DAMON runs
every Saturday. It uses the Oracle DBMS_SCHEDULER package to schedule the jobs,
and an Interval setting controls the schedule and accepts the same parameters
as the DBMS_SCHEDULER interval. For more information, refer to your Oracle database
documentation.
Microsoft SQL Server and DAMON
By default, DAMON runs every Saturday. You
can set it to run every two weeks or on a specific day. To run DAMON every two
weeks, use the following command to set the interval: -eg 2W
To set DAMON to run on a specific day, use
the following setting under namespace:‘Database.background.Damon’
DayOfWeek
DAMON Procedures DAMON cleans the:
4 BGPLOG table containing the background
logs.
4 REFRDEL table.
4
PRMQUEUE table.
4 Remaining USESSION records.
4 Logically deleted records.
4 PRMAUDIT table.
4
USESSION audit table (USESSAUD).
You can also
dynamically extend DAMON functionality via the user-defined procedure,
USER_DEFINED_BACKGROUND.
BGPLOG_CLEANUP Procedure
This procedure keeps the BGPLOG table at a
reasonable size. The default cleanup interval is 5 days which will result in a
table size of about 54,000 records.
Refer to the following table for
information about the settings associated with the BGPLOG_CLEANUP procedure.
BGPLOG_CLEANUP Settings
|
Setting Description: The oldest records to |
|
|
Namespace |
database.cleanup.BackGroundProcessLog |
|
Setting Name |
KeepInterval |
|
Default Setting |
5d |
|
Type |
Interval |
REFRDEL_CLEANUP Procedure
This procedure deletes records from the
REFRDEL table. REFRDEL_CLEANUP runs based on the frequency of data_monitor_job,
which has a default frequency of one week. Alternatively, you can run
REFRDEL_CLEANUP by itself if needed.
Refer to the following table for
information about the settings associated with the REFRDEL_CLEANUP procedure:
REFRDEL_CLEANUP Settings
|
Setting Description: Identifies the number REFRDEL table before they can be removed. For example, the default |
|
|
Namespace |
database.cleanup.Refrdel |
|
Setting Name |
KeepInterval |
|
Default Setting |
5d |
|
Type |
Interval |
|
Setting Description: Identifies the number |
|
|
Namespace |
database.cleanup.Refrdel |
|
Setting Name |
DaysToDelete |
|
Default Setting |
1 |
|
Type |
Numeric |
|
Setting |
|
|
Namespace |
database.cleanup.Refrdel |
|
Setting Name |
IntervalStep |
|
Default Setting |
15 |
|
Type |
Numeric |
REFRDEL Bypass Procedure
The REFRDEL table maintains a list of deleted records from P6 database tables.
However, when an entire project is deleted, a large amount of detailed delete
records can be inserted into the REFRDEL table resulting in the potential for downstream performance
degradation when joins are made to the REFRDEL table.
The REFRDEL Bypass procedure is an
alternative to inserting REFRDEL records
for tracking delete records on a large scale. This procedure bypasses the REFRDEL table and simply adds a single delete record for a deleted project
and project ID.
By default, the REFRDEL BYPASS procedure is
set to 0 (zero).
To enable REFRDEL Bypass, execute the
following procedure and set to a non-zero value:
SQL> exec
SET_REFRDEL_PROJECT_BYPASS(1);
Database triggers
check for the value of the REFRDEL BYPASS value and process accordingly.
Note: The bypass procedure is meant only
for a PROJECT DELETE operations.
CLEANUP_PRMQUEUE Procedure
This procedure deletes records from the
PRMQUEUE table based on the value of the KeepInterval setting. The remaining
settings are similar to the REFRDEL_CLEANUP.
Refer to the following table for
information about the settings associated with the CLEANUP_PRMQUEUE procedure:
CLEANUP_PRMQUEUE Settings
|
Setting Description: The |
|
|
Namespace |
database.cleanup.Prmqueue |
|
Setting Name |
KeepInterval |
|
Default Setting |
5d |
|
Type |
Interval |
|
Setting Description: Determines |
|
|
Namespace |
database.cleanup.Prmqueue |
|
Setting Name |
DeleteAll |
|
Default Setting |
0 (false) |
|
Type |
Boolean |
|
Setting Description: Determines |
|
|
Namespace |
database.cleanup.Prmqueue |
|
Setting Name |
DeleteAllThreshold |
|
Default Setting |
1,000 |
|
Type |
Numeric |
|
Setting Description: Percentage of records to delete on each pass. |
|
|
Namespace |
database.cleanup.Prmqueue |
|
Setting Name |
DeletePercentage |
|
Default Setting |
10(%) |
|
Type |
Numeric |
|
Setting Description: Maximum rows to delete on each pass. |
|
|
Namespace |
database.cleanup.Prmqueue |
|
Setting Name |
MaxRowsToDelete |
|
Default Setting |
10,000 |
|
Type |
Numeric |
USESSION_CLEAR_LOGICAL_DELETES
Procedure
This procedure
physically deletes all logically deleted USESSION records. This procedure does
not have settings associated with it: All logically deleted USESSION records
are cleared.
CLEANUP_LOGICAL_DELETES Procedure
This procedure
removes logically deleted rows based on the value of the KeepInterval setting.
Records in the database can be marked as deleted (logically deleted) by setting
the
DELETE_SESSION_ID
column to a non-null value. By default, records that were deleted more than 5
days ago will be deleted by this procedure.
Notes:
- The CLEANUP_LOGICAL_DELETES procedure will not delete records whose
DELETE_SESSION_ID column is set to a negative value. - This procedure will not delete records older than the earliest user
session in USESSION, as determined by the minimum value in the login_date
column.
Refer to the
following table for information about the settings associated with the
CLEANUP_LOGICAL_DELETES procedure:
CLEANUP_LOGICAL_DELETES Settings
|
Setting Description: The oldest logically |
|
|
Namespace |
database.cleanup.LogicalDelete |
|
Setting Name |
KeepInterval |
|
Default Setting |
5d |
|
Type |
Interval |
|
Setting Description: Determines whether |
|
|
Namespace |
database.cleanup.LogicalDelete |
|
Setting Name |
DeleteAll |
|
Default Setting |
0 (false) |
|
Type |
Boolean |
|
Setting Description: Maximum rows to |
|
|
Namespace |
database.cleanup.LogicalDelete |
|
Setting Name |
MaxRowsToDelete |
|
Default Setting |
10,000 |
|
Type |
Numeric |
PRMAUDIT_CLEANUP Procedure
If the auditing feature is enabled, this
procedure will physically delete records from the table based on the value of
the KeepInterval setting.
Refer to the following table for
information about the settings associated with the PRMAUDIT_CLEANUP procedure:
PRMAUDIT_CLEANUP Settings
|
Setting Description: Should the procedure |
|
|
Namespace |
database.cleanup.auditing |
|
Setting Name |
Enabled |
|
Default Setting |
1 (true) |
|
Type |
Boolean |
|
Setting Description: The oldest audit |
|
|
Namespace |
database.cleanup.auditing |
|
Setting Name |
KeepInterval |
|
Default Setting |
30d |
|
Type |
Interval |
CLEANUP_USESSAUD Procedure
The CLEANUP_USESSAUD
procedure deletes records from the USESSAUD table based on the KeepInterval
parameter setting. All other settings are similar to the REFRDEL_CLEANUP
procedure. The following table describes the settings associated with the
CLEANUP_USESSAUD procedure.
CLEANUP_USESSAUD Settings
|
Setting Description: Determines the oldest records to keep in the Based on the logout time, |
|
|
Namespace |
database.cleanup.Usessaud |
|
Setting Name |
KeepInterval |
|
Default Setting |
5d |
|
Type |
Interval |
|
Setting Description: Deletes all the REFRDEL records that satisfy |
|
|
Namespace |
database.cleanup.Usessaud |
|
Setting Name |
DeleteAll |
|
Default Setting |
0 (false) |
|
Type |
Boolean |
|
Setting |
|
|
Namespace |
database.cleanup.Usessaud |
|
Setting Name |
DeleteAllThreshold |
|
Default Setting |
1,000 |
|
Type |
Numeric |
|
Setting |
|
|
Namespace |
database.cleanup.Usessaud |
|
Setting Name |
MaxRowsToDelete |
|
Default Setting |
10,000 |
|
Type |
Numeric |
|
Setting Description: Determines the percentage of records to |
|
|
Namespace |
database.cleanup.Usessaud |
|
Setting Name |
DeletePercentage |
|
Default Setting |
10 (%) |
|
Type |
Numeric |
USER_DEFINED_BACKGROUND
Procedure
This procedure is
an optional customer procedure that DAMON runs. This procedure does not have
settings associated with it.
Oracle Database Performance
You can modify several Oracle database
settings to improve the performance of your P6 EPPM database. Run the scripts
as described below after you create the database.
Grant access to the
V_$TRANSACTION view:
V_$TRANSACTION is a system view in Oracle
that lists the active transactions in the system.
GET_SAFETY DATE
(a procedure in the Project Management schema) accesses this view to get the
oldest start time of an active transaction. If the schema owner does not have
privileges to this view, then it returns a safety date using the USESSION
table. V_$Transaction tunes performance during a refresh action. USESSION
records the login time of the logged in user, whereas data in the
V_$Transaction view is recorded at a system level. The logged in user could be
logged in for more than an hour (as seen from the USESSION table), but the
V_$Transaction view has the current transaction datetime, regardless of the
time the user logged in.
Note: Access to the V_$TRANSACTION view
was built into the procedure to tune performance with refreshing operations;
however, third party functions could impact performance with database refresh
operations that use an older time in the V_$TRANSACTION view.
To grant access to
this view, connect to Oracle as SYS. Run the RUN_AS_SYS.SQL script located in
the \Database\scripts\common folder of the P6 EPPM physical media or download.
Gather statistics for cost-based
optimization:
Oracle 11g and
later supports only cost-based optimization, which relies on accurate
statistics to determine the optimal access path for a query. To gather the
appropriate statistics for the optimizer, which will improve database
performance, run the ORPM_STATS_GATHER.SQL script located in the
\Database\scripts\common folder of the P6 EPPM physical media or download.
Safe Deletes
The P6 EPPM database
normally handles restoring select deleted data using a safe delete setting.
While using P6 Professional, the Undo command (Edit, Undo) allows users to
restore certain types of data that have been deleted. Deleted data remains in
the P6 EPPM database until the CLEANUP_LOGICAL_DELETES procedure clears it
(after 5 days, by default).
See the P6 Professional Help for more
information about using undo.
Turning Off Safe Deletes
You can turn off safe deletes to save
storage space. Turning off safe deletes disables undo functionality and
instantly clears deleted data from the P6 EPPM database.
To turn off safe deletes:
1)
Verify the current state of
your safe deletes setting. In the database, if the table
ADMIN_CONFIG has the following row, a
CONFIG_VALUE of 'N' means turn off safe deletes.
CONFIG_NAME
= 'SAFEDELETE.ACTIVE' and CONFIG_TYPE = 'SETTINGS'
Note: This is only loaded at startup. If
you change CONFIG_VALUE while a user is running P6 Professional, the setting
will not apply until the user restarts the P6 Professional session.
2)
Once you have determined the
current state of your safe deletes setting, run one of the following
statements.
4
To turn off safe deletes for the first time:
INSERT INTO ADMIN_CONFIG (CONFIG_NAME,
CONFIG_TYPE, CONFIG_VALUE)
VALUES ('SAFEDELETE.ACTIVE', 'SETTINGS',
'N')
4
To turn on safe deletes after it has been turned off:
UPDATE ADMIN_CONFIG SET CONFIG_VALUE =
'Y' WHERE CONFIG_NAME =
'SAFEDELETE.ACTIVE' AND CONFIG_TYPE =
'SETTINGS'
4
To turn off safe deletes after it has been turned on:
UPDATE ADMIN_CONFIG SET CONFIG_VALUE =
'N' WHERE CONFIG_NAME =
'SAFEDELETE.ACTIVE' AND CONFIG_TYPE =
'SETTINGS'
3)
Restart the P6 server.
PRMAUDIT Auditing
PRMAUDIT auditing permits you to log the edits,
additions, and deletions made by users of P6
EPPM
applications. When users make changes, they create a Data Manipulation Language
(DML) INSERT,
UPDATE, or DELETE statement. PRMAUDIT auditing uses the Data
Manipulation Language
(DML) INSERT, UPDATE, or DELETE statement being executed against tables in the
database schema. Since every application table in the schema has its own
auditing trigger, you can log changes made to each table regardless of who made
the change or when the change was made. The database schema owner owns the
auditing trigger: you can bypass trigger execution.
Auditing Level Configuration
You can adjust the amount
of information that is logged by adjusting the audit level for each table. You
can refine the audit further by setting the audit level individually for
insert, updates, and deletes within each table.
Auditing Levels
|
Level |
Description |
|
Level 0 |
No audit. |
|
Level 1 |
Row-level audit. Audit only the operation |
|
Level 2 |
Column-level Audit without blobs. Audit changes to the data at the |
|
Level 3 |
Full For For Microsoft SQL server, column level |
Simple Configuration
You can use two configuration procedures to
provide simple control of the auditing feature:
4
auditing_enable(table_name,
level) 4 auditing_disable(table_name)
You can set the audit
level on an individual table or the same audit level for all of the tables.
However, the simple configuration procedures do not allow for setting
individual auditing levels for insert, update, or delete operations within a
table.
Examples for Oracle:
Use the following examples as a guide to
use the simple audit configuration procedures to control the auditing feature.
4 The following code snippet enables full auditing on all tables: exec
auditing_enable(null,3);
4
The following code snippet enables level one auditing
on the task table:
exec auditing_enable('TASK',1);
4
The following code snippet disables auditing on
PROJWBS:
exec auditing_disable('PROJWBS');
4 The following code snippet completely disables auditing across the
entire database: exec auditing_disable(null);
Detailed Configuration
You can configure auditing trigger behavior
by changing values in the settings table that enable or disable:
4
The auditing feature itself
4 The auditing of specific tables
4 The auditing of table insert, update,
or delete operations within each table
You can enable or disable the auditing
feature by using the database.audit.Enable setting. Use the settings_write_bool
procedure to enable/disable the auditing feature.
Oracle Example:
To enable the auditing feature in Oracle,
use the following code:
exec
settings_write_bool(1,'database.audit','Enabled');
Microsoft SQL Server Example:
To enable the
auditing feature in Microsoft SQL Server, use the following code: exec
settings_write_bool 1,'database.audit','Enabled'
Options Setting
Each table's auditing settings are
controlled by the Options setting in each table's auditing namespace (for
example, database.audit.TASK). The Options setting is a three character string
with a numeric value in each character position representing the audit level
for insert, update, and delete.
|
Auditing Level Options Setting by Table Operation |
||||
|
Operation |
||||
|
Insert |
Update |
Delete |
Description |
|
|
Level |
0 |
0 |
0 |
No audit. |
|
1 |
1 |
1 |
Row-level audit. Audit only the operation without column details. |
|
|
2 |
2 |
2 |
Column-level audit without blobs. Audit changes to the data at the |
|
|
3 |
3 |
3 |
Full For Microsoft SQL server, column level changes to blobs are not |
|
The following
table provides some examples of the options setting:
|
Setting the Auditing Level Options Setting by Table Operation |
|||
|
Namespace |
Setting |
Value |
Description |
|
database.audit.TASK |
Options |
330 |
Fully audit any insert and update operations. Do not audit any delete operations. |
|
database.audit.PROJWBS |
001 |
Row-level audit on deletes only. |
|
|
database.audit.TASKRSRC |
333 |
Fully audit. |
|
SETTINGS_WRITE_STRING Procedure
You can change table audit settings using
the settings_write_string procedure.
Oracle Example:
To set the table settings to fully audit
insert and update operations but ignore any delete operations, use the
following code for Oracle:
exec
settings_write_string('330','database.audit.TASK','Options');
Microsoft SQL Server Example:
To set the table settings to fully audit
insert and update operations but ignore any delete operations, use the
following code for Microsoft SQL Server:
exec
settings_write_string '330','database.audit.TASK','Options'
Note: Changes to auditing settings will
not appear immediately in the application. The program will need to close the
database connection and then reconnect to the database to get the new settings.
The Audit Table
Audit records are
inserted into the PRMAUDIT table. One record is inserted into the audit table
for each row changed in the database.
|
PRMAUDIT Table |
||
|
Column |
Type |
Description |
|
audit_date |
Date |
Date and time of change |
|
table_name |
String(30) |
Table Name |
|
pk1, pk2, pk3, pk4 |
String(255) |
Primary key values for audited record |
|
oper |
String(1) |
I=Insert, U=Update, D=Delete |
|
prm_user_name |
String(32) |
P6 EPPM user name if the change was made |
|
audit_info |
String(4000) |
Column changes up to 4000 characters |
|
audit_info_extended |
BLOB |
Blob changes and overflow from audit_info |
|
logical_delete_flag |
String(1) |
Flag for deletes that are logical (marked) |
|
rdbms_user_name* |
String(255) |
Database user name (usually privuser) |
|
os_user_name* |
String(255) |
Operating system user name of connected Note: When auditing is PRMAUDIT.os_user_name will always return a null value. This is because the value for os_user_name is empty The nt_username |
|
when we connect to SQL DB using Windows |
||
|
program* |
String(255) |
Name of program connecting to the database |
|
host_name* |
String(255) |
Computer name of connected session |
|
app_name* |
String(25) |
Name of application connected to the |
|
netaddress* |
String(24) |
IP or MAC address of connected session |
Note: Grant select privileges to the
administrative user on V_$SESSION to ensure correct values for several auditing
table values.
Session Auditing
Activity for the USESSION
table is audited with its own trigger and table. When an application user logs
out of the system they logically delete, or mark, their session record in the
USESSION table. One record is written to the USESSAUD table for each logout.
The format of the USESSAUD table mirrors that of the USESSION table. This audit
can be enabled using the usessaud_enable procedure and disabled using the
usessaud_disable procedure.
Column Audit Data
The data changes for each audit are stored
in the audit_info and audit_info_extended columns. The audit_info column
contains all the row changes as long as they do not exceed 4000 characters.
Changes over 4000 characters or any edit to a blob will be written to the
audit_info_extended BLOB column.
Data in the two audit_info
columns has a specific format. Each column audit within the data begins with
either ":O" (old data) or ":N" (new data) to distinguish
between the audit of the previous (old) or the changed (new) value (for BLOB columns
the data starts with :BLOBO or :BLOBN). Directly after this is the name of the
column in lowercase. Following the column name is the length of the audited
value in a fixed four character field. Finally the actual data is placed in the
audit record. Updates will have both an old and new value for each change.
Inserts will have only a new value and deletes only an old value.
The following is
an example of the audit record for TASK to change the task_code from 'A1010' to
'B102:'
audit_info
=>:Otask_code: 5:A1010:Ntask_code: 4:B102
Using the
Data Pump Utility
The data pump utility is a java-based tool
that enables you to migrate data from a Microsoft SQL Server database to an
Oracle database.
Use the data pump utility to:
4 Import data into a newly created
database.
4
Repair a damaged database to correct database object
issues (such as constraints or views).
Do not
use the data pump utility to:
4 Convert the database type from EPPM to
PPM or from PPM to EPPM.
4 Upgrade from one database version to
another.
4
Import data into an existing database.
4 Correct data-specific issues.
4
Correct schema-related issues. It is not ideal for
large databases (more than 10 GB) due to the performance of the utility. For
larger databases, try first to manually resolve schema-related issues.
Before running
the data pump utility, you must first run a schema validation on the database.
See Running
a Schema Validation on the Database (on page 70) for details.
Running a Schema Validation on
the Database
The schema validation utility finds
missing, extra, and modified schema objects for a P6 database.
To run a schema validation, complete the
following steps:
1)
In the software download,
locate the utility in the Database
Download folder.
2)
Edit the utility similar to the
following:
@echo off
REM
--------------------------------------
REM Run the Primavera
Schema Validation Tool
REM
--------------------------------------
SET JAR_FILE_DIR=lib
SET JAR_FILE_NAME=dbmt.jar
SET DB_SCHEMA=ppm
SET
JVM_PROPERTIES=-Ddbmt.dbschema.package.location=%JAR_FILE_DIR%
-Dprimavera.db.schema=%DB_SCHEMA%
-Dcom.primavera.database.logfile=SchemaValidation.log
SET
DBMT_ACTION=application/ppmschemaval SET DBMT_COMMAND=schemavalpm set JAVA_HOME=C:\Program
Files\Java\jre6 IF NOT EXIST "%JAVA_HOME%\bin\java.exe" ( echo JAVA_HOME IS NOT SET pause
goto :EXIT )
3)
Run validate.bat (with Windows) or validate.sh
(with UNIX or Linux).
4)
For an Oracle database in an
Enterprise environment, enter values for the following:
4
Username: Use the appropriate ADMUSER username and password.
4
Database host
address: Database server name or IP address.
4
Database host
port: The port your Oracle listener is listening
on. The default port is 1521.
4
Database name
(SID): Enter the Oracle SID for your database. For
a SQL Server 2005 database, enter values for the following:
4
Database host
address: Database server name or IP address.
4 Database host port: The
SQL port.
4 Database name:
pmdb$primavera (default)
Note: When running for an Enterprise
version of the database, you will be prompted for the appropriate privileged
and public usernames.
5)
Review the results of the
schema validation utility that display in the browser.
Running the Data Pump Utility
Using the Wizard
To run the data
pump utility using the wizard, complete the following steps:
Note: Skip the first two steps if you
are using a Microsoft SQL Server Database.
1)
From the command line, execute:
sqlplus
sys/password@<db_tns_names_entry> as sysdba
2)
Go to
p6suite\database\scripts\install\PM_<release_level>, and execute manual_script_before_install.sql.
3)
Go to the <P6_EPPM_Home>\database folder.
4)
Run migrate.bat (with Windows) or migrate.sh (with
UNIX or Linux).
5)
Follow the prompts on each
screen to provide connection information for the source database and the target
database.
Note: When using an Oracle schema, the
migration utility allows you to create new tables or use existing tables in the
target instance, but new schema users must be created through the migration
process. The ability to map to existing schema users is not currently available
through the migration process.
Running the Data Pump Utility From the
Command Line
Note: Do not use the data pump utility
to convert the database type from EPPM to PPM or from PPM to EPPM.
To run the data pump utility from the
command line, complete the following steps:
1)
Open a new command line
console.
2)
Go to \install\database.
3)
Run the command with the
following parameters to define the migration: With Windows
migrate.bat -source
sa/sa@sqlserver:rcgsrv:1433:vader_pmdb -target
system/manager@oracle:rcgsrv:1521:rcg02 -db PM
With Windows (Creating Non-Default Oracle Users)
migrate.bat -source
sa/sa@sqlserver:rcgsrv:1433:vader_pmdb -target
system/manager@oracle:rcgsrv:1521:rcg02 -db PM -admuser admjeff -privuser
privjeff -pubuser pubjeff
With UNIX or Linux
sh migrate.sh -source
sa/sa@sqlserver:saumverm-lap\primavera:1433:PMDB -dattbsp <Name of data
tblspc at target> -ndxtbsp <Name of index tblspc at target> -pxtbsp
<Name
of px tblspc at target> -lobtbsp <Name of LOB tblspc at target>
-admuser <admuser at target> -admpass <admuser password at target>
-privuser <privuser at target> -privpass <privuser password at
target> -pubuser <pubuser at target> -pubpass <pubuser password at
target> -pxrptuser <pxrptuser at target> -pxrptpass
<pxrptuser password at
target> -bgjobuser <bgjobuser at target> -bgjobpass
<bgjobuser password at
target> -target system/admin@oracle:oldb-orcl:1521:PMDB For example:
sh
migrate.sh -source sa/sa@sqlserver:saumverm-lap\primavera:1433:PMDB -dattbsp
PMDB_DAT1 -ndxtbsp PMDB_NDX1 -pxtbsp PMDB_PX_DAT1 -lobtbsp PMDB_LOB1 -admuser
admuser -admpass admuser -privuser privuser -privpass privuser -pubuser pubuser
-pubpass pubuser -pxrptuser pxrptuser -pxrptpass pxrptuser -bgjobuser bgjobuser
-bgjobpass bgjobuser -target system/admin@oracle:oldb-orcl:1521:PMDB
Where To Go From Here - Post
Configuration Wizard
Now that you've installed all of your P6
EPPM applications, you can begin using P6. You may find the following guides
useful to get started:
4 P6 EPPM System Administration Guide
Note: You can use this
guide to configure E-mail Statusing Service.
4 P6 EPPM Application Administration Guide
4 P6 Help
Note: The most recent
version of all these guides are available on OTN.
In This Section
Launching Your
P6 EPPM Applications
................................................................... 74
Settings You
Must Configure in P6 Before You Begin
.............................................. 77
Installing Additional Applications
..............................................................................
78
Launching Your P6 EPPM
Applications
After you have installed and configured
your P6 EPPM applications, you can launch your applications by doing the
following:
1)
Go to the scripts folder where
you installed P6 EPPM (for example, C:\P6EPPM_1\scripts or /usr/P6EPPM_1/scripts).
2)
If you are on Windows, launch
the start_Primavera.bat. If you are
on Linux, launch the start_Primavera.sh.
Note: You need to launch the file only
once unless you stop the server or need to restart the machine.
3)
Open the HTML file you saved
when you finished your configuration and choose the URL for the application you
want to launch. 4) Login to the application.
Tips
4 If you are on Windows, you can use the
Start menu to launch your applications.
- Go to Start, P6 EPPM.
- Select the start_Primavera.bat file and wait for it to say running.
- Select the application you want
to launch and login.
4 If you want to
set up the WebLogic Admin Server and Managed Servers to run as Windows Services,
see WebLogic's documentation.
Starting and Stopping Managed
Servers
You have several
options for starting and stopping managed servers. Oracle recommends that you
use the startNodeManager file and start the server in the WebLogic
Administration Console (see Starting a Managed or Clustered Server
(on page 76)). However, you can view other ways to stop and start managed
servers at "Managing Server Startup and Shutdown for Oracle WebLogic
Server" at
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13708/overview.htm.
Note: You can use different ways to
start the managed servers, but you must ensure that the managed servers
recognize the arguments required for your application (for example, the
argument for where the bootstrap is located) and how the application
environment will start.
Starting a Managed or
Clustered Server
To start a
managed or clustered server in the WebLogic Administration Console:
Note: When starting/stopping an
environment using the node manager, the StartScriptEnabled
setting in the nodemanager.properties
file must equal true. Example: StartScriptEnabled=true
1)
Run the startNodeManager file.
4
In Windows, the file is named
"startNodeManager.cmd" and is located in: weblogic_home\server\bin
4
With Unix or Linux, the file is named
"startNodeManager.sh" and is located in: weblogic_home\server\bin
2)
Launch the WebLogic Administration Console.
Note: You can open the Administration
Console via a web browser using this address: http://serverIP:listenport/console.
The default listenport is 7001.
3)
In the Welcome window, log in using the user name and password that you
created when you created your WebLogic domain.
4)
In the Change Center pane of the Administration Console, click Lock & Edit.
5)
In the Domain Structure pane:
- Expand Environment.
- Click Servers.
6)
In the Summary of Servers pane:
- Select the Control tab.
- Select the option for your
managed server. - Click Start.
7)
In the Server Life Cycle Assistant pane, click Yes.
8)
In the Summary of Servers pane, click the 'Start Refresh' icon in the
middle of the pane to see when the State
column says 'RUNNING.'
Your managed or clustered server will stop
running when you close the startNodeManager file.
You can also stop the managed or clustered
server in the WebLogic Administration Console.
1)
Launch the WebLogic Administration Console.
Note: You can open the Administration
Console via a web browser using this address: http://serverIP:listenport/console.
The default listenport is 7001.
2)
In the Welcome window, log in using the user name and password that you
created when you created your WebLogic domain.
3)
In the Change Center pane of the Administration Console, click Lock & Edit.
4)
In the Domain Structure pane:
- Expand Environment.
- Click Servers.
5)
In the Summary of Servers pane:
- Select the Control tab.
- Select the option for your
managed server. - Click the down arrow to the
right of the Shutdown button. - Click When work completes or Force
Shutdown Now.
6)
In the Server Life Cycle Assistant pane, click Yes.
7)
In the Summary of Servers pane, click the 'Start Refresh' icon in the
middle of the pane to see when the State
column says 'SHUTDOWN.'
Settings You Must Configure in
P6 Before You Begin
The following lists things you must set in
P6 before you begin using it. Use the P6
EPPM System Administration Guide and the P6 EPPM Application Administration Guide for instructions on how to
set the following:
4 Set the base currency
Note: You must choose the base currency
if you do not want the database to use US dollars ($) as the base currency. You
cannot change the base currency once projects are in progress.
4
Add users and assign them the appropriate security
privileges.
4 Configure the
Primavera P6 Administrator for your environment.
Installing Additional
Applications
The following applications will work with
P6 EPPM, but are not installed or configured with the wizard. See the guides
mentioned for more information about each product.
4 P6 Professional
(see the P6 Professional Installation and
Configuration Guide)
4 Oracle Identity
Manager (see P6 EPPM Oracle Identity
Manager Configuration Guide)
4 Oracle
Enterprise Manager (see Primavera Oracle
Enterprise Manager Configuration Guide)
4 Oracle Access
Manager (see Primavera Oracle Access
Manager Configuration Guide)
4 Oracle BI
Publisher (see P6 EPPM BI Publisher
Configuration Guide)
4 Oracle BPM (see
P6 EPPM BPM Configuration Guide)
For More Information
For More Information
Where to Get Documentation
Complete documentation libraries for P6
EPPM releases are available on the Oracle Technology Network (OTN) at:
http://www.oracle.com/technetwork/documentation/primavera-093289.html
From this location you can either view
libraries online or download them to have local copies. We recommend viewing
them from OTN to ensure you always access the latest versions, including
critical corrections and enhancements.
The documentation assumes a standard setup
of the product, with full access rights to all features and functions.
Help System Access
P6 EPPM is
configured to access its help systems on OTN. However, downloadable versions of
the help systems are also available on OTN if you need to download, deploy, and
access a local copy.
Documentation Accessibility
For information about Oracle's commitment
to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers
that have purchased support have access to electronic support through My Oracle
Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing
impaired.
Where to Get Training
To access comprehensive
training for all Primavera products, go to: http://education.oracle.com
Oracle Learning Library
The Oracle Learning
Library (OLL) provides online learning content covering Primavera products.
Content includes whitepapers, videos, tutorials, articles, demos, step-by-step
instructions to accomplish specific tasks, and self-paced interactive learning
modules.
To access the learning library’s Primavera
content, go to:
http://www.oracle.com/oll/primavera
Where to Get Support
If you have a question about using Oracle
products that you or your network administrator cannot resolve with information
in the documentation or help, click http://support.oracle.com. This page
provides the latest information on contacting Oracle Global Customer Support,
knowledge articles, and the support renewals process. For more information
about working with Support, visit
https://support.oracle.com/epmos/faces/DocumentDisplay?id=888813.2 to view Support Tools & Tips.
Using Primavera's Support Resource Centers
Primavera’s Support
Resource Center provides links to important support and product information.
Primavera's Product Information Centers (PICs) organize documents found on My
Oracle Support (MOS), providing quick access to product and version specific information
such as important knowledge documents, Release Value Propositions, and Oracle
University training. PICs also offer documentation on Lifetime Management, from
planning to installs, upgrades, and maintenance.
Visit
https://support.oracle.com/epmos/faces/DocumentDisplay?id=1486951.1 to access
links to all of the current PICs. PICs also provide access to:
4
Communities which are moderated by Oracle providing a place for collaboration
among industry peers to share best practices.
4 News
from our development and strategy groups.
4
Education via a list of available Primavera product trainings through Oracle
University. The Oracle Advisor Webcast program brings interactive expertise
straight to the desktop using Oracle Web Conferencing technology. This capability
brings you and Oracle experts together to access information about support
services, products, technologies, best practices, and more.
Creating a Service Request
P6 EPPM integrates with different Oracle
applications; when you create a Service Request, be sure to open the request
with the proper Support team. To ensure you reach the proper Support team,
enter the correct product information when you create the Service Request. Each
product has its own support line.
4
Use the Primavera
P6 EPPM support line when you are having installation, configuration, or
connection issues related to P6 EPPM.
4
Use one of the following support lines when you are
having installation or configuration issues that do not relate to P6 EPPM.
4
Oracle WebLogic Server
4
Oracle Database Server
4
BI Publisher
4
BPM
4 Oracle WebCenter Content Core Capabilities (formerly Universal
Content Management) 4
Oracle Enterprise Manager
For More Information
4
Oracle Access Manager
4
Oracle AutoVue
Keeping Your Software Up to Date
To ensure you have the latest versions of
your products, be sure to download and install all available patch sets from
http://support.oracle.com.
Finding Security-related Patches
To get the latest information about
Critical Patch Updates, visit
http://www.oracle.com/technetwork/topics/security/alerts-086861.html.
Legal Notices
Oracle Primavera P6 EPPM Installation and
Configuration Guide
Copyright © 1999,
2016, Oracle and/or its affiliates. All rights reserved.
Oracle and Java are registered trademarks
of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
This software and related documentation are
provided under a license agreement containing restrictions on use and disclosure
and are protected by intellectual property laws. Except as expressly permitted
in your license agreement or allowed by law, you may not use, copy, reproduce,
translate, broadcast, modify, license, transmit, distribute, exhibit, perform,
publish or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject
to change without notice and is not warranted to be error-free. If you find any
errors, please report them to us in writing.
If this is software or related
documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs,
including any operating system, integrated software, any programs installed on
the hardware, and/or documentation, delivered to U.S. Government end users are
“commercial computer software" pursuant to the applicable Federal
Acquisition Regulation and agency-specific supplemental regulations. As such,
use, duplication, disclosure, modification, and adaptation of the programs,
including any operating system, integrated software, any programs installed on
the hardware, and/or documentation, shall be subject to license terms and
license restrictions applicable to the programs. No other rights are granted to
the U.S. Government.
This software or hardware
is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently
dangerous applications, including applications that may create a risk of
personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate failsafe,
backup, redundancy, and other measures to ensure its safe use. Oracle
Corporation and its affiliates disclaim any liability for any damages caused by
use of this software or hardware in dangerous applications.
This software or hardware and documentation
may provide access to or information on content, products and services from
third-parties. Oracle Corporation and its affiliates are not responsible for
and expressly disclaim all warranties of any kind with respect to third-party
content, products, and services. Oracle Corporation and its affiliates will not
be responsible for any loss, costs, or damages incurred due to your access to
or use of third-party content, products, or services.
82