Setting Up the Octave EAM Connector

Before you begin

• In Octave EAM, outbound asset events are on and published as JSON.
• DataBridge Pro is configured in Octave EAM.
• You have a Praedico API key. See how to get one.

Download connector (.json)

1. Import the connector

1. On the DataBridge Pro canvas, drag the Process Group icon onto the canvas.
2. Click Browse, select Praedico-Connector.json, and click Add.

The Praedico_Connector group appears, with its PRAEDICO-CONFIG parameter context already bound.

2. Enter your settings

Open Global menu → Parameter Contexts → PRAEDICO-CONFIG → Edit, set these parameters, and click Apply.

Parameter	Value
api_url	Your Praedico API URL followed by /v2/assets, e.g. https://<your-api-host>/<your-tenant>/v2/assets
api_key	Your Praedico API key
asset_mapping	Keep the default to start. See Field Mapping.

Caution

api_url must end in /v2/assets. A bare base URL returns 404 Not Found.

3. Start and test

1. Right-click the process group and choose Start.
2. In Octave EAM, create or re-save one test asset.
3. Check that InvokeHTTP received 202 Accepted.
4. Check that the asset appears in Praedico Rail.

Once one asset works, re-save your existing assets in EAM to send them all. For a large estate, ask Hexagon to seed the outbound events instead.

Troubleshooting

Failed events are written to the DataBridge Pro logs by the LogAttribute processors in the group, then dropped. Fix the cause and re-save the asset in EAM to send it again.

Problem	Fix
401	Check api_key. See When authentication fails.
404	Make sure api_url ends in /v2/assets and has the right tenant.
400	The invokehttp.response.body attribute names the field at fault. Correct its mapping.
ERROR_MESSAGE on the event	The asset couldn’t be mapped, e.g. it has no ID or asset_mapping isn’t valid JSON.
202, but the asset doesn’t appear	A value didn’t match Praedico, e.g. an unknown sub-area, category, or type. See Job Status.

Still stuck? Contact support with the logged attributes for the failed event.