|
|
Oracle® Primavera Portfolio Management 8.0 SP1
This file provides the following information about Primavera Portfolio Management:
· Technical Requirements and installation instructions
· Notes
· Oracle Copyright and Trademark Notice
1 Technical Support
Technical Support for Primavera Portfolio Management products is available at http://support.oracle.com.
2 DVD Content
|
Auto-run: |
Auto-run will activate the Installation Software for Primavera Portfolio Management 8.0 SP1. |
|
Documentation: |
Contains all of the documentation in PDF formats, Acrobat Reader 8.0 to enable reading the documentation, Installation guides for Primavera Portfolio Management (including system requirements) and Primavera Portfolio Management Enterprise API documentation. |
|
Utilities: |
Maintenance programs designed to enable inspection of the system, including utilities and patches for installing Primavera Portfolio Management with Oracle database. |
3 Technical Requirements and installation instructions
Application
Server:
=================
|
Operating System: |
Microsoft Windows Server 2003 SP2 (32 bit or 64 bit) or Microsoft Windows Server 2008 SP2 (32 bit or 64 bit) or Microsoft Windows Server 2008 R2 (64 bit). Note: 64 bit Itanium is not supported.
The only supported virtual operating systems are VMWare ESX version 3.5 update 5, or version 4.0 |
|
Server Utilities: |
Microsoft Windows Server 2003 SP2 / 2008 SP2 with Critical Updates Microsoft .NET Framework 2.0 SP1 and Microsoft .NET Framework 3.5 SP1
IIS 6.x or higher or
SQL Server 2008 SP1 client or
Oracle 10g
Release 2 client , Enterprise Edition (10.2.0.4) OraMTS 10.2.0.4 |
|
Disk Space: |
600 MB available disk space for Primavera Portfolio Management server installation |
Database Server:
===============
|
Operating System: |
Microsoft Windows Server 2003 SP2 (32 bit or 64 bit) or Microsoft Windows Server 2008 SP2 (32 bit or 64 bit) or Microsoft Windows Server 2008 R2 (64 bit). Note: 64 bit Itanium is not supported.
Oracle Solaris 10 10/09 (only for Oracle 10g Release 2 Enterprise Edition, with patch set 10.2.0.4) |
|
Disk Space: |
Database size according to scale of installation. |
|
Database: |
SQL Server 2005 SP3 Standard and Enterprise Editions or SQL Server 2008 SP1 Standard and Enterprise Editions or Oracle 10g Release 2 Enterprise Edition, with patch set 10.2.0.4 |
Client:
======
|
Operating System: |
Microsoft Windows XP SP3 Microsoft Vista SP2 Windows 7
|
|
Minimum Hardware: |
Pentium IV 1GHz with 512 MB RAM |
|
Browsers: |
IE 7.0 or IE 8.0 |
|
Office Versions: |
Office
2003 SP3 |
Integration
with project management systems (Optional):
=====================================================
|
Primavera P6 Enterprise Project Portfolio management |
Primavera P6 Version 6.2.1. Primavera P6 Version 7.0.
Required Components:
|
|
Microsoft Project Server 2007 |
Microsoft Project Server 2007 SP2 |
4 Anti Virus
This product has been tested for Viruses with McAfee Anti Virus.
5 Notes
Table
of Contents:
================
Installing Primavera Portfolio Management
Uninstalling Primavera Portfolio Management
Re-starting the Primavera Portfolio Management system
The default login account is "admin"
Considerations for applications using the Primavera Portfolio Management Open API via COM
Details:
=======
· Installing Primavera Portfolio Management:
Follow the instructions in the relevant 'Primavera Portfolio Management 8.0 Install and Upgrade Guide'
· Uninstalling Primavera Portfolio Management:
After uninstalling Primavera Portfolio Management the log files and custom dictionaries are left on the disk under the Primavera Portfolio Management installation directory. You can safely remove these files by deleting the directory tree starting from the Portfolios directory.
· Re-starting the System:
Click the "Start" button of your windows system and choose "programs", under the Primavera Portfolio Management entry there is Portfolio Management Console, use re-start button in order to re-start the system.
· The default login account is "admin" with the password entered when a new database is created via the Primavera Portfolio Management Console.
· Considerations for applications using the PPM Open API via COM
Applications which use the Primavera Portfolio Management (PPM) Open API via any interface (COM, SOAP/RCP or Document/Literal) and were developed and used with previous versions of PPM will continue to operate without the need for recompilation, as Primavera Portfolio Management 8.0 provides full binary backwards compatibility for all of the Open API interfaces. New functionality is available only to applications that are written to take advantage of such functionality.
Note however that any process can only load and use one version of the Microsoft .NET Framework. Therefore, applications developed with the .NET Framework 1.1 cannot use APIs to communicate with software developed using the .NET Framework 2.0 if this would cause the same process to need to load both versions of the .NET Framework.
This means that if any part of an application that uses the Open API which was developed using .NET Framework 1.1 communicates directly with PPM using the COM API (which is in-process), that part of the application would need to be recompiled to target the .NET Framework 2.0. If on the other hand, the application developed using .NET Framework 1.1, only communicates with PPM using SOAP RPC or Web Services (which are out-of-process) then there is no issue.
Instead of recompiling, it is usually sufficient to ”force” the existing executables to actually use the .NET Framework 2.0 instead of the native version of the .NET Framework for which they were compiled (1.1). This can be achieved by using an application config file with the following content:
<?xml version ="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727" />
</startup>
</configuration>
The application config file can easily be created using Notepad or something similar. It does not need to be compiled in any way. It should be named with the exact same name as the executable file plus the suffix “.config”. For example: if the application executable file is called “Tester1.exe” then the config file must be named “Tester1.exe.config”. It must be placed in the same directory as the executable file.
The config file “forces” the application to use the .NET Framework 2.0, which would mean that even when using COM (in-process) Open API calls to PPM, there would still be only one version of the .NET Framework involved in the process (.NET 2.0).
6 Oracle Copyright and Trademark Notice
Copyright © 1998-2010, Oracle and/or its affiliates. All Rights Reserved.
Oracle is registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Adobe, the Adobe logo, Acrobat, Acrobat Reader and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Microsoft, Visual C++, Visual J# and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
