go to post Marc Mundt · Feb 9, 2021 It's fairly common to use mutual TLS authentication as well. In a nutshell, both sides validate the other's cert before allowing a connection.
go to post Marc Mundt · Feb 6, 2021 It doesn't use audit events specifically, but maybe creating custom source control hooks would work? You can set actions for certain events such as compiles.
go to post Marc Mundt · Feb 5, 2021 %SQL.Statement's %Execute method returns a result set (%SQL.StatementResult) object, not a %Status. You can check if any rows were returned by checking %ROWCOUNT or %Next() in the StatementResult.
go to post Marc Mundt · Jan 29, 2021 I suspect that some of the binary bytes are getting converted to UTF-8, and this is what the "u" option in the sixth argument of %WriteJSONStreamFromObject specifies. You can try removing the "u" and see if that helps, but even if it does I believe you will find other problems because JSON isn't meant to carry raw binary data. Generally binary data is base 64 encoded when putting it in JSON. One example of the problem with binary data is that the value of binario needs to be enclosed in quotes "". But the binary data could include a byte which is the same code as a quote, which would cause the JSON recipient to think that the value of binario has ended. My suggestion is to base 64 encode the binary data.
go to post Marc Mundt · Jan 28, 2021 You are first copying the binary content into objetoSalida.informacion, which is a %String. Then you write the %String into objetoSalida.binario which is a %Stream.GlobalBinary. Why not just make objetoSalida.binario a %String?
go to post Marc Mundt · Jan 28, 2021 No, you should only stop a process using the IRIS process management tools unless instructed otherwise by the WRC.
go to post Marc Mundt · Jan 27, 2021 The task history page will display the process ID (PID) for the current running task. You can then use IRIS process management tools to monitor, suspend, or terminate the process if it's safe to do so.
go to post Marc Mundt · Jan 27, 2021 In Studio, go to File -> Change Namespace In the Cache Connection Manager window, click "Connect"In the Server Connection window, select the same server and click "OK"Here you can untick "Remember Password" and login again
go to post Marc Mundt · Jan 25, 2021 You were on the right track with %WriteJSONFromObject(), but you'll want to use %WriteJSONStreamFromObject() instead. I don't see what purpose the Body property in your request class serves. You can just create a stream object variable instead. set myTempStream=##class(%Stream.GlobalCharacter).%New() set tSC=##class("%ZEN.Auxiliary.altJSONProvider").%WriteJSONStreamFromObject(.myTempStream, pRequest) if $$$ISERR(tSC) { quit tSC } ...then later: Set tSC=..Adapter.PostURL(tURL,.tHttpResponse, , myTempStream)
go to post Marc Mundt · Jan 20, 2021 A pool size of 1 is the recommendation when you need to maintain FIFO (process all messages strictly in the sequence that they arrived). Going above 1 is fine if FIFO isn't required. Each additional pool job will result in an additional OS-level process, which adds a little bit of memory usage. How much CPU is used by each process depends on how much work the operation is doing. Essentially, changing pool size from 1 to 2 has the same resource impact as adding another identical business operation. The max possible pool size depends on lots of factors. I would suggest starting small (2? 4?), see how that affects the queue, and increase accordingly. Having a pool size of 10, for instance, isn't likely to cause performance or resource problems unless your operation is doing something crazy. If you start getting into a pool size of dozens you might want to take a closer look with the WRC. One of your main limitations might be how many concurrent connections System A allows you to make.
go to post Marc Mundt · Jan 20, 2021 Check the settings on the business operation -- you should set the Pool Size > 1. This controls how many processes the operation uses to process requests.
go to post Marc Mundt · Jan 20, 2021 Edit: Oops... I see Jeff Drumm already nailed this! The best way to do this is to define your own custom utility function (which is just a class method). Your custom function will then appear in the function list in the DTL editor along side the standard functions.
go to post Marc Mundt · Jan 19, 2021 Can the customer provide you with a sample XML file?If not, you can try something like this online tool which accepts an XSD file and generates a sample XML document with fake data according to the XSD schema.Demo.HL7.MsgRouter.Schema:ORM_O01 really isn't applicable to your use case. Not worth spending your time on it.
go to post Marc Mundt · Jan 19, 2021 $this is a reference to the currently executing DTL. We need a reference to the BP that's calling the DTL.Code action in DTL set ^zmm("$this")=$this set ^zmm("%Ensemble(""%Process"")")=%Ensemble("%Process") TESTING>zw ^zmm ^zmm("$this")="Demo.DTL.ChainTest1" ^zmm("%Ensemble(""%Process"")")="7@EnsLib.HL7.MsgRouter.RoutingEngine"
go to post Marc Mundt · Jan 15, 2021 No worries, it's always hard to understand from a forum post how far along someone is with their project. Have you been given any sample XML files that adhere to the schema? If so, you can just copy the XML into the test tool window. If you do this, does it work? One other question: what version of Ensemble or HealthShare are you using?
go to post Marc Mundt · Jan 15, 2021 It looks like the ENSDEMO namespace doesn't have an example for XML v-docs. The basic steps are:- Import an XSD (XML schema) for the document format you need to work with:https://docs.intersystems.com/healthconnectlatest/csp/docbook/Doc.View.c...- In your DTL, select XML as the Source Type and for Source Document Type select the schema that you just imported- The DTL editor will use the imported schema to display a document structure that you can use to visually build your mappingsAt this point you can paste into the testing tool a sample XML that follows the XSD. If you just want to do a quick test to see how this works, you can find a simple XSD online and import that. I found this sample which includes an XSD and sample XML that follows the XSD's structure:https://www.w3schools.com/XML/schema_example.asp
go to post Marc Mundt · Jan 15, 2021 That's an HL7 vdoc (EnsLib.HL7.Message) and that sample is HL7 code (though with strange delimiters). So yes, if your input message is HL7 (EnsLib.HL7.Message) then you can just paste a raw HL7 message into the testing tool. If your input message is XML (EnsLib.EDI.XML.Document) then you can just paste raw XML into the testing tool. If your input message is an EnsLib.EDI.XML.Document and the message content is HL7 there's going to be a problem :)
go to post Marc Mundt · Jan 15, 2021 That makes it easy. You can just paste raw XML into the Input Message box in the testing tool.
