- 4 minutes to read

Step 7: Import Monitoring Agents

Import Monitoring Agents into the Portal using the JSON exported in Step 6. The import is done through the Nodinite 6 staged upgrade panel in the Portal's Review and Download step.

Important

Rename agent databases before this step. Before exporting and importing, rename existing agent databases to include the environment name. This avoids conflicts when importing into the portal and allows the portal to match the correct databases.

Examples:

  • Nodinite_Agent_AzureLogicApps → Nodinite_DEV_Agent_AzureLogicApps
  • Nodinite_MonitoringAgent_BizTalk → Nodinite_DEV_Agent_BizTalk

After renaming, re-export the agent configuration from the Web Client (Step 6) so the exported JSON reflects the new database names.

Prerequisites

Steps

1. Check Core Services Installed

Return to the Portal and open your environment. Navigate to the Review and Download step. The Nodinite 6 staged upgrade panel is visible at the bottom of the page.

Staged upgrade panel – checkbox and JSON input
Example of the staged upgrade panel. Check the "I have installed the Nodinite 7 core services..." checkbox to enable the JSON text area. Then paste the exported JSON and click Analyze exported agents.

Check the checkbox:

☑ I have installed the Nodinite 7 core services and the new Web Client is up and running

This enables the Step 3: Import exported monitor agents JSON text area.

2. Paste the Exported JSON and Analyze

Paste the JSON copied in Step 6 into the text area, then click Analyze exported agents:

Analyze exported agents button
Example of the Analyze exported agents button in the staged upgrade panel.

Important

Datapower and Dynamics CRM agents must not be imported. If the JSON contains entries for these agents, remove them before pasting. These are legacy agents that must be updated using the old MSI-based installer, not the Portal.

3. Select the Local Server Hostname

After analysis, the portal displays all unique server hostnames found in the JSON. Select only the hostname(s) that refer to the local Nodinite server:

Hostname resolver – select local server
Example of the hostname resolver. Select only the server name(s) that belong to the local Nodinite Application Server. Deselect any remote servers.

Warning

Do not use localhost as a hostname. If localhost appears in the list, replace it with the actual machine name. localhost entries in the Agents configuration tab must be corrected to the real hostname or you will not be able to save later.

Rules for selection:

  • Keep entries that match the actual machine name of the Nodinite Application Server
  • Keep localhost only if you immediately update it to the actual machine name in the Agents tab afterwards
  • Deselect all remote server hostnames — agents on other servers are not supported in the Portal single-server model

Click Import selected agents to import the filtered list.

4. Review the Import Result

Import selected agents result
Example of the import result showing successfully imported agents with their types, ports, and service accounts.

Verify the imported list:

  • Only local-server agents are present
  • Datapower and Dynamics CRM agents are NOT in the list (remove them if present)
  • All agent entries show the correct service accounts and database names

5. Download the Agents Package

After a successful import, the portal enables the agents package download. If you have unsaved changes, a prompt appears:

Unsaved changes modal
Example of the unsaved changes modal — click Save and download to save the configuration and generate the agents package.

Click Save and download (or save first, then download) to generate the agents ZIP bundle. The ZIP is named:

<EnvironmentName>-upgrade-agents-environment.zip

Proceed to Step 8: Download and Update Monitoring Agents.

Completion Checklist

  • Core services installed checkbox checked in portal
  • Agent databases renamed before export (recommended)
  • JSON pasted and analyzed
  • Local server hostname(s) selected — no remote servers, no bare localhost
  • Datapower and Dynamics CRM agents excluded
  • Import completed successfully
  • Agents package downloaded

Troubleshooting

Analyze Button Does Nothing

Problem: Clicking Analyze exported agents has no visible effect.

Solution:

  • Verify the core services checkbox is checked first
  • Confirm the JSON is valid (use an online JSON validator)
  • Ensure the UniqueId field is populated on each entry — re-run Step 4 if missing

Cannot Save – localhost Validation Error

Problem: Portal rejects save because an agent still references localhost.

Solution:

  • Go to the Agents tab in the portal wizard
  • Find the agent entry with localhost as the server
  • Replace localhost with the actual machine hostname
  • Save and retry download

Duplicate Agent Type in List

Problem: Two or more agents of the same type appear after import.

Solution:

  • Edit the exported JSON before pasting to keep only one agent entry per type
  • Re-paste and re-analyze

Next Step