Primavera Web Access 6.1 SP2

P6 Web Access
Release: 6.1 SP2
Release Date: December 2008

Contents

· Fixes and New Features from Previous Fix Packs

· Prerequisites

· Files Included with the Patch

· Deployment Instructions

Fixes and New Features from Previous Fix Packs

This service pack includes fixes and new features from previous 6.1 Web Access service packs and fix packs, as described below. For details, refer to the solution ID in the Primavera Knowledge Base.

· Support for LDAP referrals. LDAP referral is a method for a domain controller to indicate to a client application that it does not have a copy of a requested object, and giving the client a location where the object might be found. The client can then use DNS to search for it.

· prim52815: Histogram timescale does not stay set in Team Usage view.

· prim62410: Request Workflow with UDF multiplied by 10 with comma.

· prim62891: Unable to Export a subset of Activities to Excel via P6 Web.

· prim65157: Legends do not print in color in the Web Application.

· prim66837: Potential security issues with Primavera 6.1 Web Application.

· prim69141: Duration Type rules are not always followed when updating Role Budgeted Units/Time in P6 Web Access.

· prim70515: Cross-site scripting security enhancements.
This service pack includes an additional security feature that protects against cross-site scripting attacks. This new feature enables the server to do additional checks against URL requests to determine if the request is legitimate, or whether it contains unsafe parameter values. In essence, it acts like a blacklist filter against all URL parameters. If a page request is considered unsafe by the server, a 403 error (Access Forbidden) will be returned to the browser.
This feature is off by default, and can be enabled by adding a JVM parameter to the application server’s JVM environment. See prim70515 for application server-specific instructions.

Prerequisites

This Primavera service pack can be applied to any P6 Web Access version 6.1 deployment, including previous service packs and hot fixes.

Files Included with the Patch

The following files are included with this patch:

61toSP2Upgrade.jar
6.1sp2_readme.txt

Deployment Instructions

After downloading the 61SP2_WebAccess.zip file and extracting its contents, follow the instructions in 6.1sp2_readme.txt to upgrade your existing myprimavera.ear file. Then use the following instructions to deploy your upgraded myprimavera.ear file.

WebSphere 6.1 (Windows, AIX, RedHat Linux, and Solaris)

1. Log in to the WebSphere Administrative Console.

2. In the left-hand navigation tree, expand Applications and click the Enterprise Applications link.

3. Check the box next to Primavera and click Stop.

4. When the process completes, check the box next to Primavera again, then click Uninstall.

5. When the uninstall is complete, save the configuration. NOTE: The save option might be presented more than once. Click both Save options (top and middle) until Master Configuration has been saved successfully.

6. Log out of the WebSphere Administrative Console, then stop the WebSphere Application Server.

7. On the WebSphere server, the Primavera.ear directory might appear multiple times. Search the machine for Primavera.ear directories. They might be located in the <WebSphere home >\installed apps\<server name> directory. Delete all Primavera.ear directories.

8. Copy the new myprimavera.ear file into the < P6 Web Access home> directory.

9. Restart the WebSphere Application Server.

10. Log in to the WebSphere Administrative Console.

11. In the left-hand navigation tree, expand Applications and click Install New Application.

12. Point the application server to the location of the new myprimavera.ear file in the <P6 Web Access home> directory.

13. Enter the myPrimavera context root (default is myPrimavera) and click Next.

14. On the New Install Application screen, check the box next to Pre-compile JSP, then click Next.

15. On the Map Modules to Server screen click the checkbox for myprimavera and click Next.

16. On the Map Virtual Hosts for Web Modules screen click the checkbox for myprimavera and click Next.

17. Verify the installation options and click Finish (it could take up to 30 minutes or longer to precompile).

18. Save to the Master Configuration.

19. Close the Adminstrative Console.

20. Restart the WebSphere application server.

WebLogic 9.2 (Windows, Solaris, and HP-UX)

1. Stop the myPrimavera/WebLogic application server.

2. Overwrite the existing ear file in the <P6 Web Access home> directory with the extracted myPrimavera.ear file.

3. Overwrite the myPrimavera.ear file in the \bea\user_projects\domains\<mydomain>\autodeploy\ directory with the version in the <P6 Web Access home> directory.

4. Go to \bea\user_projects\domains\<mydomain>\servers\AdminServer\stage\ and delete the _appsdir_myprimavera_ear directory.

5. Go to \bea\user_projects\domains\<mydomain>\servers\AdminServer\tmp\_WL_TEMP_APP_DOWNLOADS and delete the _appsdir_myprimavera_ear directory.

6. Go to \bea\user_projects\domains\<mydomain>\servers\AdminServer\_WL_user and delete the _appsdir_myprimavera_ear directory.

7. Start the WebLogic Server.

JBoss 4.0.5

1. Stop the myPrimavera/JBoss application server.

2. Overwrite the existing ear file in the <P6 Web Access home> directory with the extracted myPrimavera.ear file.

3. Overwrite the myPrimavera.ear file in the <JBoss installation folder>\server\<server name>\deploy\ directory with the version in the <P6 Web Access home> directory.

4. Go to <JBoss home>\server\<server name>\tmp\deploy and delete the tmpXXXXXmyprimavera.ear-contents directory and the tmpXXXXXmyprimavera.ear file.

5. Go to < JBoss home >\server\<server name>\work\jboss.web\localhost and delete the myprimavera directory.

6. Start the myPrimavera/JBoss application server.

Copyright © Primavera 1999-2008. All rights reserved.