Migrating Projects Set Up with Primavera Gateway Integration to Oracle Integration

Company Administrators and Shell Administrators can migrate projects configured with Primavera Gateway integration for P6 System Activity Sheets to use Oracle Integration as its default integration engine.

Benefits
  • Clear Engine Selection: Administrators can explicitly select the integration engine for each project, preventing misconfiguration and ensuring systems route integration requests to the correct platform.
  • Reduces operational friction.
  • Ensures a supported integration path going forward.
  • Simplified Management: Configuration and migration steps are visible and straightforward, reducing ambiguity over which integration path is active.
  • Confirmation on Migration: Built-in confirmation dialogs to switch engines help avoid accidental data or configuration loss.
  • Consistent Schema: No changes to field names or data types when switching engines means existing reports and workflows.
  • Enhanced Auditing: Each integration run is recorded with engine details, status, and user activity, supporting efficient troubleshooting and compliance tracking.
  • Enables the use of updated and Oracle Integration-only APIs.
Limitations
  • Primavera Gateway configuration is removed. Rollback is not available without reconfiguration.
  • Users must complete any required Oracle Integration mappings after migration, before Get/Send is enabled.
Prerequisites
  • Oracle Integration is enabled at the company level as the integration engine as outlined Initial Oracle Integration Setup.
  • You have the required permissions to set up and manage integrations.
  • You have administration permissions for the project.
  • One or more projects are configured with Primavera Gateway integration.
  • The required mappings are in place for Get/Send calls to succeed with Oracle Integration.

Procedure

To migrate current projects configured with Primavera Gateway integration to use Oracle Integration as the default integration engine:
  1. 1. Go to the Company Workspace tab, and switch to Admin mode.
  2. In the left Navigator, go to the targeted single shell node.
    For example, select Vision Corporation.
  3. In the <Shell_Name> log (right pane), select the applicable single shell of CBS type and then select Open from the gear menu.
  4. 4. On the Shell’s landing page, from the My Dashboard menu, select Details, and then select the Integration tab.
    The Integration tab displays only those projects that are configured to use Oracle Integration as the default integration engine.
  5. If you choose to migrate one or more projects that are already configured with Primavera Gateway integration, they will be migrated to use Oracle Integration by default when you select the Integration tab. A confirmation dialog displays indicating these projects will be migrated to use Oracle Integration as the default integration engine.
    • • Select Yes to migrate projects to use Oracle Integration. The projects listed in the Gateway Integration tab are relocated to the Integration tab.
    • Select No to retain the projects configured with Primavera Gateway integration.
  6. Complete Oracle Integration mappings as required.
  7. To save the changes, select Save.
  8. (Optional) At the shell template level, update templates to use Oracle Integration by default for all new projects as outlined in Configuring Oracle Integration for P6 System Activity Sheets in Shell Templates.
Alternative Method

You can also configure shells to use Oracle Integration as the default engine using theUpdate ShellREST endpoint.