Installation and configuration of Primavera P6 EPPM R.8.3. Author: Vinoth Kumar Subramani Required Binaries: 1. DB Binaries 2. JDK 3. Weblogic 4. P6 EPPM NOTE: Check certification metrix for version compactibility. Installation and configuration of DB: For this installation I have used Oracle XE 11g R2. XE DB will come as an RPM and not as a runInstallr. So, you can install only in root user.
When prompted, run the following command: # /etc/init.d/oracle-xe configure To start the database manually, run this command as root user: # /etc/init.d/oracle-xe start To stop the database manually, run the following command as root user: # /etc/init.d/oracle-xe stop
To start and Stop the DB.
JDK: In this environment I have installed the DB in root user and the applications in application user (oracle). You can access the DB from application user.
Weblogic: Set the java environemnt as shown below and start the Weblogic installation.
Start with the domain configuration.
Password: welcome1
No need to configure the managed servers for EPPM. While configuring the EPPM, the managed servers will get created with application.
Since I have created the environment in Production mode am creating the boot.properties.
Then start the Weblogic Admin server and Node Manager
Install EPPM:
EPPM Configuration.
Go to the below mentioned path and change owner for manual_script_before_install.sql to root and give 775 or 777 permissions and execute.
Since my DB and application is running on the same host I ran like this. If your DB and application is running on different host, copy the manual_script_before_install.sql to the DB host and run as shown below.
Once this is done continue with the configuration.
Password: welcome1
Since I have created the domain already I am using the same here.
As of now I am not doing any integrations.
No need to worry if, Start Weblogic Domain for P6 got failed. The configuration was done already. It will try to restart the server. You can ignore this. It will proceed for next step.
The configuration of P6 EPPM completed successfully. You can now try to log on to P6 as well as PR. Below are the server details. Since, I would be logging the console from my local machine (The server is running in Linux VM – Gust machine and I am accessing the URL from my host machine), I am using the IP address instead of local host.
P6 DB configuration. Go to the P6 home and run dbconfigpv.sh
Update the P6 DB configuration. Go to the P6 home and rin adminpv.sh.
Update to latest version and then Save changes.
Performance tuning Although not required for P6, precompilation helps to reduce the amount of time it takes for users to load P6 pages for the first time. The following instructions apply to all application servers supported by P6 EPPM and need to be performed while the application server is running. Note: Your application server must be listening on a HTTP port (non-SSL) for the precompile utility to work. You can later disable the HTTP port after precompilation if you will only be using HTTPS. To precompile P6: 1. Copy the precompile_utility directory from the P6 folder of the physical media or download to the server where P6 is installed. 2. Open a command prompt and go to the newly created "precompile" directory. 3. Run a command similar to the following: java -jar JSPPrecompile.jar -u baseURL -f inputfile where baseURL is the P6 URL and inputfile is the location of the P6 EAR file. Note: The file path of the P6 EAR file cannot contain spaces. For example, assuming a standard P6 installation on WebLogic, the command should look similar to the following: java -jar JSPPrecompile.jar -u http://localhost:7001/p6 -f p6home/p6.ear
It will take close to 15 minutes to compile. Configuring Performance in Services Settings To set your performance settings: 1) Open the P6 Administrator application. 2) In the Configurations tab, expand your configuration. 3) Expand Services/Performance. a. In the Use Enterprise Summary field, choose true to use enterprise level summary data for resources and roles (EPS records). Choose false to use Project records. This setting specifies whether you want to
use EPS level records or Project level records to draw resource or role histograms. If true, performance is better because the histogram uses only one record (EPS record). If false, the histogram uses a larger number of records (Project records) to draw the histogram chart, so performance is slower. Note that histogram data is more accurate when the setting is false. b. In the Maximum Summary Node Count field, enter the threshold for displaying summarized data in views such as Resource Usage and Resource Analysis. If the number of child elements contained in a node exceeds this number, data does not display. The default is 1000. Enter anything from 1 - 50000.
I have left Maximum Summary Node as default.
Logon to P6 Console: Once the installations and configurations are done, Log on to P6 console as follows. http://
:/p6
I have created few projects.
To log on to admin config: http://:/p6/action/adminconfig
Logon to PR Admin: Logon to PR admin (with privuser) to set the configurations: http://:/pr/admin/login
Check the connection details are updated properly and do a test connection.
Click Save.
Restart the PR managed server. Logon to PR:
Click Launch P6 progress Reporter. But, still you cannot logon since you need to assign the users to create timesheet in PR. Now logon to P6 web and Administer -> User Access -> Users -> Select the user you want to give access to Progress Report and click on module Access. Enable Progress Reporter as shown below.
Meanwhile, Go to Resources -> Administration -> Resource Management -> Resources and create a resource or select the existing resource which you want to fill time sheet and in the settings tab, Progress Reporter -> Select Timesheet User Login ( The user you want to book the time sheet).
Now launch the Progress reporter.
Now it got logged in:
