Updating the Connector

For sites already on the current line of the ABB Knowledge Manager connector (after the upgrade from the legacy connector, or a new install). An update moves the connector on an agent host to a newer release. It is a smaller step than the legacy upgrade: your configuration, your license and your credentials stay where they are.

This page describes how updates are planned to run. No customer host has been updated on the current line yet; the first updates will refine it, and this page will change with them.

When an update comes

EEI starts an update when there is a reason to: a new release with a fix or a feature you need, a change in Seeq that a new release adapts to, an issue EEI's checks find in a deployed version, or, at the least, about every six months, so no host falls far behind. Each release is described in the release notes, including anything it needs. See Versions & Seeq Compatibility for how releases relate to Seeq's.

How it runs

When	What
About a week before	EEI opens an update request at support.endeavoreng.com, on your behalf, with the people from your side. It lists the facts EEI holds about your agent host; you confirm them, or say what has changed
Before the session	EEI checks the release against your host and your license, and posts the release zip and its checksum in the request. You copy it to the agent host and check the hash
The session (plan about an hour)	The steps below. The datasources are interrupted only between stopping and starting the agent
The next scheduled index	It completes with the same counts; you confirm it in the request
One index cycle later	You delete the rollback copies; EEI closes the request

If something has changed on the host (connections added, the Seeq server moved, a new agent host), EEI adds a short form to the request, and may ask for a fresh set of agent facts. A move to a new agent host is handled as a new onboarding, with a new license for that host.

The license usually stays. It is bound to the agent host, not to a version. A new one is needed only when the update adds datasources beyond your license, the license is due to expire, or a feature is added; EEI tells you in the request, and the license steps are then those of the legacy upgrade (Window 5–7).

The session

The same step labels as the legacy upgrade, fewer steps. The commands run in the Seeq Command Prompt (seeq stop, seeq start) and an Administrator PowerShell on the agent host.

Step	Action	You should see
Window 1. Stop the agent	seeq stop	Success: No Seeq-related ports appear to still be in use.
Window 2. Set aside the current version	Copy ABB KM Connector V3.json to <rollback folder>, and move the current vforge-seeq-link-connector-abbkm-<previous version> folder there from <data folder>\plugins\connectors. Leave the vforge folder where it is: it holds your license and the secrets store	Both in <rollback folder>; no other ABB Knowledge Manager folder in connectors
Window 3. Place the new version	From the zip, copy only the folder vforge-seeq-link-connector-abbkm-<connector version> into connectors. Leave the configuration as it is	It contains a .jar file and lib and bin folders
Window 4. Start	seeq start	EEI confirms the new version loaded, still licensed, credentials read from the store; your datasources connect

Verify

Check	Expected
Seeq, Administration → Datasources	Each datasource connected, showing the new version
Index	Request Index on each datasource; it completes with about the same counts as before
Existing content	A familiar worksheet still trends
vfa secrets verify --require-store	Every row PASS (see Move the credentials for vfa)

If any of these fails and cannot be fixed in the session, roll back the same day.

Rolling back

seeq stop; remove the new connector folder; move the previous version's folder back, and put back your configuration copy from <rollback folder>; seeq start. No license or credential step is needed: the license is bound to the host, and both versions read the secrets store. Keep the rollback copies for one full index cycle.