Introduction

In this article, we will explore various approaches to extending and customizing the behavior of InterSystems IRIS (and IRIS Health) built-in interoperability message routers.

Message routers perform one of the core functions of Enterprise Application Integration (EAI) and are among the most frequently used business processes in interoperability productions.

InterSystems IRIS interoperability production development involves using or writing various types of components. They include services (which handle incoming data), processes (which deal with the data flow and logic), and operations (which manage outgoing data or requests). Messages flowing through those components constantly require being adapted to consuming applications. Therefore,Data transformations are by far the most common component in interoperability productions.

In the early stages of data transformation development, thetest tool from the Management Portal becomes quite handy.

Introduction

What's in a name? That which we call a rose
By any other name would smell as sweet

William Shakespeare, "Romeo & Juliet"

In this article, we will describe a set of naming conventions for ObjectScript code.

When using VS Code client-side editing in combination with a file-based revision control system such as git, I find activities such as branch switching and moving/renaming classes and packages a bit tedious, since you to maintain the connected namespace in sync manually.
I am not aware of a built-in way to do this with VS Code Extension. Just added an idea to the portal that is about adding some kind of mechanism to do this automatically, please do not hesitate to comment, amend and vote for idea DPI-I-608  😊

Introduction

This article attempt to summarize and update on the exchanges in this post. Please feel free to comment.
ObjectScript is based on MUMPS, a programming language dating back to 1966. At the time, and for quite a long period, memory and cpu resources were scarce, as was terminal screen space, and a very concise (and easily decodable) syntax was preferred (as, for example in C). Nowadays,  we no longer have the same memory and screen limitations,  and code readability and maintainability is far more important.

Hi,
I am dealing with a very old code base (some routines date back to 1985 and were running on a M system 😉). It is rather huge and currently contains around 5000 compilable *.int routines.

My goal is to export all routine code as *.int UDL files and setup a git repository containing all routines.

The issue is, approximatively 200 of those routines have storage names that differ only in case. I am using Windows and when exporting those routines using vscode, files gets overwritten depending on routine export order, as Windows NTFS file system names are not case-sensitive.

Hi everyone,

This one had me breaking a sweat 😅

When a SOAP request has a %Stream.GlobalBinary property, it fails to serialize to base64 when stream is larger than ~43MB with 

ERROR #6301: SAX XML Parser Error: <MAXSTRING>xeWrite+7^%occXMLInternal

Unless you enable the following parameters :

Parameter BASE64LINEBREAKS = 1;
Parameter USEPPGHANDLER = 1;

The first one instructs %SOAP.

GitLab is using the rouge ruby gem, that apparently does not support ObjectScript at the moment. Is there an easy way to add syntax highlighting to GitLab ?