Configure Scheduler for Discovery Data Sync

The purpose of this scheduler is to move processed device data from the Hardware table to the Discovery Details table.

• The Hardware table acts as a staging area where raw data from agents is initially stored.

• The Discovery Details table stores structured and normalized data used for reporting, CMDB, and asset visibility.

This scheduler ensures that data collected from agents is transformed, synchronized, and made usable within the discovery module.

To Configure Scheduler for Discovery Data Sync, perform the following steps:

1. Log in to the application as an Application Designer.
   

2. Navigate to Discovery > Settings > Design Studio > Scheduler.
   

3. Click New to create a scheduler specifically for discovery sync.
   

4. Enter the required details on the General step.
   For more information, refer to the Field Description.
   

   Figure: Scheduler

   
   Field Description

   Field Name	Description
   Scheduler Name	Enter the name of the scheduler used for syncing agent-based discovery data. In this case, Agent Based Discovery Sync clearly indicates that the scheduler processes and moves agent data into the discovery module.
   Scheduler Type	Define the type of scheduler execution. Custom Event is selected to allow invocation of a specific API-based process rather than a predefined system event.
   Description	Provide additional information about the scheduler's purpose. This can be used to describe that the scheduler is responsible for moving data from the hardware table to the discovery table using the configured API.
   Domain	Specify the Domain under which the scheduler operates. This ensures that the scheduler processes data specific to the selected organizational domain.
   Department	Identify the Department associated with the scheduler. In this case, it indicates that the scheduler is managed and used by the IT (Information Technology) team handling asset and discovery operations.
   Sub Domain	Further categorize the scheduler within a specific subdivision of the domain, ensuring data segregation and proper execution context.
   Scheduler Owner	Enter the user responsible for managing and monitoring the scheduler. This helps in assigning ownership for maintenance and troubleshooting.
   Table	Define the target table where processed data will be stored. Here, Discovered Details indicates that the scheduler inserts transformed data into the discovery table.
   Execute at	Specify the execution environment for the scheduler. Web Server indicates that the scheduler runs on the application server where API calls and processing logic are executed.
   Active	Enable or disable the scheduler. When enabled, the scheduler runs as per the configured schedule to sync agent-based discovery data.

5. Enter the details in other steps such as Frequency and Condition.
   This can be configured as per normal scheduler configuration. For more information, refer to Configure Scheduler.
   

6. Enter the required details in the Call API tab of the Actions step.
   For more information, refer to the Field Description.
   
   Figure: Scheduler Actions

   Field Description
   

   Field	Description
   Exclude already processed records	When enabled, ensures that records already processed in previous scheduler runs are skipped. This avoids duplicate data insertion into the Discovery table.
   Archive Days for Impacted Records	Define the number of days processed records are retained before being archived. Useful for maintaining data history and optimizing storage.
   Action Type	Specify the direction of the API interaction. Inbound indicates that the scheduler receives data from the configured API into the system for processing.
   Target Action	Define the operation performed on the target table. Create Record inserts new discovery records, while Update Record modifies existing records if matching data is found.
   API	Specify the API configuration used for fetching agent-based discovery data. In this case, AgentBase Discovery Sync is used to retrieve data from the hardware table. For more information, refer to Configure Agent-Based API.
   Process Type	Define how the API request is processed. Bulk Request indicates that multiple records are processed in a single execution, improving efficiency for large datasets.

   
   

7. Enter value in Request Body on the Actions step.
   This includes mentioning about the API Payload.
   
   Figure: Request Body
   

   Note

   The Request Body section defines the input payload sent to the API during scheduler execution. It determines which data is fetched from the hardware table before being processed and inserted into the Discovery table.

   
   {
     "tableUniqueId": "3xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx91",
     "filters": [
       {
         "columnName": "Data Source",
         "value": "Agent"
       }
     ]
   }
   

Request Parameters

8. Select Display Type and enter the Response in the Response field.
   
   Figure: Response

Sample Response

[
  {
    "Agent Version": "2.5.6.27",
    "CPU": "Intel(R) Xeon(R) Gold 6342 CPU @ 2.80GHz - 4 Core",
    "Data Source": "Agent",
    "Device Type": "Computer",
    "IP Address": "**.***.**.**",
    "Mac Address": "00-xx-xx-xx-xx-66;",
    "OS Caption": "Microsoft Windows Server 2019 Datacenter",
    "System Name": "N**********"
  }
]

9. Publish the Scheduler.