go to post Marc Mundt · Jan 3, 2020 Have you considered using web services to exchange messages between the productions? This has the advantage of allowing the two productions to later be placed on separate instances. If you want to do it through the mapped DB, you could write a custom business operation to store the records in a custom table which is mapped to from both namespaces and then write a custom business service that polls that table for new entries. I have 2 productions A and B on the same IRIS instance sharing one operational database. To be sure the two productions aren't conflicting with each other, I'm assuming that only custom tables/globals are mapped to the shared database and not any of the Ens* globals/tables/routines/packages.
go to post Marc Mundt · Jan 3, 2020 The error is complaining that the message doesn't have a doctype category. In the message trace for this test message, under "Body", what is the value of the "DocType" field?
go to post Marc Mundt · Jan 2, 2020 Are these standard HL7 batch headers and footers (BHS/BTS, FHS/FTS, etc) or something custom to your organization? If they are one of the HL7 standards, have a look at these docs on HL7 batches:https://docs.intersystems.com/healthconnect20191/csp/docbook/Doc.View.cl... One tricky part will be triggering when an old batch ends/new batch begins -- this will depend on your local requirements. If they are custom, there are a few approaches you can consider: You could use the Record Mapper to define a record map class with header/footer and a single field record for the HL7 content. You would then use one of the EnsLib.RecordMap.Operation.* classes instead of EnsLib.HL7.Operation.FileOperation: https://docs.intersystems.com/healthconnect20191/csp/docbook/DocBook.UI.... In particular, have a look at RolloverSchedule and/or RolloverLimit to control when a new batch file is created. If you're comfortable creating a custom class that extends EnsLib.HL7.Operation.FileOperation, you could override the outputDocument method. In your custom version of outputDocument you could check if the file already exists using ##class(%File).Exists(pathToFile) and if it doesn't you would write out the footer to the previous file and the header to the new file before calling the standard version of outputDocument using ##super. https://docs.intersystems.com/healthconnect20191/csp/docbook/Doc.View.cl...
go to post Marc Mundt · Jan 2, 2020 A few questions: You didn't mention what format these files are in -- XML? flat-file/CSV? Something else? Which InterSystems product are you working with and what kind of application is this (interoperability production, web service, etc.)? If these are flat-files or CSV, and if you're working with a Health Connect or IRIS interoperability production, you can look at using the Record Mapper, which will read a flat file using a format you define and allow you to work with records from the file as objects:https://docs.intersystems.com/healthconnect20191/csp/docbook/DocBook.UI.... If the files are XML you can do something similar by importing an XSD and using XML virtual documents, or use %XML.Adaptor methods:https://docs.intersystems.com/healthconnect20191/csp/docbook/DocBook.UI....
go to post Marc Mundt · Dec 18, 2019 The ConfirmComplete setting in EnsLib.File.PassthroughService allows you to specify how the service decides if a file is complete before picking it up.
go to post Marc Mundt · Dec 4, 2019 Or something uglier... set tDefined=$ISOBJECT(##class(Ens.Config.Production).%OpenId(##class(Ens.Director).GetActiveProductionName()).FindItemByConfigName(tHostName))
go to post Marc Mundt · Dec 4, 2019 How about: &sql(select count(*) into :tDefined from ENS_Config.Item where Name=:tHostName and Production=:tProductionName)
go to post Marc Mundt · Oct 22, 2019 From a custom ObjectScript Business Process, you would use ..SendRequestSync or ..SendRequestAsync to make calls to other components. These will do the same thing as <CALL> in a BPL.
go to post Marc Mundt · Oct 21, 2019 Ok, EnsLib.REST.GenericOperation also expects to receive an EnsLib.HTTP.GenericMessage. Are you using EnsLib.File.PassthroughService to pick up the files? If so, it is sending an Ens.StreamContainer message to the target component (your business operation). You'll need to create a data transformation that creates a new EnsLib.HTTP.GenericMessage and populates it with the stream content from the Ens.StreamContainer. Then you'll need a router in the middle to run the data transformation and send the resulting EnsLib.HTTP.GenericMessage to the business operation.
go to post Marc Mundt · Oct 21, 2019 What type of object is your business process sending to your business operation? EnsLib.HTTP.GenericOperation expects to receive a message of type EnsLib.HTTP.GenericMessage.
go to post Marc Mundt · Oct 21, 2019 Thanks Anton. Maybe I didn't dig deep enough in that github link but it looks like that is for AWS, not Azure?
go to post Marc Mundt · Oct 21, 2019 Neerav, I'll just note that if you use Jenna's suggestion your code doesn't need to be a part of a business service -- it can be any normal ObjectScript code and can be called from anywhere (CSP, scheduled task, etc.). And your code can make as many calls as it needs to and can receive response messages. It will appear in message traces as if a business service sent requests to the process or operation, but in reality it's just your code sending the requests. Jenna's approach is a good one, and it's the standard way to achieve what you describe. Having said that, if you can provide more details on your use case and/or why this approach doesn't fit your need we can help you explore alternatives.
go to post Marc Mundt · Oct 18, 2019 Just wondering if anyone has put together similar examples for Azure -- preferably for uploading Azure Blobs.
go to post Marc Mundt · Oct 10, 2019 Agreed, if it's a simple protocol like ASTM that would be a better option. I was assuming that the device is using something complex like SCSI-over-USB like scanners do, or some proprietary protocol based on USB bulk transfers -- something that requires a driver on the PC.
go to post Marc Mundt · Oct 10, 2019 My understanding is that the Caché application is terminal based (accessed on the client PC through telnet). The signature device connects to the client PC using USB. So the question/challenge is for the terminal-based application to send a request to the signature device when a signature is needed and to receive the signature image. Seems like you need a daemon running on the PC which uses the signature device's SDK to communicate with it. The daemon would then exchange messages with Caché to manage the signature process -- possibly via web services or web sockets.
go to post Marc Mundt · Oct 9, 2019 I would double-check that a TargetConfig in the new service is set to the correct router. After that, I'd check the event log and see if there are any errors logged.
go to post Marc Mundt · Oct 9, 2019 Which business service are you using to read the file? Are you using EnsLib.RecordMap.Service.FileService and specifying the record map type in the configuration? It sounds like you might be using EnsLib.File.PassthroughService
go to post Marc Mundt · Sep 12, 2019 Just wanted to point out that concatenating columns in the where clause will mean the DB will be forced to look at every single row, which will mean slow performance if you have a large number of rows. It won't be able to use the indices on FirstName or LastName to improve performance.Can you just check against FirstName and LastName directly?
go to post Marc Mundt · Sep 5, 2019 There is a simple explanation!Your output will have two columns named Category, because you've specified it explicitly and it's also included in "*". So the query engine doesn't know which of these two columns you're asking to sort by.Either remove the explicit specification for Category, or give it a unique name:select category as Category2 ...
go to post Marc Mundt · Sep 4, 2019 You could use Apache's mod_rewrite to take all requests that fall under a certain sub-path and transform them on the fly to point to your CSP page. It could add the information about which specific page/resource was requested as a URL parameter that could be accessed by your CSP page.For example, if a client makes a request for:http://myserver/reporting/Dashboard1/resource2.jsmod_rewrite could change it to:http://myserver/csp/dashboards/proxy.csp?targetResource=Dashboard1/resou...After mod_rewrite changes the URL in the request, Apache continues processing it as usual using the new URL. Since the new URL refers to a CSP page Apache will pass it to CSP Gateway as we want.
