Question
Yone Moreno · Jun 3

SOAP Service: Managing ER7 returns HTTP 500

Good morning,

We would appreciate if you could read us and if you have the opportunity, please respond to us.

 

The current situation is as follows:

We have 2 environments PREproduction and INTegration :

Ensemble version in PREproduction:

Cache for UNIX (Red Hat Enterprise Linux for x86-64) 2018.1.6 (Build 717U) Thu Feb 24 2022 13:27:54 EST

Version of the tool to convert XML to ER7 and vice versa, the ITB, in PRE (we get it in the ITB.info.cls file):

Parameter VERSION = 2.1;

 

Ensemble version on INTegration:

IRIS for UNIX (Red Hat Enterprise Linux for x86-64) 2020.1.1 (Build 408U) Sun Mar 21 2021 22:21:14 EDT

Version of the tool to convert XML to ER7 and vice versa, the ITB, in INTegration (we get it in the ITB.info.cls file):

Parameter VERSION = 3.4;

 

Our need is the following:

Why in PREproduction do we get an http 500 when invoking a SOAP service that makes use of the ITB to convert from XML to ER7?

We observe part of the SOAP service's code:

Class Servicios.SOAP.DragoAPtoVNAv01r00 Extends (EnsLib.SOAP.Service, ITB.HL7.BS.XMLService) [ ProcedureBlock ]
{
...
set ackXML = ##class(ITB.HL7.Util.Convert).ER7ToXML(ackER7,.tSC,"2.5")
...
}

However, when invoking the same service (with the same code) in the INTegration environment, we observe that it returns an http 200 ok:

Could you please tell us, explain, or point us to relevant documentation on why in PREproduction, with Ensemble 2018 and ITB 2.1 it generates http 500 (which would be wrong); and yet in INTegration in Ensemble 2020 and ITB 3.4 it responds with http 200 ok (which is correct)?

 

▶️ Thank you very much in advance 🙏👌, your time, assistance and support on this issue is 🙏 appreciated.

Best regards

 

0
0 36
Discussion (1)2
Log in or sign up to continue