Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Transcription

1 Installation and Upgrade Guide for Primavera Portfolio Management 9.1

2 Copyright , Oracle and/or its affiliates. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR , Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate failsafe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. 2

3 Types of installation This document describes the installation of Primavera Portfolio Management. There are two types of installations, each with their own installation steps: New Installation A New Installation is an installation in which you are installing Primavera Portfolio Management on a server which does not and did not have any version of Primavera Portfolio Management (formerly Primavera ProSight ) installed on it. For this type of installation, follow these steps: 1. Verify the prerequisites. See below. 2. Login to your server with administrative privileges. 3. Install Primavera Portfolio Management. Refer to the instructions in Chapter Configure a database. In this step you will either create a new Primavera Portfolio Management database, or connect to an existing Primavera Portfolio Management database (from Primavera Portfolio Management (formerly Primavera ProSight ) 5.0 SP3 and later versions). Refer to the instructions in Chapter Configure the SMTP Server Smart Host. Follow the instructions in Chapter Verify the installation, as per the instructions in Chapter 5. Upgrade from Primavera Portfolio Management (formerly Primavera ProSight ) 5.0 and later An Upgrade from Primavera Portfolio Management (formerly Primavera ProSight ) 5.0 and later is an installation in which you are installing Primavera Portfolio Management 9.1 over an existing installation of any version of Primavera Portfolio Management (formerly Primavera ProSight ) 5.0 and later (including for example installing a Primavera Portfolio Management 9.1 Service Pack). For this type of installation, follow these steps: 1. Verify the prerequisites. See below. 2. Login to your server with administrative privileges. 3. Install Primavera Portfolio Management without uninstalling the older version of Primavera Portfolio Management (formerly Primavera ProSight ). Refer to the instructions in Chapter The database will be automatically upgraded during the install. The instructions in Chapter 3 can therefore be skipped. 5. Configure the SMTP Server Smart Host if necessary. Follow the instructions in Chapter Verify the installation, as per the instructions in Chapter 5. 3

4 Note on Application Pools Note that the settings of the ProSightApplicationPool in IIS changed in Primavera Portfolio Management (formerly Primavera ProSight ) 9.1 compared to earlier versions of Primavera Portfolio Management (formerly Primavera ProSight ). Any application pools that were created by cloning the ProSightApplicationPool should be deleted and created again by cloning the Primavera Portfolio Management 9.1 ProSightApplicationPool. 4

5 Configurations Primavera Portfolio Management can be installed in varying configurations, depending on your requirements. As a minimum, every installation of Primavera Portfolio Management must consist of one and only one instance of the Primavera Portfolio Management Primary Back-End, one or more instances of the Primavera Portfolio Management Front-End, and one database server. Common configurations supported are: One machine, running the Primavera Portfolio Management Primary Back-End and the Primavera Portfolio Management Front-End, as well as the database server. An environment comprised of two machines, one of which hosts the Primavera Portfolio Management Primary Back-End and the Primavera Portfolio Management Front-End, the other hosting the database server. An environment comprised of two machines, one of which hosts the Primavera Portfolio Management Front-End, the other hosting the database server and the Primavera Portfolio Management Primary Back-End. An environment comprised of three machines, one of which hosts the Primavera Portfolio Management Front-End, another hosting the Primavera Portfolio Management Primary Back- End, and the third machine hosting the database server. An environment comprised of more machines, one of which hosts the Primavera Portfolio Management Primary Back-End, several machines hosting the Primavera Portfolio Management Secondary Back-End, several machines hosting the Primavera Portfolio Management Front-End and participating in a Network Load Balancing (NLB) cluster, and one machine hosting the database server. For all configurations, make sure all servers are in compliance with the prerequisites as listed below. 5

6 Prerequisites For detailed prerequisite information including version numbers, please refer to the Primavera Portfolio Management Platform Requirements in the Readme document. A Primavera Portfolio Management server must be configured with: 1. Microsoft Windows 2003 or 2008 Server. This server must be set up as an application server. Use the Configure Your Server Wizard in Administrative Tools to accomplish this. 2. All Critical Updates for Windows 2003 or 2008, delivered via Automatic Update or installed from the Microsoft Windows Update site. 3. On Windows 2003: Microsoft Internet Information Services (IIS) 6.0, which is part of Windows On Windows 2008: Microsoft Internet Information Services (IIS) 7.0, which is part of Windows To use Primavera Portfolio Management Collaboration features, you will also need to install SMTP; on Windows 2003 this is the SMTP Service part of IIS, while on Windows 2008 this is referred to as the SMTP Server. 4. Microsoft Transaction Server (MTS), which is part of Windows 2003 or Microsoft Distributed Transaction Coordinator (MSDTC), which is part of Windows 2003 or Client access software for your database server of choice, as follows: a. If the database server resides on the same physical machine as the application server: i. If the database server software is Microsoft SQL Server 2005 or 2008: The necessary software is installed when you installed the database server. No further action is needed. ii. If the database server is Oracle 10g Release 2 or Oracle 11 Release 2: The necessary client software (Oracle InstantClient) is installed by the Primavera Portfolio Management installer. No further action is needed. b. If the database server resides on another physical machine: i. If the database server software is Microsoft SQL Server 2005 or 2008: Install Microsoft SQL Server 2005 or 2008 Client Access software on the application server. ii. If the database server is Oracle 10g Release 2 or Oracle 11 Release 2: The necessary client software (Oracle InstantClient) is installed by the Primavera Portfolio Management installer. No further action is needed. 7. The person running the Primavera Portfolio Management installer needs to have full administrative privileges on the server. On Windows 2008 this requires logging in using the local administrator account, or disabling User Account Control (UAC), or starting the install by right-clicking the install executable and selecting Run as administrator. Note that on Windows 2008, if the install was not performed using the local administrator account, the Change option in the Control Panel s Software Explorer will not work; however, you will be able to change the list of installed features by running the original install from its source location by right-clicking the install executable and selecting Run as administrator. 8. If Microsoft SharePoint Portal Server 2003 is to be installed on the application server, its installation, including Extending any web sites, should be completed before installing Primavera Portfolio Management. If SharePoint Portal Server 2003 is installed after Primavera Portfolio Management has already been installed, the instructions included in 6

7 Microsoft Knowledge Base article (see should be followed. Please note that Primavera Portfolio Management should not be installed into a web site managed by SharePoint. When installing Primavera Portfolio Management on Windows 2003, please follow the instructions provided in steps When installing Primavera Portfolio Management on Windows 2008, please skip these instructions and instead follow the instructions provided in steps On Windows 2003: 9. After installing the above prerequisites, click Start, then Settings, then Control Panel, then Add or Remove Programs, then click Add/Remove Windows Components, then select Application Server and click the Details button. Verify that components are selected as shown in figure 1: Figure Select Internet Information Services (IIS), and then click the Details button. Verify that at least the following components are selected: a. Common Files b. Internet Information Services Manager c. SMTP Service d. World Wide Web Service (gray) 11. Select World Wide Web Service, and then click the Details button. Verify that at least the World Wide Web Service is selected. 7

8 12. On all servers (including the database server), if Service Pack 1 or later of Microsoft Windows 2003 Server is installed, click Start, then Programs, then Administrative Tools, then Component Services. In the tree on the left, click on the plus sign next to the Component Services node to open up the tree, then click on the Computers node, then click on the plus sign next to the Computers node to open it up, and then right-click the My Computer node underneath. Select Properties. In the resulting tabbed dialog box, click on the MSDTC tab. On this tab, click on the Security Configuration button. You will see the dialog box shown in figure 2: Figure 2 Verify that all settings are as shown above. In particular, pay attention to the checkbox next to Network DTC Access (which is checked), the checkboxes entitled Allow Inbound and Allow Outbound (which are checked), and the radio button which selects No Authentication Required. If you made any changes, click OK to accept them. A dialog box will inform you that MSDTC will be restarted. Click Yes, then click OK in the notification message box that states that MSDTC has been restarted, then click OK again to close the tabbed dialog box. Close Component Services. 8

9 On Windows 2008: 13. After installing the above prerequisites, click Start, then Control Panel, then Programs and Features, then click Turn Windows features on or off, then select Roles and scroll down until the Role Services section. Verify that Role Services are installed as shown in figure 3: Figure 3 9

10 14. Scroll further down until the Web Server (IIS) section and find the next Role Services section. Verify that Role Services for the Web Server are installed as shown in figure 4: Figure On all servers (including the database server), click Start, then Administrative Tools, then Component Services. In the tree on the left, click on the plus sign next to the Component Services node to open up the tree, then click on the Computers node, then click on the plus sign next to the Computers node to open it up, then click on the My Computer node, then click on the plus sign next to the My Computer node to open it up, then click on the plus sign next to Distributed Transaction Coordinator to open it up, then right-click on Local DTC. Select Properties. In the resulting tabbed dialog box, click on the Security tab. You will see the dialog box shown in figure 5: 10

11 Figure 5 Verify that all settings are as shown above. In particular, pay attention to the checkbox next to Network DTC Access (which is checked), the checkboxes entitled Allow Inbound and Allow Outbound (which are checked), and the radio button which selects No Authentication Required. If you made any changes, click OK to accept them. A dialog box will inform you that MSDTC will be restarted. Click Yes, then click OK in the notification message box that states that MSDTC has been restarted. Close Component Services. Note that the Microsoft.NET Framework 2.0 and 3.5, as well as ASP.NET, are automatically installed during the installation of Primavera Portfolio Management Previous versions of the.net Framework will remain installed and fully functional. Note that Primavera Portfolio Management does not require a Java Runtime Environment (JRE) or Java Virtual Machine (JVM) on client workstations or servers, and is indifferent to a JRE or JVM if installed. 11

12 2. Primavera Portfolio Management Installation To install Primavera Portfolio Management (PPM) follow these steps: 2.1 Insert the Primavera Portfolio Management optical media into the optical drive of the server. The following install screen will be displayed. If for some reason this screen does not appear, open Windows Explorer, highlight the driveletter containing the Primavera Portfolio Management CD, and doubleclick startup.hta. Click the link Install PPM 9.1. You may also double-click setup.exe to start the install without displaying this first screen. To start the install on 64-bit servers, double-click setup.exe do not click the link. 2.2 On Windows 2008, if User Account Control is enabled, this dialog box is displayed. Click. 2.3 The Choose Setup Language dialog box is displayed. Select the desired language in which the installation screens will be displayed, and click OK. Note that this does not influence the language in which the User Interface of Primavera Portfolio Management itself will be displayed. 12

13 2.4 If this is not the first time you install Primavera Portfolio Management on this computer, you will see the screen depicted in step 2.6. If this is the first time you install Primavera Portfolio Management on this computer, the screen depicted here will be displayed. Note that the exact list of prerequisites displayed depends on the platform and the state of the server. Click to continue. 2.5 The screen will indicate that the pre-requisite requirements listed are being installed. Please wait. 2.6 The following screen will be displayed. Please wait. The following screen may be displayed briefly. Please wait. 13

14 2.7 The Welcome screen is displayed. Click to continue. 2.8 The Customer Information screen is displayed. The fields User Name and Organization are by default filled out with default values from the computer installation. You may accept these values or correct them. Click to continue. 2.9 The Destination Folder screen is displayed. If you wish to change the folder into which Primavera Portfolio Management will be installed, click. If the displayed folder is acceptable, click continue with step to 14

15 2.10 If you clicked on the previous screen, the Change Current Destination Folder screen is displayed. Browse to or type in another folder to install into, or create a new folder. When done, click to return to the screen shown in step The Select Default User Interface Settings screen is displayed. Select the desired Default User Interface Skin: Oracle Blue or ProSight Classic. Note that individual users cannot change the User Interface Skin selection Select the desired Default User Interface Language. Note that each user can later individually change this default language selection. Click to continue. 15

16 2.13 The Feature Selection screen is displayed. Each instance of Primavera Portfolio Management must include one and only one installation of the Portfolio Management Primary Back- End, and at least one installation of the Portfolio Management Front-End. These may be installed on the same or on separate physical servers. For the simplest installation of all required features of Primavera Portfolio Management on one server, make sure that Portfolio Management Front-End and Portfolio Management Primary Back-End are both selected to be installed (as shown here). To install optional features, select the optional feature(s) you desire to install: If you wish to use the legacy SOAP RPC interface, select the SOAP RPC interface. If you wish to use the Web Services interface, select the Web Services interface. If you wish to use Propose, select Propose. After the install, follow the instructions in Chapter 7 to configure Propose. If you wish to use the Bridge for Project Management systems, select the Bridge for Primavera P6 and Microsoft Project Server. After the install, follow the instructions in Chapter 8 to configure the Bridge. For details on installing Primavera Portfolio Management in a scaled-out environment, see Chapter 6. Click to continue The Internet Information Server (IIS) Properties screen is displayed. Next to Install in:, select the Web Site you wish to install Primavera Portfolio Management. The Web Site to install into must have been created in Internet Information Server Manager prior to the install of Primavera Portfolio Management. 16

17 If you wish the Web Site selected to be redirected to the virtual directory created by Primavera Portfolio Management, select the checkbox next to Redirect Web Site to Primavera Portfolio Management. The Primavera Portfolio Management install automatically detects if a SSL certificate is already installed on your server. If no certificate is found, it will generate a self-signed SSL certificate for you, so that you will be able to use https (http protocol secured by SSL). Select to use https only for screens on which passwords are entered, or to use https for all screens. Click to continue The Internet Information Server (IIS) Properties screen is displayed. If your users will be accessing the Primavera Portfolio Management server with different URLs than displayed here by default (for example because your organization s DNS defines a different name for the server, or because Primavera Portfolio Management is hosted on a NLB cluster), correct the URLs accordingly. Click to continue The Ready to Install screen is displayed. Click to continue. 17

18 2.17 The Installing Primavera Portfolio Management screen is displayed. Please wait The InstallShield Wizard Completed screen is displayed. Read the text underneath the header to verify that Primavera Portfolio Management was successfully installed. If a New Installation was performed, the screen will display text stating that you should now run the Primavera Portfolio Management Console to create a new Primavera Portfolio Management database or to connect to an existing database. If an Upgrade from an earlier version of the product was performed, the screen will display text stating that Primavera Portfolio Management is currently connected to a database which may have been upgraded during this installation. Click wizard. to exit the 18

19 When performing a New Installation, continue with Chapter 3 to create or configure a database. When performing an Upgrade from an earlier version of the product, continue with Chapter 4. 19

20 3. Configure a database To configure a database for use with Primavera Portfolio Management, follow these steps: 3.1 If you just completed the install of Primavera Portfolio Management, you will see the install screen displayed here. If for some reason this screen does not appear, open Windows Explorer, highlight the driveletter containing the Primavera Portfolio Management installation media, and doubleclick startup.hta. Click the link Configure a PPM Database. Alternatively, run the Primavera Portfolio Management Console from the Start menu. 3.2 The Primavera Portfolio Management Console is displayed, with the Add Database window open. Select the checkbox next to Make this database the current Primavera Portfolio Management database. In the combo box next to Type:, select the type of database server on which your database resides. 20

21 3.3 If you selected SQL Server (versions 2005, 2008) as the database server type, fill out the field next to Name: by typing the name of the database. This can be the name of a new database, or the name of an existing database created by the current or a previous version of the product. In the field next to Server:, type the name of the database server. In the field next to User:, type a username of a database user with appropriate rights, and in the field next to Password:, type the password for this database user. Click. 3.4 If you selected Oracle ( , ) as the database server type, first select the appropriate connection method (TNS or EZ CONNECT) in the Method: field. For the TNS connection method, next fill out the field next to Service: by typing the name of the Oracle service. In the field next to User:, type the name of the Oracle schema that you are connecting to, or click to create a new Oracle schema using the Oracle Database Configuration Utility. In the field next to Password:, type the Oracle password for this schema. Click. Note that use of the TNS connection method requires a full Oracle database client to be installed on all Primavera Portfolio Management application servers. The Oracle InstantClient installed by the Primavera Portfolio Management installer is not capable of supporting TNS by itself. 21

22 For the EZ CONNECT connection method, next fill out the field next to Instance: by typing the name of the Oracle instance. In the field next to Server:, type the name of the Oracle database server. In the field next to User:, type the name of the Oracle schema that you are connecting to, or click to create a new Oracle schema using the Oracle Database Configuration Utility. In the field next to Password:, type the Oracle password for this schema. Click. For more information about the Oracle Database Configuration Utility and configuring Primavera Portfolio Management for operation with an Oracle database, please see the Primavera Portfolio Management Oracle 10g Configuration Supplement or the Primavera Portfolio Management Oracle 11g Configuration Supplement. 3.5 If you entered the name of a new database, the Creating a new database message is displayed to inform you that Primavera Portfolio Management will be stopped and restarted. Click. 3.6 If you entered the name of a new database, the Properties of New Database screen is displayed. Under Administrator Password, type an initial password for the Primavera Portfolio Management admin account. Under Confirm Password, enter the same password again. 22

23 Under First quarter start date, select the appropriate start date for the first quarter of the year as defined in your organization. (Important! Once set, the first quarter start date cannot be changed. The first quarter start date can only be set once, at the time a database is created with the Primavera Portfolio Management Console. The first quarter start date cannot be changed on existing databases.) Click. 3.7 If you entered the name of a new database, the Creating new database message is displayed. Please wait until the database is created and the Primavera Portfolio Management Console main screen is displayed again. 3.8 If you entered the name of an existing ProSight database (from Primavera Portfolio Management 5.0 SP3 or later versions), and this database has to be upgraded, the Old database message will be displayed to inform you that the database will be upgraded to version 9.1, and that Primavera Portfolio Management will be stopped and restarted. Click. The following message will be presented if the Database recovery model is not set to Simple. In this case, please contact your DBA and have him make the necessary change for the duration of the database upgrade. Then click. The database will be upgraded. Please wait until the database is upgraded; click OK on the message stating that the upgrade has completed. The Primavera Portfolio Management Console main screen is displayed again. 23

24 3.9 If you entered the name of an existing PPM database, the Changing databases message is displayed to inform you that Primavera Portfolio Management will be stopped and restarted. Click. Please wait until the database you entered is made the current database and the Primavera Portfolio Management Console main screen is displayed again The Primavera Portfolio Management Console main screen is displayed, with the database listed as the Current Database. Click to close the Primavera Portfolio Management Console. 24

25 4. Configure the SMTP Service Smart Host To use the Send Mail capability in Primavera Portfolio Management, the SMTP service must be configured properly. This requires that your SMTP mail server is specified as your "smart host", so that the IIS SMTP Service automatically routes any SMTP sent to your local server to your SMTP mail server for delivery. For more details, see the document Primavera Portfolio Management Configuring SMTP. 4.1 On the Taskbar, click Start, point to Settings, point to Control Panel, point to Administrative Tools, and then click Internet Information Services (IIS) Manager to open the IIS Manager. 4.2 Open the tree for your server. Right-click Default SMTP Virtual Server, and then click Properties. 25

26 4.3 Navigate to the Delivery tab, and then click Advanced. 4.4 Enter the name or IP Address of your SMTP mail server in the Smart Host* text box. (Contact your mail administrator if you do not know the name or IP Address of your SMTP mail server). Click to close the Advanced Delivery screen, and click again to close the SMTP Virtual Server Properties screen. Close IIS Manager. 4.5 Make sure that Simple Mail Transfer Protocol (SMTP) service is running. The SMTP service is part of the IIS Admin Service, so the IIS Admin Service must also be running. *(Note: Smart Host allows you to route all outgoing messages for remote domains through a smart host instead of sending them directly to the domain. This allows you to route messages over a connection that may be more direct or less costly than other routes. The smart host is similar to the route domain option for remote domains. The difference is that once a smart host is designated, all outgoing messages are routed to that server. With a route domain, only messages for the remote domain are routed to a specific server. 26

27 If you set up a smart host, you can still designate a different route for a remote domain. The route domain setting overrides the smart host setting. Type a Fully Qualified Domain Name (FQDN) or an IP address to identify the smart host. If you use an IP address, enclose it in square brackets [ ] (for example: [ ]) to increase system performance. Microsoft SMTP Service checks first for a name, then an IP address. The brackets identify the value as an IP address, so the DNS lookup is bypassed.) 27

28 5. Verifying the installation To verify that Primavera Portfolio Management has been installed correctly, follow these steps: 5.1 On the Primavera Portfolio Management server, or on any client workstation with network access to that server, open up Microsoft Internet Explorer. Type the URL you entered in step 2.15 above, into the browser s address bar, and hit Enter or click the little button in the browser s address bar. The Primavera Portfolio Management login screen will appear. Type a user name and password as appropriate for your Primavera Portfolio Management installation, and hit Enter or click the button. You should be logged into Primavera Portfolio Management. 28

29 6. Distributed Setup of Primavera Portfolio Management Primavera Portfolio Management can be installed in a distributed setup ( scale-out ), thereby spreading the load of the system over several physical servers. In a distributed installation, the Primavera Portfolio Management Primary Back-End is installed on one and only one server, while the Primavera Portfolio Management Secondary Back-End is installed on one or more other servers. The Primavera Portfolio Management Front-End is likewise installed on one or more servers. When installing the Primavera Portfolio Management Front-End on more than one server, it is necessary to install and configure a Microsoft Network Load Balancing (NLB) cluster on all servers hosting the Front-End. When installing the Primavera Portfolio Management Front-End on only one server, installing and configuring a Microsoft NLB cluster is not necessary, but all other steps documented here should be followed unmodified. Note that all servers must comply with the general prerequisites as outlined in the beginning of this Guide. In addition, these are the prerequisites for the NLB cluster and the Front-End servers participating in it: Fixed IP addresses on all servers participating in the NLB cluster One reserved fixed virtual IP address (i.e. not used by any physical server) Recommended: separate Network Interface Card (NIC) in each server participating in the NLB cluster, to route the NLB cluster communications NLB clusters can be set up and configured in many different ways, depending on overall network infrastructure, hosts, protocols, etc. The following section provides a basic guide on how to configure a NLB cluster. For more information, please refer to Microsoft s documentation. When installing the Primavera Portfolio Management Front-End on only one server, skip to step To install and configure the Network Load Balancing (NLB) cluster, follow these steps: 6.1 On a Windows 2003 Server which is not to become a member of the cluster, start the Network Load Balancing Manager by clicking Start, then Programs, then Administrative Tools, then Network Load Balancing Manager. 29

30 6.2 Right-click on the first node in the tree on the left called Network Load Balancing Clusters and select New Cluster. 6.3 In the IP address field, fill out the IP address of the cluster; this must be a virtual (i.e. reserved but unused) fixed IP address. 6.4 Check that the automatically filled out Subnet mask field, is filled out correctly. 6.5 In the Full internet name field, fill in the full name by which you will access the cluster of ProSight servers. The DNS system of the domain should be configured such that it will resolve this name to the virtual fixed IP address entered in step Click Next. 30

31 6.7 Click Next. 6.8 Click Edit. 6.9 Change Affinity from Single to None. Note: when using SSL with Primavera Portfolio Management, leave the Affinity setting at Single Click OK. 31

32 6.11 Click Next In the Host field, type the name or the fixed IP address of one of the Windows 2003 Server machines that is to become a member of the NLB cluster, then click the Connect button In the bottom half of the screen, select the interface that is to be used for NLB cluster communication. If the server has a Network Interface Card (NIC) dedicated to NLB cluster communication, select that interface. 32

33 6.14 Click Next Click Finish Network Load Balancing Manager will perform the requested operation and will show the status in the bottom part of its main screen. 33

34 6.17 When Network Load Balancing Manager successfully completes the configuration change, the bottom part of the screen will show that the operation succeeded To add another Windows 2003 Server to this NLB cluster, right-click the cluster name that was entered in step 6.5, and select Add Host to Cluster Repeat steps for each server to be added to the cluster When done adding hosts to the NLB cluster, close Network Load Balancing Manager. 34

35 To install the Primavera Portfolio Management Front-End, follow these steps: 6.21 If an NLB cluster has been set up and configured, complete the below instructions on each of the Windows 2003 or 2008 Server machines that have been made members of the NLB cluster. If installing the Primavera Portfolio Management Front-End on only one server, complete the below instructions on that server. Start the Primavera Portfolio Management setup by following the instructions of Chapter 2. In step 2.10, de-select the Portfolio Management Primary Back-End feature. If installing optional features (such as SOAP RPC, Web Services, Propose or the Bridge), these features must be selected and installed on all servers on which the Primavera Portfolio Management Front-End is installed. If installing on servers that are members of a NLB cluster, in step 2.12, change the server name in the proposed URLs to the cluster name entered in step 6.5. For example, if in step 6.5 the full Internet name of the cluster was entered as portfolios6.domain.com, the URLs in step 2.12 of the installation should look like To install the Primavera Portfolio Management Primary Back-End, follow these steps: 6.22 On a Windows 2003 or 2008 Server machine which is not part of a NLB cluster, install the Primavera Portfolio Management Primary Back-End. Start the Primavera Portfolio Management setup by following the instructions of Chapter 2. In step 2.10, de-select the Portfolio Management Front-End component. Note that there should be only one server running the Portfolio Management Primary Back-End component in a given installation of Primavera Portfolio Management. To install the Primavera Portfolio Management Secondary Back-End, follow these steps: 6.23 On a Windows 2003 or 2008 Server machine which is not part of a NLB cluster, install the Primavera Portfolio Management Secondary Back-End. Start the Primavera Portfolio Management setup by following the instructions of Chapter 2. In step 2.10, de-select the Portfolio Management Front-End component and the Portfolio Management Primary Back-End component, and instead select the Portfolio Management Secondary Back-End component. Note that the Portfolio Management Secondary Back-End component can be installed on as many servers as is necessary to achieve a given performance level in a given installation of Primavera Portfolio Management. 35

36 The following steps, from step 6.24 up to and including step 6.38, should be completed only if multiple Primavera Portfolio Management Front-End servers have been installed and are operating in a load-balancing cluster. If the Primavera Portfolio Management database is hosted on Microsoft SQL Server, follow these steps to create the ASPState database for persisting session information: 6.24 On one of the servers on which the Primavera Portfolio Management Front-End has been installed, run Microsoft SQL Server Query Analyzer Login to the Microsoft SQL Server which is hosting the Primavera Portfolio Management database, using the sa database login From the menu, select File, then Open. Navigate to \WINDOWS\Microsoft.NET\Framework\v on the local drive on which the Windows 2003 Server is installed Select the file installpersistsqlstate.sql and click Open From the menu, select Query, then Execute. The ASPState database will be created. When finished, close Microsoft SQL Server Query Analyzer Using Microsoft SQL Server Enterprise Manager, create a new SQL Server login called ASPState. Set the properties for this login as follows: Use SQL Server authentication and specify a password Set the default database to ASPState On the Database Access tab, allow access to the ASPState database only, as user ASPState, and grant the public and db_owner roles. 36

37 If the Primavera Portfolio Management database is hosted on an Oracle database server, follow these steps on the Primavera Portfolio Management Primary Back-End server to enable the Microsoft ASP.NET State Service for persisting session information: 6.30 Open up Registry Editor and locate the following registry value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\ Parameters\AllowRemoteConnection If the value AllowRemoteConnection doesn t exist, create a new REG_DWORD value named AllowRemoteConnection; set its value to By default, the ASP.NET State Service handles communications on port If desired, this can be changed by modifying the following registry value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\ Parameters\Port 6.32 Open up the Services screen, and start the ASP.NET State Service. Modify the settings for this service such that it will start automatically next time the server is restarted. To share the session information amongst all Primavera Portfolio Management application servers, follow these steps: On all of the Windows 2003 or 2008 Server machines (including the single Primavera Portfolio Management Primary Back-End server and any/all of the Primavera Portfolio Management Front-End servers as well as all of the Primavera Portfolio Management Secondary Back-End), use Notepad to open the file web.config which is located in the IisRoot folder off the Primavera Portfolio Management install directory. By default, this file would be located at C:\Program Files\Oracle\Primavera Portfolio Management\Portfolios\IisRoot. Locate the section which looks like the following: <sessionstate mode="inproc" timeout="1440"/> 6.35 If the Primavera Portfolio Management database is hosted on Microsoft SQL Server and an ASPState database was created as per the instructions in steps , modify this section such that it reads as follows: <sessionstate mode="sqlserver" sqlconnectionstring= "data source=sqlserver;user id=aspstate;password= ASPStatePassword" timeout="1440" /> where instead of sqlserver the actual name of the SQL Server hosting the ASPState database is used, and instead of ASPStatePassword the actual password for this account as set in step 6.29 is used. 37

38 6.36 If the Primavera Portfolio Management database is hosted on an Oracle database server and the ASP.NET State Service service was started as per the instructions in step , modify this section such that it reads as follows: <sessionstate mode="stateserver" stateconnectionstring="tcpip=ppmbackend:42424" timeout="1440" /> where instead of ppmbackend the actual name of the Primavera Portfolio Management Primary Back-End server is used, and if the default port was changed in step 6.31, the actual port number is used instead of Locate the <system.web> section, and within this section add the following new text: <machinekey validationkey="<nlb1>" decryptionkey="<nlb2>" validation="sha1" decryption="aes" /> Instead of <NLB1>, write 128 hexadecimal characters, representing the 64- byte validation key used by the SHA1 hashing algorithm. Instead of <NLB2>, write 64 hexadecimal characters, representing the 32-bit decryption key used by the AES encryption algorithm. For further instructions, explanations and how to generate stronger keys, please see the following MSDN article: Save the web.config file and close Notepad. 38

39 Important note in case Primavera Portfolio Management is not installed into the Default Web Site: Any web site other than the Default Web Site, is identified by a random number created by IIS when the web site is created (the Default Web Site is usually identified by the number 1). Because the number is random, it is different on each server. Within the ASPState database that contains the sessions, each session is identified by an identifier consisting of the full path to the application, for example: /lm/w3svc/ /root/prosight. In this path, the number is the random number identifying the web site. Since the random numbers are different on each server, the servers do not identify each other s sessions; each is simply writing its sessions to the ASPState database identified by its own random number. To fix this, it is necessary to ensure that the non-default web sites into which Primavera Portfolio Management is installed, all use the same random number. Fortunately, this change can be made even after Primavera Portfolio Management is installed. To look at the number representing the web site, open up regedit on each of the Microsoft Windows 2003 Server machines on which Primavera Portfolio Management was installed. Look up the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Primavera Portfolio Management\Portfolios\Server\UI\WebSite Note the value on one of the servers (we will call it the target value), and follow the below procedure to change the value of the non-default web site on all other Windows 2003 or 2008 Server machines (those that are members of the NLB cluster as well as the single server hosting the Primavera Portfolio Management Primary Back-End and the multiple servers hosting the Primavera Portfolio Management Secondary Back-End): 1. To change the random number of a non-default web site, one must first enable Direct Metabase Edit on the server(s) on which the change has to be made. a. Open up Internet Information Services (IIS) Manager. b. Right-click the computer name and select Properties. c. Place a checkmark next to Enable Direct Metabase Edit, and click OK. 2. Make a backup of the IIS Metabase XML file. The file is called Metabase.xml and is located in system32\inetsrv off the Windows directory. 3. Open up Metabase.xml in a text editor such as Notepad. 4. Use the Replace functionality to search for the non-default web site random number found in the above registry location on this server and replace it with the target value noted above (the value of one of the other servers to which we want to change). Change all instances of the number. Then save the Metabase.xml file. 5. Replace the value at the above registry entry such that it refers to the same target value. 6. Restart Primavera Portfolio Management. 7. Disable Direct Metabase Edit: a. Open up Internet Information Services (IIS) Manager. b. Right-click the computer name and select Properties. c. Clear the checkmark next to Enable Direct Metabase Edit, and click OK. 8. Repeat the above procedure on all other servers on which the random number needs to be changed. 39

40 Important note in case SSL is used in the load balancing environment: The certificates used on all Primavera Portfolio Management Front-End server(s) as well as on the single Primavera Portfolio Management Primary Back-End Server and the multiple Primavera Portfolio Management Secondary Back-End server(s) must all be in sync. To achieve this, please follow these steps: 1. Install a certificate on one server as detailed in the document Primavera Portfolio Management Enabling SSL. 2. Use IIS Manager on this server to export the certificate into a pfx file. 3. Use IIS Manager on all other servers to import the pfx file as a certificate. To connect Primavera Portfolio Management to its database and complete the installation, follow these steps: 6.39 When done installing Primavera Portfolio Management, follow the steps in Chapter 3 to connect each of the servers (Primavera Portfolio Management Front-End server(s) as well as the single Primavera Portfolio Management Primary Back-End Server and the multiple Primavera Portfolio Management Secondary Back-End server(s)) to the same Primavera Portfolio Management database. First connect all Primavera Portfolio Management Front-End servers, then connect the Primavera Primary Back- End server, and finally connect all Primavera Portfolio Management Secondary Back- End servers. Note that in order to change databases, the Primavera Portfolio Management Console must be run and configured accordingly on all of the servers separately. Also note, that if a new Primavera Portfolio Management database is created, the actual database creation will be performed from the (first) Primavera Portfolio Management Front-End server on which the Console is run, while all other servers will then need to be connected to this newly created database using the Console To configure SMTP, follow the steps in Chapter 4 on each of the servers To verify the installation, follow the steps in Chapter 5. As the URL, enter the Primavera Portfolio Management URL with the server name being the full Internet name of the NLB cluster, as entered in step 6.5. This ensures connecting to the cluster (which will forward the request to the server least busy at this particular moment) instead of to a particular server in the cluster. Note that if the DNS system of the domain was not configured to resolve the NLB cluster name, you must use the IP address of the cluster as entered in step 6.3 instead. 40

41 7. Configuring Propose Enabling the ProSight Guest user 7.1 Start Internet Explorer on any server or workstation. Go to the URL appropriate for your Primavera Portfolio Management installation and log on as a Primavera Portfolio Management administrator Click Setup, and in the resulting screen select Users from the dropdown box at the top. In the right pane, select the row representing the "ProSight Guest" user, which is currently grayed out. Click Enable. 7.4 At the question "Enable user ProSight Guest?", click OK. 41

42 7.5 The row representing the "ProSight Guest" user will become black to indicate that the user has been enabled. Note that the "ProSight Guest" user is not counted as a "Named User" in the terms of your product license. Note that the "ProSight Guest" user must have its License Type set to "Full-use". Granting access to Propose to the ProSight Guest user In the "Setup" screen, select Modules from the drop-down box at the top. Select the Add-Ons folder in the left pane, and select the Propose module in the right pane. Click Edit. 7.8 Click Add and select the "ProSight Guest" user from the list, making sure that its "Permission Set" is "Read." This grants "Read" permission to the ProSight Guest user, allowing this user to use Propose. If the Permission is not "Read", use the Edit button to set it to Read (for more information refer to the Primavera Portfolio Management Users Guide). Click OK to close the Module dialog box. 7.9 Close the Setup screen. 42

43 Configuring a Form to be used with Propose Specific requirements for a Form to allow use by Propose To allow use of a Form by Primavera Portfolio Management Propose, the Form must comply with the following special requirements: 1. The Form must be usable in "New" mode, in which the Form creates a new Item or Portfolio. To comply with this requirement, the Form must include the "Item Name" component on its first Tab. 2. The Form must have a "Default Home Portfolio" assigned. The "ProSight Guest" user must have at least "Create" permission in this Home Portfolio. Note that by assigning a "Default Home Portfolio" to the Form, it becomes unnecessary to include the "Item Parent" component on any one of its tabs. 3. The Form must be accessible to the "ProSight Guest" user, that is, the "ProSight Guest" user must have at least "Read" permission on the folder in which the Form resides. Defining a Form to be used by Propose 7.10 If you are already logged in as an administrator, skip to the next step. Start Internet Explorer on any server or workstation. Go to the URL appropriate for your Primavera Portfolio Management installation and log on as a Primavera Portfolio Management administrator Click Setup, and in the resulting screen select Forms from the dropdown box at the top Click the down arrow to the right of the New button to open the dropdown box, and select Folder. 43

44 7.13 In the New Folder dialog, type the name of the folder that will be used to store the Form(s) that will be used with Propose, for example "Propose Forms". Click OK. The folder will be created While the newly created folder is highlighted, click the Edit button. The Folder Wizard will open Click on "Security" on the left hand side to go directly to the Security step of the wizard. 44

45 7.16 Click Add to add a new security setting In the resulting "Add User" screen, make sure that "Read" is selected as the "Permission", and select the "ProSight Guest" user Click OK In the Form Wizard Security step, the newly added setting for the "ProSight Guest" user is shown Click Finish. 45

46 Note that this configuration grants the ProSight Guest user "Read" on all Forms contained in the folder "Propose Forms" and in any folder below the "Propose Forms" folder which inherits its security settings. It is recommended not to grant "Read" permission to the ProSight Guest user on any folders which do not contain Forms that need to be accessible via Primavera Portfolio Management Propose In the Setup screen, keep the newly created folder selected. Click the down arrow to the right of the New button to open the drop-down box, and select Form to start creating a new Form in the folder. This Form will by default inherit the security settings from the folder In the "New Form" screen, enter a Name for the Form in the Name field Click Next In the "Tabs" step of the wizard, click New to add a new Tab or click Add to add an existing Tab to this Form. 46

47 7.25 The Tab to be used as the first Tab in the Form must have the Item Name component. Note: it is not necessary to include the Item Parent component if a Default Home Portfolio is assigned in step For more information on how to design and configure Tabs, see the Primavera Portfolio Management Users Guide When finished adding or creating Tabs for the Form, click Next In the "Defaults" step of the wizard, select the option Allow Creation of New Items, and select one of the Creation Options to indicate what type of Item should be created by the Propose Form. Open the Default Home Portfolio combo box and select an appropriate Portfolio as the Default Home Portfolio for the Form. It is highly recommended to use a non-calculating Portfolio as the Default Home Portfolio for the form. Note that by selecting a Default Home Portfolio here, it becomes unnecessary to include the Item Parent component in any one of the tabs of the form Click Finish to complete the wizard. 47

48 Configuring Security on the Default Home Portfolio The following steps show how to configure the security on the Default Home Portfolio for the ProSight Guest user to only have "Create" permission, thereby turning the Default Home Portfolio into a type of "mailbox" into which the ProSight Guest user can "drop" the Items to be created using Propose In the "Setup" screen, select Items and Portfolios from the dropdown box at the top Navigate to the Portfolio selected as the Default Home Portfolio in step 7.28, and click Edit In the Portfolios wizard screen, select the "Security" step Click Add to add a new security setting. 48

49 7.34 In the resulting screen, select "Edit and Create" in the Permission combo box Select the "ProSight Guest" user and click Edit In the resulting screen, clear all check boxes in the "Allow" column except for the first "Create" permission, indicating that the "ProSight Guest" user can create portfolios and items in this Portfolio, but cannot do anything else Click the Items tab. 49

50 7.38 On the "Items" tab, clear all checkboxes such that no permissions are assigned to the "ProSight Guest" user on the items to be created within Propose Click OK In the "Add User" screen, the "Permission" combo box will now show "Custom" Click OK. 50

51 7.42 In the "Security" step of the Portfolio wizard, the "Permission Set" for the "ProSight Guest" user will show as "Custom" Click Finish When done, close the Setup screen. Configuring security to allow creation of sub-items and submission of documents using Propose The following steps show the additional security settings that should be made on the Default Home Portfolio for the ProSight Guest user to allow the submission of documents through Propose In the "Setup" screen, select Items and Portfolios from the dropdown box at the top Navigate to the Portfolio selected as the Default Home Portfolio in step 7.28, and click Edit. 51

52 7.47 In the Portfolios wizard screen, select the "Security" step Select the "ProSight Guest" user and then click Edit to modify the existing security setting In the resulting screen, in the "Allow" column, select the "Create" check box under "Sub-items, Deliverables, Action Items, Links, Contacts and Documents". This indicates that the "ProSight Guest" user is granted the right to Create sub-items, deliverables, action items, links, contacts and documents in portfolios Click the Items tab. 52

53 7.51 On the "Items" tab, in the "Allow" column, select the "Create" check box under "Sub-items, Deliverables, Action Items, Links, Contacts and Documents". This indicates that the "ProSight Guest" user is granted the right to Create sub-items, deliverables, action items, links, contacts and documents in items Click OK In the "Security" step of the Portfolio wizard, the "Permission Set" for the "ProSight Guest" user will show as "Custom", and the text under "Description" will include the ability to create sub-items, deliverables, action items, links and documents Click Finish When done, close the Setup screen. 53

54 Obtaining the URL to be used to access the Form with Propose The URL format The format of the URL to be used to access a particular Form using Primavera Portfolio Management Propose, is defined as the URL of that Form when put in "New" mode, while replacing the word prosight by the word propose within the URL. The following steps show how to obtain the correct URL If you are already logged in as an administrator, skip to the next step. Start Internet Explorer on any server or workstation. Go to the URL appropriate for your Primavera Portfolio Management installation and log on as a Primavera Portfolio Management administrator In the main Primavera Portfolio Management screen, select the Forms module Select the Form to be used with Propose in the Form selection box Click the New button From the "Collaborate" menu, select Obtain Page Address Make sure that both Include item as well as Include form are selected Click the Copy button to copy the URL to the clipboard, then click Close to close the window. 54

55 7.63 Paste the URL from the clipboard into the desired location, for example into the HTML code of a page which should open the Propose Form. (For testing purposes, paste the URL directly into the Address Bar of Internet Explorer.) Original URL as copied by Obtain Page Address: View.htm?window=form&formName=Prop ose%20form&tabname=propose%20tab%2 01&itemID=-2&newItemType= Replace prosight by propose The resulting URL will access the Form using Propose. Resulting URL for accessing the Form through Propose: iew.htm?window=form&formname=propo se%20form&tabname=propose%20tab%20 1&itemID=-2&newItemType= When pasting the resulting URL directly into Internet Explorer, the Form will be displayed in Primavera Portfolio Management Propose. 55

56 8. Configuring the Bridge for Project Management Systems 8.1 After the install has been completed, start Internet Explorer on any server. Go to the URL appropriate for your Primavera Portfolio Management installation and log on as a Primavera Portfolio Management administrator Click Setup, and in the resulting screen select Modules from the drop-down box at the top. Select the Add-Ons folder in the left pane, and select the PM Bridge module in the right pane. Click Edit. 8.4 Click Add and select the appropriate group or user from the list. As an example we selected the All group from the list. Make sure that the group or users Permissions Set is Read. This grants Read permission to the appropriate users of Primavera Portfolio Management, allowing them to use the PM Bridge. If the Permission is not Read, use the Edit button to set it to Read (for more information refer to the Primavera Portfolio Management Users Guide). Click OK to close the Module dialog 56

57 box Now select the MS Project 2007 Bridge module in the right pane. Click Edit. 8.7 Click Add and select the appropriate group or user from the list. As an example we selected the All group from the list. Make sure that the group or users Permissions Set is Read. This grants Read permission to the appropriate users of Primavera Portfolio Management, allowing them to add a connection to a MS Project Server 2007 in the Bridge. If the Permission is not Read, use the Edit button to set it to Read (for more information refer to the Primavera Portfolio Management Users Guide). Click OK to close the Module dialog box. 57

58 8.8 Now select the appropriate P6 Bridge module in the right pane. As an example we selected the P6 v8.0 Bridge module. Note that if you have multiple versions of P6 within your organization and the Bridge should be able to connect to all of them, you may repeat this procedure for the other P6 Bridge modules. 8.9 Click Edit Click Add and select the appropriate group or user from the list. As an example we selected the All group from the list. Make sure that the group or users Permissions Set is Read. This grants Read permission to the appropriate users of Primavera Portfolio Management, allowing them to add a connection to a Primavera P6 server in the Bridge. If the Permission is not Read, use the Edit button to set it to Read (for more information refer to the Primavera Portfolio Management Users Guide). Click OK to close the Module dialog box Close the Setup screen, log out of Primavera Portfolio Management and log back on as an administrator. 58

59 Connecting to one or more MS Project Servers 8.12 If you are already logged in as an administrator, skip to the next step. Start Internet Explorer on any server. Go to the URL appropriate for your Primavera Portfolio Management installation and log on as a Primavera Portfolio Management administrator From the Primavera Portfolio Management Tools menu, select Bridge Console The Bridge Console screen will open Click the Add button. A small popup will allow selection of the type of Project Management system to add. Highlight Microsoft Project 2007 and click it. The Bridge Settings Wizard will open. 59

60 Under Server Name:, fill in the name of the MS Project Server you are adding. This name is used for descriptive purposes within Primavera ProSight only. Under MS Project Server URL:, fill in the URL of the MS Project Server you are adding. Under Reporting Database Server Name:, fill in the name of the database server hosting the Microsoft Project Server 2007 Reporting Database. Under Reporting Database Name:, fill in the name of the Microsoft Project Server 2007 Reporting Database. Under Description:, you may add a description of the MS Project Server you are adding. Under Access to MS Project Server:, under Authentication:, select the authentication method for the Microsoft Project Server: Forms Authentication or Windows Authentication. Under User Name:, enter the MS Project Server user name of a user with full access to the MS Project Server you are adding. Under Password:, enter the password of the user with full access to the MS Project Server you are adding. Click Finish To add another MS Project Server, go back and repeat the process from step

61 Connecting to one or more Primavera P6 Enterprise Project Management servers 8.26 If you are already logged in as an administrator, skip to the next step. Start Internet Explorer on any server. Go to the URL appropriate for your Primavera Portfolio Management installation and log on as a Primavera Portfolio Management administrator From the Primavera Portfolio Management Tools menu, select Bridge Console The Bridge Console screen will open Click the Add button. A small popup will allow selection of the type of Project Management system to add. Highlight Primavera P6 and click it. The Bridge Settings Wizard will open. 61

62 Under Server Name:, fill in the name of the Primavera P6 Server you are adding. This name is used for descriptive purposes within Primavera Portfolio Management only. Under P6 Web Services URL:, fill in the URL of the P6 Web Services for the P6 server you are adding. Under P6 Web Access URL:, fill in the URL for the P6 Web UI ( My Primavera ). Under Description:, you may add a description of the MS Project Server you are adding. Under Access to Primavera P6, under User Name:, enter the P6 user name of a user with full access to the P6 server you are adding. Under Password:, enter the password of the user with full access to the P6 server you are adding. Under Authentication:, select the same authentication method that was selected when the P6 Web Services were installed. Select either HTTP or HTTPS as the communication protocol between Primavera Portfolio Management and Primavera P6. If Username Token is selected in step 8.36 and HTTPS is selected in step 8.37, then by clicking on Settings the Authentication Settings dialog will open. In this dialog you may configure Message security and enter the thumbprint of the SSL certificate that should be used for the signing and encrypting of the messages. Click OK when done. Click Finish. 62