I’m exploring deployment options for InterSystems IRIS in cloud environments such as AWS or Azure.

What deployment architectures, scaling strategies, or infrastructure best practices are commonly recommended by the community? I’d also appreciate guidance regarding high availability, backups, and monitoring in cloud-based deployments.

 What logging and auditing strategies are commonly recommended for InterSystems IRIS environments?

I’m interested in learning about best practices for tracking user activity, troubleshooting issues, monitoring integrations, and maintaining compliance in enterprise or healthcare systems.

Are there built-in tools or external integrations that work especially well for this purpose?

Hi Community!

It's time to celebrate our 18 fellow members who took part in the latest InterSystems Technical Article Contest and wrote

🌟 21 AMAZING ARTICLES 🌟

The competition brought together outstanding publications, each showcasing expertise and innovation. With so many high-quality submissions, selecting the best was a true challenge for the judges.

Let's meet the winners and look at their articles:

 I’m looking for recommendations to improve interoperability performance in InterSystems IRIS, especially when handling large volumes of HL7 or healthcare-related messages.

What are the best practices for optimizing productions, business services, operations, and message processing performance? I’d also like to know if there are recommended monitoring tools or settings commonly used in production environments.

 I’m currently working with REST APIs in InterSystems IRIS and would like to better understand the recommended security practices for production environments.

I’m especially interested in:

• Authentication and authorization methods
• Token management strategies
• Role-based access control
• API gateway recommendations
• Encryption and secure communication practices
• Monitoring and logging for API activity

I would also appreciate learning about common mistakes to avoid when deploying APIs publicly or integrating with external systems.

What approaches or tools have worked best in your environments?

I'm running a shell script and the q isn't exiting the screen. this is RHEL 7.9  I used to issue in VMS just fine but we have found that Linux scripts behave different.  after these run I search the file for the status and depending on what it comes back with it will send an email.

if someone has anything better I'm listening 

thanks

Paul

#!/bin/bash
TO_DAY=$(date +%A)
echo "Today is $TO_DAY"
#
touch /temp/CHECK_MIRROR_RPT.TXT
#
exec > /temp/CHECK_MIRROR_RPT.TXT
#
cache -U "%SYS" "Monitor^MIRROR"
q
#

#North American Demo Showcase entry. 

>> Answer the question below to be entered in the raffle!

⏯️ IRIS Agents

A Python framework for building and orchestrating AI agents on InterSystems IRIS.

🗣 Presenter: @Suprateem Banerjee, Sales Engineer at InterSystems 

 I’m looking for practical recommendations to monitor InterSystems IRIS performance in a production environment. What are the most useful built-in tools, metrics, or best practices to track system health, database performance, and possible bottlenecks?

I would also like to know if there are recommended dashboards, logs, or monitoring integrations commonly used by the community.

Hi Community,

Stay ahead with content relevant to your role and goals with the InterSystems Learning Services newsletter!

See how to customize your journey! 👇

What's the most straight-forward way to install this on an offline server? I'm trying to set this up on an Azure DevOps server to support our CI/CD pipelines. I've tried using zpm installing the tgz from the local filesystem. I note zpm seems to need a repo configured to install but I can't work out how to setup a bare-bones Filesystem repo (please point me to some documentation on this). I have no idea what I'm doing...

Abstract

Common Table Expressions (CTEs) provide a structured framework for defining reusable intermediate result sets within SQL statements. InterSystems IRIS implements CTEs via the WITH clause, enabling clearer query composition and modular analytical processing while remaining fully integrated with the IRIS cost-based optimizer.

This article explores the semantics of CTEs in InterSystems IRIS, explains their interaction with query optimization, discusses appropriate deployment scenarios, and presents executable examples illustrating practical patterns for production environments.

When building a Production, should I create separate message classes for each integration flow, or is it acceptable to reuse generic request/response classes across different Business Operations? I'm trying to understand how to keep things organized as the number of integrations grows.

What is the recommended way to handle errors inside a Business Process in IRIS? Should I use Try/Catch within the BPL, return error responses to the caller, or rely on the built-in retry mechanism of the Production? Looking for guidance on what's considered good practice.

What is the recommended approach for handling upgrades in an InterSystems IRIS Kubernetes environment?

For example, if we deploy version 1.0.0 of our product and subsequently need to upgrade to 1.0.1, and this upgrade requires changes to SQL tables containing customer data.

The quickest solution that comes to mind is creating an 'upgrade method' that runs on startup to check if any data migration actions are required. However, I'm wondering if there are better solutions or established best practices for this.

Thanks in advance!

Hey Community,

Here are the bonuses for participants' articles that take part in the InterSystems Technical Article Contest 2026:

Hello Community,  

What is the most efficient, memory-safe way to get the names of the corrupted indexes on very large tables for a rebuild. However, if an index has millions of corrupted rows, the .errors array in %ValidateIndices grows too large and throws a errorerror.

I recently started using Cursor/VSCode with an IRIS container for development rather than Studio/Terminal.  
I've noticed that whenever I use %G (so basically all the time), when I exit %G, the terminal window simply closes, rather than returning me to my usual namespace prompt.  
%G also does not retain the command stack like it does in old school terminal, so I'm forced to constantly retype every global reference.  
Anyone figured out a solution to this?  It's a relatively minor problem in the grand scheme of things, but a time consuming and irritating one.  
 

When developing Python applications with InterSystems IRIS, you can quickly end up with several execution contexts:

• Python launched directly by IRIS with Embedded Python;
• a regular python3 process that loads the Embedded Python libraries from a local IRIS installation;
• an external Python application that connects to IRIS through the official native driver.

These three cases are useful, but they do not behave exactly the same way for imports, system configuration, object APIs, and SQL access.

Redoc is an Open Source solution capable of rendering API specifications in OpenAPI 2.0 or 3.0+ as very beautiful and functional web portals. Currently, to have something similar, we need the ZPM SwaggerUI extension or we need to install IAM - InterSystems API Manager and then configure the IAM Developer Portal. Well, now the community has one more option, iris-redoc. This solution installs a web application on your IRIS instance that uses Redoc to present a beautiful web portal for your REST APIs:

For those who learned Caché ObjectScript from scratch: what kind of personal or practice projects did you build to get comfortable with the language? I come from a C# background and I'm looking for project ideas that are small enough to be feasible but meaningful enough to actually teach the core COS concepts.

Hello Community!

We’re excited to invite you to our upcoming Hebrew webinar, presented by @Keren Skubach, an InterSystems Senior Sales Engineer:

👉A Practical Guide to Leveraging AWS Adapters and APIs 👈

📅 Date & time: June 2nd, 3:00 PM IDT

Discover how to accelerate cloud-based integration with InterSystems' native AWS adapters for S3, SQS, SNS, and CloudWatch.

This session provides a practical look at building modern interoperability workflows — from secure file ingestion and asynchronous messaging to automated notifications and centralized monitoring.

Recently, a question on the Community was asked by @Vermon Ferre about storing data from inherited classes in different globals. So, I decided to simulate the following behavior: I created a superclass called Article.MainClass and two subclasses, Article.Class1 and Article.Class2. By default, when each class extends %Persistent IRIS creates independent storage structures for them. This will work as intended if the first class in the list of superclasses is %Persistent. But it also means that if there are any parameters in the main class, they will be lost, because only parameters from the first class in the list get inherited.

IRIS 2026.1 provided Partitioned Tables as a new option for large data sets
It's a great improvement as it offers standardization of this feature.

Though:
It was possible also before, matching requirements and leaving room for creativity.
less elegant with a bit more coding and fewer automatisms.

Hi Community!

Welcome to Issue #29 of the InterSystems Ideas newsletter! Let's look at the latest news from the Ideas Portal, such as:

✓ General Statistics
✓ Results of the sweepstakes asking for topics for tutorials
✓ New Community Bounty Program "Idea to Application"

Hi Community!

We are excited to announce that the Hospitals On FHIR Meetup will take place during SantExpo 2026!

📅 Date: May 20, 2026, starting at 6:30 PM CEST

📌 Location: HIFE Paris Issy, 15 Rue Guynemer, 92130 Issy-les-Moulineaux, France

Welcome to another installment of the Platforms Update. A few notables to highlight:

• Ubuntu 26.04 has been released, and corresponding IRIS support is coming soon.
• IRIS 2026.2 will bring an end to support for Ubuntu 22.04 and Windows 10.
• Revised minimum CPU specifications are in effect for 2025.3+

For those newly acquainted with these communications, this update provides details about recent enhancements as well as anticipated changes based on current information; however, future projections remain uncertain and the content should not be interpreted as a definitive product roadmap.

1. VS Code version 1.60.0 and above

2. install below 3 extensions

   

3. Ctrl + Shift + P show all commands

4. InterSystems: Connect to Server

5. input connection details 

   IP：localhost

        Port: 52773

       choose global & http connection method

       Input username and password of Intersystems management portal

       screenshot for success connection:

At READY 2026, for the very first time, we held a customer hackathon — and it was an amazing experience!
The hackathon took place on the pre-event day at 9 am. Some participants, like me, arrived early due to jet lag—but that actually helped us connect with fellow hackers before the event kicked off.
 

The Beginning