Pesquisar

Anúncio
· Out. 2

[Video] Deploying HealthShare Solution Modules with InterSystems Package Manager

Hi, Community!

Need to install a HealthShare solution module? Follow this simple step-by-step process to get started!

Deploying HealthShare Solution Modules with InterSystems Package Manager

In this video, you will see how to:

  • Download modules.
  • Create configuration files.
  • Deploy via the command line.
Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· Out. 2 2min de leitura

How to compare the contents of two globals

InterSystems FAQ rubric

The ^%GCMP utility can be used to compare the contents of two globals.

For example, to compare ^test and ^test in the USER and SAMPLES namespaces, it would look like this:
*In the example below, 700 identical globals are created in the two namespaces, and the contents of one of them is changed to make it the detection target.

USER>kill ^test
USER>for i=1:1:100 { for j=1:1:7 { set ^test(i,j)="Test"_i } }
 
USER>zn "samples"                  // change namespace to SAMPLES
SAMPLES>kill ^test
SAMPLES>for i=1:1:100 { for j=1:1:7 { set ^test(i,j)="Test"_i } }
 
SAMPLES>set ^test(50,5,1)=1        // Change one of the globals created in the SAMPLES namespace.
SAMPLES>do ^%GCMP
Compare global ^test               // Global to compare.
on directory set: (this system)    // Enter
in namespace: SAMPLES =>           // Enter (if this namespace is OK)
with global ^test=>                // Global to compare
on directory set: (this system)    // Enter
in namespace: SAMPLES => USER      // Namespace to compare
Output differences on
Device:                            // Destination for output results. Press <Enter> to view in a terminal.
                                   // If you enter the full path of the log file name, the output will be sent there.
Right margin: 80 =>

Compare global ^test in SAMPLES
 with global ^test in USER
 
^test(50,5,1) exists in ^|"SAMPLES"|test but not in ^|"USER"|test    // Detects differing globals
Time=.001822
SAMPLES>

If you want to compare between instances on different servers, rather than within the same instance, use the ^DATACHECK utility. For instructions on how to use the ^DATACHECK utility, see the related article below:

How to compare multiple globals and routines in two databases

Discussão (0)0
Entre ou crie uma conta para continuar
Pergunta
· Out. 2

Login Failure for a single person (not user!) in IRIS for Health

Hi community,

A colleague gets ERROR #822: Access denied every time he tries to log in via Management portal. It is NOT the case of wrong credentials: I reset his password password to a temporary one so it would prompt him to create a new one upon first login. He did get the prompt, changed his password and his next attempt at logging in displayed the same error.

The audit log record displays this:
Error message: ERROR #862: User is restricted from running application /csp/sys/op, %Admin_Operate:U required -- cannot execute.
Web Application: /csp/sys/op
$I: |TCP|1972|1533396
$P: |TCP|1972|1533396

Other information:

  • he can get access with the same credentials via R, so it is absolutely not the problem with credentials
  • the login works just fine on my device. He provided me with his old password, which I tested before setting a new one, and I created a test user with the same permissions. Both worked for me but not for him
  • no one else encounters this error. I asked a different colleague (also a Mac user like the first colleague) to try it (test user with the same permissions) just to be sure. It works for the second colleague but the first one still cannot log into Management portal
  • changing browsers (Chrome, Safari) or devices doesn't help. The first colleague encounters the same error (Access denied) in Chrome and Safari, both on his work laptop and an old one he's tried at my request
  • we cannot tell when it started because this colleague usually connects programmatically, not via Management portal. This was the first time he's tried it in about a month

In short, one person encounters the error that no one else trying the same thing does. IRIS Audit log reports a LoginFailure event and claims that "%Admin_Operate:U required" - but it shouldn't require that to just log in! The issue seems to be localized to him specifically  (somehow!) but Audit log claims it's a permissions error. I am deeply confused.

Has anyone else encountered anything like this?

3 Comments
Discussão (3)2
Entre ou crie uma conta para continuar
Artigo
· Out. 2 2min de leitura

Un Hook útil de pre-commit de Git para Health Connect Cloud

Hola,

He pensado en compartir con vosotros un hook bastante útil que me ha ayudado cuando desarrollo en Health Connect Cloud con VS Code y GitBash. Al desarrollar en Health Connect Cloud, si hacéis cambios directamente en el servidor, como reglas de enrutamiento o despliegue de componentes, estos no se incluyen automáticamente en el control de versiones; por lo tanto, debéis exportarlos desde el servidor a vuestros archivos locales y hacer push a vuestro repositorio remoto. Estoy seguro de que hay métodos más sencillos para gestionar esto, que estoy en proceso de probar, pero como solución rápida pensé que sería útil tener un hook de pre-commit que active un recordatorio en GitBash. Mirad el ejemplo a continuación.

Este recordatorio se puede ajustar para mencionar las reglas de enrutamiento y cualquier otra cosa que penséis que debe tenerse en cuenta para exportar.

El código del hook:

#!/bin/bash
# Git pre-commit hook - gentle reminder for Production.cls
targetFile="src/HCC/Connect/Production.cls"
# Check if Production.cls is already staged
staged=$(git diff --cached --name-only | grep "$targetFile")

# If Production.cls is not staged, show a gentle reminder
if [ -z "$staged" ]; then
    echo ""
    echo "💡 Gentle reminder: Have you made any changes to the Production class on the server?"
    echo ""
    echo "   If YES: Export and add $targetFile to this commit"
    echo "   If NO:  Continue with: git commit --no-verify"
    echo ""
    echo "   (This reminder appears on every commit - use --no-verify to skip)"
    echo ""
    exit 1
fi
# Production.cls is staged, proceed normally
exit 0

Espero que esto os resulte útil a quienes desarrolláis con Health Connect Cloud.

Jordan

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· Out. 2 25min de leitura

Exécution d'InterSystems IRIS avec Docker : guide étape par étape - Partie 1 : A partir des principes de base au fichier Dockerfile personnalisé

Table des matières

  1. Objectif de l'article
  2. Les conteneurs : définition et pertinence dans le cadre d'IRIS
     2.1 Les conteneurs et les images en quelques mots
     2.2 Avantages des conteneurs pour les développeurs
     2.3 Pourquoi IRIS fonctionne bien avec Docker
  3. Conditions préalables
  4. Installation de l'image InterSystems IRIS
     4.1 Utilisation de Docker Hub
     4.2 Extraction de l'image
  5. Exécution de l'image InterSystems IRIS
     5.1 Démarrage d'un conteneur IRIS
     5.2 Vérification de l'état des conteneurs
     5.3 Exécution de code dans le terminal conteneur
     5.4 Accès au portail de gestion IRIS
     5.5 Connexion du conteneur à VS Code
     5.6 Arrêt ou suppression du conteneur
     5.7 Configuration d'un mot de passe spécifique avec un montage de type bind
     5.8 Utilisation de volumes %SYS durables
      5.8.1 Contenu stocké sous %SYS durable
      5.8.2 Comment activer %SYS durable
  6. Utilisation de Docker Compose
     6.1 Exemple d'utilisation de l'outil Docker Compose
     6.2 Exécution de Docker Compose
  7. Utilisation d'un fichier Dockerfile pour l'exécution d'un code source personnalisé
     7.1 Exemple de fichier Dockerfile
     7.2 Exemple de Docker Compose
     7.3 Compréhension des couches, du balisage des images et de la différence entre le temps de compilation et le temps d'exécution
     7.4 Code source et script d'initialisation
     7.5 Création de l'image avec le fichier Dockerfile
     7.6 Exécution d'instructions dans le terminal IRIS conteneurisé
  8. Conclusion et suite

1 Comment
Discussão (1)2
Entre ou crie uma conta para continuar