Integrate with Oracle Primavera

Prerequisites

Before you install and configure an Oracle Primavera orchestrated system, you should consider the following prerequisites and tasks.

Certified Components

The system must be the following:

  • Oracle Primavera P6 Enterprise Project Portfolio Management / Unifier Cloud Service - Version 20.1 and later

Supported Modes

Oracle Primavera orchestrated system supports the following mode:
  • Managed System

Supported Operations

The Oracle Primavera orchestrated system supports the following operations. These operations may be initiated during provisioning of the Oracle Primavera system from Oracle Access Governance.
  • Create User
  • Reset Password
  • Assign Roles
  • Revoke Roles

Default Supported Attributes

The Oracle Primavera orchestrated system supports the following default attributes. These attributes are mapped depending on the direction of the connection, for example:
  • Data being ingested by Oracle Access Governance from Oracle Primavera: Identity.firstName will map to Account.firstName
  • Data being provisioned into Oracle Primavera from Oracle Access Governance: Account.lastName will map to Identity.lastName

Table - Default Attributes - Managed System Mode

Primavera Entity Attribute Name On Managed System Oracle Access Governance Account Attribute Name Oracle Access Governance Account Attribute Display Name
User id uid Unique Id
  loginId name User Login
  password password Password
  firstName firstName First Name
  lastName lastName Last Name
  userType userType Person Type
  status status Status
  emailAddress email Email
  Company company Company

Default Matching Rule

The default matching rule for Oracle Primavera orchestrated system

is:

Table - Default Matching Rules

Mode Default Matching Rule
Managed System

Screen value:

User login = Employee user name

Attribute name:

Account.name = Identity.userName

Create Oracle Primavera User Account

To create a user account for the Oracle Primavera Orchestrated System perform the following steps:
  1. Create a user account on the Orchestrated System with the following:
    • User name
    • Password
    • Host
    • Port
    • TenantId
  2. Assign necessary privileges such as, Cloud administrator and P6 to the same user to perform the integration operations.

Configure

You can establish a connection between Primavera and Oracle Access Governance by entering connection details. To achieve this, use the Orchestrated Systems functionality available in the Oracle Access Governance Console.

Navigate to the Orchestrated Systems Page

Navigate to the Orchestrated Systems page of the Oracle Access Governance Console, by following these steps:
  1. From the Oracle Access Governance navigation menu icon Navigation menu, select Service Administration → Orchestrated Systems.
  2. Click the Add an orchestrated system button to start the workflow.

Select system

On the Select system step of the workflow, you can specify which type of system you would like to onboard. You can search for the required system by name using the Search field.

  1. Select Primavera.
  2. Click Next.

Enter details

On the Enter Details step of the workflow, enter the details for the orchestrated system:
  1. Enter a name for the system you want to connect to in the What do you want to call this system? field.
  2. Enter a description for the system in the How do you want to describe this system? field.
  3. Determine if this orchestrated system is an authoritative source, and if Oracle Access Governance can manage permissions by setting the following checkboxes.
    • This is the authoritative source for my identities
    • I want to manage permissions for this system
    The default value in each case is Selected.
  4. Click Next.

Add owners

You can associate resource ownership by adding primary and additional owners. This drives self-service as these owners can then manage (read, update or delete) the resources that they own. By default, the resource creator is designated as the resource owner. You can assign one primary owner and up to 20 additional owners for the resources.

Note:

When setting up the first Orchestrated System for your service instance, you can assign owners only after you enable the identities from the Manage Identities section.
To add owners:
  1. Select an Oracle Access Governance active user as the primary owner in the Who is the primary owner? field.
  2. Select one or more additional owners in the Who else owns it? list. You can add up to 20 additional owners for the resource.
You can view the Primary Owner in the list. All the owners can view and manage the resources that they own.

Account settings

On the Account settings step of the workflow, enter details of how you would like to manage accounts with Oracle Access Governance when configured as a managed system:
  1. Select where to send notification emails when an account is created. The default setting is User. You can select one, both, or none of these options. If you select no options then notifications will not be sent when an account is created.
    • User
    • User manager
  2. When an identity moves within your enterprise, for example when moving from one department to another, you may need to adjust what accounts the identity has access to. In some cases the identity will no longer require certain accounts which are not relevant to their new role in the enterprise. You can select what to do with the account when this happens. Select one of the following options:
    • Disable
    • Delete
  3. When an identity leaves your enterprise you should remove access to their accounts. You can select what to do with the account when this happens. Select one of the following options:
    • Disable
    • Delete

Note:

If you do not configure your system as a managed system then this step in the workflow will display but is not enabled. In this case you proceed directly to the Integration settings step of the workflow.

Note:

If your orchestrated system requires dynamic schema discovery, as with the Generic REST and integrations, then only the notification email destination can be set (User, Usermanager) when creating the orchestrated system. You cannot set the disable/delete rules for movers and leavers. To do this you need to create the orchestrated system, and then update the account settings as described in Configure Orchestrated System Account Settings.

Integration settings

On the Integration settings step of the workflow, enter the configuration details required to allow Oracle Access Governance to connect to the required Oracle Primavera instance.

Note:

The following fields are mandatory, except for the Port field.
  1. In the User Name field, enter the username of a user you have created on the Primavera system for performing integration operations.

    Sample Value : johnsmith

  2. In the Password field enter the password of the user on your Primavera system.

    Sample Value : password

  3. In the Confirm password field, confirm the password of the user on your Primavera system.
  4. In the Host field, enter the host name of the machine hosting your system.

    Sample value: myhost.example.com

  5. In the Port field, enter the port number the system is listening on.
  6. In the TenantId field, enter the value for TenantID. This information is mandatory and the information specified is used for calling the API details.
  7. Click Add to create the orchestrated system.

Finish Up

The final step of the workflow is Finish Up, where you are given a choice whether to further configure your orchestrated system before running a data load, or accept the default configuration and initiate a data load. Select one from:
  • Customize before enabling the system for data loads
  • Activate and prepare the data load with the provided defaults

Post Configuration

There are no post configuration steps associated with an Oracle Primavera system.