Hello community,

we opened up a WRC call meanwhile and I'll share the gained information in case anyone stumbles into this post.

The information "Web IP Address" is received from the machine (client) which sends messages to the messagebank. It is configured in the client's %SYS Namespace in a global ^SYS in the subscripts ("WebServer","Name") and ("WebServer","Port").

The information NodeId is derived from another client setting stored in every namespace in a global ^Ens.MsgBank("NodeId"). If a message has been sent to the messagebank, a new node with a new NodeId is created, when the given nodeId has not sent any messages before.

In our setup we were able to change the ^SYS("Webserver") to the correct settings and the automatically created nodes were merged with the manually created nodes by the given NodeId and Web IP Address. This enabled us to select messages from the messagebank's message viewer an resend them to the original target without any further action. This also works for messages, which have been sent in the past containing a wrong Web IP Address.

If you want to change a client seemlessly, then make sure to check these globals, especially the NodeId, before any messages will be sent. Hopefully this explanation helps other desperate messagebank users to understand what's going on in the background and not to fall into the same traps we did.

Kind regards,

Martin

Hello everybody,

as nobody seems to share the demand for an Orbis HL7 schema definition (or at least nobody seems to have one), I started to create one by myself. If anybody is interested in the schema feel free to write a PM, I'm happy to share my results.

Regards,

Martin

Hello everybody,

after some hours of searching it appeared, that I was mislead by the "404 Not Found" error. In the end is was nothing more than an authentication problem, which should have been answered by "403 Forbidden".

Regards and a happy new year,

Martin