Table of Contents

The goal of configuration planning is to help the IT group, executives, and process owners to select a Project Portfolio Management 2009 R1 configuration that meets the needs of the organization. Ultimately, the goal is to provide users with an agreed-upon levels of service as they perform their work, while consuming predictable and maintainable levels of system resources as service is delivered.

An important part of this process is for your organization to identify common usage patterns (including number of users, user roles, and security requirements), estimated data loads and network usage, and average/peak system usage. Use these measurements to help identify the Project Portfolio Management 2009 R1 configuration that will work best for your organization.

After you have a high-level understanding of what your Project Portfolio Management 2009 R1 deployment will look like (who will be using Project Portfolio Management 2009 R1, how often, and when), the next step is to deploy a Project Portfolio Management 2009 R1 in a baseline configiration. This baseline configuration (including the baseline hardware pre-requisites) is not intended to be a recommended configuration; rather it represents a starting point in the configuration planning process. It is from this baseline configuration that you will then continue to configure Project Portfolio Management 2009 R1 so that it accurately reflects your organization's work and resource structures, project management style, and data capture and reporting needs. A baseline configuration will evolve into a pilot and (eventually) into a production environment that meets your organization's business goals and requirements and into a project management application which everyone in your organization will use.

For many enterprise software deployment processes, such as installing Project Portfolio Management 2009 R1, configuration drivers often come to the information technology (IT) group from outside of IT. Executives and process owners often play a large role in the decision-making process around how Project Portfolio Management 2009 R1 should be deployed, including helping to define how Project Portfolio Management 2009 R1 will be used to help address specific business needs and how it should be configured so that Project Portfolio Management 2009 R1 can be used to help achieve specific business goals.

This kind of top-down decision-making process typically arrives at the IT group in the form of business and technical requirements. The following diagram compares executive, process owner, and IT involvement:

Executives help initiate the process of deploying Project Portfolio Management 2009 R1 by driving the vision for what will become an IT implementation project. At this level, IT group representatives work with the executives to define the requirements and scope of the deployment and to allocate the budget and with process owners to help define project and portfolio management requirements, analyze usage patterns, and to identify business process changes and improvements.

Additionally, the IT group works to define Project Portfolio Management 2009 R1 architectural requirements as determined by the performance, capacity, and service level needs of your organization. During this part of the deployment process, Serena Professional Services can arrange a product demonstration that can help show how Project Portfolio Management 2009 R1 can most effectively be used to address your organization's planned requirements and goals.

As the deployment path gets closer to a pilot, a test environment, or a small-scale deployment, the IT group will be working closely with process owners to help ensure that Project Portfolio Management 2009 R1 is configured to your organization's specific needs. These needs include adding the right items, creating needed custom attributes, defining work and resource breakdown structures, adding custom reports, and so on. Serena Professional Services can work closely with your organization to help ensure that all of your organization's configuration requirements are met.

Project Portfolio Management 2009 R1 can be scaled-up and it can be scaled-out. The decision to do either is dependent on several factors, including maintenance costs, hardware budget, and more, such as:

There are four zones. Zone 1 represents low concurrency and simple configuration and usage patterns. Zone 4 is highest end of the spectrum, representing high concurrent user load and complex data and usage patterns.

From a hardware and software perspective, Project Portfolio Management 2009 R1 has a relatively simple deployment story. Before deploying Project Portfolio Management 2009 R1, you should understand the four components of Project Portfolio Management 2009 R1, how they interact with each other, and what they are used for. As part of this analysis, you should understand the hardware and software requirements for each of the Project Portfolio Management 2009 R1 components, and the different configuration options that are available. Before installing any component of Project Portfolio Management 2009 R1, you should acquire hardware with the appropriate specifications, and then you should install and configure the appropriate version of the Windows Server operating system, SQL Server 2005 (and/or SQL Server 2005 Reporting Services), and other software prerequisites (such as components like IIS or ASP.NET) on to the computers that will be running the various components of Project Portfolio Management 2009 R1.

Project Portfolio Management 2009 R1 has three layers (client, application, and data) and four components (client, application, reports, and database).

From a configuration perspective, another important part of your deployment strategy includes thorough configuration planning and rigorous testing of that configuration in a non-production setting. Part of your configuration planning should include understanding your organization's business requirements and processes needed to manage your portfolio. This helps ensure Project Portfolio Management 2009 R1 will be configured to address your needs.

The Project Portfolio Management 2009 R1 Web server is the core Project Portfolio Management 2009 R1 component in a deployment. Project Portfolio Management 2009 R1 uses Microsoft .NET Framework, version 2.0 and leverages many of its enterprise application capabilities, including memory management, database access, and Web services. Project Portfolio Management 2009 R1 Web services are built on ASP.NET 2.0 and are hosted in Microsoft Internet Information Services (IIS). Project Portfolio Management 2009 R1 reports leverage Microsoft SQL Server 2005 and SQL Reporting Services, in addition to using Web services.

In addition to the hardware and software requirements listed in this section, you should review the software configuration prerequisites necessary for a successful deployment.

The Project Portfolio Management 2009 R1 report server is both a database and application server that provides the reporting functionality of Project Portfolio Management 2009 R1. It requires SQL Server 2005 Reporting Services and access to the Project Portfolio Management 2009 R1 database.

If your server has sufficient capacity, the Project Portfolio Management 2009 R1 reports server can be installed on the same computer as the Project Portfolio Management 2009 R1 Web server. If you put the Project Portfolio Management 2009 R1 Web server and the Project Portfolio Management 2009 R1 reports server on the same hardware, use the recommended requirements as your organization's sizing baseline.

Project Portfolio Management 2009 R1 uses a SQL Server 2005 database server to store and protect portfolio data. Access to the repository is accomplished exclusively through an API defined for and used by the Project Portfolio Management 2009 R1 application; direct access to the SQL Server database is not recommended.

This section provides you with the deployment prerequisites for the database server used by Project Portfolio Management 2009 R1. The Project Portfolio Management 2009 R1 database is a data-intensive application. To help ensure that the Project Portfolio Management 2009 R1 database has adequate resources available to it, the average CPU utilization on the server running SQL Server 2005 (and the Project Portfolio Management 2009 R1 database) should be less than 25% of total CPU capacity (before the Project Portfolio Management 2009 R1 database is added).

Project Portfolio Management 2009 R1 has a zero-footprint client. That is, the user interface is implemented using HTML, JavaScript, and AJAX (Asynchronous JavaScript and XML) and requires no client installation. This means that any computer that is running Microsoft Internet Explorer 7.0 (recommended) or Internet Explorer 6.0 or later can access Project Portfolio Management 2009 R1. AJAX is a collection of programming technologies that efficiently deliver additional information to a browser when a user performs an action, without requiring a refresh of the entire page. JavaScript is the programming language that provides the interactive elements, such as pop-up menus, while AJAX uses XML to retrieve additional page data as needed, instead of all at once. When compared to traditional Web pages, this provides a much faster, and more seamless user experience.

This section provides you with the deployment prerequisites for the Project Portfolio Management 2009 R1 clients. The performance of Project Portfolio Management 2009 R1 clients can depend on the hardware capabilities of the client itself (older computers with less powerful processors and less RAM will not run as quickly as newer computers with more powerful processors and more RAM) and on the network environment in which the client is running (for example, if your environment has high levels of latency).

The standard deployment for Project Portfolio Management 2009 R1 relies on dedicated hardware for the three primary components of Project Portfolio Management 2009 R1: Project Portfolio Management 2009 R1 Web Server, Project Portfolio Management 2009 R1 Reports Server, and Project Portfolio Management 2009 R1 Database Server. All other components, such as Project Portfolio Management 2009 R1 Notifications and Project Portfolio Management 2009 R1 Documents Manager, are run as part of the Project Portfolio Management 2009 R1 Web Server component.

The standard deployment applies to all Project Portfolio Management 2009 R1 on-premise deployments, including migrations from Project Portfolio Management 2009 R1 6.2, and including advanced scenarios such as load-balancing the Project Portfolio Management 2009 R1 Web Server or offloading the Project Portfolio Management 2009 R1 Documents Manager.

The Project Portfolio Management 2009 R1 Database Server is installed on a server that is running Microsoft SQL Server 2005, SP2. Unless noted, all items in the checklist are required.

1. Open SQL Server Management Studio.
2. Expand Security.
3. Right-click Logins, and then select New Login.
4. In the Login dialog box, on the General page, type a name for the account, click SQL Server Authentication and enter a password, select Master database from the Default Database drop-down, and then click OK.
5. On the Server Roles page, under Server Role, select dbcreator, and then click OK.
6. On the Confirm Password dialog, type the account password, and then click OK.

The Project Portfolio Management 2009 R1 Report Server is installed on a server that is running Microsoft SQL Server 2005 Reporting Services, SP2. Unless noted, all items in the checklist are required.

1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In Internet Information Services Manager, expand the server name, right-click the Web Sites folder, and then click Properties.
3. Click the Services tab.
4. In the Isolation mode section, clear the Run WWW service in IIS 5.0 isolation mode checkbox. (The Run WWW service in IIS 5.0 isolation mode check box is only selected if you have upgraded to IIS 6.0 on Microsoft Windows Server 2003 from IIS 5.0 on Windows 2000 Server. New installations of IIS 6.0 default to IIS 6.0 worker process isolation mode.)
5. Click OK.

1. Click Start, point to Administrative Tools, and then click Manage Your Server.
2. On the Manage Your Server page, click Add or remove a role.
3. On the Preliminary Steps pane, click Next.
4. On the Server Role pane, click Application server (IIS, ASP.NET), and then click Next.
5. In the Application Server Options pane, select the Enable ASP.NET check box.
6. Click Next, and then click Next again to begin installation.
7. When installation is complete, on the This Server is Now an Application server page, click Finish.
8. Close the Manage Your Server tool.

1. On the server you installed SQL Server Reporting Services, log on to Reporting Services as an administrator.
2. Navigate to http://servername/reports/pages/folder.aspx.
3. Click the Properties tab.
4. Click New Role Assignment.
5. In the Group or user name box, type the IUSR_servername, and then under Role, select the Browser, Content Manager, and Publisher check boxes.
6. Click OK.

1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. Expand Internet Information Services (IIS).
3. Expand Web Sites, expand Default Web Site, right-click Reports, and then click Properties.
4. On the Directory Security tab, under Authentication and access control, click Edit.
5. Make sure the Enable Anonymous Access and Integrated Windows Authentication check boxes are selected, and then click OK.
6. Click OK to close the Reports Properties dialog box.
7. On the IIS Default Web Site tree, right-click ReportServer, and then click Properties.
8. Repeat steps 4-6.
9. In IIS Manager, right-click the name of the server, point to All Tasks, and then click Restart IIS.

1. Start setup. On the Welcome page, click Next.
2. On the License Agreement page, review and accept the license agreement.
3. On the Customer Information page, in the User Name box, type your name, the name of the server, or some other designation. In the Organization box, type the name of your organization. Click Next. This information is optional.
4. On the Destination Folder page, select the installation location. To accept the default installation location, click Next. Otherwise, click Change and select a different location.
5. On the Setup Type page, accept the Typical installation settings (which will install the application server, the Notifications and Scheduler services, and the Administration Module). Select Custom to choose different installation options.
6. On the Custom Setup page (if selected), Click a feature, such as Administration, or a sub-feature. Click This feature will be installed on local hard drive or This feature, and all sub-features will be installed on local hard drive. Repeat for all features and sub features you want to install. For any features you do not want to install, click This feature will not be available. Click Space to view the disk space required by the selected feature and click Change to modify the destination location for the selected feature.
7. On the Server Configuration page, select the location of the installation. By default, this is a Web site in IIS. In the Virtual Directory box, the default name is Project Portfolio Management. To change the virtual directory name, type it and then click Next.
8. On the Ready to Install page, click Install to begin the installation or Back to modify your installation options.
9. On the Installation Complete page, click Finish.

1. Navigate to http://servername/Reports/Pages/Folder.aspx.
2. You should see a folder called PESReports. That folder should contain the following folders: ITAccelerator, PESInvReports, PESAdminReports, PESResourceReports, and PESCustomReports.
3. Click PESInvReports.
4. Click DataSource1.
5. As part of <ConnectString>, verify that the Location element is in the following format: Location=servername/virtualdirectoryname;.
6. Repeat steps 4-5 for each of the other PESReports subfolders.

1. On the server where you installed SQL Reporting Services, log on as Administrator.
2. Navigate to http://servername/Reports/Pages/Folder.aspx.
3. On the Properties tab, next to the IUSR_servername account, click Edit.
4. Under Role, clear the Content Manager checkbox, and then click Apply.

1. Using a text editor, open the machine.config file, located by default in the c:\Windows\Microsoft.NET\Framework\v2.2\CONFIG directory.
2. Under httpRuntime, change the default value of executionTimeout from 90 to 1800.
3. Under processModel, change the default value of memoryLimit from 60 to 80.
4. Under processModel, change the default value of responseDeadlockInterval from 00:03:00 to 00:30:00.
5. Save and close the machine.config file.

This should be done for all servers on which the Project Portfolio Management 2009 R1 Web Server component will be installed, whether a single server or a distributed, multi-server deployment. Unless noted, all items in the checklist are required.

1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In Internet Information Services Manager, expand the server name, right-click the Web Sites folder, and then click Properties.
3. Click the Services tab.
4. In the Isolation mode section, clear the Run WWW service in IIS 5.0 isolation mode checkbox. (The Run WWW service in IIS 5.0 isolation mode check box is only selected if you have upgraded to IIS 6.0 on Microsoft Windows Server 2003 from IIS 5.0 on Windows 2000 Server. New installations of IIS 6.0 default to IIS 6.0 worker process isolation mode.)
5. Click OK.

1. Click Start, point to Administrative Tools, and then click Manage Your Server.
2. On the Manage Your Server page, click Add or remove a role.
3. On the Preliminary Steps pane, click Next.
4. On the Server Role pane, click Application server (IIS, ASP.NET), and then click Next.
5. In the Application Server Options pane, select the Enable ASP.NET check box.
6. Click Next, and then click Next again to begin installation.
7. When installation is complete, on the This Server is Now an Application server page, click Finish.
8. Close the Manage Your Server tool.

1. Open Internet Information Services (IIS) Manager.
2. Expand servername, and then click Web Service Extensions.
3. In the Results Pane, select ASP.NET v2.0, and then click Allow. (ASP.NET 1.1 is not supported.)

1. Click Start, point to Settings, click Control Panel, and then double-click Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. In the Windows Components Wizard, open the details of the Application Server, select Message Queuing, click OK and then click Next.
4. Complete the wizard, accepting the default selections.

1. Create a folder for the Document Repository (DocStore) on the server where the Documents Manager is located.
2. Right-click the folder and click Properties.
3. In the Properties dialog box, click the Sharing tab.
4. Click Share this folder, and then click Permissions.
5. Select the Everyone group, and then click Remove.
6. Click Add.
7. Ensure that the name of the server is listed under From this Location; otherwise, click Locations and then select it.
8. Under Enter the object names to select, type servername\ASPNET, and then click OK to close the Select Users or Groups dialog box.
9. Select ASP.NET Machine Account (servername\ASPNET), and then under Allow, select the Change check box.
10. Click OK.
11. On the Security tab, click Add.
12. Select ASP.NET Machine Account (servername\ASPNET), and then under Allow, select the Modify check box.
13. Click OK.

1. Start Project Portfolio Management 2009 R1 setup. On the Welcome page, click Next.
2. On the License Agreement page, review and accept the license agreement.
3. On the Customer Information page, in the User Name box, type your name, the name of the server, or some other designation. In the Organization box, type the name of your organization. Click Next. This information is optional.
4. On the Destination Folder page, select the installation location. To accept the default installation location, click Next. Otherwise, click Change and select a different location.
5. On the Setup Type page, accept the Typical installation settings (which will install the application server, the Notifications and Scheduler services, and the Administration Module). Select Custom to choose different installation options.
6. On the Custom Setup page (if selected), Click a feature, such as Administration, or a sub-feature. Click This feature will be installed on local hard drive or This feature, and all sub-features will be installed on local hard drive. Repeat for all features and sub features you want to install. For any features you do not want to install, click This feature will not be available. Click Space to view the disk space required by the selected feature and click Change to modify the destination location for the selected feature.
7. On the Server Configuration page, select the location of the installation. By default, this is a Web site in IIS. If you want to install to a Web site not included on this list, you must manually create the site in IIS and then re-run setup. In the Virtual Directory box, the default name is Project Portfolio Management. To change the virtual directory name, type it and then click Next.
8. On the Ready to Install page, click Install to begin the installation or Back to modify your installation options.
9. On the Installation Complete page, click Finish.

1. Double-click the Documents Manager Administration shortcut on the desktop, or click Start, point to All Programs, point to Serena, point to Mariner, point to Documents Manager and then click Documents Manager Administration.
2. In the Server box, type the name of the Documents Manager server.
3. Click New. The Create New Documents Manager Connection dialog box appears.
4. In the Connection Name box, type the Documents Manager database connection name.
5. In the Repository Location box, type the path of or browse to the Documents Manager repository folder. The repository folder is the storage location for documents checked into the Documents Manager.
6. In the Server box, type the Documents Manager database server name.
7. In the Database Name box, type the Documents Manager database name.
8. In the Database User Name box, type the Documents Manager database server user name. The user name entered in this field must have permissions to read and update database tables.
9. In the Password box, type the password for the Documents Manager database server user name.
10. Under Repository Administrator Password, in the Password and Confirm Password boxes, type the document repository administrator password for the database.
11. Under Creation, select Database and tables, Only connection, Only tables, or Create database SQL/DDL script file. Then type the database administrator user name in the Database User Name box, and the Documents Manager database administrator password in the Password box.
12. Click Create to create a Documents Manager database and a database connection. The Documents Manager Administration dialog box appears.
13. Under Select Connection, click the database connection name, and then click OK to log on to Documents Manager Administration. Once the initial Documents Manager database connection is established, you can modify the database connection and add additional databases.

1. Double-click Administration shortcut on the desktop, or click Start, point to All Programs, point to Serena, point to Project Portfolio Management 2009 R1, and then click Administration. The Administration Logon dialog box appears.
2. Click New. The Create New Connection dialog box appears.
3. In the Connection Name box, type a name for this database connection. (This is the connection name that users will select when logging.)
4. In the Server box, type the database server name.
5. In the Database Name box, type the database name.
6. In the Database User Name box, type the database server user name. The user name entered in this field must have permissions to read and update database tables.
7. In the Password box, type the password for the database server user name.
8. Under Creation, click Only Connection, and then click Create. The Administration dialog box appears.
9. Under Select Connection, click the database connection name and click OK to log on to Administration. Once the database connection is established, you can modify the database connection and add additional databases.

1. Open the Administration module.
2. Select the Environment Settings view.
3. On the System Settings tab, under Reporting Settings, in the Report Server box, enter the path to the reporting server, e.g. http://<reporterservername>/ReportServer.
4. In the Reports Root box, enter /PESReports.
5. In the Report Service Path box, type/ReportService.asmx.
6. Click Save.

1. Open SQL Server Management Studio.
2. Expand Databases.
3. Right-click the database you want to restore, point to Tasks, point to Restore, and then select Database.
4. In the Restore Database dialog box, on the General page, select the database you want to restore and the location in which the backup file is located, and then click OK.
5. On the Options page, ensure that the backup is pointing to the appropriate path on your system, for example: c:\Program Files\Microsoft SQL Server\MSSQL\Data.
6. Select the Overwrite the existing database check box and click OK.
7. When the restore operation is finished, click OK.

Unless noted, all items in the checklist are required.

1. On the application server, click Start, click Settings, and then click Control Panel.
2. Double-click Add/Remove Programs.
3. Click Add/Remove Windows Components.
4. In the Components list, clear the Internet Explorer Enhanced Security Configuration check box, and then click Next. The Internet Explorer Enhanced Security Configuration component is removed.
5. Click Finish.

1. On the application server, open Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the Security tab, click the Local intranet, and then click Sites.
4. Click Advanced.
5. In the Add this Web site to the zone box, type the URL for the site, and then click Add and then click Close.
6. Click OK twice.

1. Open Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the General tab, under Temporary Internet Files, click Delete Files.
4. On the Delete Files dialog box, select the Delete all offline content check box, and then click OK.
5. Click OK to close the Internet Options dialog box.

1. Open Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the General tab, under Check for newer versions of stored pages, click Automatically.
4. Make sure that Amount of disk space to use is larger than 10 MB.

1. Open Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the Security tab, select the Trusted sites zone, and then click Site.
4. If the Web site is not listed under Web sites, type the Web address under Add this Web site to the zone, and then click Add.

You can migrate Mariner 6.2 to Mariner 2008. Mariner databases can be migrated after the upgrade of the Mariner components has been completed. If your organization is migrating from Mariner 6.2 to Mariner 2008 R2, you must first migrate to Mariner 2008 R1 and then to Mariner 2008 R2 (i.e. you must migrate from major release to major release). You must use the Migration Tool specific to the version to which you are migrating.

The version of Mariner that is installed can be verified in the PES_VersionHistory table in the Mariner database. For example, the data in the PES_VersionHistory table for Mariner 2008 R1 is "2008.01.00" and the data for Mariner 2008 R2 is "2008.02.00".

Custom plug-ins may require an update before they can be migrated to Mariner 2008. If your organization has custom plug-ins that you want to migrate to Mariner 2008, contact Serena Professional Services before you begin the migration process. After the plug-ins have been updated, they can be added to Mariner 2008.

During the migration process, you should follow the planning and sizing recommendations contained in this guide, as well as following the steps outlined in the section titled Standard Deployment. For each of the migrations between versions of Mariner 2008, follow the same steps as outlined below.

1. On the server, navigate to the location of your item request pages. By default, this location is C:\Program Files\Serena\Mariner\Mariner\InvestmentRequest.
2. Backup the contents of that directory or copy that directory to another location on the hard disk.
3. Make note of your administrative settings for the item request pages in your environment.

1. On the Welcome page, click Next.
2. On the License Agreement page, review and accept the license agreement.
3. On the Customer Information page, in the User Name box, type your name, the name of the server, or some other designation. In the Organization box, type the name of your organization, and then click Next. The information entered on this page is optional and not required.
4. On the Destination Folder page, accept the default installation and click Next. Or click Change to modify the installation location.
5. On the Server Identification page, in the Server Name box, type the name of the Web server. In the Virtual Directory box, the default name is Mariner. To change the virtual directory name, type it and then click Next.
6. On the Ready to Install page, click Install.
7. On the Installation Complete page, click Finish.

1. Double-click Administration shortcut on the desktop, or click Start, point to All Programs, point to Serena, point to Project Portfolio Management 2009 R1, and then click Administration. The Administration Logon dialog box appears.
2. Click New. The Create New Connection dialog box appears.
3. In the Connection Name box, type a name for this database connection. (This is the connection name that users will select when logging.)
4. In the Server box, type the database server name.
5. In the Database Name box, type the database name.
6. In the Database User Name box, type the database server user name. The user name entered in this field must have permissions to read and update database tables.
7. In the Password box, type the password for the database server user name.
8. Under Creation, click Only Connection, and then click Create. The Administration dialog box appears.
9. Under Select Connection, click the database connection name and click OK to log on to Administration. Once the database connection is established, you can modify the database connection and add additional databases.

1. Run the 2008 migration tool. It is located in the c:\Program Files\Serena\Marinre Migration folder.
2. To begin the migration, in the Database list, select the database to migrate and then click Migrate. The database is updated and the progress is reported in the lower box. If you have more than one database, the migration tool needs to be run against each database individually.
3. On the Migration complete pop-up dialog, click OK.

1. Navigate to http://servername/Reports/Pages/Folder.aspx.
2. You should see a folder called PESReports. That folder should contain the following folders: ITAccelerator, PESInvReports, and PESResourceReports.
3. Click PESInvReports.
4. Click DataSource1.
5. As part of <ConnectString>, verify that the Location element is in the following format: Location=servername/virtualdirectoryname;.
6. Repeat steps 4-5 for each of the other PESReports subfolders.

1. On the server, navigate to the location of your item request pages. By default, this location is C:\Program Files\Serena\Mariner\Mariner\InvestmentRequest.
2. Restore the contents of that directory or copy your backed up item request pages into the new InvestmentRequest directory.
3. Open the Configuration module.
4. In the Item Setup view, click the IRP tab.
5. Recreate each item request, taking care to match the name, item type, and item location with its former value. The URL should remain unchanged.
6. You want to ensure that the URL shortcuts used by end users is still valid. For example, if the item request page prior to migrating was located at http://servername/Mariner/InvestmentRequest/InvestmentRequest.aspx?DBTitle=Sample&PageId=4, the URL should be valid. If the PageId changes to, say "5", you will need to update the shortcuts to this page.

You can use the Project Portfolio Management 2009 R1 setup wizard to modify your installation (including adding and removing installed components), or to remove Project Portfolio Management 2009 R1.

When optimizing the performance of your Project Portfolio Management 2009 R1 deployment, it is best to focus on providing the servers with the fastest possible CPUs, ample memory, hard disk space, and so on. Second, look closely at memory utilization and ensure that usage is not excessive. Then, consider multiple processor configurations and other advanced deployment options that are available with the Windows Server operating system. In the end, any single Project Portfolio Management 2009 R1 operation happens fastest when CPU speed, network bandwidth, and available memory are high. Using the fastest possible CPU at the client, server, and repository tiers results in the best user experience.

HTTP compression is enabled during the installation of Project Portfolio Management 2009 R1. It is recommended that HTTP compression remain enabled as the default state in your organization, but it can be managed manually.

During the installation of Project Portfolio Management 2009 R1, HTTP compression is enabled as part of the installation process as long as the \inetpub\adminscript folder contains the files adsutil.vbs and synciwam.vbs. If your installation of Project Portfolio Management 2009 R1 uses a non-default location, you should verify that the \inetpub\adminscript folder contains the files adsutil.vbs and synciwam.vbs before installing Project Portfolio Management 2009 R1. If these files are not present, HTTP compression will fail during Project Portfolio Management 2009 R1 installation; it will need to enabled manually after the installation of Project Portfolio Management 2009 R1 is complete.

1. Right-click the batch file, and then click Edit (or open it in your favorite text editor.)
2. Ensure the default values for Drive, ScriptPath, Website Identifier and Virtual Directory are correct in the line SupportFiles\EnableGzip.bat C: \InetPub\adminscripts 1 Mariner 9. Drive refers to the drive on which the application is installed. ScriptPath is the location of native IIS scripts and will only be different if you installed IIS to a custom location. WebSite Identifier is the value obtained from running RunFindWebSiteID. Virtual Directory is the virtual directory. CompressionLevel refers to the level of compression that will be set; this value should not be changed.
3. Run the batch file. A command prompt window opens and the results are displayed.
4. Look though the results in the command prompt window and look for the indication of error conditions. Each script action will report individually. For example, if you enter the name of your virtual server as "Marinr", you will receive an error. In that case, return to the batch file file, correct the spelling to "Mariner," and re-run it.

Some organizations may require users to connect to and interact with Project Portfolio Management 2009 R1 over an encrypted channel. Enabling Secure Sockets Layer (SSL) encryption for all Project Portfolio Management 2009 R1 Web traffic, does provide additional data security, however the impacts to performance can be significant.

In most cases, encrypted communication is used to protect user passwords from being sent over the network in plain text; user interactions with their Project Portfolio Management 2009 R1 data may not require that level of security, especially considering the potential performance implications. One trade-off between security and performance involves enabling SSL encryption exclusively for user authentication. After a user logs on to Project Portfolio Management 2009 R1 using SSL (https://), the rest of a user’s session in Project Portfolio Management 2009 R1 carries forward without SSL encryption (http://). This can provide optimal balance for many organizations.

Configuring SSL for Internet Information Services is beyond the scope of this section; organizations wishing to use SSL for all communications can visit Microsoft.com for instructions.

1. In IIS Manager, expand Web Sites, expand Default Web Site, and then click Mariner.
2. In the view pane, right-click Logon.aspx, and then click Properties.
3. On the Directory Security tab, under the Secure Communications, click Edit.
4. On the Secure Communications dialog, select the Require secure channel (SSL) check box, and then click OK. You can optionally select 128-bit encryption and client certificate options.
5. Click OK.

1. On the Web server, open the web.config file. By default, this file is located at C:\Program Files\Serena\Mariner\Mariner.
2. Locate the <appSettings> parameter, and then locate the following XML: <add key="SSLOnlyForLogon" value="true"></add>. If this text does not appear within the <appSettings> parameter, you must add it.
3. Uncomment the <Add> parameter, that is, move it just after the ending comment arrow -->.
4. Locate the <forms> parameter, and then change loginUrl=“Logon.aspx” to LoginUrl=“https://servername/virtual_directory/Logon.aspx” (the virtual directory is typically “mariner”).
5. Locate the <location path=“DialogHost.aspx”> parameter. Immediately after the closing </location> tag, add the following XML: <location path="logon.aspx"> <system.web> <authorization> <allow users="*"> </allow> </authorization> </system.web> </location>. Close and save the web.config file.
6. Reset IIS.

For increased scalability and performance, Project Portfolio Management 2009 R1 can be deployed in a load-balanced configuration. This can be configured using the network load balancing (NLB) features of Windows Server or by using hardware-based load balancing.

This section focuses on using hardware to load-balance the Project Portfolio Management 2009 R1 Web server. After the installation process for the Project Portfolio Management 2009 R1 Web server is complete, there are additional steps that must be completed in order for Project Portfolio Management 2009 R1 to function properly in a load-balanced environment.

1. After obtaining a new machine key for the farm, open the machine.config file on the first server. By default, this file is located at C:\WINDOWS\Microsoft.NET\Framework\v2.0\CONFIG.
2. Comment out or delete the existing <machinekey> value (Enter <!- - in front of the text and -- > at the end of the text). If you are having trouble locating the entry, search for "machinekey" in the file. The third reference will be the value shown above.
3. Enter the new key value you obtained directly beneath the old value: <machineKey validation="SHA1" validationKey="newKeyValue" decryptionKey="newDecryptionKeyValue" />
4. Repeat for each server in the farm, entering the duplicate key each time.

1. Right-click My Computer, and then click Manage.
2. Expand System Tools, expand Local Users and Groups, and then click Groups.
3. Right-click IIS_WPG, click Add to Group, and then click Add.
4. Under Enter the object names to select, type the name of the specific user account, and then click OK.

1. Click Start, and then click Run.
2. In the Run box, type regedit, and then click OK.
3. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters.
4. In the results pane, double-click AllowRemoteConnection.
5. In the Edit DWORD Value dialog, under Value Data, type 1.
6. Repeat this procedure on each server in the farm.

1. On one of the servers in the farm, open the web.config file.
2. Locate the <sessionState> parameter.
3. Change <sessionState mode="InProc" to <sessionState mode="StateServer"> and then in the stateConnectionString parameter, change the value from the default IP address to the static IP address of the designated state server. Leave the port number (:42424) unchanged.
4. Repeat for each server in the farm, including the server designated as the state server.

1. On the server you designated as the master server, create a folder called ChartPreviews.
2. Right-click the folder and then click Properties.
3. On the Properties dialog, click the Sharing tab.
4. Click Share this folder, and then click Permissions.
5. Select the Everyone group, and then click Remove.
6. Click Add.
7. Under Enter the object names to select, type NETWORK SERVICE, and then click OK to close the Select Users or Groups dialog box.
8. Select NETWORK SERVICE and then under Allow, select the Full Control check box.
9. Click OK.
10. Repeat steps 7-9 to add the MarinerAppAdmin domain account you created in above.
11. On the Security tab, click Add.
12. Repeat steps 6-10.
13. Select the NETWORK SERVICE account, and then under Allow, select the Full Control check box. Repeat for the MarinerAppAdmin account.
14. Click OK.
15. Repeat this procedure for two additional shared folders, which should be called ChartTemp and PrintJobs, respectively.

1. From any of the servers that are part of the load-balanced environment, copy the contents of the ChartPreviews folder. By default, this is located at c:\Program Files\Serena\Mariner\Charts\Previews.
2. On the State Server, add the contents to the ChartsPreviews shared folder.

1. From any of the servers that are part of the load-balanced environment, copy the web.config file from the PrintJobs directory. By default, this is located at c:\Program Files\Serena\Mariner\Mariner\PrintJobs.
2. On the State Server, add the web.config file to the PrintJobs shared folder.

1. In IIS Manager, expand Web Sites, and expand the Web site where the application is installed.
2. Right-click Charts, point to New, and then click Virtual Directory. The Virtual Directory Creation Wizard appears. Click Next.
3. In the Alias box, type previews, and click Next.
4. In the Path box, type the local path to the shared ChartPreviews directory you created above or click Browse to navigate to it, and then click Next.
5. Clear the Always use the authenticated user's credentials when validating access to the network directory check box, and enter the user name and password for the specific account created above, and then click Next.
6. Under Allow the following permissions, select the Read and Run scripts check boxes, and then click Next.
7. Click Finish.
8. Repeat steps 2-8 and create a virtual directory called temp, which points at the shared directory ChartTemp created above.
9. Create the third virtual directory under Project Portfolio Management 2009 R1, at the same level as Charts. This virtual directory is called PrintJobs, and points to the PrintJobs shared folder created above.

1. Click Start, point to Administrative Tools, and then click Local Security Policy.
2. Expand Local Policies, and then click on User Rights Assignment.
3. Double-click the policy Adjust memory quotas for a process. On the Properties dialog, add the MarinerAppAdmin domain account, and then click OK.
4. Repeat step 3 to add the MarinerAppAdmin account to Log on as a service and Replace a process level token.
5. On the File menu, click Save, and then close the console.
6. The servers must be rebooted for the changes to take effect.

1. In IIS Manager, right-click Application Pools, point to New, and then click Application Pool.
2. In the Add New Application Pool dialog, type PESpool, leave Use default settings for new application pool selected, and then click OK. Click Next.
3. Right-click PESpool, and then click Properties.
4. On the Recycling tab, clear the Recycle worker processes (in minutes) check box.
5. On the Identity tab, click Configurable, enter the user name and password for the specific user account you created, and then click OK.

1. Click Start, and then click Run.
2. In the Run box, type cmd, and then press ENTER.
3. In the command prompt window, type iisreset, and then press ENTER.
4. Close the command prompt window.
5. Repeat for each server in the farm.

1. On the Web server, open the web.config file. By default, this file is located at C:\Program Files\Serena\Mariner\Mariner.
2. Locate the <appSettings> parameter, and then locate the following: <add key="ProxyReportServer" value="true"></add>. If this text does not appear within the <appSettings> parameter, you must add it.
3. Uncomment the <Add> parameter, that is, move it just after the ending comment arrow -->.
4. Reset IIS.

1. On the Web server, open the web.config file. By default, this file is located at C:\Program Files\Serena\Mariner\Mariner.
2. Locate the <appSettings> parameter, and then locate the following: <add key="SSLOnlyForLogon" value="true"></add>. If this text does not appear within the <appSettings> parameter, you must add it.
3. Uncomment the <Add> parameter, that is, move it just after the ending comment arrow -->.
4. Locate the <forms> parameter, and then change loginUrl=“Logon.aspx” to LoginUrl=“https://servername/virtual_directory/Logon.aspx” (the virtual directory is typically “mariner”).
5. Locate the <location path=“DialogHost.aspx”> parameter. Immediately after the closing </location> tag, add the following section: <location path="logon.aspx"> <system.web> <authorization> <allow users="*"> </allow> </authorization> </system.web> </location>. Close and save the web.config file.
6. Reset IIS.

1. On the Web server, open the web.config file. By default, this file is located at C:\Program Files\Serena\Mariner\Mariner.
2. Locate the <appSettings> parameter, and then locate the following: <sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20">. If this text does not appear within the <appSettings> parameter, you must add it.
3. Uncomment the <Add> parameter, that is, move it just after the ending comment arrow -->.
4. Change mode="InProc" to mode="StateServer" and then in the stateConnectionString parameter, change the value from the default IP address to the static IP address of the designated state server. Leave the port number (:42424) unchanged.
5. You can change the timeout value for logons (set to a default of 20 minutes) by modifying the timeout parameter, for example a value of 60 sets the timeout at 60 minutes. If your organization modifies this setting, be sure to match that setting with the timeout value for logon.aspx, which is located in the web.config file: <authentication mode="Forms"> <forms name="PESPortfolioEdge" path="/" loginUrl="Logon.aspx" protection="All" timeout="20" /> </authentication>.

The Project Portfolio Management 2009 R1 Documents Manager is typically installed on the same server that is running the Project Portfolio Management 2009 R1 Web Server. However, some configurations may use the Project Portfolio Management 2009 R1 Documents Manager on dedicated hardware, such as when the Project Portfolio Management 2009 R1 Web Server is load balanced in a deployment with a large number of users, resources, and items, or if your organization requires a lot of space for documents storage.

Unless noted, all items in the checklist are required.

1. Create a folder on the server where the Documents Manager is located.
2. Right-click the folder and click Properties.
3. In the Properties dialog box, click the Sharing tab.
4. Click Share this folder, and then click Permissions.
5. Select the Everyone group, and then click Remove.
6. Click Add.
7. Ensure that the name of the server is listed under From this Location; otherwise, click Locations and then select it.
8. Under Enter the object names to select, type servername\ASPNET, and then click OK to close the Select Users or Groups dialog box.
9. Select ASP.NET Machine Account (servername\ASPNET), and then under Allow, select the Change check box.
10. Click OK.
11. On the Security tab, click Add.
12. Repeat steps 6 and 7.
13. Select ASP.NET Machine Account (servername\ASPNET), and then under Allow, select the Modify check box.
14. Click OK.

1. Start Project Portfolio Management 2009 R1 setup. On the Welcome page, click Next.
2. On the License Agreement page, accept the license agreement.
3. On the Customer Information page, in the User Name box, type your name, the name of the server, or some other designation. In the Organization box, type the name of your organization. Click Next. This information is optional.
4. On the Destination Folder page, select the installation location. To accept the default installation location, click Next. Otherwise, click Change and select a different location.
5. On the Setup Type page, select Custom the Typical installation settings (which will install the application server, the Notifications and Scheduler services, and the Administration Module). Select Custom to choose different installation options.
6. On the Custom Setup page (if selected), Click a feature, such as Administration, or a sub-feature. Click This feature will be installed on local hard drive or This feature, and all sub-features will be installed on local hard drive. Repeat for all features and sub features you want to install. For any features you do not want to install, click This feature will not be available. Click Space to view the disk space required by the selected feature and click Change to modify the destination location for the selected feature.
7. On the Server Configuration page, select the location of the installation. By default, this is a Web site in IIS. If you want to install to a Web site not included on this list, you must manually create the site in IIS and then re-run setup. In the Virtual Directory box, the default name is Project Portfolio Management. To change the virtual directory name, type it and then click Next.
8. On the Ready to Install page, click Install to begin the installation or Back to modify your installation options.
9. On the Installation Complete page, click Finish.

1. Using a text editor, open the machine.config file, located by default in the c:\Windows\Microsoft.NET\Framework\v2.2\CONFIG directory.
2. Under httpRuntime, change the default value of executionTimeout from 90 to 1800.
3. Under processModel, change the default value of memoryLimit from 60 to 80.
4. Under processModel, change the default value of responseDeadlockInterval from 00:03:00 to 00:30:00.
5. Save and close the machine.config file.

When SQL Server 2005 Reporting Services is installed as a second instance on a server that is already running SQL Server 2000 Reporting Services, a version key may not be created. However, a version key is required in order for Project Portfolio Management 2009 R1 to recognize SQL Server 2005 Reporting Services.

In addition to adding a version key, you will need to ensure that each instance of SQL Server reporting services is represented in Application Pools folder in Internet Information Services (IIS) Manager and that Project Portfolio Management 2009 R1 points to the correct instance.