go to post Deepak Ghansala · Sep 5 Probably you can have your document limit listed in a lookup table to begin with, lets say Limit = 100 to begin with. Then within your business process, add an if-else section, where the test condition is to evaluate current time against the XXXX and YYYY times you have in mind. If the current time is within your XXXX and YYYY, plus the limit is > 0 from the lookup table, you send the document and decrease the lookup table value by 1. On the else condition, you just send the document without checking the limit value from the table, but update the lookup table again to your limit (100). The key here is accessing and updating the lookup table value from within your business process. Hope this makes sense.
go to post Deepak Ghansala · Apr 12 You can create a custom schema based on the current schema you have listed in your business service that reads the file. Once you have the custom schema, if its a specific ADT message you need the NTE segment on, then can create that message type from the base schema and edit the Doc Type Structure by putting ~[NTE] at the end of the raw structure.
go to post Deepak Ghansala · Feb 22 Hi Heorhiy, Your error message talks about the TLS configuration with name "HTTPSCert" in use, however the screenshot lists TLS configuration name as "TSL". Can you check your operation is using this "TSL" config. Regards, Deepak
go to post Deepak Ghansala · Oct 16, 2023 Hi Scott, So rather than having one centralised location for webserver and web gateway, which could become your single point of failure, you install the webserver and web gateway alongside Healthconnect on the actual instances. And when you configure the individual web gateway, for telling it which instance of HealthConnect it needs to connect, just specify it as localhost and your superserver port on that instance. https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls... https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls... https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls... When you give the server access parameters, enter IP Address as localhost (127.0.0.1) and port as your superserver port of the instance and do not check "Configuration is Mirror Aware". Regards, Deepak
go to post Deepak Ghansala · Nov 24, 2022 Hi Warren, We also have a similar situation, this not limited to FTP adapter, it is there on Email and SQL adapter as well, where you don't get an option on the config to choose the local interface (VIP in this). I think the short term solution we have been suggested from Intersystems is to allow both your mirror member IP addresses through the firewall, yet to test it though how it will play out with NAT. Probably, Intersystems will come up with a solution maybe in next couple of months to support this configuration of local interface natively on the adapter classes. Thanks, Deepak Ghansala
go to post Deepak Ghansala · Oct 6, 2022 Refer to this documentation https://docs.intersystems.com/iris20201/csp/docbook/DocBook.UI.Page.cls?...
go to post Deepak Ghansala · Aug 5, 2022 I think IRIS uses Apache httpd as its webserver, so probably go through this first. https://community.intersystems.com/post/apache-httpd-web-server-configur... And this link to figure out how to enable https on a certain port in httpd https://www.ibm.com/docs/en/aspera-on-demand/3.9?topic=appendix-enable-s... Probably should also think around performance and scalability of httpd and raise a call with WRC for their opinion on this. Regards, Deepak Ghansala
go to post Deepak Ghansala · Dec 3, 2021 Can you compare the certificate chain between your local system and the cache instance ? It could be possible your local instance trusts the root CA in the certificate chain but the server where cache instance is doesn't.
