Configuring UCM 10g to Work with P6

Contents

Note: These instructions contain information only on configuring Oracle Universal Content Management (UCM) to work with P6. They do not include information on installing UCM. For UCM's installation instructions, see the documentation included with Oracle UCM.

Except where noted, the guidelines below are recommendations. Depending on your organization, you can choose to use existing configurations or your own naming conventions. Refer to the documentation included with Oracle Universal Content Management for detailed instructions on how to complete the guidelines in this section.

To configure Oracle UCM:

1. (required) Establish a Trusted Connection to the P6 EPPM database by adding the P6 EPPM machine name or IP address as a trusted server in the UCM server’s configuration file.
   1. For UCM 10g, go to UCM_Home\config\.
   2. Edit the config.cfg file.
   3. Find the SocketHostAddressSecurityFilter line and add the P6 EPPM machine name or IP address to the end of the line.
   4. Restart the UCM server.
2. (required) Create a P6 EPPM documents home folder on the UCM server by adding a unique path to Contribution Folders.
   1. Log into the UCM Content Server as an administrative user.
   2. Create a new Contribution Folder (see the UCM documentation for more information). A sample folder name would be:

      \\Contribution Folders\Production\Oracle Primavera\

3. Create a P6 EPPM Security Group in UCM and grant the appropriate rights for P6 EPPM users. Security considerations include the following:
   • P6 EPPM user names must match the UCM user names, unless using "Single User" for the Authentication Mode.

     Note: "Single User" Authentication Mode will log all P6 EPPM users into UCM via the administrative user created below and/or as specified in the Database/Instance/Content Repository setting in the P6 Administrator application.

   • All P6 EPPM-related UCM user names must have appropriate assignments to UCM Roles and Users. For a quick setup, you can simply create one P6 EPPM-specific Role to map to, with full privileges (Read, Write, Delete, Admin).
   • All P6 EPPM-related UCM user names must have access to the P6 EPPM Security Group, either directly or through a role.
4. (required) Create an administrative user in UCM and provide it with Read, Write, Delete, and Admin privileges to the P6 EPPM Security Group. A user account with administrative privileges is required for P6 EPPM document access when using "Single User" Authentication Mode, and for creating or changing P6 EPPM document organization when using "Single User" or "Multiple User" Authentication Mode.

   Note: When using "Single User" for Authentication Mode, users will have the ability to browse for documents outside of the P6 EPPM documents home folder, as long as the administrative user has access to all appropriate Security Groups, including the P6 EPPM Security Group.

5. If you enabled Security Accounts, create a P6 EPPM Security Account. For example, depending on your organization, you might need to set up a Security Account for performance and storage reasons. Security considerations, similar to those made for the Security Group above, include the following:
   • P6 EPPM user names must match the UCM user names, unless using "Single User" for the Authentication Mode.
   • All P6 EPPM-related UCM user names must have appropriate assignments to UCM Roles and Users. For a quick setup, you can simply create one P6 EPPM-specific Role to map to, with full privileges (Read, Write, Delete, Admin).
   • All P6 EPPM-related UCM user names must have access to the P6 EPPM Security Account.
6. Create a Document Type for P6 EPPM documents in UCM.
   1. Log into the UCM Content Server as an administrative user.
   2. Use the Configuration Manager to create a new Content Type for P6 Documents (see the UCM documentation for more information).

      For example:

      Enter the Document Type as ADACCT.

      Note: These document types are the defaults in their repositories.

7. (required) Create the following metadata text fields, exactly as specified (including case), in UCM for P6 EPPM:

   Note: Add the metadata fields to the Information Fields tab.

   • PrmUserId
   • PrmProjectId
   • PrmWorkgroupId
   • PrmWorkflowId
   • PrmWorkflowStatus
   • PrmWorkflowAction
   • PrmSecurityPolicy
   • PrmTemplate (clear the "Enabled" and "Searchable" attributes)
   • PrmCheckedOutUserId
   • PrmCheckedOutDate
   • PrmLocalFilePath (make Type = Long Text)
   • PrmAuthorId

   Using "Prm" as a prefix is optional. You can use any prefix. If you don't use a prefix, ensure that none of the P6 EPPM metadata fields conflict with existing metadata fields.

8. (required) Configure the appropriate database instance settings for the P6 Administrator application either through the configuration wizard or in the P6 Administrator application depending on your installation process.