Nueva publicación

Encontrar

Anuncio
· 13 ene, 2025

Boletim Anual do InterSystems Community de 2024

Olá e boas-vindas ao Boletim Anual do Developer Community de 2024 .
Estatísticas gerais:
272 postagens publicadas em 2024:
 159 artigos
 102 anúncios
 8 perguntas
 3 discussões
62 membros ingressaram no Developer Community em 2024
✓ Total de 1,251 posts publicadas ao todo
✓ Total de 17,547 membros ingressaram ao todo
Mais populares:
127
Por Danusa Calixto
109
Por Danusa Calixto
Mais discutidos
4
Por Yuri Marx
1
Por Heloisa Paiva
Mais curtidos
Autores mais populares
Autores com mais artigos
!resumo do anoComunidade de desenvolvedores da InterSystems
Comentarios (0)1
Inicie sesión o regístrese para continuar
Pregunta
· 13 ene, 2025

How do you debug embedded python (Docker Container) in VSCode

Just curious what the process is for debugging either a .py file that is uploaded to a specific namespace/location or a python classmethod defined in a .cls file.

 

My method can be run via the "Debug" breadcrumb but it doesnt hit breakpoints it just runs without a debugger. Also objectscript methods debug correctly

3 comentarios
Comentarios (3)5
Inicie sesión o regístrese para continuar
Anuncio
· 13 ene, 2025

[Video] InterSystems Package Manager

Hi Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯ InterSystems Package Manager @ Global Summit 2024

InterSystems Package Manager (IPM) is a tool to deploy the packages and solutions into InterSystems IRIS with dependencies. Learn about why you should use it, how to use it, and recent updates for software supply chain security.

 Presenters
🗣 @Timothy Leavitt, Development Manager, Application Services, InterSystems
🗣 @Bob Kuszewski, Product Manager, Developer Experience, InterSystems

Dive in and enjoy the video—we hope you find it insightful! 👍

Comentarios (0)1
Inicie sesión o regístrese para continuar
Artículo
· 13 ene, 2025 Lectura de 3 min

Configuring Mirroring for Healthcare Products

You may have noticed that to configure a mirror for InterSystems IRIS for Health and HealthShare® Health Connect there is a special requirement. I wanted to go through it step by step in this article.

This assumes you have already configured the second failover member and confirmed a successful failover member status in the mirror monitor:

Step 1: Enable HS_Services user (on backup and primary

 

Step 2: Switch to Namespace HSSYS and go to Interoperability > Configure > Credentials. Enter the Password for your predefined HS_Services user (on backup and primary)

Step 3: Schedule the Mirror Monitor Launch Task (on backup and primary). Do so by running the following from IRIS terminal from HSSYS namespace:

HSSYS>do ##class(HS.Util.Mirror.Task).Schedule("HSSYS")

Confirm it was scheduled successfully and is scheduled to run every five minutes:

Step 4: Add HSSYS database to the mirror on the primary server. System Administration > Configuration > System Configuration > Local Databases. Choose "Add To Mirror" and select HSSYS

Step 5: Dismount HSSYS from the primary and backup servers. System Operation > Databases. Choose HSSYS and select "Dismount"

Step 6: Copy the HSSYS IRIS.DAT from the primary to the backup server's appropriate HSSYS directory.

Make sure the permissions are appropriate. You should see something like this:

-rw-rw---- 1 irisowner irisowner 22020096 Jan 12 15:26 IRIS.DAT

If you do not see this, modify it with chown and chmod so that it is so.

Step 7: Mount database on the primary server. System Operation > Databases. Choose HSSYS and select "Mount". Choose "Start Mirror Catchup?" but do not select Read Only.

Step 8: Mount the database on the backup server. System Operation > Databases. Choose HSSYS and select "Mount". Do not select Read Only. There will not be a Start Mirror Catchup option.

Step 9: On your backup server open the Mirror Monitor (System Operation > Mirror Monitor). You should now see HSSYS added to your list of mirrored databases. But you need to click activate it and make it catchup:

After a few seconds your backup should be "Caught Up"

HSSYS is now mirrored.

And we should see the Mirror Monitor Agent running (Health > Mirror Monitor Agent)

Step 10: Configure Network Host Name on Primary server (Home > Health > Installer Wizard)

The Network Host Name should be set to the mirror VIP (or DNS entry for the mirror VIP).

Step 11: Configure Secure Communication

Step 12 (optional): Configure Foundation

Remember to activate your namespace once it is created.

Since we selected Mirror Database you should see it in your Mirrored Databases in the Mirror Monitor:

The extra mirroring requirement for healthcare products is now complete and testing a failover we see that both servers are caught up per the Mirror Monitor Agent:

You can now set up your FHIR Endpoints and see the resource (R) and resource history (V) databases be automatically mirrored:

Comentarios (0)1
Inicie sesión o regístrese para continuar
Resumen
· 13 ene, 2025

Publicações Desenvolvedores InterSystems, Janeiro 06 - 12, 2025, Resumo

Artigos
Anúncios
#Developer Community Oficial
Perguntas
#InterSystems IRIS
Globais de uma rotina
Por Jenifer Arendt
Janeiro 06 - 12, 2025Week at a GlanceInterSystems Developer Community