Go to documentation repository
...
application/json – a message is sent and received in JSON format. If Axxon PSIM cannot parse the message in JSON format, an attempt is made to recognize the message in plain/text format.
plain/text – the Axxon PSIM event is sent and received in the format "TYPE|ID|EVENT".
...
amq.topic allows for subscriptions ranging. Each event sent from Axxon PSIM is signed with a special header, which is built according to the following scheme:
routingkey = "Axxon PSIMpsim.event." + msg.GetSourceType() +"." + msg.GetSourceId() + "." + msg.GetAction();
...
amqp_listen.exe localhost 5672 amq.topic Axxon PSIMpsim.event.#
Subscription to Action==”RUN” events
amqp_listen.exe localhost 5672 amq.topic Axxon PSIMpsim.event.*.*.RUN
| Note | ||
|---|---|---|
| ||
Events enter the RabbitMQ queue from each Axxon PSIM core individually. For example, if there are two cores in the system, and the event occurred on a core that has incorrect settings or does not have a connection to RabbitMQ, the event will not get into the queue, despite the fact that the second core will receive it. Each core sends only its own messages. |
...
The receiver is implemented according to the amq.direct scheme. It is subscribed to all events with the "bindingkey" key. bindingkey should have the following format: "Axxon PSIMpsim." + ComputerName (case sensitive).
...
amqp_sendstring.exe localhost 5672 amq.direct Axxon PSIMpsim.ASUS "CAM|1|HELLO"
or JSON
amqp_sendstring.exe localhost 5672 amq.direct Axxon PSIMpsim.ASUS {\"Type\":\"MACRO\",\"Id\":\"1\",\"Action\":\"RUN\",\"Params\":{\"test1\":\"+++\",\"test2\":\"000\"}}