# Let's Integrate
{% hint style="info" %}
Let's start the integration process. :smiley:
{% endhint %}
## **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** |
{% hint style="info" %}
Sequence of creating the connectors does not effect the flow process
{% endhint %}
{% tabs %}
{% tab title="Unifier" %}
#### Steps:
* [x] 1\. Give name to the connector which will also be used to identify the system e.g. Unifier, P6 etc
* [x] 2\. Select an extension from the drop down as Unifier is a generic SOAP Web Services , so select the same .
* [x] 3\. Click (+Add service) to add the services under this connector.
{% endtab %}
{% tab title="Unifier" %}
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
* [x] 1.Provide the title and name for the service.
* [x] 2\. Provide the URL of Unifier Web Services and service end point for the operations declared as per the WSDL.
{% endtab %}
{% tab title="Contract Management" %}
#### Steps:
* [x] 1\. Give name to the connector which will also be used to identify the system e.g. Unifier, P6 etc
* [x] 2\. Select an extension from the drop down as Unifier is a generic SOAP Web Services , so select the same .
* [x] 3\. Click (+Add service) to add the services under this connector.
{% endtab %}
{% tab title="Contract Management" %}
#### In the services, We are going to see read contracts.
The idea behind the operation is to read contracts from the Contract Management .
#### Steps
* [x] 1.Provide the title and name for the service.
* [x] 2\. Provide the URL of CM Web Services and service end point for the operations declared as per the WSDL.
{% endtab %}
{% tab title="Contract Management" %}
#### 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
* [x] 1.Provide the title and name for the service.
* [x] 2\. Provide the URL of CM Web Services and service end point for the operations declared as per the WSDL.
{% endtab %}
{% endtabs %}
## Environment 
Environment gives a full set up to connectors in terms of Base URL, Authentication type , Username and Password.
{% tabs %}
{% tab title="Environment" %}
\*
\[x] 1. Click on a Add Environment to create a new environment.
{% endtab %}
{% tab title="Contract Management" %}
* [x] Provide the Base URL for the contact management and the Authentication Type along with username and password details.
{% endtab %}
{% tab title="Unifier" %}
* [x] Provide the Base URL for the contact management and the Authentication Type along with username and password details.
{% endtab %}
{% endtabs %}
## Data Mapping .png?alt=media&token=c09a1d6d-629c-431f-b44d-99987d8e257d)
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.
{% tabs %}
{% tab title="Data Mapping" %}
\*
\[x] 1. Click on Add data mapping to create a new mapping.
{% endtab %}
{% tab title="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:
| Contract Management | Unifier |
| :-----------------: | :---------------------: |
| Title | title |
| DocumentNumber | uconContractnumberTXT16 |
{% endtab %}
{% tab title="Data mapping" %}
#### 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' ;
{% endtab %}
{% endtabs %}
## Integration 
#### Integration has four sub process i.e. Designer, Configuration,Execution, Notification.
{% tabs %}
{% tab title="Designer" %}
#### 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. |
{% endtab %}
{% tab title="Configuration" %}
#### Configuration steps involves configuring connectors and properties . By providing the constant values such as shortname, authcode, BPName.
* [x] Here Contract Management and Unifier is the connectors configured.
{% endtab %}
{% tab title="Execution" %}
#### 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.
{% endtab %}
{% tab title="Notification" %}
{% endtab %}
{% endtabs %}
## Deployment 
{% tabs %}
{% tab title="Deploy" %}
#### By clicking the Deploy button you can deploy your integration.
{% endtab %}
{% tab title="Run Deploy" %}
#### Click Run now button to run your integration on demand.
{% endtab %}
{% endtabs %}
## Monitoring 
{% tabs %}
{% tab title="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.
{% endtab %}
{% tab title="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.
{% endtab %}
{% endtabs %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.nexus-platform.com/integration/lets-integrate.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.