Using socket/ism messages in large environment, which DGE to target?

[krisztian]

Hi,
If I try to use the socket/ism interface to send messages to Traverse in an environment with a lot of DGEs (we have a message handler running with each DGE) do I need to target a specific DGE when I send a message or can it be sent to any DGE? In other words does my external script need to know which DGE the device it sends the message for belongs to?
Thanks,
Krisztian

[sysadmin]

Hi Krisztian,

Messages (regardless of whether sent via socket/ism or other message source) by default must be sent to the DGE the device is provisioned against. However, message handlers can be paired to multiple DGEs, allowing you to specify what DGEs each message handler can receive messages for. If you log in as superuser and navigate to Administration -> other -> Message Handler Configuration you will see an entry for each message handler.

If desired, you can pair a single message handler with all DGEs (using the "publish" method) and send the socket/ism messages to that server for publishing. Alternatively, you may choose to associate each message handler to one or more DGEs - for example one designated msg handler per geographical region. After pairing the DGEs to your liking, the messages can be sent to the desired sytem and will be published to the event management console (no restart required).

- Zyrion Support

[krisztian]

If desired, you can pair a single message handler with all DGEs (using the "publish" method) and send the socket/ism messages to that server for publishing. Alternatively, you may choose to associate each message handler to one or more DGEs - for example one designated msg handler per geographical region. After pairing the DGEs to your liking, the messages can be sent to the desired sytem and will be published to the event management console (no restart required).


Thanks for the explanation, it makes sense now. One question I still have is if I assign multiple DGEs to a message handler, do I have to use the 'publish' method? (Since according to the docs, 'direct' means that the message handler writes to the DGE database directly, but it might not have access to DGE databases running on other hosts, right?)
Krisztian

[rajib]

if I assign multiple DGEs to a message handler, do I have to use the 'publish' method? (Since according to the docs, 'direct' means that the message handler writes to the DGE database directly, but it might not have access to DGE databases running on other hosts, right?)
Krisztian

Correct - if the "direct" method is selected, the Message Handler in question will attempt to record the event directly into the DGE database, which may or may not be accessible (as you have noted) from that host. In contrast, the "publish" method uses the internal communication bus where the events will be exchanged from the Message Handler to the appropriate DGE via the BVE.

You are probably familiar with the EDF interface, which is similar to ISM but for test results.
It might be worth noting that there is a Web Services API that is complementary to the socket based EDF interface. The Web Services API allows client applications to insert test results by communicating with the BVE (webapp to be specific) without having to know which DGE is responsible for a device/test. If you feel that a similar API for the ISM interface might be useful, you can submit a feature request (there is a topic within the user forum).

Regards