Step 6: Import Monitoring Agents

Import the Monitoring Agents into the Portal with the JSON you exported in Step 5. The import runs in the Nodinite 6 staged upgrade panel of the Portal's Review and Download step and produces the second package, the agents package, that you deploy in Step 7.

Understanding the Staged Agent Import

The staged agent import. Blue nodes are user interfaces (Nodinite Overview in the Web Client, and the Portal), purple nodes are the agent definitions, orange nodes are the package, its CLI deployment, and the agents on other servers in Step 7, and green is the result.

Prerequisites

• Step 5 completed – Monitoring Agents exported to JSON, with agent databases renamed as recommended there
• The edited JSON copied to the clipboard

Steps

1. Confirm the Core Services Are Installed

Return to the Portal, open your environment, and go to the Review and Download step. The Nodinite 6 staged upgrade panel is at the bottom of the page. It has three numbered parts: Step 2: Core services package (the package you deployed in Step 4), Step 3: Import exported monitor agents, and Step 4: Core plus agents package, which stays disabled until the import is done.

Example of the staged upgrade panel before you confirm the Core Services: the JSON text area and Analyze exported agents are locked.

Select the checkbox:

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

This unlocks Step 3: Import exported monitor agents.

Example of the panel after you select the checkbox: paste the JSON exported from the Nodinite Overview in the new Web Client, then click Analyze exported agents.

2. Paste the Exported JSON and Analyze

Paste the JSON from Step 5 into the text area, then click Analyze exported agents:

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

Important

IBM DataPower and Dynamics CRM agents must not be imported. Remove them from the JSON before you paste. They stay on the MSI-based installer.

3. Select the Local Server Host Name

The Portal lists every unique server host name found in the JSON. Select only the host name of the Core Services server:

Example of the hostname resolver. Select only the server name that belongs to the local Nodinite application server, and clear any remote servers.

• Keep the entries that match the machine name of the Nodinite application server.
• Clear all remote server host names; the staged upgrade imports only agents on the Core Services server. You update the agents on other servers locally on each server, see Update Agents on Other Servers.
• Never keep localhost. Replace it in the JSON before you paste (Step 5). If a localhost entry slips through, change it to the machine name in the Agents step before you save, or the Portal won't let you save.

Click Import selected agents.

4. Review the Import Result

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

Verify that:

• Only agents on the local server are listed
• No IBM DataPower or Dynamics CRM agents are listed
• Every agent shows the correct service account, port, and database name

5. Download the Agents Package

After a successful import, the Portal enables Step 4: Core plus agents package. The package contains one folder per server; you run each folder's command on its own server. If you have unsaved changes, a prompt appears:

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

Click Save and download. The ZIP is named <EnvironmentName>-upgrade-agents-environment.zip. Continue with Step 7: Download and Update Monitoring Agents.

Completion Checklist

• Core services installed checkbox selected in the Portal
• JSON pasted and analyzed
• Only the local server host name selected; no remote servers, no localhost
• IBM DataPower and Dynamics CRM agents excluded
• Import completed and agents package downloaded

Troubleshooting

Analyze Button Does Nothing

Clicking Analyze exported agents has no visible effect. Check the following:

• The core services checkbox is selected
• The JSON is valid
• Every entry has a populated UniqueId; run Step 4 again if it's missing

Cannot Save – localhost Validation Error

The Portal rejects the save because an agent still references localhost. Check the following:

• Open the Agents step of the wizard
• Find the agent entry with localhost as the server
• Replace localhost with the machine name, then save and download again

Duplicate Agent Type in List

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

• Edit the exported JSON to keep only one entry per agent type
• Paste and analyze again

Next Steps

• Step 7: Download and Update Monitoring Agents

Related Topics

• Updating from v6 to v7 – Migration Guide
• Step 5: Agents – fresh install reference
• Monitoring Agents Overview