Where Data APIs Are Published

Two settings decide it. The installation sets DATA_API_TARGET on the server:

• LOCAL: every account publishes in DataIQ.
• HUB: every account publishes on the Hub.
• TENANT, or not set: each account chooses. An account starts on the Hub until its admin switches it. When DataIQ has no Hub backend to publish to, accounts publish in DataIQ.

When accounts can choose, an account admin switches it in System Settings, on the Data APIs tab, with Publish data APIs in DataIQ. The choice applies to everyone in the account, and only account admins can change it. When the installation decides for every account, the toggle is disabled and the tab says which value is set.

Switching to DataIQ

The dialog lists the account's Hub connections. Tick the ones to copy into DataIQ: connections that already have APIs are ticked for you. A copy keeps the connection's id, so APIs already made on it keep working. If a DataIQ connection already has the same name, give the copy a new name; the dialog shows which API URLs move to it. Connections DataIQ cannot query stay on the Hub and are listed with the reason. The Hub itself is not changed.

Switching back to the Hub

Create API publishes on the Hub again, and the connection list shows the Hub's connections. Connections copied into DataIQ stay there, hidden until you switch back. The dialog lists any API that stops answering because its connection exists only in DataIQ.

Good to know

• While an account publishes in DataIQ, its connection list, the query console and the APIs all use DataIQ's own connections.
• Other servers of the same installation pick up a switch within 30 seconds.