Introduction
Smart Features
Architecture
Connectors
Environment
Data Mapping
Deployment
Monitoring
Email Template
Extension
- BigQuery Extension
Integration
Deployment
- Nexus installation guide
- Connect Nexus with Oracle Autonomous Database
Services
Changelog

Powered by GitBook

On this page

Use Case
Connectors
Environment
Data Mapping
Integration
Deployment
Monitoring

Was this helpful?

Integration

Let's Integrate

Let's start the integration process. 😃

Use Case

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

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

As per the use case, the first step requires you to create two 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.

The idea behind this operations is to get data from contract manager and then create the contracts in Unifier and approve it.

For this we require three operation :

createBPRecord , to create the contracts in Unifier.
getBPList, to get the record number.
updateBPRecordV2, to approve the contracts.

Steps

1.Provide the title and name for the service.
2. Provide the URL of Unifier Web Services and service end point for the operations declared as per the WSDL.

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.

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

The idea behind the operation is to read contracts from the Contract Management .

Steps

1.Provide the title and name for the service.
2. Provide the URL of CM Web Services and service end point for the operations declared as per the WSDL.

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

The idea behind the operation is to read contracts from the Contract Management .

Steps

1.Provide the title and name for the service.
2. Provide the URL of CM Web Services and service end point for the operations declared as per the WSDL.

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.

Provide the Base URL for the contact management and the Authentication Type along with username and password details.

Provide the Base URL for the contact management and the Authentication Type along with username and password details.

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.

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

Contract Management

Unifier

Title

title

DocumentNumber

uconContractnumberTXT16

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

As here Contract Management(source system) is not providing value for upoContactTypePD. In that scenario Nexus provides functionality of knitting customized Java Script coding to get desired input in 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.

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.

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

Here Contract Management and Unifier is the connectors configured.

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

CRON expression

You can choose any CRON expression of you requirement by clicking the link given in the below picture and schedule the job.

Once you enable the button it will start running based on the schedule.

REST URL

This is the second way of scheduling the integration based on the Rest endpoint. Once you enable the button it will start running based on the schedule.

Deployment

By clicking the Deploy button you can deploy your integration.

Click Run now button to run your integration on demand.

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.

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.

PreviousNotification NextBasic scripting

Last updated 2 years ago

Was this helpful?