---
title: "Deploying and Using the Application"
canonical: "https://docs.infoblox.com/space/DeploymentGuideIPAMwithServiceNow/1297483494/Deploying%20and%20Using%20the%20Application"
format: markdown
---
To enable the integration, you’ll need both **destinations** and **traffic flows**. After deploying the integration from the Ecosystem Portal, these components are automatically populated.

**Steps to Deploy the ServiceNow Integration**

1. **Access the Ecosystem Portal**:  
Log in to the Infoblox CSP.
2. **Navigate to the Marketplace**:
  - Go to **Integrations** in the top menu.
  - Click on **Marketplace**.
    
3. **Deploy the Integration**:  
You will be redirected to the Infoblox Marketplace. Locate the integration name, and click **Deploy** to add it to your Infoblox portal.

Once deployed, the integration script will appear in the **Automation** tab of the Data Connector.

**Configure the Data Connector**

To use the Integration of Infoblox IPAM with ServiceNow a source and destination for the data connector is required. Perform the following steps to configure the Data Connector.

1. On the Infoblox CSP highlight on **Integrations, click** on ** Data Connector** in the revealed list
2. On the Data Connector tab, use Infoblox Cloud Source as the Source Type.

 

![image-20240911-101530.png](media://ad377b0a-1fdd-42be-928e-f411869cb89f)

 

3. **Destination Configuration **:- On the Data Connector tab, click on the **Destination Configuration** tab on the top of the Data Connector Page.

![image-20260817-080925.png](media://1274c926-ecb1-4b94-b1f6-4808605c688d)

 

> ℹ️ There should be two destination configurations: one for the scheduler and one for the event handler. The scheduler handles the bulk import of data from Infoblox to ServiceNow during the initial sync, ensuring the data between both systems is aligned. After the initial sync, the event handler takes over, managing any new device creations or updates by syncing them to ServiceNow in real-time.

 

![image-20260817-081023.png](media://d03ce03a-822f-41c6-bd56-fc3b46ecb9ed)

  

- Select the destination that is automatically populated for the Integration of Infoblox IPAM  with ServiceNow, as displayed in the Ecosystem Portal and configure the desired **Variables** for Authentication and Integration.
  
  - Variables
    - **cspInstance:** The CSP instance URL.
    - **cspApiKey**: The API key for Infoblox CSP.
    - **servicenowInstance: **The ServiceNow instance URL.
    - **servicenowUsername: **The username for ServiceNow API authentication.
    - **servicenowPassword:** The password for ServiceNow API authentication.
    - **servicenowDeduplication:** Flag to determine if deduplication should be performed.(Default value : false)
    - **syncOnlyTaggedEntities: **This parameter controls **which resources are synchronized** during the integration process—either **only tagged resources** or **all discovered resources**.  
  
Behavior
      - `true`
        - Only resources that have **tags assigned** will be considered for synchronization.
        - Untagged resources are **ignored**.
        - Useful when you want **fine-grained control** over which assets are synced.
      - `false`
        - **All resources** are synchronized, regardless of whether they are tagged.
        - Tags are not required for inclusion.
        - Useful for **full inventory synchronization**.
      

> ℹ️ ### Use Case for `syncOnlyTaggedEntities`
> ℹ️ 
> ℹ️ Some users want **only selected IPAM resources** to be synchronized with **ServiceNow**, while others prefer to sync the **entire IPAM database**.
> ℹ️ 
> ℹ️ The `syncOnlyTaggedEntities` setting supports both requirements:
> ℹ️ 
> ℹ️ - Users who want **selective synchronization** can enable `syncOnlyTaggedEntities` and tag only the required IPAM resources. This ensures that **only approved, relevant assets** are sent to ServiceNow.
> ℹ️ - Users who want **full visibility** can disable `syncOnlyTaggedEntities`, allowing the **entire IPAM dataset** to be synchronized without requiring tagging.


- Enable the destination by changing **State** to Enabled.


4. **Traffic Flow Configuration**

It is required to have two traffic flows

- **Scheduler**:  Triggers based on Cron job
- **Events**: Triggers based on Events

1. Click on the **Traffic Flow Configuration** tab located near the top of the Data Connector page. The traffic flow is also auto-populated upon deployment. It’s recommended to verify the traffic flow settings
  
  1. **Scheduler Traffic Flow:**
    - Enable the configuration by toggling the **State** to Enabled.
    - Select **Schedule Source** as the Source of Log Source Configuration with desired cron job, it is recommended to configure the cron to run on daily basis.
    - Expand the Destination Configuration list by clicking on the Destination Configuration header. Then, select the destination that was created earlier in this guide from the drop-down list
    - Expand the **Service Instance** list by clicking on the Service Instance header. Then, select the created Data Connector service from the list. Click on **Finish** to confirm the creation of the Traffic Flow.
  2. **Event Handler Traffic Flow:**
    1. Enable the configuration by toggling the State to Enabled.
      
    2. Select Infoblox Cloud Source as the Source of Log Source Configuration and select Audit Logs and DDI DHCP Lease Log.
      
    3. Expand the Destination Configuration list by clicking on the Destination Configuration header. Then, select the destination that was created earlier in this guide from the drop-down list.
      
    4. Expand the **Service Instance** list by clicking on the Service Instance header. Then, select the created Data Connector service from the list. Click on **Finish** to confirm the creation of the Traffic Flow

> 📝 It is recommended to enable event traffic 24 hours after the scheduler traffic flow is activated. The scheduler traffic flow is responsible for syncing all data from IPAM to ServiceNow, and the time required for this process depends on the volume of objects. To ensure the sync is completed successfully, it's advisable to allow a 24-hour buffer period before enabling event traffic.