First of all thanks for your time, and thanks for your help.

We have the following doubt: how HTTP status is being replied from a SOAP Service to the Outbund System?

Where in HealtShare 2020's classes is being replied an HTTP/200 OK or an HTTP/500 or any SOAP HTTP status code?

We ask this because some outbound systems do need to have an HTTP 200 to being able to process our SOAP responses.

We have been examining the following classes:


0 2
0 64

First of all, thanks for your help, and time reading this question.

Why, when we send a SOAP message from SoapUI to a SOAP service in a HealthShare environment called 'ESBCHUIMI,' it recognizes the 'Credenciales' header, which has 'usuario' and 'password' as properties. This class is a %SOAP.Header.

However, when we load the WSDL using the SOAP wizard from this SOAP Service to another HealthShare environment called ESBSSCC and send it from SoapUI to ESBSSCC, when it is being forwarded from ESBSSCC to ESBCHUIMI, the ESBCHUIMI's service outputs:

0 5
0 76


First of all thanks for your help, time, and answers.

We would like to know what are we doing wrong and how could we improve it and fix it.

We need to convert the Api Monitor Metrics which are a String with this format:

iris_cache_efficiency 13449.122
iris_cpu_pct{id="CSPDMN"} 0
iris_cpu_pct{id="ECPWorker"} 0


iris_wdwij_time 11
iris_wd_write_time 8
iris_wij_writes_per_sec 0


We would expect them to look like a normal JSON as follows:

0 4
1 114


First of all thanks for your time, thoughts, teaching and help:

We wonder how could we get the metrics from http://[Ip]:[Port]/api/monitor/metrics and use them in Kibana to chart statistics.

We would like to ask you how do you use the api monitor metrics, and as a second question, how would you suggest to utilize them in a third party software as Kibana to chart them.

We have thought to do the following:

0 0
1 100


First of all thanks for your time reading this doubt.

We have discovered the following behaviour. Inside a Router we have a roule which needs to filter out the ADT_A08 messages which have not OBXs.

The legacy system had this rule implemented:


However we have tested it and it does not filter out the ADT_A08 messages.

0 5
0 124