Vous êtes sur la page 1sur 2

SDK installation

For Release 8 and below


This assumes youve successfully configured EPPM or PPM and also installed the SDK component.
1. Run Setup.exe from the installation media. This file will always be located with the Professional Client
installation source.
2. Select the option for Software Development Kit under Other Components. Click Next.
Note: DO NOT UNCHECK the Primavera Client Applications. That will uninstall the client.
3. Click the install button.
4. An instruction box will appear. Please read the instruction box entirely, and then click OK.
5. Select the driver type from the drop down list for the SDK to connect to your database, then click Next.
6. For Oracle Users: Enter the Oracle Service name in the Oracle Connect Sting box, over-writing the Database
Name entry. Click Next.
7. Note: Your system must have the Oracle Client software installed on your machine and configured to connect
to the database you wish to connect the SDK.
8. For MS SQL/MSDE Users: Enter the SQL Server Host Name (i.e. Machine Name). Enter the SQL Database
Name. This is the database name as it appears in the SQL Server Enterprise Manager. Click Next.
9. The installation wizard will check your database connection once you click Next. If successful, click Finish. If
unsuccessful, please verify the information.
10. Setup will display the Borland Data Engine Configuration Box. Click the Ok button. If the information in the
Database Alias (BDE) box is blank, click on the create database alias and follow the instructions above
depending on the type of database connection chosen.
11. The Installation Complete Box will appear. Click Finish
For Release 8 and Standalone Oracle XE Database
Oracle discontinued offering their XE database with the newer releases of P6, but there may be the odd few
that still have their database configured. Although it is slightly faster, many opt for MS SQL because it is less
complicated to manage and fix.
1. Double-click setup.exe in the P6 EPPM physical media or download. This file will always be located with the
Professional Client installation source.
2. At the Setup Maintenance program screen, choose to Modify the current installation and click Next.
3. On the Select Features to install dialog box, select the Software Development Kit option and click Next.
4. On the Ready to Install the Program screen, click Install to begin the installation.
5. After reading the explanation of the remaining process, click on the OK button to proceed to the Database
Configuration Wizard.
6. Configure the Database Connection for the P6 SDK to a Standalone Oracle XE Database
7. In the Select Driver Type dialog box, select Oracle and click Next.
8. In the Configure Oracle Connection dialog box, enter the Oracle connection string as XE and click Next.
9. In the Enter Public Login Information dialog box, enter the following information for a default standalone
Oracle XE database:
Username: pubprm$pm
Password: pubprm$pm
Public group ID: 1
NOTE: If these settings were changed by you or the administrator, enter the new values here.
10. In the Validate Database Connection dialog box, click Next to test the database connection.
11. If the connection was not successful, click Back to revise the database information. If the connection was
successful, click Finish to complete the database connection configuration. A database alias named PMSDK will
be created.
12. On the Primavera Software Development Kit Setup dialog box, change the public group ID, password, and
username fields to match the values entered in step 3 during the database configuration and click OK to create
an ODBC DSN named Primavera P6 SDK.

Public group ID: 1

Password: pubprm$pm

Username: pubprm$pm
NOTE: If these settings were changed by you or the administrator, enter the new values here.
13. If the log file directory does not exist, click Yes, when prompted, to create one.
14. Click Finish to complete the installation.
Source: My Oracle Support
Conclusion

SDK installation
The main question is, is it worth your time to utilize these free solutions while you have access to them? Or is it
worth your money to purchase a finished product that will do the same thing and more? The answer to these
questions will be different for everyone, because time is money. It would also depend on your expertise and the
amount of time you think youd spend on learning some of the solutions mentioned above. It is very risky if you
do not know what you are doing, so please make backups of your projects before exploring some of this fun
stuff. If you are worried about solutions being too expensive, a good way to get the tools you need is to
expense them with your project, rather than through your department/general budget.