検索 | InterSystems Developer Community

記事

Robert Cemper · 2025年9月4日 4m read

The article was motivated by the 2025 September Article Bounty ***************************************************************

The principle of Docker is just convincing to me.

Get a sandbox where you play and try whatever you want/need to do
Once done. You drop it without leaving traces in your working environment

This was the technical base for me to run about 700 reviews in OEX
with almost no side effects (except those caused by myself).

For beginners, I'll start with straight pure IRIS, no *health, *ML, *whatever

First, you need a Docker installation. It's available on almost any platform.
My personal preference is Windows Docker Desktop for its comfortable admin console.
I don't dig into detailed Docker management.
There's enough reading material around to search in Docker Docs

Second, you decide on an IRIS incarnation of your choice
the most simple: intersystemsdc/iris-community ready to use

runs on Ubuntu
has a valid community licence
has Apache httpd installed
has IPM/ZPM client installed

Warning #1: As a beginner, don't study packages offered on OEX
They are great (mostly) but always targeted to some Functionality
to some special Application that requires special settings and a tricky installation.

Warning #2: Docker has a rich set of commands with everything you need
And those commands offer a flood of (sometimes confusing) parameters.
So, I suggest making them reproducible using dedicated scripts.
Dockerfile is the way to take with complex constructs with lots of extras to be
loaded upfront. I typically saw them related to Python and to various AI demo cases
There's no need for this example.
docker-compose.yml is the real to blow your container. It needs:

a definition of what you want to "compose" >> service:
- a name for it >> iris:
- which image to run >> image: intersystemsdc/iris-community
Next, you need to define how SuperServer Port 1972 and the default WebServer Port 52773 will be visible outside the container
- ports: - 41773:1972 - 42773:52773
Finally, it' not an urgent requirement but often very useful to map your local directory to some internal in the container. I used /external Especially at the beginning, this bi-directional path makes life really easy
- volumes: - ./:/external

Now this is the final text of docker-compose.yml

services: iris: image: intersystemsdc/iris-community ports: - 41773:1972 - 42773:52773 volumes: - ./:/external

And now you are ready to run your first IRIS instance in Docker

docker-compose up allows you to watch the full startup
docker-compose up -d launches a start in the background and keeps your command line free
docker ps -a shows ports and running images of your IRIS container

OK your fresh IRIS is in Docker now.
But how can you use it?

You have the WebServer and so the Management Portal http://localhost:42773/csp/sys/UtilHome.csp
You have the SuperServerPort for ODBC access, IRIS NATIVE, ... (and even Studio)
And you can access IRIS also from the command line inside the container
- docker-compose exec iris iris session iris

Splitting this single line, you access the container first and then IRIS

docker-compose exec iris bash

Then iris view

Instance 'IRIS'   (default)
        directory:    /usr/irissys
        versionid:    2025.1.0.223.0com
        datadir:      /usr/irissys
        conf file:    iris.cpf  (WebServer port = 52773)
        status:       running, since Thu Sep  4 14:35:19 2025
        SuperServers: 1972
        state:        ok
        product:      InterSystems IRIS

And iris session iris

Node: 3266c5c8b21f, Instance: IRIS 
USER>

Here at the bash level, you have all the options for IRIS operating in your hands Your Ubuntu user is irisowner
for the rare cases where you might need root access docker-compose exec -u root iris bash
Stop your container with docker-compose down

A few considerations on changes during the container session.

Whatever you create, change, or modify exists as long as the container exists
- Once the container is deleted, all changes, .... are gone.
This might be annoying with large setups.
Dockerfile takes care of a setup that is done once in a build cycle, differently to run the setup at every start of the container.
This is good practice in OEX packages, though it might look like overkill in some cases

2件の新着コメント

ディスカッション (2)3

続けるにはログインするか新規登録を行ってください

記事

Heloisa Paiva · 2025年9月4日 2m read

#ヒントとコツ #InterSystems IRIS #InterSystems IRIS for Health

Rubrica InterSystems FAQ

No InterSystems IRIS, você pode criar tabelas vinculadas usando comandos, ao invés de usar o caminho System Explorer > SQL > Wizard > Linked Tables do Portal de Administração:

Para criar uma tabela vinculada, use o método CreateLinkedTable da classe %SYSTEM.SQL.Schema. Veja a documentação da classe para detalhes.

Para executar, siga os passos:

set sc = $SYSTEM.SQL.Schema.CreateLinkedTable("<dsn>","<Schema>","<Table>","<primaryKeys>","<localClass>","<localTable>","")

/// 1st argument: dsn - SQL Gateway connection name
/// 2nd argument: Schema - Source schema name
/// 3rd argument: Table - Source table name
/// 4th argument: primaryKeys - Primary key
/// 5th argument: localClass - Linked class name (e.g., User.LinkedClass)
/// 6th argument: localTable - Linked SQL table name (SqlTableName)
/// 7th argument: columnMap - Linked field information

Se você executar o código dessa maneira, a tabela vinculada será criada com o atributo ReadOnly. Se quiser removê-lo, é necessário especificá-lo no sétimo argumento, columnMap.

set columnMap("external field name") = $lb("new class property name","new sql field name","read-only(1/0)")

Nessa amostra, um columnMap é criado, definindo ReadOnly como 0 para todos os campos (colunas), e uma tabela vinculada é criada. A primaryKey é definida para herdar a primaryKey da tabela vinculada. O uso é como a seguir:

do ##class(ISC.LinkUtils).LinkTable("<dsn>","<Schema>","<Table>","<localClass>")

/// First argument: dsn - SQL Gateway connection name
/// Second argument: Schema - Link source schema name
/// Third argument: Table - Link source table name
/// Fourth argument: localClass - Link destination class name (e.g., User.LinkedClass)

Você também pode ver o exemplo usado aqui: https://github.com/Intersystems-jp/CreateLinkedTable

ディスカッション (0)1

続けるにはログインするか新規登録を行ってください

記事

Megumi Kakechi · 2025年9月4日 2m read

#ヒントとコツ #InterSystems IRIS #InterSystems IRIS for Health

InterSystems FAQ rubric

In InterSystems IRIS, you can create linked tables using commands, instead of using System Explorer > SQL > Wizard > Linked Tables in the Management Portal:

To create a linked table, use the CreateLinkedTable method of the %SYSTEM.SQL.Schema class. See the class reference for details.

To execute it, follow these steps:

set sc = $SYSTEM.SQL.Schema.CreateLinkedTable("<dsn>","<Schema>","<Table>","<primaryKeys>","<localClass>","<localTable>","")

/// 1st argument: dsn - SQL Gateway connection name
/// 2nd argument: Schema - Source schema name
/// 3rd argument: Table - Source table name
/// 4th argument: primaryKeys - Primary key
/// 5th argument: localClass - Linked class name (e.g., User.LinkedClass)
/// 6th argument: localTable - Linked SQL table name (SqlTableName)
/// 7th argument: columnMap - Linked field information

If you run it this way, the linked table will be created with the ReadOnly attribute. If you want to remove the ReadOnly attribute, you need to specify it in the seventh argument, columnMap.

set columnMap("external field name") = $lb("new class property name","new sql field name","read-only(1/0)")

In this sample, a columnMap is created that sets ReadOnly to 0 for all fields (columns), and a linked table is created. The primaryKey is set to inherit the primaryKey of the linked table. The usage is as follows:

do ##class(ISC.LinkUtils).LinkTable("<dsn>","<Schema>","<Table>","<localClass>")

/// First argument: dsn - SQL Gateway connection name
/// Second argument: Schema - Link source schema name
/// Third argument: Table - Link source table name
/// Fourth argument: localClass - Link destination class name (e.g., User.LinkedClass)

You can also see the sample used here: https://github.com/Intersystems-jp/CreateLinkedTable

ディスカッション (0)0

続けるにはログインするか新規登録を行ってください

質問

Matheus Augusto · 2025年9月4日

#Caché #Ensemble

Dear, Community!

I have a concern about using %Stream.TmpCharacter for storage purposes. Reading the class's source code, I can understand a bit about how it works. But I'd like to know from the community how it actually works. Is it necessary to use the .Clear() method to clear this buffer, or is it done automatically upon disposal?

Note: Please forgive my poor English.

6件の新着コメント

ディスカッション (6)3

続けるにはログインするか新規登録を行ってください

ダイジェスト

Anastasia Dyubaylo · 2025年9月4日

#IRIS contest

Dear Community Member,

We’re entering the final stretch of the InterSystems Demo Games voting period! You’ve seen how our Sales Engineers bring InterSystems technologies to life through creative demos. At this time, all the demos are in. Now it’s time to make your voice heard!

👉 How to vote:

Watch the demos on the Demo Games Contest Page.
Select your favorite entries before September 14, 2025.

Your vote will decide the winners, so don’t miss the chance to support the demos that inspired you the most.

🔗 Full contest details here

Thank you for being part of the Demo Games — and may the best demo win! 🏆

検索

IRIS in Docker for beginners

Vincular tabelas programaticamente

Link tables programmatically

About %Stream.TmpCharacter

Last chance to cast your vote in the InterSystems Demo Games!