Let's Integrate

Source System

Target System

Contract Management

Unifier

Nexus offers a very trivial procedure of creating integration. It is mostly of the six processes , as depicted in the below diagram.

Connectors

Connector

For

1️⃣

Unifier

2️⃣

Contract Management

Sequence of creating the connectors does not effect the flow process

Steps:

1. Give name to the connector which will also be used to identify the system e.g. Unifier, P6 etc
2. Select an extension from the drop down as Unifier is a generic SOAP Web Services , so select the same .
3. Click (+Add service) to add the services under this connector.

Environment

Environment gives a full set up to connectors in terms of Base URL, Authentication type , Username and Password.

1. Click on a Add Environment to create a new environment.

Data Mapping

Data mapping helps you to take source field from source system , and to map with target fields of target system in very simple way.

You can also customize you data according to the target source field through JavaScript code which includes data validation and any change in format.

1. Click on Add data mapping to create a new mapping.

Integration

Integration has four sub process i.e. Designer, Configuration,Execution, Notification.

Designer space can be distributed to different staging process , according to the use case is divided in three states.

Load

to read contracts and cost details from the Contract Management

Transform

data mapping and script writing

Create

to create , read and approve contracts in Unifier system.

Deployment

By clicking the Deploy button you can deploy your integration.

Monitoring

As you run the deployment in the previous step, the detailed stature of the process can be seen by clicking the monitoring menu card which is populated with no of running integration.No of completed/Failed.

Use Case

The use case involves integration between Oracle Primavera contract management through Nexus into Oracle Unifier .

Nexus offers a very trivial procedure of creating integration. It is mostly of the six processes , as depicted in the below diagram.

Connectors

Steps:

For this we require three operation :

Steps

Steps:

In the services, We are going to see read contracts.

Steps

In the services, we are going to see read cost details.

Steps

Environment

Data Mapping

The purpose of data mapping is to map the source Contract Management's source field to Unifier target field. e.g. as below:

Data Mapping allows you to validate your input to the target field,.

e.g. return 'Lump Sum' ;

Integration

Integration has four sub process i.e. Designer, Configuration,Execution, Notification.

Designer space can be distributed to different staging process , according to the use case is divided in three states.

Configuration steps involves configuring connectors and properties . By providing the constant values such as shortname, authcode, BPName.

The execution process can be scheduled based on the CRON expression or by Rest URL

CRON expression

REST URL

Deployment

By clicking the Deploy button you can deploy your integration.

Click Run now button to run your integration on demand.

Monitoring

Once you click on card you will be able to see the details as such Job Id , start time, end time , time elapsed and status of integration.

Once you click on any particular job Id, it expands into various staging level details.

On further expanding you can see each service levels detail of every integration.

hashtagUse Case

hashtagThe use case involves integration between Oracle Primavera contract management through Nexus into Oracle Unifier .

hashtagNexus offers a very trivial procedure of creating integration. It is mostly of the six processes , as depicted in the below diagram.

hashtagConnectors

hashtagSteps:

hashtagFor this we require three operation :

hashtagSteps

hashtagSteps:

hashtagIn the services, We are going to see read contracts.

hashtagSteps

hashtagIn the services, we are going to see read cost details.

hashtagSteps

hashtagEnvironment

hashtagData Mapping

hashtagThe purpose of data mapping is to map the source Contract Management's source field to Unifier target field. e.g. as below:

hashtagData Mapping allows you to validate your input to the target field,.

hashtage.g. return 'Lump Sum' ;

hashtagIntegration

hashtagIntegration has four sub process i.e. Designer, Configuration,Execution, Notification.

hashtagDesigner space can be distributed to different staging process , according to the use case is divided in three states.

hashtagConfiguration steps involves configuring connectors and properties . By providing the constant values such as shortname, authcode, BPName.

hashtagThe execution process can be scheduled based on the CRON expression or by Rest URL

hashtagCRON expression

hashtagREST URL

hashtagDeployment

hashtagBy clicking the Deploy button you can deploy your integration.

hashtagClick Run now button to run your integration on demand.

hashtagMonitoring

hashtagOnce you click on card you will be able to see the details as such Job Id , start time, end time , time elapsed and status of integration.

hashtagOnce you click on any particular job Id, it expands into various staging level details.

hashtagOn further expanding you can see each service levels detail of every integration.

Use Case

The use case involves integration between Oracle Primavera contract management through Nexus into Oracle Unifier .

Nexus offers a very trivial procedure of creating integration. It is mostly of the six processes , as depicted in the below diagram.

Connectors

Steps:

For this we require three operation :

Steps

Steps:

In the services, We are going to see read contracts.

Steps

In the services, we are going to see read cost details.

Steps

Environment

Data Mapping

The purpose of data mapping is to map the source Contract Management's source field to Unifier target field. e.g. as below:

Data Mapping allows you to validate your input to the target field,.

e.g. return 'Lump Sum' ;

Integration

Integration has four sub process i.e. Designer, Configuration,Execution, Notification.

Designer space can be distributed to different staging process , according to the use case is divided in three states.

Configuration steps involves configuring connectors and properties . By providing the constant values such as shortname, authcode, BPName.

The execution process can be scheduled based on the CRON expression or by Rest URL

CRON expression

REST URL

Deployment

By clicking the Deploy button you can deploy your integration.

Click Run now button to run your integration on demand.

Monitoring

Once you click on card you will be able to see the details as such Job Id , start time, end time , time elapsed and status of integration.

Once you click on any particular job Id, it expands into various staging level details.

On further expanding you can see each service levels detail of every integration.