I am trying to troubleshoot an issue I am having with the JDBC Gateway Server crashing at the %SYS level. I have numerous Linked Tables that are using JDBC to connect to a MS SQL database/tables to query values. I have written queries in other class files and within the class definition of the linked table to do the queries.

1. Should I be running the query in the class definition of the linked table as a class method? or is it best practice to run the query as a class method outside of the class definition of the linked table?

I was attempting to test a Linked JDBC View to MS SQL database and noticed I could not connect. When I look at the JDBC Gateway I noticed that at the Server Level it was down. However the page keeps timing out when ever I attempt to make any changes or start it, it will not respond.

I thought I had found the Cache command to start it but it will not start. Is the following steps correct?

I am trying to pull down the webgateway from containers.intersystems.com and I am receiving the following errors... Please advise

Note sure if anyone would know this.... But I presented my team with a Proof of Concept of running SAM to monitor our IRIS Development and Test Clusters. In talking with them we would like additional OS metrics that aren't provided by what is built into SAM. Looking at more OS detail I found node_exporter from Promethus. I added node_exporter to our server that we want to monitor, but then tried to config isc_prometheus.yml to use node_exporter. That did not go well and when I restarted SAM, it would not download the built in metrics to SAM.

Now that I have SAM up and running, out of the box I would like to add some Application Metrics. Does anyone have templates, or have suggested classes that someone could use to add custom metrics to SAM? Maybe we should start a repository somewhere? Or would someone be willing to share custom metrics on the Open Exchange?

What I am looking to do is capture the overall HL7 message and header count per day.

I am starting to look at add-ons/enhancements that can be made to our environment as we move from 2018.1.3 to IRIS 2022.1. During one of our internal meetings it was mentioned that it would be helpful to gather and keep track of metrics as we move to IRIS 2022.1. I am looking to at trying to capture Message Count, Database size, global sizes, etc... Through Global Summit, and Open exchange, I know there is SAM, Grafana, and Promethus. I am struggling with getting SAM working on a Red Hat Environment using podman and not docker, but that is another story.

I was wondering if someone could help me. I do not have docker available to me however a lot of the Open Exchange apps require it. Since I am using a Virtual Windows Machine I can not get docker installed, so I was wondering how to get around this? Someone at GS2022 suggested looking at the docker_compose.yml to figure out how to get around docker, but I am not sure I understand how to read it.

We are upgrading from Health Connect 2018.1.3 to IRIS Health Connect 2022.1, and one thing that we are particularly hesitant about is if our Business Rules will work in the new version.

I am trying to come up with a testing process for bulk testing our rules, and wanted to know if this could be done programmatically instead of having to modify all the Business Operations to have them write the HL7 data to a file. I caught Orlando Health's presentation at GS2022 but I am not sure that will work for my team.

I noticed today that when we are creating a message from one doc type to another doc type, that the message type categories are not necessarily set. This is causing some issues with routing rules when we try to reference the Message Type Categories. Is there a way to make sure the Message Type Categories are being set within a DTL to make sure this doesn't cause problems down the road?

Thanks

Scott