Migrating Projects Configured with Primavera Gateway Integration to Oracle Integration

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

Benefits

Migrating projects to Oracle Integration provides these benefits:

Clear Engine Selection: Administrators can select the integration engine for each project. This selection helps route integration requests to the appropriate platform.
Reduced operational effort: Administrators can manage integrations with fewer configuration steps.
Supported integration path: Projects can use Oracle Integration for supported integrations.
Simplified Management: Configuration and migration options identify which integration engine is active for a project.
Migration confirmation: A confirmation dialog box helps prevent unintended migration and or configuration loss when you switch integration engines.
Consistent Schema: Field names and data types do not change when you switch integration engines. Existing reports and workflows can continue to use the same schema.
Enhanced Auditing: Each integration run records the integration engine, status, and user activity to support troubleshooting and compliance tracking.
Updated APIs: Projects can use updated APIs and APIs that are available only with Oracle Integration.

Limitations

Consider these limitations before you migrate projects:

Schedule integrations associated with Primavera Gateway are deleted when you switch the integration source from Primavera Gateway to Oracle Integration on the Integration tab of the shell Details.
ThePrimavera Gateway configuration is removed during migration. To return to Primavera Gateway, you must reconfigure the integration.
You must complete the required Oracle Integration mappings after migration before Get and Send operations are available.

Prerequisites

Before you migrate a project, ensure that these prerequisites are met:

Oracle Integration is enabled at the company level as the integration engine. For more information, see Initial Oracle Integration Setup.
You have the required permissions to configure and manage integrations.
You have administration permissions for the project.
One or more projects use Primavera Gateway integration.
The required mappings are configured so that Get and Send operations can use Oracle Integration.

Migrate Projects to Oracle Integration

To migrate projects that use Primavera Gateway integration to Oracle Integration:

Go to the Company Workspace tab, and switch to Admin mode.
In the left Navigator, go to the targeted single shell node.
For example, select Vision Corporation.
In the [Shell_Name] log, select the applicable CBS-type single shell, and then select Open from the gear menu () menu.
On the shell landing page, from the My Dashboard menu, select Details, and then select the Integration tab.
The Integration tab displays projects that use Oracle Integration as the default integration engine.
If one or more projects use Primavera Gateway integration, confirm whether you want to migrate the projects to Oracle Integration.
A confirmation dialog indicates that the projects will be migrated to use Oracle Integration as the default integration engine.
- Select Yes to migrate the projects to Oracle Integration. The projects that were listed on the Gateway Integration tab move to the Integration tab.
- Select No to retain the Primavera Gateway integration for the projects.
Complete the required Oracle Integration mappings.
Select Save.
(Optional) At the shell template level, configure Oracle Integration as default integration engine for new projects. For more information, see Configuring Oracle Integration for P6 System Activity Sheets in Shell Templates.

Configure Oracle Integration by Using REST API

You can also configure shells to use Oracle Integration as the default engine by using the Update Shell REST endpoint.