#Azure

TL;DR This article explains how to deploy InterSystems IRIS Community Edition on Azure using the Azure Marketplace and a Virtual Machine. It covers prerequisites, instance selection, authentication, SSH access, first verification steps, and how to delete resources to avoid charges. The deployment can typically be done using Azure free credits and is suitable for developers who want to quickly start working with IRIS in the cloud.

Who this guide is for. This guide is intended for developers, solution architects, and DevOps engineers who want to deploy InterSystems IRIS Community Edition on Microsoft Azure. No prior Azure automation experience is required, but basic familiarity with the Azure Portal and SSH is helpful.

After following this guide, you will be able to:

• Launch InterSystems IRIS Community Edition from the Azure Marketplace
• Configure a small, secure Azure VM
• Connect to IRIS using SSH and the Management Portal
• Reset the default IRIS password and verify that IRIS is running

Prerequisites

• An active Azure subscription (new accounts may have free credits)
• Permissions to create resource groups, VMs, and networking resources
• An SSH client and a private key (.pem) you can store securely
• Basic knowledge of Linux command line

Deployment overview

• Open the IRIS Community Edition listing in Azure Marketplace and click Get it now
• In Azure Portal, choose Start with a pre-set configuration (or Create)
• Configure Basics: subscription, resource group, VM name, region, image, and size (a small VM is usually sufficient)
• Choose SSH key authentication and generate/download the key if needed
• Review + Create, accept terms, and deploy; then Go to resource → Connect → SSH
• First SSH login: run iris password to change _SYSTEM/SYS; start a session with iris session iris
• Management Portal: http://YOUR_VM_IP:52773/csp/sys/UtilHome.csp

Hi all,

I'm developing a Azure Pipeline to automate the deployment process in Caché.

I use selfhosted agent to execute code im my Caché Server.

My problem is that cession execution via cmd always terminate with exit code 1 and the pipeline finishes with error, but the execution in Caché is fine, the method executed returns $$$OK
I use the following line to execute a class in Caché.
C:\InterSystems\Cache\bin\csession.exe CACHE -U  %RELEASE_TRIGGERINGARTIFACT_ALIAS% "##Class(sgf.pipeline.DeploymentManager).

Background

For a variety of reasons, users may wish to mount a persistent volume on two or more pods spanning multiple availability zones. One such use case is to make data stored outside of IRIS available to both mirror members in case of failover.

We currently have Business Operation that we built to use the EnsLib.SQL.OutboundAdapter so we can make Microsoft SQL Server Stored Procedure calls. The BO is attached to a Java Gateway Service.

Some of our MS SQL Databases have moved from being OnPrem to Azure Cloud. We have started seeing where we are receiving errors on the BO saying that we cannot connect to the Azure Database, but we never receive a Disconnect from the Azure Database.