Search

This document describes considerations around SDDC and HCI solutions for InterSystems Clients.Software Defined Data Centers (SDDC) and Hyper-Converged Infrastructure (HCI) – Important Considerations for InterSystems ClientsA growing number of IT organizations are exploring the potential use of SDDC and HCI solutions. These solutions appear attractive and are marketed as simplification of IT management and potential cost reductions across heterogeneous data centers and cloud infrastructure options. The potential benefits to IT organizations are significant, and many InterSystems clients are embracing SDDC, HCI, or both.If you are considering SDDC or HCI solutions, please contact your Sales Account Manager or Sales Engineer to schedule a call with a Technical Architect. This is important to ensure your success.These solutions are highly configurable, and organizations can choose from many permutations of software and hardware components. We have seen our clients use a variety of SDDC and HCI solutions, and through those experiences we have realized that it is important to carefully consider solution configurations to avoid risk. In several cases, there have been clients whose implementations did not match the performance and resiliency capabilities required for mission-critical transactional database systems. This resulted in poor application performance and unexpected downtime. Where the goal is to provide mission-critical transactional database systems with high resiliency and consistently low-latency storage performance, component selection and configuration requires careful consideration and planning for your situation, including:Selecting the right componentsProperly configuring those componentsEstablishing appropriate operational practicesSDDC and HCI offer flexibility and ease of management and they operate within or alongside the hypervisor layer between the operating system and the physical storage layers. This adds varying degrees of overhead. When misconfigured, this can radically affect disk latency – which is disastrous for performance of applications.Design Considerations for InterSystems IRIS, Caché, and EnsembleThe following list of minimum requirements and design considerations is based on our internal testing of SDDC and HCI solutions. Note that this is not a reference architecture, which means that your application-specific requirements will depend on your situation and performance targets.NetworkingTwo or more 10Gb NIC interfaces per node that are dedicated for the exclusive use of storage traffic.Two local non-blocking line-rate 10Gb switches for switch connectivity resiliency.As an option, 25, 40, 50, or 100Gb instead of 10Gb for future-proofing investment in HCI and the specific benchmarked and measured application requirements.ComputingAt least a six-node cluster for higher resiliency and predictable performance during maintenance and failure scenarios.Intel Scalable Gold or Platinum processors or later, at 2.2Ghz or higher.Installing RAM in groups of 6 x DDR4-2666 DIMMs per CPU socket (384GB minimum).StorageAll-flash storage. This is the only recommended option for storage. InterSystems strongly recommends against hybrid or tiered HCI storage for production workloads.Minimum of two disk groups per physical node. Each disk group should support at least three capacity drives.Exclusive use of write-intensive 12Gbps SAS SSDs or NVMe SSDs.For all-flash solutions with cache and capacity tiers, it is recommended to use NVMe for the cache tier and write-intensive 12Gbps SAS for the capacity tier.Use of LVM PE striping with Linux virtual machines, which spreads IO across multiple disk groups (contact InterSystems for guidance).Use of the Async IO with the rtkaio library for all databases and write image journal (WIJ) files with Linux virtual machines. This bypasses file-system caching and reduces write latency (see the documentation or contact the WRC for assistance with properly enabling Async IO on Linux).These minimum recommendations have shown to alleviate the overhead of SDDC and HCI but do not ensure application performance. As with any new technology, testing of your own application for performance and resiliency is paramount to any successful deployment.So again, If you are considering SDDC or HCI solutions, please contact your Sales Account Manager or Sales Engineer to schedule a call with a Technical Architect. This is important to ensure your success.

In this series of articles, I'd like to present and discuss several possible approaches toward software development with InterSystems technologies and GitLab. I will cover such topics as:Git 101Git flow (development process)GitLab installationGitLab WorkflowContinuous DeliveryGitLab installation and configurationGitLab CI/CDWhy containers?Containers infrastructureCD using containersCD using ICMIn this article, we'll build Continuous Delivery with InterSystems Cloud Manager. ICM is a cloud provisioning and deployment solution for applications based on InterSystems IRIS. It allows you to define the desired deployment configuration and ICM would provision it automatically. For more information take a look at First Look: ICM.WorkflowIn our Continuous Delivery configuration we would:Push code into GitLab repositoryBuild docker imagePublish image to docker registryTest it on a test serverIf tests pass, deploy on a production serverOr in graphical format:As you can see it's all pretty much the same except we would be using ICM instead of managing Docker containers manually.ICM configurationBefore we can start upgrading containers, they should be provisioned. For that we need to define defaults.json and definitions.json, describing our architecture. I'll provide these 2 files for a LIVE server, definitions for a TEST server are the same, defaults are the same except for Tag and SystemMode values.defaults.json: { "Provider": "GCP", "Label": "gsdemo2", "Tag": "LIVE", "SystemMode": "LIVE", "DataVolumeSize": "10", "SSHUser": "sample", "SSHPublicKey": "/icmdata/ssh/insecure.pub", "SSHPrivateKey": "/icmdata/ssh/insecure", "DockerImage": "eduard93/icmdemo:master", "DockerUsername": "eduard93", "DockerPassword": "...", "TLSKeyDir": "/icmdata/tls", "Credentials": "/icmdata/gcp.json", "Project": "elebedyu-test", "MachineType": "n1-standard-1", "Region": "us-east1", "Zone": "us-east1-b", "Image": "rhel-cloud/rhel-7-v20170719", "ISCPassword": "SYS", "Mirror": "false" } definitions.json [ { "Role": "DM", "Count": "1", "ISCLicense": "/icmdata/iris.key" } ] Inside the ICM container /icmdata folder is mounted from the host and: TEST server definitions are placed in /icmdata/test folderLIVE server definitions are placed in /icmdata/live folder After obtaining all required keys: keygenSSH.sh /icmdata/ssh keygenTLS.sh /icmdata/tls And placing required files in /icmdata: iris.keygcp.json (for deployment to Google Cloud Platform) Call ICM to provision your instances: cd /icmdata/test icm provision icm run cd /icmdata/live icm provision icm run This would provision one TEST and one LIVE server with one standalone InterSystems IRIS instance on each. Please refer to ICM First Look for a more detailed guide. Build First, we need to build our image. Our code would be, as usual, stored in the repository, CD configuration in gitlab-ci.yml but in addition (to increase security) we would store several server-specific files on a build server. iris.key License key. Alternatively, it can be downloaded during container build rather than stored on a server. It's rather insecure to store in the repository. pwd.txt File containing default password. Again, it's rather insecure to store it in the repository. Also, if you're hosting prod environment on a separate server it could have a different default password. load_ci_icm.script Initial script, it: Loads installerInstaller does application initializationLoads the code set dir = ##class(%File).NormalizeDirectory($system.Util.GetEnviron("CI_PROJECT_DIR")) do ##class(%SYSTEM.OBJ).Load(dir _ "Installer/Global.cls","cdk") do ##class(Installer.Global).init() halt Note that the first line is intentionally left empty. Several things are different from previous examples. First of all we are not enabling OS Authentication as ICM would interact with container instead of GitLab directly. Second of all I'm using Installer manifest to initialize our application to show different approaches to initialization. Read more on Installer in this article. Finally we'll publish our image in a Docher Hub as a private repo. Installer/Global.cls Our installer manifest looks like this: <Manifest> <Log Text="Creating namespace ${Namespace}" Level="0"/> <Namespace Name="${Namespace}" Create="yes" Code="${Namespace}" Ensemble="" Data="IRISTEMP"> <Configuration> <Database Name="${Namespace}" Dir="${MGRDIR}/${Namespace}" Create="yes" MountRequired="true" Resource="%DB_${Namespace}" PublicPermissions="RW" MountAtStartup="true"/> </Configuration> <Import File="${Dir}MyApp" Recurse="1" Flags="cdk" IgnoreErrors="1" /> </Namespace> <Log Text="Mapping to USER" Level="0"/> <Namespace Name="USER" Create="no" Code="USER" Data="USER" Ensemble="0"> <Configuration> <Log Text="Mapping MyApp package to USER namespace" Level="0"/> <ClassMapping From="${Namespace}" Package="MyApp"/> </Configuration> <CSPApplication Url="/" Directory="${Dir}client" AuthenticationMethods="64" IsNamespaceDefault="false" Grant="%ALL" /> <CSPApplication Url="/myApp" Directory="${Dir}" AuthenticationMethods="64" IsNamespaceDefault="false" Grant="%ALL" /> </Namespace> </Manifest> And it implements the following changes: Creates application Namespace.Creates application code database (data would be stored in USER database).loads code into application code database.Maps MyApp package to USER namespace.Creates 2 web applications: for HTML and for REST. gitlab-ci.yml Now, to Continuous Delivery configuration: build image: stage: build tags: - master script: - cp -r /InterSystems/mount ci - cd ci - echo 'SuperUser' | cat - pwd.txt load_ci_icm.script > temp.txt - mv temp.txt load_ci.script - cd .. - docker build --build-arg CI_PROJECT_DIR=$CI_PROJECT_DIR -t eduard93/icmdemo:$CI_COMMIT_REF_NAME . What is going on here? First of all, as docker build can access only subdirectories of a base build directory - in our case repository root, we need to copy our "secret" directory (the one with iris.key, pwd.txt and load_ci_icm.script) into the cloned repository. Next, first terminal access requires a user/pass so we'd add them to load_ci.script (that's what empty line at the beginning of load_ci.script is for btw). Finally, we build docker image and tag it appropriately: eduard93/icmdemo:$CI_COMMIT_REF_NAME where $CI_COMMIT_REF_NAME is the name of a current branch. Note that the first part of the image tag should be named same as project name in GitLab, so it could be seen in GitLab Registry tab (instructions on tagging are available in Registry tab). Dockerfile Building a docker image is done using Dockerfile, here it is: FROM intersystems/iris:2018.1.1-released ENV SRC_DIR=/tmp/src ENV CI_DIR=$SRC_DIR/ci ENV CI_PROJECT_DIR=$SRC_DIR COPY ./ $SRC_DIR RUN cp $CI_DIR/iris.key $ISC_PACKAGE_INSTALLDIR/mgr/ \ && cp $CI_DIR/GitLab.xml $ISC_PACKAGE_INSTALLDIR/mgr/ \ && $ISC_PACKAGE_INSTALLDIR/dev/Cloud/ICM/changePassword.sh $CI_DIR/pwd.txt \ && iris start $ISC_PACKAGE_INSTANCENAME \ && irissession $ISC_PACKAGE_INSTANCENAME -U%SYS < $CI_DIR/load_ci.script \ && iris stop $ISC_PACKAGE_INSTANCENAME quietly We start from the basic iris container. First of all, we copy our repository (and "secret" directory) inside the container. Next, we copy license key to mgr directory. Then we change the password to the value from pwd.txt. Note that pwd.txt is deleted in this operation. After that, the instance is started and load_ci.script is executed. Finally, iris instance is stopped. Note that I'm using GitLab Shell executor and not Docker executor. Docker executor is used when you need something from inside of the image, for example, you're building an Android application in java container and you only need an apk. In our case, we need a whole container and for that, we need Shell executor. So we're running Docker commands via GitLab Shell executor. Publish Now, let's publish our image in a Docker Hub publish image: stage: publish tags: - master script: - docker login -u eduard93 -p ${DOCKERPASSWORD} - docker push eduard93/icmdemo:$CI_COMMIT_REF_NAME Note ${DOCKERPASSWORD} variable, it's a GitLab secret variable. We can add them in GitLab > Project > Settings > CI/CD > Variables: Job logs also do not contain password value: Running with gitlab-runner 10.6.0 (a3543a27) on icm 82634fd1 Using Shell executor... Running on docker... Fetching changes... Removing ci/ HEAD is now at 8e24591 Add deploy to LIVE Checking out 8e245910 as master... Skipping Git submodules setup $ docker login -u eduard93 -p ${DOCKERPASSWORD} WARNING! Using --password via the CLI is insecure. Use --password-stdin. Login Succeeded $ docker push eduard93/icmdemo:$CI_COMMIT_REF_NAME The push refers to repository [docker.io/eduard93/icmdemo] master: digest: sha256:d1612811c11154e77c84f0c08a564a3edeb7ddbbd9b7acb80754fda97f95d101 size: 2620 Job succeeded and on Docker Hub we can see our new image: Run We have our image, next let's run it on our test server. Here is the script. run image: stage: run environment: name: $CI_COMMIT_REF_NAME tags: - master script: - docker exec icm sh -c "cd /icmdata/test && icm upgrade -image eduard93/icmdemo:$CI_COMMIT_REF_NAME" With ICM we need to run only one command (icm upgrade) to upgrade existing deployment. We're calling it by running "docker exec icm sh -c " which executes a specified command inside the icm container. First we mode into /icmdata/test where our ICM deployment definition is defined for a TEST server. After that we call icm upgrade to replace currently existing container with a new container. Test Let's run some tests. test image: stage: test tags: - master script: - docker exec icm sh -c "cd /icmdata/test && icm session -namespace USER -command 'do \$classmethod(\"%UnitTest.Manager\",\"RunTest\",\"MyApp/Tests\",\"/nodelete\")' | tee /dev/stderr | grep 'All PASSED' && exit 0 || exit 1" Again, we're executing one command inside our icm container. icm session executes a command on a deployed node. The command runs unit tests. After that it pipes all output to the screen and also to grep to find Unit Tests results and exit the process successfully or with an error. Deploy Deploy on a Production server is absolutely the same as deploy on test, except for another directory for the LIVE deployment definition. In the case where tests failed this stage would not be executed. deploy image: stage: deploy environment: name: $CI_COMMIT_REF_NAME tags: - master script: - docker exec icm sh -c "cd /icmdata/live && icm upgrade -image eduard93/icmdemo:$CI_COMMIT_REF_NAME" Conclusion ICM gives you a simple, intuitive way to provision cloud infrastructure and deploy services on it, helping you get into the cloud now without major development or retooling. The benefits of infrastructure as code (IaC) and containerized deployment make it easy to deploy InterSystems IRIS-based applications on public cloud platforms such as Google, Amazon, and Azure, or on your private VMware vSphere cloud. Define what you want, issue a few commands, and ICM does the rest. Even if you are already using cloud infrastructure, containers, or both, ICM dramatically reduces the time and effort required to provision and deploy your application by automating numerous otherwise manual steps. Links Code for the articleTest projectICM DocumentationFirst Look: ICM

InterSystems FAQ rubric If you restart the OS after changing the machine name without stopping InterSystems IRIS (hereinafter referred to as IRIS), a problem occurs when IRIS cannot start. To get started, delete the <installation directory>\mgr\iris.ids file. iris.ids file stores the started node name and shared memory information (shared memory ID). It is created when IRIS starts and deleted when stopped (iris stop or iris force). If you stop (restart) the OS without stopping IRIS, iris.ids, which contains IRIS startup information, may remain. IRIS checks iris.ids during the next startup process. If the machine name has been changed, IRIS will not start properly because the information on the name of the node being started is different from the contents of iris.ids. When stopping (rebooting) the OS after changing the machine name, be sure to stop IRIS in advance. To prevent unexpected problems, it is ideal to stop IRIS before stopping the OS. * The same applies to other InterSystems products.

Motivation I didn't know about ObjectScript until I started my new job. Objectscript isn't actually a young programming language. Compared to C++, Java and Python, the community isn't as active, but we're keen to make this place more vibrant, aren't we? I've noticed that some of my colleagues are finding it tricky to get their heads around the class relationships in these huge projects. There aren't any easy-to-use modern class diagram tool for ObjectScript. Related Work I have tried relavant works: - InterSystems class view:1. https://github.com/intersystems-community/ClassExplorerThis is great work, and the class diagram looks really good and clean. But there's still an issue with the docker build: "#0 0.512 exec ./irissession.sh: no such file or directory". I'm guessing it's a support feature for the studio rather than VSCode. It seems to need to import your project manually. It seems like it needs some configuration to use this product. 2. https://github.com/gjsjohnmurray/vscode-objectscript-class-viewThis is another great work which gives me inspiration. The class structure is clear and it supports not only class in project also class from library. But it looks like a enhanced version of vscode outline. - Other language VSCode class diagramm view plugins 1. https://github.com/OH318/J-DiagramThe readme shows the running results with draw.io really well. But when I tested it locally, I couldn't use it. So I won't use it as a reference. 2. https://github.com/pierre3/PlantUmlClassDiagramGeneratorIt's relative good and it requires some configuration. I took the idea of generating uml first, then use PlantUML to generate class diagram. - Best Implementation of class diagram:1. Jetbrains products, like Intellij Idea and Pycharm, are amazing for class diagrams. Just drag and drop classes, click a hyperlink, and you're all set to generate a powerful class diagram. 2. VSCode typescript class diagram pluginhttps://marketplace.visualstudio.com/items?itemName=AlexShen.classdiagram-tsdrag, drop, hyperlink click, support of folder class diagram generation. I took the design idea from them. Unfortunately, they are closed source, so I'll have to design the project on my own. InterSystems ObjectScript Class Diagram View is a Visual Studio Code extension that generates UML class diagrams from InterSystems ObjectScript (.cls) files. It provides interactive visualization and navigation features, built on PlantUML for reliable diagram rendering. Key Features Generate UML class diagrams from .cls files Support for both single class and folder-level diagram generation Right-click context menu integration in both editor and explorer Visualize class relationships, properties, and methods Built on PlantUML for reliable diagram rendering Generate diagrams using PlantUML Web Server (no Java required) Interactive Class Diagram Browsing Click on class names, properties, or methods to quickly jump to the corresponding code SVG diagrams embedded in HTML for smooth interaction Visual navigation of class relationships I tested the plugin on another great objectscript project apiPub I have offered two modes, generate class diagram based on parse local file system of the project or with iris integration. Generating Class Diagrams This mode parse class structure from local project, the inheritance structure of library class wont be generated and library class cannot be clicked to enter. For a single class: For a folder: For the whole project. The class diagram is in SVG format, and it's always sharp and clear. Generate Class Diagram with IRIS Integration This feature is dependent on InterSystems plugins and it will generate all the class properties, parameters and methods from the chosen class. It is important to note that the feature generates the entire inheritance hierarchy, even for classes that are not present in the local project. Configure your IRIS connection in VS Code settings: Go to Settings > Extensions > InterSystems ObjectScript Class Diagram Enter your IRIS server host, port, namespace, username, and password Open a .cls file in the editor Right-click and select "Generate InterSystems Class Diagram" The extension will connect to your IRIS server and generate a diagram using class information from the server Click on class names, properties, or methods in the diagram to: Open the class in IRIS Documatic View property definitions in IRIS Navigate to method implementations in IRIS Requirements OS Required Optional (for local PlantUML generation) Windows - VSCode 1.96.0+- ObjectScript Class Files(.cls) - Java 8+ Linux - VSCode 1.96.0+- ObjectScript Class Files(.cls) - Java 8+- Graphviz Usage Open a .cls file and generate a class diagram using: Ctrl+Alt+U shortcut Right-click on a file or folder and select "Generate Class Diagram" Click on elements in the diagram to jump to class definitions, properties, and methods Known Issues Subclass Generation: Missing functionality to generate subclass diagrams for the current class Large Project Performance: Generating diagrams for large folders via right-click may experience significant delays Generated webview/SVG for large projects lacks smooth zoom functionality and proper scaling IRIS Pwd Plaintext: Passwords shouldn't be shown as plain text. This will be fixed in the next version. I don't store the connection information and the code is open source, so you can check it to see if it's safe. Please report any issues on the GitHub repository. Contributing & License Open for contributions via GitHub Licensed under MIT You can find this plugin on the marketplace, feel free to create issues at issue and contribute with PR. thank you, @Jinyao ! Do you want to add the github repo to https://openexchange.intersystems.com ? to increase the audience? Hi. @Evgeny.Shvarov I have submitted an application to intersystem openexchange. Very nice extension, I have myself experimented with PlantUML diagrams generation and made my own bare-bone python script in the past, but you have nailed it as a fully automated vscode extension with integrated preview. Good work. Just as a FYI this is not working if using server side editing with no local source code. Thanks for the feedback.I was thinking about using Java or Python to generate class diagrams, but the VSCode extension can only use JS and TypeScript.Yeah, PlantUML is fantastic. Hi Timo. After I implemented "navigate to intersystem objectscript library definitions". I will try to implement diagram generation on server side.

The first part of this article provides all the background information. It also includes links to the DATATYPE_SAMPLE database, which you can use to follow along with the examples. In that section, we explored an error type ("Access Failure") that is easy to detect, as it immediately triggers a clear error message when attempting to read the data via the database driver. The errors discussed in this section are more subtle and harder to detect. I’ve referred to them as “Silent Corruption” and “Undetected Mutation” Let’s start with “Silent Corruption”:In the Employee table of the DATATYPE_SAMPLE database, there is a deliberately manipulated record that demonstrates this behavior – it’s the row with ID = 110. At first glance – and even at second glance – no issues are apparent. Neither the database driver nor the query tool indicates a problem if read this row. Only upon closer inspection does it become clear that the value in the red-marked cell does not match the transmitted (and defined) metadata. The column "Name" is defined as VARCHAR(50), but the actual value is 60 characters long! There are scenarios where this behavior doesn’t cause any issues — for example, when the driver handles such inconsistencies leniently.However, problems can arise when downstream systems rely on the provided metadata. If further processing is based on these metadata definitions, errors may occur when the actual content doesn’t conform to the agreed interface. A typical example involves ETL tools, which often generate target tables or define transformations based on metadata. The following SQL query can be used to identify records where the content deviates from the defined metadata: SELECT Name, CASE WHEN LENGTH(Name) > 50 THEN 1 ELSE 0 END AS Name_LENGTH_CHECK ,SSN, CASE WHEN LENGTH(SSN) > 50 THEN 1 ELSE 0 END AS SSN_LENGTH_CHECK FROM SQLUser.Employee WHERE LENGTH(Name) > 50 OR LENGTH(SSN) > 50 If you execute this query, it will return only the rows that contain errors. In each row, the faulty cell will be marked with a 1 if the value exceeds the length defined by the metadata. Now let’s take a look at the next error type: “Undetected Mutation.”To demonstrate this issue, the DATATYPE_SAMPLE database includes a faulty record specifically changed to illustrate this behavior. The record in question is the row with ID = 120 Again, neither the database driver nor the query tool will indicate a problem when reading this row. In this case, the value even appears to match the metadata! The column is defined as INTEGER, and the row returns an integer value (in this example: 0) in that cell. However, this value is not actually stored in the database! A direct look at the underlying Global reveals the true content. Through manipulation, a string value was injected into this field. SELECT CAST(Age AS VARCHAR(255)) AS Age, ISNUMERIC(CAST(Age AS VARCHAR(255))) AS Age_ISNUMERIC FROM SQLUser.Employee WHERE ISNUMERIC(CAST(Age AS VARCHAR(255))) = 0 If you execute this query, it will return only those rows that contain metadata inconsistencies. In each result row, the problematic cell is flagged with a 0 if the value cannot be interpreted as numeric by the driver Final Thoughts These scenarios highlight how seemingly well-formed data can conceal subtle inconsistencies—especially in legacy systems that bypass standard safeguards. While "Access Failures" are easy to spot, issues like "Silent Corruption" and "Undetected Mutation" often go unnoticed but can cause serious problems downstream, particularly in systems that rely on strict metadata compliance. The DATATYPE_SAMPLE database and the diagnostic queries shared here provide a foundation for identifying such issues manually. But let’s face it—writing these checks by hand is tedious and error-prone. Fortunately, SQL DATA LENS (min. version 3.22) makes this process much easier. 😉With just a click, it can generate comprehensive integrity checks for Tables, Views, and Stored Procedures—saving time and helping you stay ahead of hidden data quality issues.

InterSystems is announcing an end of maintenance event for Zen Reports beginning in Intersystems IRIS and IRIS for Health 2025.1. This follows the deprecation notice made when InterSystems IRIS was introduced in 2018 and subsequent inclusion of InterSystems Reports in 2020 to provide replacement reporting functionality. An overview of the timeline is: March 2018. InterSystems IRIS 2018.1: Announcement of Zen Reports deprecation, continued shipment to provide continuity for existing applications April 2020. InterSystems IRIS 2020.1: Intersystems Reports incorporated as part of user-based InterSystems IRIS and IRIS for Health and Advanced Server licenses May 2023. End of maintenance notification for Zen Reports 2H 2024. Zen Reports available as an ipm module 2H 2025 (InterSystems IRIS 2025.3) Zen Reports package removed from InterSystems IRIS and IRIS for Health distributions InterSystems introduced InterSystems Reports, powered by Logi Reports from insightsoftware (formerly Logi Analytics) as an embedded reporting solution starting with InterSystems IRIS and IRIS for Health 2020.1. InterSystems Reports provide a modern, drag and drop reporting solution for InterSystems customers and partners. We expect to transition Zen Reports to an independent package using IPM (InterSystems Package Manager) and to stop shipping Zen Reports with InterSystems IRIS and IRIS for Health version 2025.3. Zen Reports will continue to be available as an ipm module and may be distributed but will not be maintained by InterSystems. The WRC will continue to provide support on prior versions of Cache and IRIS that contain Zen Reports but no updates are expected to Zen Reports software. For more information on getting started with InterSystems Reports:InterSystems Learning Path InterSystems documentation Global Summit session: Intersystems Application Services' move from Zen Reports to InterSystems Reports insightsoftware's Logi Report documentation and tutorial Please comment below or contact dbpprodmgrs@intersystems.com with any questions about this announcement. Is there much of an API for Intersystems Reports? We've used a lot of Zen reports as part of our ERP system where we're feeding parameters to a report and generating it to a stream, or emailing it as an attachment, or saving it to a file. Hi @David.Hockenbroch! There is a set of articles related to InterSystems reports - maybe they talk about API also. I don't see anything in that list about them. I'm concerned that we're getting rid of something without really having a suitable replacement just yet. @Carmen.Logue - can you please speak to this question? I found this in the docs: From the server, users can: Run, filter and modify reports. Export to a variety of formats. Schedule reports to be distributed via email or FTP. https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cls?KEY=GISR_intro And docs on the API:https://reportkbase.logianalytics.com/v23.1/api/index.html and I could be incorrect as I don't speak for InterSystems but I read this message as %ZEN.Report* won't be included in standard ISC kits in the future, ie the kits will be slightly smaller. You can always get this code using IPM As reported in the past, ZEN Reports are deprecated which means no more enhancements, maybe even means no bug fixes. Maybe(my guess) this means at some point %ZEN.Report* will become open sourced and we can contribute where needed... but again that's purely a guess. I'm a big user/developer of ZEN Reports and it is important that I still have the ability to utilize ZEN Reports. At the same time, it just might be the time to look at what LogiReport offers and see if it's on the whole, a better reporting environment. Marc, I'm not asking about doing all of that from within the Intersystems report server. I'm asking about doing it from, say, an ObjectScript routine within IRIS. Steve is correct that our plan is to make Zen Reports available as an IPM module so that those who continue to use Zen Reports can package it into their applications. InterSystems Reports, which packages Logi Report, does have APIs -- see this documentation. It also includes the ability to schedule reports to be sent as email attachments (pdf, csv, html,xls and any combination of those) or to publish to a printer, fax, or file system. Let me know about use cases you think will not be addressed. I am certain I don't know all the creative ways our partners have been using Zen reports. Important news: We will *not* be removing Zen Reports from 2025.1. This has been delayed with a new target timeframe in one of our interim releases, possibly 2025.3. Will post more once we have a final date.

Developing with InterSystems Objects and SQL – Virtual July 28-August 1, 2025 This 5-day course teaches programmers how to use the tools and techniques within the InterSystems® development environment. Students develop a database application using object-oriented design, building different types of IRIS classes. They learn how to store and retrieve data using Objects or SQL, and decide which approach is best for different use cases. They write code using ObjectScript, Python, and SQL, with most exercises offering the choice between ObjectScript and Python, and some exercises requiring a specific language. This course is applicable for users of InterSystems IRIS® data platform and InterSystems Caché® Self-Register Here

UPDATE: Developer Preview 7 has been released. Update 7 includes a number of stability improvements over previous updates and support for support for all of the planned 2022.1 features. If you notice any problems at all, now's the time to let us know. The docker pull commands below have been updated with the latest build numbers. Enjoy! Developer Preview releases are now available for the 2022.1 version of InterSystems IRIS, IRIS for Health, and HealthShare Health Connect. As this is InterSystems' first developer preview release, let's take a moment to describe what these are. The developer preview program enhances the previous IRIS preview program with approximately bi-weekly releases that add features as they are ready. This allows us to get feedback on capabilities and enhancements as they're available. You'll see below a list of enhancements that are targeted for 2022.1, which are not included in the first developer preview. Look for those over the coming weeks. We are eager to learn from your experiences with this new release ahead of its General Availability release. Please share your feedback through the Developer Community so we can build a better product together. InterSystems IRIS Data Platform 2022.1 is an extended maintenance (EM) release. 2022.1 includes the many important new capabilities and enhancements have been added in 2021.2, the continuous delivery (CD) release, since 2021.1, the previous EM release. Please refer to the release notes for 2021.2 for an overview of these enhancements.New in InterSystems IRIS Data Platform 2022.1 will be expanded support for both production and development platforms. InterSystems IRIS will support (NOTE: these enhancements are not in the developer preview 1): Windows Server 2022 Windows 11 AIX 7.3 Oracle Linux 8 Additionally, we are happy to announce the addition of support Apple's M1 chipset for development environments. Support for MacOS Monterey (12) is planned for the 2022.1 release, but is not included in developer preview 1. Other important enhancements include: Speed and Scale improvements to System Alerting & Monitoring (SAM) The IRIS .NET SDK now support .NET 5 Improvements to InterSystems Reports Ease-of-use improvements to Production Extensions (PEX), which enables easy reuse of customer interoperability components More details on all of these features can be found in the product documentation: InterSystems IRIS 2022.1 documentation and release notes InterSystems IRIS for Health 2022.1 documentation and release notes HealthShare Health Connect 2022.1 documentation and release note EM releases come with classic installation packages for all supported platforms, as well as container images in OCI (Open Container Initiative) a.k.a. Docker container format. For a complete list, please refer to the Supported Platforms document. Installation packages and preview keys are available from the WRC's preview download site. They're also available from evaluation.intersystems.com. Container images for the Enterprise Editions of InterSystems IRIS and IRIS for Health and all corresponding components are available from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/irishealth:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/iris-arm64:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/irishealth-arm64:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/iris-ml:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/iris-ml-arm64:2022.1.0.191.0 For a full list of the available images, please refer to the ICR documentation. Container images for the Community Edition can also be pulled from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris-community:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/irishealth-community:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/iris-community-arm64:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/irishealth-community-arm64:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/iris-ml-community:2022.1.0.191.0 docker pull containers.intersystems.com/intersystems/iris-ml-community-arm64:2022.1.0.191.0 Alternatively, tarball versions of all container images are available via the WRC's preview download site. InterSystems IRIS Studio 2022.1 is a standalone IDE for use with Microsoft Windows and can be downloaded via the WRC's preview download site. It works with InterSystems IRIS and IRIS for Health version 2022.1 and below. InterSystems also supports the VSCode-ObjectScript plugin for developing applications for InterSystems IRIS with Visual Studio Code, which is available for Microsoft Windows, Linux and MacOS. The build number for this developer preview release is 2022.1.0.191.0. And images with ZPM package manager 0.3.2 are available accordingly. From clause could look like: FROM intersystemsdc/iris-community:2022.1.0.114.0-zpm And change the image to any of the following: intersystemsdc/iris-community:2022.1.0.114.0-zpm intersystemsdc/irishealth-community:2022.1.0.114.0-zpm intersystemsdc/irishealth-ml-community:2022.1.0.114.0-zpm intersystemsdc/irishealth-community:2022.1.0.114.0-zpm intersystemsdc/iris-community:2021.2.0.651.0-zpm intersystemsdc/iris-ml-community:2021.2.0.651.0-zpm intersystemsdc/irishealth-community:2021.2.0.651.0-zpm intersystemsdc/irishealth-ml-community:2021.2.0.651.0-zpm Also you can benefit from the latest and preview tags. Latest is equal to the latest GA IRIS, and preview is for the latest Preview version. e.g. FROM intersystemsdc/iris-community:2021.2.0.651.0-zpm equals to: FROM intersystemsdc/iris-community:latest FROM intersystemsdc/iris-community And FROM intersystemsdc/iris-community:2022.1.0.114.0-zpm equals to: FROM intersystemsdc/iris-community:preview And to launch IRIS do: docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community:2022.1.0.114.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-ml-community:2021.2.0.651.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community:2021.2.0.651.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2021.2.0.651.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-ml-community:2022.1.0.114.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2021.2.0.651.0-zpm And for terminal do: docker exec -it my-iris iris session IRIS and to start the control panel: http://localhost:9092/csp/sys/UtilHome.csp To stop and destroy container do: docker stop my-iris Thanks for having the :previewThat's comfort Interoperability callbacks can now be written in Python. Class dc.DFOperation Extends Ens.BusinessOperation { Method OnMessage(ByRef request As Ens.StringContainer, Output response As Ens.Response) As %Status [ Language = python ] { import pandas import iris query = request.value.StringValue response.value = iris.cls('Ens.Response')._New() stmt = iris.sql.prepare(query) rs = stmt.execute() df = rs.dataframe() iris.cls('Ens.Util.Log').LogInfo("dc.DFOperation", "OnMessage", "Dataframe load success") return iris.cls('%SYSTEM.Status').OK() } } And to launch IRIS do... Thanks, Evgeny. Can't notice a difference between the lines: 1 and 3, 4 and 6. Just a typo? I tried to run the docker image on my Apple Silicon, but the docker run fails with the following error: ----- [INFO] Executing command /home/irisowner/irissys/startISCAgent.sh 2188... [INFO] Writing status to file: /home/irisowner/irissys/iscagent.status Reading configuration from file: /home/irisowner/irissys/iscagent.conf ISCAgent[18]: Starting ISCAgent[19]: Starting ApplicationServer on *:2188 [INFO] ...executed command /home/irisowner/irissys/startISCAgent.sh 2188 [INFO] Copying InterSystems IRIS license key from /durable/iris.key to /usr/irissys/mgr... [INFO] ...copied key [INFO] Starting InterSystems IRIS instance IRIS... [INFO] Invalid registry ownership [ERROR] Command "iris start IRIS quietly" exited with status 256 [ERROR] See the above messages or /durable/iris/mgr/messages.log for more information [FATAL] Error starting InterSystems IRIS ----- I get the same error on Ubuntu ARM. I am using the image, containers.intersystems.com/intersystems/iris-arm64:2022.1.0.114.0. There is was a change in users, and before starting a new container with durable %SYS, you have to change permissions. Look at the documentation Thanks. I thought that was relevant, but even with the directory and files owned by 51773.52773, it failed with the same error. It fails even without mounting a volume outside the container and no durable %SYS, so I was wondering if the image itself had the problem. The issue could be also, if you using some different user, set with USER line in Dockerfile, or with user parameter when you run it. The user running the IRIS inside the container should be irisowner. Ah.. That was it. I was switching to root while building the image for installing jdk.. Adding 'USER irisowner' at the end of Dockerfile solved the issue. Thank you!

Hello again CCR community, We have officially released our CCR Technical Implementation Specialist certification exam for beta testing. The beta test will be available until March 1st, 2022. Interested in beta testing? Please review all the exam details and recommended preparation here, and then contact the Certification Team at certification@intersystems.com to get signed up as a beta tester! Thank you! Congratulations @Shane.Nowack and team! To our users of CCR in the field, thank you in advance for making time this month for participating as a Beta Tester of InterSystems' newest Certification Exam!

Hello programmers I would like to build a simple app where I could register data from a user like a name, age, and the phone just to practice, but for that, I would like to build the frontend and backend and also I need to be able to insert, update and delete information.Does anyone have any recommendations for me on how I could do that using Intersystems IRIS? Look at this project Check RESTForms2 and RESTFormsUI2.

December 13, 2021 - Advisory: Vulnerability in Apache Log4j2 Library Affecting InterSystems Products InterSystems is currently investigating the impact of a security vulnerability related to Apache Log4j2. The vulnerability — impacting at least Apache Log4j2 (versions 2.0 to 2.14.1) — was recently announced by Apache and is reported in the United States National Vulnerability Database (NVD) as CVE-2021-44228 with the highest severity rating, 10.0. Please see this page for more details about the vulnerability and updates on whether InterSystems Products are affected.

Developer Preview releases are now available for the 2022.2 version of InterSystems IRIS, IRIS for Health, and HealthShare Health Connect. This is the first in a series of releases that are part of the developer preview program. Future preview releases are expected to be updated biweekly and we will add features as they are ready. This program allows us to get feedback on capabilities and enhancements as they're available. You'll see below a list of enhancements that are targeted for 2022.2. Some these are not included in the first developer preview. Look for those over the coming weeks. We are eager to learn from your experiences with this new release ahead of its General Availability release. Please share your feedback through the Developer Community so we can build a better product together. InterSystems IRIS Data Platform 2022.2 is a continuous delivery (CD) release. Many updates and enhancements have been added in 2022.2, in SQL management, cloud integration, Kafka and JMS adapters, the SQL Loader, and other areas. There are also brand new capabilities, such as a new Rule Editor, and Columnar Storage, which are available trough the Early Access Program. New in InterSystems IRIS Data Platform 2022.2 will be expanded support for both production and development platforms. InterSystems IRIS will add support for: Linux Red Hat 9.0 (Linux Red Hat 7.x support is being retired) Ubuntu 22.04 (Ubuntu 18.04 support is being retired) (NOTE: support for these platforms is not in the developer preview 1) InterSystems IRIS for Health 2022.2 includes all of the enhancements of InterSystems IRIS. In addition, this release includes enhancements and updates to further extend the platform's extensive support for the FHIR® standard. HealthShare Health Connect 2022.2 includes all of the enhancements of InterSystems IRIS for Health, as applicable to integration engine use cases. More details on all of these features can be found: InterSystems IRIS 2022.2 documentation and release notes InterSystems IRIS for Health 2022.2 documentation and release notes HealthShare Health Connect 2022.2 documentation and release notes CD releases come with classic installation packages for all supported platforms, as well as container images in OCI (Open Container Initiative) a.k.a. Docker container format. For a complete list, please refer to the Supported Platforms document. Installation packages and preview keys are available from the WRC's preview download site or through the evaluation services website (use the flag "Show Preview Software"to get access to 2022.2). Container images for the Enterprise Editions of InterSystems IRIS and IRIS for Health and all corresponding components are available from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris:2022.2.0.270.0 docker pull containers.intersystems.com/intersystems/irishealth:2022.2.0.270.0 docker pull containers.intersystems.com/intersystems/iris-arm64:2022.2.0.270.0 docker pull containers.intersystems.com/intersystems/irishealth-arm64:2022.2.0.270.0 For a full list of the available images, please refer to the ICR documentation. Container images for the Community Edition can also be pulled from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris-community:2022.2.0.270.0 docker pull containers.intersystems.com/intersystems/irishealth-community:2022.2.0.270.0 docker pull containers.intersystems.com/intersystems/iris-community-arm64:2022.2.0.270.0 docker pull containers.intersystems.com/intersystems/irishealth-community-arm64:2022.2.0.270.0 Alternatively, tarball versions of all container images are available via the WRC's preview download site. InterSystems IRIS Studio 2022.2 is a standalone IDE for use with Microsoft Windows and can be downloaded via the WRC's preview download site. It works with InterSystems IRIS and IRIS for Health version 2022.2 and below. InterSystems also supports the VSCode-ObjectScript plugin for developing applications for InterSystems IRIS with Visual Studio Code, which is available for Microsoft Windows, Linux and MacOS. The build number for this developer preview release is 2022.2.0.270.0. The Community and Enterprise Preview Editions are also now available on evaluation.intersystems.com Here are also the docker images of InterSystems IRIS 2022.2 prevew with ZPM package manager 0.3.2 inside. From clause could look like: FROM intersystemsdc/iris-community:2022.2.0.270.0-zpm available images: intersystemsdc/iris-community:2022.2.0.270.0-zpm intersystemsdc/irishealth-community:2022.2.0.270.0-zpm intersystemsdc/irishealth-ml-community:2022.2.0.270.0-zpm intersystemsdc/irishealth-community:2022.2.0.270.0-zpm intersystemsdc/iris-community:2022.2.0.270.0-zpm intersystemsdc/iris-ml-community:2022.2.0.270.0-zpm intersystemsdc/irishealth-community:2022.2.0.270.0-zpm intersystemsdc/irishealth-ml-community:2022.2.0.270.0-zpm Or you can use preview clause: FROM intersystemsdc/iris-community:preview And to launch IRIS do: docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community:2022.2.0.270.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-ml-community:2022.2.0.270.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community:2022.2.0.270.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2022.2.0.270.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-ml-community:2022.2.0.270.0-zpm docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2022.2.0.270.0-zpm To open a terminal: docker exec -it my-iris iris session IRIS and to start the control panel: http://localhost:9092/csp/sys/UtilHome.csp To stop and destroy container: docker stop my-iris I think it is worth mentioning, that parameter --check-caps added with the previous version was removed in this version, and a container will fail to start with this parameter

Developer Preview releases are now available for the 2022.2 version of InterSystems IRIS, IRIS for Health, and HealthShare Health Connect. This is the second in a series of releases that are part of the developer preview program for 2022.2 Future preview releases are expected to be updated biweekly and we will add features as they are ready. This program allows us to get feedback on capabilities and enhancements as they're available. You'll see below a list of enhancements that are targeted for 2022.2. Some these are not included in this developer preview. Look for those over the coming weeks. We are eager to learn from your experiences with this new release ahead of its General Availability release. Please share your feedback through the Developer Community so we can build a better product together. InterSystems IRIS Data Platform 2022.2 is a continuous delivery (CD) release. Many updates and enhancements have been added in 2022.2, in SQL management, cloud integration, Kafka and JMS adapters, the SQL Loader, and other areas. There are also brand new capabilities, such as a new Rule Editor, and Columnar Storage, which are available trough the Early Access Program. New in InterSystems IRIS Data Platform 2022.2 will be expanded support for both production and development platforms. InterSystems IRIS will add support for: Linux Red Hat 9.0 (Linux Red Hat 7.x support is being retired) Ubuntu 22.04 (Ubuntu 18.04 support is being retired) (NOTE: support for these platforms is not in the developer preview 2) InterSystems IRIS for Health 2022.2 includes all of the enhancements of InterSystems IRIS. In addition, this release includes enhancements and updates to further extend the platform's extensive support for the FHIR® standard. HealthShare Health Connect 2022.2 includes all of the enhancements of InterSystems IRIS for Health, as applicable to integration engine use cases. More details on all of these features are available using these links below: InterSystems IRIS 2022.2 documentation and release notes InterSystems IRIS for Health 2022.2 documentation and release notes HealthShare Health Connect 2022.2 documentation and release notes CD releases come with classic installation packages for all supported platforms, as well as container images in OCI (Open Container Initiative) a.k.a. Docker container format. For a complete list, please refer to the Supported Platforms document. Installation packages and preview keys are available from the WRC's preview download site or through the evaluation services website (use the flag "Show Preview Software"to get access to 2022.2). Container images for the Enterprise Editions of InterSystems IRIS and IRIS for Health and all corresponding components are available from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris:2022.2.0.281.0 docker pull containers.intersystems.com/intersystems/irishealth:2022.2.0.281.0 docker pull containers.intersystems.com/intersystems/iris-arm64:2022.2.0.281.0 docker pull containers.intersystems.com/intersystems/irishealth-arm64:2022.2.0.281.0 For a full list of the available images, please refer to the ICR documentation. Container images for the Community Edition can also be pulled from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris-community:2022.2.0.281.0 docker pull containers.intersystems.com/intersystems/irishealth-community:2022.2.0.281.0 docker pull containers.intersystems.com/intersystems/iris-community-arm64:2022.2.0.281.0 docker pull containers.intersystems.com/intersystems/irishealth-community-arm64:2022.2.0.281.0 Alternatively, tarball versions of all container images are available via the WRC's preview download site. InterSystems IRIS Studio 2022.2 is a standalone IDE for use with Microsoft Windows and can be downloaded via the WRC's preview download site. It works with InterSystems IRIS and IRIS for Health version 2022.2 and below. InterSystems also supports the VSCode-ObjectScript plugin for developing applications for InterSystems IRIS with Visual Studio Code, which is available for Microsoft Windows, Linux and MacOS. The build number for this developer preview release is 2022.2.0.281.0. I decided to try Columnar Storage (IRIS CE): Property p As %String(STORAGEDEFAULT = "columnar"); When compiling a class, I get the following error: ERROR #15804: Columnar Storage (STORAGEDEFAULT=COLUMNAR) is not available with this license I turn to the documentation to find out what's the matter:Error Codes 15000 and Higher There is no description of error #15804 next, I check the current license restrictions: InterSystems IRIS Community Edition Limitations There are no Columnar Storage restrictions Maybe you need to sign up on the Columnar Storage Early Access Program at https://gs2022.isccloud.io/#early-access If this feature is not available in the Community Edition, then it makes no sense for me to try it. I just thought that in the preview version, all the features for testing are available. But thanks anyway for the quick response.

This is the third in a series of releases that are part of the developer preview program for 2022.2 Future preview releases are expected to be updated biweekly and we will add features as they are ready. Many updates, fixes and enhancements have been added in 2022.2, in SQL management, cloud integration, Kafka and JMS adapters, the SQL Loader, and other areas. Please share your feedback through the Developer Community so we can build a better product together. The Early Access Program (EAP) is still active for the Columnar Storage. Customers interested in exercising it should join the Early Access Program. CD releases come with classic installation packages for all supported platforms, as well as container images in OCI (Open Container Initiative) a.k.a. Docker container format. For a complete list, please refer to the Supported Platforms document. Installation packages and preview keys are available from the WRC's preview download site or through the evaluation services website (use the flag "Show Preview Software"to get access to the 2022.2). Container images for the Enterprise Editions of InterSystems IRIS and IRIS for Health and all corresponding components are available from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris:2022.2.0.293.0 docker pull containers.intersystems.com/intersystems/irishealth:2022.2.0.293.0 docker pull containers.intersystems.com/intersystems/iris-arm64:2022.2.0.293.0 docker pull containers.intersystems.com/intersystems/irishealth-arm64:2022.2.0.293.0 Container images for the Community Edition can also be pulled from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris-community:2022.2.0.293.0 docker pull containers.intersystems.com/intersystems/irishealth-community:2022.2.0.293.0 docker pull containers.intersystems.com/intersystems/iris-community-arm64:2022.2.0.293.0 docker pull containers.intersystems.com/intersystems/irishealth-community-arm64:2022.2.0.293.0 For a full list of the available images, please refer to the ICR documentation. Alternatively, tarball versions of all container images are available via the WRC's preview download site. The build number for this developer preview release is 2022.2.0.293.0. Stay tuned for a new update in about two weeks! Preview docker images on 2022.2.0.293.0 build with ZPM onboard are updated too and can be pulled as: docker pull intersystemsdc/iris-community:preview docker pull intersystemsdc/irishealth-community:preview docker pull intersystemsdc/iris-community-arm64:preview docker pull intersystemsdc/irishealth-community-arm64:preview

This is the fourth in a series of releases that are part of the developer preview program for 2022.2 Future preview releases are expected to be updated biweekly and we will add features as they are ready. Many updates, fixes and enhancements have been added in 2022.2, in SQL management, cloud integration, Kafka and JMS adapters, the SQL Loader, and other areas. Please share your feedback through the Developer Community so we can build a better product together. The Early Access Program (EAP) is still active for the Columnar Storage. Customers interested in exercising it should join the Early Access Program. This developer preview 4 adds support to Red Hat RHEL 9. As usual, CD releases come with classic installation packages for all supported platforms, as well as container images in Docker container format. For a complete list, refer to the Supported Platforms document. Installation packages and preview keys are available from the WRC's preview download site or through the evaluation services website (use the flag "Show Preview Software"to get access to the 2022.2). Container images for the Enterprise Editions of InterSystems IRIS and IRIS for Health and all corresponding components are available from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris:2022.2.0.304.0 docker pull containers.intersystems.com/intersystems/irishealth:2022.2.0.304.0 docker pull containers.intersystems.com/intersystems/iris-arm64:2022.2.0.304.0 docker pull containers.intersystems.com/intersystems/irishealth-arm64:2022.2.0.304.0 Container images for the Community Edition can also be pulled from the InterSystems Container Registry using the following commands: docker pull containers.intersystems.com/intersystems/iris-community:2022.2.0.304.0 docker pull containers.intersystems.com/intersystems/irishealth-community:2022.2.0.304.0 docker pull containers.intersystems.com/intersystems/iris-community-arm64:2022.2.0.304.0 docker pull containers.intersystems.com/intersystems/irishealth-community-arm64:2022.2.0.304.0 For a full list of the available images, please refer to the ICR documentation. Alternatively, tarball versions of all container images are available via the WRC's preview download site. The build number for this developer preview release is 2022.2.0.304.0. Stay tuned for a new update in about two weeks!