The following explains the end-to-end solution for Unifier Provider (Project/Shell). The configuration settings are for:
- Unifier
- Unifier Provider
To configure the creation of projects in Unifier via Gateway
Note: This is an optional step. You can skip deploying the objects from Unifier and add relevant fields in Gateway Data Mapping Templates directly, manually.
In Unifier, go to Company Workspace > Admin mode > Gateway > Business Objects.
Deploy the Shell Attribute Forms of the shells that you want to create in Unifier, via Gateway Integration.
All fields from the deployed Shell Attribute Forms appear as attributes of Project object in Unifier Provider Data Dictionary.
To configure the creation of projects in Unifier Provider via Gateway
You must:
- Create Data Mapping Templates
- Define Business Flow
- Define Synchronizations
- Synchronize
The following provides the details for each step:
Create Data Mapping Templates
Create Data Mapping Templates to map attributes of the Shell that needs to integrate with the Oracle application. All attributes of the Unifier Data Dictionary Project object are available to be added to the Data Mapping Template.
Note: Ensure that you create one Data Mapping Template per Shell type.
If you do not want to deploy from Unifier and want to create the Data Mapping Templates in Gateway directly, then add each Shell Attribute Form Data Element that needs to receive data from the Oracle application Project object, manually.
If you want to deploy from Unifier, after adding the Shell Attribute Form Data Element, then:
- If the manually added field is same as one of the fields that were deployed from Unifier, then there will be no adverse impact on the existing fields.
- If the manually added field does not exist as a Data Element in Unifier, then there will be no adverse impact on the existing fields.
The fields remain as they are when the Oracle application sends values for the fields that were added to Unifier Provider and those values are not sent to Unifier.
Define Business Flow
Define Business Flow using the appropriate Data Mapping Template.
Create one Business Flow per Shell type in Unifier.
Add the appropriate source (Source) application parameters to filter the projects that you want to create in Unifier.
Add the values of relevant destination (Destination) application parameters (Location and Template).
Configure the Business Flow to be used for creating (Create) and updating (Update) the project in Unifier.
Define Synchronizations
Define Synchronizations by using the appropriate Business Flow.
Define the appropriate parameter values for data exchange.
Define the schedule frequency so that the synchronization does not have to be run manually for the project creation or update.
Synchronization
When a synchronization is run, Unifier Provider sends data to Unifier to:
- Create or update a Shell instance (as per Business Flow configuration).
- Populate the Data Element with the name of the application that is integrating with Unifier, if the destination Shell Attribute Form contains the "uuu_integrated_with" Data Element.
Note: The application name value is sent by Gateway. The name is not hard-coded by Unifier.
Gateway maintains a cross-reference table between objects of the two applications to monitor whether to create or update the records of an object. The cross-reference table has IDs of projects in Unifier and P6. If the cross-reference table has and entry for a Unifier project against a P6 project, then Gateway will update the Unifier project; otherwise, Gateway will create a Unifier project.
Note: If a project exists in Unifier and does not have an entry in the Gateway cross-reference table, then when Gateway proceeds to create a project in Unifier, to prevent creating aduplicat project in Unifier, Unifier converts the create request to update request and proceeds to update the existing project, instead of creating a new project.