Overview
Client-mode REST API connector for Rhize, the ISA-95 manufacturing data hub: record job responses and equipment actuals from production topics, add and update equipment, query equipment, job responses, material lots, data sources, KPIs and the audit log, and start BPMN workflows, through the Rhize GraphQL API with Keycloak tokens. This is one of the templates in the Rhize (ISA-95 manufacturing data hub) REST API app (rhize). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No reachable Rhize instance or credentials (self-hosted, commercial; no public image or sandbox). Ran static, mock, a real local Keycloak for the token events and a real Dgraph engine with the public Libre SDL; no call to a real Rhize API
Auth
Keycloak OpenID Connect. RhizeAuth GetAccessToken (client_credentials) or GetPasswordToken (password grant) returns a JWT (docs example expires_in 28800); publish authorization ‘Bearer <access_token>’ on every RhizeApi event. Hub secrets RHIZE_REALM, RHIZE_CLIENT_ID, RHIZE_CLIENT_SECRET (+ RHIZE_USERNAME / RHIZE_PASSWORD for the password grant). Auth headers used by the template:Authorization: {value.json.authorization}.
Template parameters
BASE_ADDRESS default: https://YOUR_RHIZE_HOST.
Events
Deploy
Get the template card (JSON withtemplate and metadata) from the broker, then deploy the connector:
BASE_ADDRESS already filled in:
-addRoute (do not include ADD METADATA).
Usage example
CallQueryEquipment by publishing a JSON payload to its request topic, and read the reply on the response topic:

