検索

お知らせ
· 2025年11月9日

Key Questions of the Month: October 2025

Hey Community,

It's time for the new batch of #KeyQuestions from the previous month.

120+ Deepest Questions That Make You Think Profoundly | 2025 Reveals -  AhaSlides

Here are the Key Questions of October chosen by InterSystems Experts within all Communities:

📌 ¿Cómo procesar ficheros en EnsLib.RecordMap.Service.FTPService files uno a uno? by @Kurro Lopez (ES)

📌 *.inc file For loop by @Michael Akselrod (EN)

📌 Can we save Message Viewer Query output to file (eg CSV) by @Colin Brough (EN)

These questions will be highlighted with the #Key Question tag, and their authors will get the Key Question badge on Global Masters.

If you find the key question(s) from other communities interesting, just drop us a line in the comments, and we will translate the question(s) and the accepted answer(s).

Congrats, and thank you all for your interesting questions. Keep them coming!

See you next month😉

ディスカッション (0)2
続けるにはログインするか新規登録を行ってください
記事
· 2025年11月9日 3m read

Consuming REST-APIs for dummies (beginner-friendly)

As a developer who uses Cache as DB for a couple of projects, I'm using REST API's every time, knowing how to consume a resource from REST API, in my opinion, it's crucial to know how to consume external REST Api's using %Net.HttpRequest because it enables integration with modern web applications and services, and it's a crucial skill for a backend developer who loves and uses Cache as a DB.

What and who is %Net.HttpRequest

its just a class but this is the proper way of making request outside of the framework, this is just a simple class who provide HTTP methods like GET, POST and PUT and all others request methods, let you "play" with the headers and craft the request as you want to and how to handle the response you got, for every request send using %Net.HttpRequest, we got in return a %Net.HttpResponse object that contains the response in the same pattern.

A proper way to handle REST Api requests with %Net involves checking both the %Status returned value and the response status codes, which let you raise specific error messages and filter the responses when the request fails. The recommended way is to use macros like $$$ISER() or $SYSTEM.Status.IsOK(), we can use $SYSTEM.Status.DisplayError() to inspect the HTTP status code for handling.

Before we get our hands dirty, we should know who JSONPlaceHolder is, so from the official site, they said:

"Free fake and reliable API for testing and prototyping" 

And it is what it is, it's a free online REST API to play with, it's fake data, and we can even POST data to it, but this guide is all about consuming data, so let's focus on that, and this is a simple example of how to consume a JSON from a REST API Service:

Set request = ##class(%Net.HttpRequest).%New()
Set request.Server = "jsonplaceholder.typicode.com"
Set status = request.Get("/posts/1")

If $$$ISERR(status) {
    Do $SYSTEM.Status.DisplayError(status)
    Quit
}

Set response = request.HttpResponse
Set httpStatus = response.StatusCode
Set body = response.Data.Read()

If httpStatus < 200 || httpStatus >= 300 {
    Write "HTTP Error: ", response.StatusLine, !
    Quit
}

Write "HTTP Status: ", response.StatusLine, !
// Do what ever you want with it!

What do we do?

  1. Assign "request" from a new instance of %New.HttpRequest object
  2. Assign a location/address to the property Server on the request instance.
  3. Making a GET request to the endpoint we provided to the function "/posts/1", which means we request data from "posts" with id equal to 1 (to get just the first message, we can specify just "posts" and get all of them, it's good to play with it)
  4. Check if there is any error in the function using $$$ISERR with the status returned from the request GET method. If there is none, the request was sent successfully from our endpoint.
  5. Assign the response variable from the request object itself.
  6. Extract the status and the body.
  7. Check if the response code is OK If the code returned is above 200 and below or equal to 300, it's OK. (307 is redirecting, so it's less what we need here)

So, in a general perspective, what are we doing here?

  1. Craft a pre-defined request using the class
  2. trying to consume the data we needed
  3. Handle both use cases of failure and success

If everything goes well, you should get something like this as a JSON object:

And this is how we consume data from a REST API, but what can we do with it?
Let's see how to extract the data from the response:

Set reponseBodyAsJSON = {}.%FromJSON(body)

Write "id: ", reponseBodyAsJSON.id, !
Write "title: ", reponseBodyAsJSON.title, !
Write "body: ", reponseBodyAsJSON.body, !

In this way, we break the response into key-value pairs like JSON should be.
This is how we can easily access and consume a REST API resource using the GET method and %Net.HttpRequest class, this is a really beginner-friendly guide that lets you "overview" how we do it.

Learning the magic of REST APIs is your duty.

Since this topic is very approachable, you can easily experiment by making requests and trying out different methods. In the next guide, we’ll look at how to securely transfer data between two REST-based services.

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
お知らせ
· 2025年11月8日

Videos for InterSystems Developers, October 2025 Recap

Hello and welcome to the October 2025 Developer Community YouTube Recap.
InterSystems Ready 2025
By Don Woodlock, Sean Kennedy, Alex MacLeod, Erica Song, James Derrickson, Julie Smith, Kristen Nemes, Varun Saxena, Dimitri Fane, Jonathan Teich, Judy Charamand
By Thomas McCoy
By John Paladino, Mike Brand, Mike Fuller, Peter Cutts
By Stefan Wittmann, Raj Singh
 
"Code to Care" videos
Before the Lightbulb: Understanding the First Phase of the AI Revolution in Medicine
By Don Woodlock, Head of Global Healthcare Solutions, InterSystems
More from InterSystems Developers
How Technology Communities Drive Professional Careers
By Rochael Ribeiro Filho, Guido Orlando Jr
Foreign Tables In 2025.2
By Michael Golden
ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
記事
· 2025年11月8日 4m read

How to run a process on an interval or schedule?

When I started my journey with InterSystems IRIS, especially in Interoperability, one of the initial and common questions I had was: how can I run something on an interval or schedule? In this topic, I want to share two simple classes that address this issue. I'm surprised that some similar classes are not located somewhere in EnsLib. Or maybe I didn't search well? Anyway, this topic is not meant to be complex work, just a couple of snippets for beginners.

So let's assume we have a task "Take some data from an API and put it into an external database". To solve this task, we need:

  1. Ens.BusinessProcess, which contains an algorithm of our data flow: How to prepare a request for taking data, how to transform the API response to a request for DB, how to handle errors and other events through the data flow lifecycle
  2. EnsLib.REST.Operation for making HTTP requests to the API using EnsLib.HTTP.OutboundAdapter
  3. Ens.BusinessOperation with EnsLib.SQL.OutboundAdapter for putting data into the external database via a JDBC connection

Details of the implementation of these business hosts lie outside the scope of this article, so let's say we already have a process and two operations. But how to run it all? The process can run only by inbound request... We need an Initiator! Which one will just be run by interval and send a dummy request to our process.

Here is such an initiator class. I added a bit of additional functionality: sync or async calls will be used, and stop or not process on error if we have many hosts as targets. But mainly here it's a target list. To each item (business host) on this list will be sent a request. Pay attention to the OnGetConnections event - it's needed for correct link building in Production UI.

/// Call targets by interval
Class Util.Service.IntervalCall Extends Ens.BusinessService
{

/// List of targets to call
Property TargetConfigNames As Ens.DataType.ConfigName;

/// If true, calls are made asynchronously (SendRequestAsync)
Property AsyncCall As %Boolean;

/// If true, and the target list contains more than one target, the process will stop after the first error
Property BreakOnError As %Boolean [ InitialExpression = 1 ];

Property Adapter As Ens.InboundAdapter;

Parameter ADAPTER = "Ens.InboundAdapter";

Parameter SETTINGS = "TargetConfigNames:Basic:selector?multiSelect=1&context={Ens.ContextSearch/ProductionItems?targets=1&productionName=@productionId},AsyncCall,BreakOnError";

Method OnProcessInput(pInput As %RegisteredObject, Output pOutput As %RegisteredObject, ByRef pHint As %String) As %Status
{
    Set tSC = $$$OK
    Set targets = $LISTFROMSTRING(..TargetConfigNames)

    Quit:$LISTLENGTH(targets)=0 $$$ERROR($$$GeneralError, "TargetConfigNames are not defined")

    For i=1:1:$LISTLENGTH(targets) {
        Set target = $LISTGET(targets, i)
        Set pRequest = ##class(Ens.Request).%New()

        If ..AsyncCall {
            Set tSC = ..SendRequestAsync(target, pRequest)
        } Else  {
            Set tSC = ..SendRequestSync(target, pRequest, .pResponse)
        }
        Quit:($$$ISERR(tSC)&&..BreakOnError)
    }

    Quit tSC
}

ClassMethod OnGetConnections(Output pArray As %String, pItem As Ens.Config.Item)
{
    If pItem.GetModifiedSetting("TargetConfigNames", .tValue) {
        Set targets = $LISTFROMSTRING(tValue)
        For i=1:1:$LISTLENGTH(targets) Set pArray($LISTGET(targets, i)) = ""
    }
}

}

After it, you just need to add this class to Production, and mark our business process in the TargetConfigNames setting. 

But what if requirements were changed? And now we need to run our data grabber every Monday at 08:00 AM. The best way for it is using Task Manager. For this, we need to create a custom task that will run our Initiator programmatically. Here is a simple code for this task:

/// Launch selected business service on schedule
Class Util.Task.ScheduleCall Extends %SYS.Task.Definition
{

Parameter TaskName = "Launch On Schedule";

/// Business Service to launch
Property ServiceName As Ens.DataType.ConfigName;

Method OnTask() As %Status
{
    #dim tService As Ens.BusinessService
    Set tSC = ##class(Ens.Director).CreateBusinessService(..ServiceName, .tService)
    Quit:$$$ISERR(tSC) tSC
    
    Set pRequest = ##class(Ens.Request).%New()
    Quit tService.ProcessInput(pRequest, .pResponse)
}

}

Two important things here:

  • You must set the Pool Size of the Initiator Business Service to 0 to prevent running it by call interval (option Call Interval, you can clear or leave as is - it's not used when Pool Size is 0)

             

  • You need to create a task in Task Manager, choose "Launch On Schedule" as task type (don't forget to check a Namespace), set our Initiator Business Service name to the ServiceName parameter, and set up the desired schedule. See: System Operation > Task Manager > New Task

And a bonus

I often faced cases when we need to run something in Production only on demand. Of course, we can create some custom UI on CSP for it, but reinventing the wheel is not our way. I believe it is better to use the typical UI of the Management Portal. So, the same task that we created previously can be run manually. Just change the task run type to On Demand for it. On-demand task list is available at System > Task Manager > On-demand Tasks, see the Run button. Furthermore, the Run button (manual run) is available for any kind of task.

It is all. Now we have a pretty architecture of interoperability for our business hosts. And 3 ways to run our data grabber: by interval, on a timetable, or manually.

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
お知らせ
· 2025年11月7日

[Video] Document Server: Improving Performance While Reducing Stored Data

Hey Community!

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

⏯  Document Server: Improving Performance While Reducing Stored Data @ Ready 2025
 

The presentation introduces the upcoming Document Server feature for InterSystems Cloud Document, a schemaless JSON database with SQL access. The new system uses two key innovations: Pack Vector Array (PVA): a compact, binary format for fast and efficient storage and retrieval and Common Key Map, which stores shared field names only once across similar documents. Together, these features significantly reduce storage size (up to 90% for deeply nested data) and improve query performance by enabling direct field access and faster indexing. This approach is especially useful for large, flexible datasets like medical records, offering both speed and efficiency in cloud document storage.

🗣 Presenter: Yiwen Huang, Data Platforms

Enjoy watching, and subscribe for more videos! 👍

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください