Configuring WCCC to Work with P6

Contents

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

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 Webcenter Content Core Capabilities for detailed instructions on how to complete the guidelines in this section. See the Tested Configurations document for information on supported versions.

To configure Oracle WCCC:

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 WCCC server’s configuration file.
   1. Go to WCCC_Home\ucm\cs\config\.

      where WCCC_Home is the location where you installed WCCC.

   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.

      Note: Values must be separated by the pipe | symbol.

   4. Restart the WCCC server.
2. (required) Create a P6 EPPM documents home folder on the WCCC server by adding a unique path to the root folder.
   1. Log into the WCCC Content Server as an administrative user.
   2. Create a new Folder (see the WCCC documentation for more information).

      For example:

      /Production/Oracle Primavera

      Note: In WCCC 11.1.1.6 or later, the Framework folder interface is not enabled by default. To enable it, see the WCCC documentation for more information.

3. (optional) Follow this step only if you want to use a custom security group. Create a P6 EPPM Security Group in WCCC and grant the appropriate rights for P6 EPPM users. Security considerations include the following:
   • P6 EPPM user names must match the WCCC user names, unless using "Single User" for the Authentication Mode.

     Note: "Single User" Authentication Mode will log all P6 EPPM users into WCCC 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 WCCC user names must have appropriate assignments to WCCC 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 WCCC user names must have access to the P6 EPPM Security Group, either directly or through a role.
4. (required) Create an administrative user in WCCC and provide it with Read, Write, Delete, and Admin privileges to the P6 EPPM Security Group.

   If you are using Single User authentication, you need to create the admin user that they would then populate to the P6 Admin.

   If using Multiple User authentication, you need to create a user for each P6 user that will use WebCenter. You can then assign admin level access to any user.

   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. (optional) 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 WCCC user names, unless using "Single User" for the Authentication Mode.
   • All P6 EPPM-related WCCC user names must have appropriate assignments to WCCC 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 WCCC user names must have access to the P6 EPPM Security Account.
6. (optional) Create a Document Type for P6 EPPM documents in WCCC (there are pre-existing document types you can use if you don't want to create one).
   1. Log into the WCCC Content Server as an administrative user.
   2. Use the Configuration Manager to create a new Content Type for P6 Documents (see the WCCC documentation for more information).

      For example:

      Enter the Document Type as Document.

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

7. (required) Create the following metadata text fields in the Information Fields tab, exactly as specified (including case), in WCCC for P6 EPPM:
   • PrmUserId
   • PrmProjectId
   • PrmWorkgroupId
   • PrmWorkflowId
   • PrmWorkflowStatus
   • PrmWorkflowAction
   • PrmSecurityPolicy
   • PrmTemplate
   • 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.

   To put these changes into effect, click the Update Database Design button.

8. (required) Configure the appropriate settings for the P6 Administrator application.

   Note: You will configure the P6 Administrator application settings when you run the P6 EPPM Configuration Wizard. See About the P6 EPPM Configuration Wizard.