9 4
1 477
Article
· Jan 25, 2016 1m read
2016.2 Field Test

I am pleased to announce the field test of Caché and Ensemble 2016.2 - an exciting new release with improvements on many different fronts.

The entire product team at InterSystems looks forward to your participation in the field test and feedback over the coming months.

Some of the more profound changes in 2016.2 include:

6 6
0 1.2K

Hello everyone,

My team lead mentioned that users can sometimes create globals directly without associating them with tables or classes. In this case, these globals would not be accessible via SQL.

Is this correct? Can a global exist independently in this way, and if so, is there a specific approach to access or manage them without SQL?

1 9
0 105

Who hasn't been developing a beautiful example using a Docker IRIS image and had the image generation process fail in the Dockerfile because the license under which the image was created doesn't contain certain privileges?

In my case, what I was deploying in Docker is a small application that uses the Vector data type. With the Community version, this isn't a problem because it already includes Vector Search and vector storage. However, when I changed the IRIS image to a conventional IRIS (the latest-cd), I found that when I built the image, including the classes it had generated, it returned this error:

14 6
1 327

The third developer previews of InterSystems IRIS® data platform, InterSystems IRIS® for Health, and HealthShare® Health Connect 2026.1 have been posted to the WRC developer preview site. Containers can be found on our

1 1
0 38

Hey Community!

We're happy to share a new video from our InterSystems Developers YouTube:

Taking the Fear out of FHIR - Fast Tracking Organizational FHIR Readiness @ Ready 2025

https://www.youtube.com/embed/TLWXlDCpU84
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

1 0
0 9

cover

In Part 1, we laid the technical foundation of MAIS (Multi-Agent Interoperability Systems). We have successfully wired up the 'Brain', built a robust Adapter using LiteLLM, locked down our API keys with IRIS Credentials, and finally cracked the trick code on the Python interoperability puzzle.

2 0
0 9

France & Benelux READY 2026 has just come to an end, and once again, these two days demonstrated how dynamic, curious, and engaged the Developer Community truly is. Here is a look back in words and images at this great edition.

The event kicked off with welcome remarks from @Adeline Icard and @Geoffroy Vitoux, setting the tone for the days ahead: innovation, sharing, and collaboration.

3 0
0 10
Article
· 21 hr ago 11m read
IKO Plus: HSSYS Mirroring with IKO

Enabling HSSYS Mirroring Out of the Gate with IKO

For those of us building InterSystems workloads on Kubernetes, we are definitely spoiled with the InterSystems Kubernetes Operator (IKO) doing the heavy lifting and mirroring on day one. Where us spoiled brats jump up and down is when we try to add additional databases/namespaces when we provision from HealthConnect containers on day two, while others get to utilize HealthShare Mirroring for this task, the prerequisite of mirroring HSSYS out of the gate has been somewhat elusive. Here is example on how you can this powerful feature up and running with the employment of IKO and IrisClusters.

2 0
0 9

Hi everyone,

Does anyone know how to export projects via VSC?

I opened the project through the "InterSystems Tools" plugin (command is "Edit Code in Project") and I can correctly work on it.

However, when I try using the "ObjectScript" plugin to export the project (right click on the project -> "Export Project Contents")

This message appears and it is not possible to export the project:

0 14
0 3.2K

Hi Community,

We’re excited to invite you to take part in shaping the next generation of ObjectScript development tools. We’re working on an AI-powered ObjectScript coding assistant designed specifically for IRIS developers. Not a generic AI adapted for ObjectScript, but a solution built from the ground up to understand ObjectScript idioms, IRIS APIs, interoperability productions, and real-world developer workflows.

To make sure we build something truly useful, we need your input.

👉 ObjectScript Coder Agent Developer Survey 👈

13 15
2 247

As applications grow, every database eventually hits scaling limits. Whether it's storage capacity, concurrent users, query throughput, or I/O bandwidth, single-server architectures have inherent constraints. This guide explains fundamental approaches to database scalability and shows how InterSystems IRIS implements these patterns to support enterprise-scale workloads.

We'll explore two complementary scaling strategies: horizontal scaling for user volume (distributing computational load) and sharding for data volume (partitioning datasets). Understanding the general principles behind these approaches will help you make informed decisions about when and how to scale your IRIS applications.

The examples in this guide use InterSystems IRIS in Docker containers.

10 4
4 157

Hi Community! 👋

As 2026 gets underway, we’d love to hear what you’re focusing on this year.

This discussion is a space to share your resolutions, goals, and focus areas for 2026 - technical, professional or community-related.

These don’t have to be traditional New Year’s resolutions. Think of them as intentions or priorities you’d like to work on this year.

💬 What you can share

4 9
0 151

Here are the technology bonuses for the InterSystems Full Stack Contest 2026, which will give you extra points in the voting:

  • IRIS Vector Search usage -3
  • InterSystems Native SDK for Python or Embedded Python usage -3
  • Developer Community Idea implemented - 2
  • Docker container usage -2
  • IPM Package Deployment - 2
  • Online Demo -2
  • Find and report a bug - 2
  • Article on Developer Community - 2
  • The second article on Developer Community - 1
  • Video on YouTube - 3
  • YouTube Short - 1
  • First Time Contribution - 3

See the details below.<--break->

0 0
0 25

I've modified the class file, but messages still arrive as a single line (e.g., "H|.../rQ|.../rL") instead of separate lines in the ASTM service. The <ENQ>..<EOT> header looks correct, logs show no errors, and the service receives messages fine. Is there an Ensemble 2018.1 engine setting (like line terminator handling or TCP framing) to fix the line splitting? ​

1 4
0 54