- 3 minutes to read

Step 5: Export Monitoring Agents

The Core Services now run v7, but the Monitoring Agents are still v6. Export the locally installed agents to JSON from the Nodinite Overview page in the v7 Web Client; in Step 6 the Portal turns that JSON into the agents package. The export comes from the upgraded Configuration Database, so it carries each agent's identity (UniqueId) into v7.

Prerequisites

Important

Recommended: rename agent databases before you start the migration, not only before this export. Include the environment name in each agent database name, for example Nodinite_Agent_AzureLogicApps → Nodinite_DEV_Agent_AzureLogicApps or Nodinite_MonitoringAgent_BizTalk → Nodinite_DEV_Agent_BizTalk. This avoids conflicts during the Portal import and lets the Portal match the right databases. See Agent Database for how agent databases are installed and updated.

Steps

  1. Open the Web Client.

  2. Navigate to Administration → Tools → Nodinite Overview.

    Nodinite Overview page with the Export Monitor Agents button
    Example of the Nodinite Overview page showing the 'Export Monitor Agents' button in the top-right corner.

  3. Click Export Monitor Agents. A modal opens with the JSON output.

    Export Monitor Agents modal with JSON output
    Example of the Export Monitor Agents modal with the MonitorAgentId, UniqueId, ConnectionType, and ServiceURL fields of each Monitoring Agent. Click the text area to copy all content to the clipboard.

  4. Verify that the UniqueId field is present and populated; the database upgrade in Step 4 sets it.

  5. Click the text area to copy the JSON to the clipboard.

  6. Edit the JSON:

    • Keep only agents installed on the Core Services server. Remove agents installed on other servers; you update them locally in Step 7.
    • Remove the IBM DataPower and Dynamics CRM agents. They stay on the MSI-based installer and are not imported into the Portal.
    • Replace localhost in every Service URL with the machine name of the server where the agent runs, the same name you used in the Servers step. The Portal doesn't accept localhost on import.

  7. Keep the edited JSON ready for the next step.

Completion Checklist

  • Agent databases renamed (recommended)
  • Monitoring Agents exported to JSON with populated UniqueId fields
  • Remote, IBM DataPower, and Dynamics CRM agents removed from the JSON
  • No localhost in any Service URL
  • JSON copied for Step 6

Troubleshooting

Export Button Missing

You can't find Export Monitor Agents. Check the following:

  • You are signed in as an administrator
  • You opened Administration → Tools → Nodinite Overview
  • Clear the browser cache and reload

JSON Missing UniqueId

The exported JSON has no UniqueId field. Check the following:

  • The Step 4 deployment completed successfully
  • The database upgrade ran without errors
  • Run the CLI deployment from Step 4 again if needed

Next Steps