Search

In an earlier article (hope, you’ve read it), we took a look at the CircleCI deployment system, which integrates perfectly with GitHub. Why then would we want to look any further? Well, GitHub has its own CI/CD platform called GitHub Actions, which is worth exploring. With GitHub Actions, you don’t need to rely on some external, albeit cool, service. In this article we’re going to try using GitHub Actions to deploy the server part of InterSystems Package Manager, ZPM-registry, on Google Kubernetes Engine (GKE). As with all systems, the build/deploy process essentially comes down to “do this, go there, do that,” and so on. With GitHub Actions, each such action is a job that consists of one or more steps, together known as a workflow. GitHub will search for a description of the workflow in the YAML file (any filename ending in .yml or .yaml) in your .github/workflows directory. See Core concepts for GitHub Actions for more details. All further actions will be performed in the fork of the ZPM-registry repository. We’ll call this fork "zpm-registry" and refer to its root directory as "<root_repo_dir>" throughout this article. To learn more about the ZPM application itself see Introducing InterSystems ObjectScript Package Manager and The Anatomy of ZPM Module: Packaging Your InterSystems Solution. All code samples are stored in this repository to simplify copying and pasting. The prerequisites are the same as in the article Automating GKE creation on CircleCI builds. We’ll assume you’ve read the earlier article and already have a Google account, and that you’ve created a project named "Development," as in the previous article. In this article, its ID is shown as <PROJECT_ID>. In the examples below, change it to the ID of your own project. Keep in mind that Google isn’t free, although it has a free tier. Be sure to control your expenses. Workflow Basics Let’s get started. A simple and useless workflow file might look like this: $ cd <root_repo_dir>$ mkdir -p .github/workflows$ cat <root_repo_dir>/.github/workflows/workflow.yaml name: Traditional Hello Worldon: [push]jobs: courtesy: name: Greeting runs-on: ubuntu-latest steps: - name: Hello world run: echo "Hello, world! When pushing to the repository, you need to execute a job named "Greeting," which consists of a single step: printing a welcome phrase. The job should run on a GitHub-hosted virtual machine called the Runner, with the latest version of Ubuntu installed.After pushing this file to the repository, you should see on the Code GitHub tab that everything went well: If the job had failed, you’d see a red X instead of a green checkmark. To see more, click on the green checkmark and then on Details. Or you can immediately go to the Actions tab: You can learn all about the workflow syntax in the help document Workflow syntax for GitHub Actions. If your repository contains a Dockerfile for the image build, you could replace the "Hello world" step with something more useful like this example from starter-workflows: steps:- uses: actions/checkout@v2- name: Build the Docker image run: docker build . --file Dockerfile --tag my-image:$(date +%s) Notice that a new step, "uses: action/checkout@v2", was added here. Judging by the name "checkout", it clones the repository, but where to find out more? As in the case of CircleCI, many useful steps don’t need to be rewritten. Instead, you can take them from the shared resource called Marketplace. Look there for the desired action, and note that it’s better to take those that are marked as "By actions" (when you hover over - "Creator verified by Github"). The "uses" clause in the workflow reflects our intention to use a ready-made module, rather than writing one ourselves. The implementations of the actions themselves can be written in almost any language, but JavaScript is preferred. If your action is written in JavaScript (or TypeScript), it will be executed directly on the Runner machine. For other implementations, the Docker container you specify will run with the desired environment inside, which is obviously somewhat slower. You can read more about actions in the aptly titled article, About actions. The checkout action is written in TypeScript. And in our example, Terraform action is a regular bash script launched in Docker Alpine. There’s a Dockerfile in our cloned repository, so let's try to apply our new knowledge. We’ll build the image of the ZPM registry and push it into the Google Container Registry. In parallel, we’ll create the Kubernetes cluster in which this image will run, and we’ll use Kubernetes manifests to do this. Here’s what our plan, in a language that GitHub understands, will look like (but keep in mind that this is a bird's eye view with many lines omitted for simplification, so don’t actually use this config): name: Workflow description# Trigger condition. In this case, only on push to ‘master’ branchon: push: branches: - master # Here we describe environment variables available # for all further jobs and their steps# These variables can be initialized on GitHub Secrets page# We add “${{ secrets }}” to refer themenv: PROJECT_ID: ${{ secrets.PROJECT_ID }} # Define a jobs list. Jobs/steps names could be random but# it’s better to have they meaningfuljobs: gcloud-setup-and-build-and-publish-to-GCR: name: Setup gcloud utility, Build ZPM image and Publish it to Container Registry runs-on: ubuntu-18.04 steps: - name: Checkout - name: Setup gcloud cli - name: Configure docker to use the gcloud as a credential helper - name: Build ZPM image - name: Publish ZPM image to Google Container Registry gke-provisioner: name: Provision GKE cluster runs-on: ubuntu-18.04 steps: - name: Checkout - name: Terraform init - name: Terraform validate - name: Terraform plan - name: Terraform apply kubernetes-deploy: name: Deploy Kubernetes manifests to GKE cluster needs: - gcloud-setup-and-build-and-publish-to-GCR - gke-provisioner runs-on: ubuntu-18.04 steps: - name: Checkout - name: Replace placeholders with values in statefulset template - name: Setup gcloud cli - name: Apply Kubernetes manifests This is the skeleton of the working config in which there are no muscles, the real actions for each step. Actions can be accomplished with a simple console command ("run" or "run |" if there are several commands): - name: Configure docker to use gcloud as a credential helper run: | gcloud auth configure-docker You can also launch actions as a module with "uses": - name: Checkout uses: actions/checkout@v2 By default, all jobs run in parallel, and the steps in them are done in sequence. But by using "needs", you can specify that one job should wait for the rest to complete: needs:- gcloud-setup-and-build-and-publish-to-GCR- gke-provisioner By the way, in the GitHub Web interface, such waiting jobs appear only when the jobs they’re waiting for are executed. The "gke-provisioner" job mentions Terraform, which we examined in the previous article. The preliminary settings for its operation in the GCP environment are repeated for convenience in a separate markdown file. Here are some additional useful links: Terraform Apply Subcommand documentation Terraform GitHub Actions repository Terraform GitHub Actions documentation In the "kubernetes-deploy" job, there is a step called "Apply Kubernetes manifests". We’re going to use manifests as mentioned in the article Deploying InterSystems IRIS Solution into GCP Kubernetes Cluster GKE Using CircleCI, but with a slight change. In the previous articles, IRIS application has been stateless. That is, when restarting the pod, all data is returned to its default place. This is great, and it’s often necessary, but for ZPM registry you need to somehow save the packages that were loaded into it, regardless of how many times you need to restart. Deployment allows you to do this, of course, but not without limitations. For stateful applications, it’s better to choose the StatefulSet resource. Pros and cons can be found in the GKE documentation topic on Deployments vs. StatefulSets and the blog post Kubernetes Persistent Volumes with Deployment and StatefulSet. The StatefulSet resource is in the repository. Here’s the part that’s important for us: volumeClaimTemplates:- metadata: name: zpm-registry-volume namespace: iris spec: accessModes: - ReadWriteOnce resources: requests: storage: 10Gi The code creates a 10GB read/write disk that can be mounted by a single Kubernetes worker node. This disk (and the data on it) will survive the restart of the application. It can also survive the removal of the entire StatefulSet, but for this you need to set the correct Reclaim Policy, which we won’t cover here. Before breathing life into our workflow, let's add a few more variables to GitHub Secrets: The following table explains the meaning of these settings (service account keys are also present): Name Meaning Example GCR_LOCATION Global GCR location eu.gcr.io GKE_CLUSTER GKE cluster name dev-cluster GKE_ZONE Zone to store an image europe-west1-b IMAGE_NAME Image registry name zpm-registry PROJECT_ID GCP Project ID possible-symbol-254507 SERVICE_ACCOUNT_KEY JSON key GitHub uses to connect to GCP. Important: it has to be base64-encoded (see note below) ewogICJ0eXB... TF_SERVICE_ACCOUNT_KEY JSON key Terraform uses to connect to GCP (see note below) {…} For SERVICE_ACCOUNT_KEY, if your JSON-key has a name, for instance, key.json, run the following command: $ base64 key.json | tr -d '\n' For TF_SERVICE_ACCOUNT_KEY, note that its rights are described in Automating GKE creation on CircleCI builds. One small note about SERVICE_ACCOUNT_KEY: if you, like me, initially forgot to convert it to base64 format, you’ll see a screen like this: Now that we’ve looked at the workflow backbone and added the necessary variables, we’re ready to examine the full version of the workflow (<root_repo_dir>/.github/workflow/workflow.yaml): name: Build ZPM-registry image, deploy it to GCR. Run GKE. Run ZPM-registry in GKEon: push: branches: - master # Environment variables.# ${{ secrets }} are taken from GitHub -> Settings -> Secrets# ${{ github.sha }} is the commit hashenv: PROJECT_ID: ${{ secrets.PROJECT_ID }} SERVICE_ACCOUNT_KEY: ${{ secrets.SERVICE_ACCOUNT_KEY }} GOOGLE_CREDENTIALS: ${{ secrets.TF_SERVICE_ACCOUNT_KEY }} GITHUB_SHA: ${{ github.sha }} GCR_LOCATION: ${{ secrets.GCR_LOCATION }} IMAGE_NAME: ${{ secrets.IMAGE_NAME }} GKE_CLUSTER: ${{ secrets.GKE_CLUSTER }} GKE_ZONE: ${{ secrets.GKE_ZONE }} K8S_NAMESPACE: iris STATEFULSET_NAME: zpm-registry jobs: gcloud-setup-and-build-and-publish-to-GCR: name: Setup gcloud utility, Build ZPM image and Publish it to Container Registry runs-on: ubuntu-18.04 steps: - name: Checkout uses: actions/checkout@v2 - name: Setup gcloud cli uses: GoogleCloudPlatform/github-actions/setup-gcloud@master with: version: '275.0.0' service_account_key: ${{ secrets.SERVICE_ACCOUNT_KEY }} - name: Configure docker to use the gcloud as a credential helper run: | gcloud auth configure-docker - name: Build ZPM image run: | docker build -t ${GCR_LOCATION}/${PROJECT_ID}/${IMAGE_NAME}:${GITHUB_SHA} . - name: Publish ZPM image to Google Container Registry run: | docker push ${GCR_LOCATION}/${PROJECT_ID}/${IMAGE_NAME}:${GITHUB_SHA} gke-provisioner: # Inspired by: ## https://www.terraform.io/docs/github-actions/getting-started.html ## https://github.com/hashicorp/terraform-github-actions name: Provision GKE cluster runs-on: ubuntu-18.04 steps: - name: Checkout uses: actions/checkout@v2 - name: Terraform init uses: hashicorp/terraform-github-actions@master with: tf_actions_version: 0.12.17 tf_actions_subcommand: 'init' tf_actions_working_dir: 'terraform' - name: Terraform validate uses: hashicorp/terraform-github-actions@master with: tf_actions_version: 0.12.17 tf_actions_subcommand: 'validate' tf_actions_working_dir: 'terraform' - name: Terraform plan uses: hashicorp/terraform-github-actions@master with: tf_actions_version: 0.12.17 tf_actions_subcommand: 'plan' tf_actions_working_dir: 'terraform' - name: Terraform apply uses: hashicorp/terraform-github-actions@master with: tf_actions_version: 0.12.17 tf_actions_subcommand: 'apply' tf_actions_working_dir: 'terraform' kubernetes-deploy: name: Deploy Kubernetes manifests to GKE cluster needs: - gcloud-setup-and-build-and-publish-to-GCR - gke-provisioner runs-on: ubuntu-18.04 steps: - name: Checkout uses: actions/checkout@v2 - name: Replace placeholders with values in statefulset template working-directory: ./k8s/ run: | cat statefulset.tpl |\ sed "s|DOCKER_REPO_NAME|${GCR_LOCATION}/${PROJECT_ID}/${IMAGE_NAME}|" |\ sed "s|DOCKER_IMAGE_TAG|${GITHUB_SHA}|" > statefulset.yaml cat statefulset.yaml - name: Setup gcloud cli uses: GoogleCloudPlatform/github-actions/setup-gcloud@master with: version: '275.0.0' service_account_key: ${{ secrets.SERVICE_ACCOUNT_KEY }} - name: Apply Kubernetes manifests working-directory: ./k8s/ run: | gcloud container clusters get-credentials ${GKE_CLUSTER} --zone ${GKE_ZONE} --project ${PROJECT_ID} kubectl apply -f namespace.yaml kubectl apply -f service.yaml kubectl apply -f statefulset.yaml kubectl -n ${K8S_NAMESPACE} rollout status statefulset/${STATEFULSET_NAME} Before you push to a repository, you should take the terraform-code from the Terraform directory of github-gke-zpm-registry repository, replace placeholders as noted in main.tf comment, and put it inside the terraform/ directory. Remember that Terraform uses a remote bucket that should be initially created as noted in Automating GKE creation on CircleCI builds article. Also, Kubernetes-code should be taken from the K8S directory of github-gke-zpm-registry repository and put inside the k8s/ directory. These code sources were omitted in this article to save space. Then you can trigger a deploy: $ cd <root_repo_dir>/$ git add .github/workflow/workflow.yaml k8s/ terraform/$ git commit -m “Add GitHub Actions deploy”$ git push After pushing the changes to our forked ZPM repository, we can take a look at the implementation of the steps we described: There are only two jobs so far. The third, "kubernetes-deploy", will appear after the completion of those on which it depends.Note that building and publishing Docker images requires some time: And you can check the result in the GCR console: The "Provision GKE cluster" job takes longer the first time as it creates the GKE cluster. You’ll see a waiting screen for a few minutes: But, finally, it finishes and you can be happy: The Kubernetes resources are also happy: $ gcloud container clusters get-credentials <CLUSTER_NAME> --zone <GKE_ZONE> --project <PROJECT_ID> $ kubectl get nodesNAME STATUS ROLES AGE VERSIONgke-dev-cluster-dev-cluster-node-pool-98cef283-dfq2 Ready <none> 8m51s v1.13.11-gke.23 $ kubectl -n iris get poNAME READY STATUS RESTARTS AGEzpm-registry-0 1/1 Running 0 8m25s It's a good idea to wait for Running status, then check other things: $ kubectl -n iris get stsNAME READY AGEzpm-registry 1/1 8m25s $ kubectl -n iris get svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEzpm-registry LoadBalancer 10.23.248.234 104.199.6.32 52773:32725/TCP 8m29s Even the disks are happy: $ kubectl get pv -oyaml | grep pdName pdName: gke-dev-cluster-5fe434-pvc-5db4f5ed-4055-11ea-a6ab-42010af00286 And happiest of all is the ZPM registry (we took the External-IP output of "kubectl -n iris get svc"): $ curl -u _system:SYS 104.199.6.32:52773/registry/_ping{"message":"ping"} Handling the login/password over HTTP is a shame, but I hope to do something about this in future articles. By the way, you can find more information about endpoints in the source code: see the XData UrlMap section. We can test this repo by pushing a package to it. There’s a cool ability to push just a direct GitHub link. Let’s try with the math library for InterSystems ObjectScript. Run this from your local machine: $ curl -XGET -u _system:SYS 104.199.6.32:52773/registry/packages/-/all[]$ curl -i -XPOST -u _system:SYS -H "Content-Type: application/json" -d '{"repository":"https://github.com/psteiwer/ObjectScript-Math"}' 'http://104.199.6.32:52773/registry/package'HTTP/1.1 200 OK$ curl -XGET -u _system:SYS 104.199.6.32:52773/registry/packages/-/all[{"name":"objectscript-math","versions":["0.0.4"]}] Restart a pod to be sure that the data is in place: $ kubectl -n iris scale --replicas=0 sts zpm-registry$ kubectl -n iris scale --replicas=1 sts zpm-registry$ kubectl -n iris get po -w Wait for a running pod. Then what I hope you’ll see: $ curl -XGET -u _system:SYS 104.199.6.32:52773/registry/packages/-/all[{"name":"objectscript-math","versions":["0.0.4"]}] Let’s install this math package from your repository on your local IRIS instance. Choose the one where the ZPM client is already installed: $ docker exec -it $(docker run -d intersystemsdc/iris-community:2019.4.0.383.0-zpm) bash$ iris session irisUSER>write ##class(Math.Math).Factorial(5)<CLASS DOES NOT EXIST> *Math.MathUSER>zpmzpm: USER>listzpm: USER>repo -listregistry Source: https://pm.community.intersystems.com Enabled? Yes Available? Yes Use for Snapshots? Yes Use for Prereleases? Yeszpm: USER>repo -n registry -r -url http://104.199.6.32:52773/registry/ -user _system -pass SYSzpm: USER>repo -list registry Source: http://104.199.6.32:52773/registry/ Enabled? Yes Available? Yes Use for Snapshots? Yes Use for Prereleases? Yes Username: _system Password: <set>zpm: USER>repo -list-modules -n registryobjectscript-math 0.0.4zpm: USER>install objectscript-math[objectscript-math] Reload START...[objectscript-math] Activate SUCCESS zpm: USER>quitUSER>write ##class(Math.Math).Factorial(5) 120 Congratulations!Don’t forget to remove the GKE cluster when you don’t need it anymore: Conclusion There are not many references to GitHub Actions within the InterSystems community. I found only one mention from guru @mdaimor. But GitHub Actions can be quite useful for developers storing code on GitHub. Native actions supported only in JavaScript, but this could be dictated by a desire to describe steps in code, which most developers are familiar with. In any case, you can use Docker actions if you don’t know JavaScript. Regarding the GitHub Actions UI, along the way I discovered a couple of inconveniences that you should be aware of: You cannot check what is going on until a job step is finished. It’s not clickable, like in the step "Terraform apply". While you can rerun a failed workflow, I didn’t find a way to rerun a successful workflow. A workaround for the second point is to use the command: $ git commit --allow-empty -m "trigger GitHub actions" You can learn more about this in the StackOverflow question How do I re-run Github Actions? 💡 This article is considered as InterSystems Data Platform Best Practice.

InterSystems IRIS Deployment Guide for AWS using CloudFormation template Please note: following this guide, especially the prerequisites section requires Intermediate to Advanced level of knowledge of AWS. You'll need to create and manage S3 buckets, IAM roles for EC2 instances, VPCs and Subnets. You'll also need access to InterSystems binaries (usually downloaded via WRC site) as well as IRIS license key. Aug 12, 2020Anton Umnikov Templates Source code is available here: https://github.com/antonum/AWSIRISDeployment Table of Contents InterSystems IRIS Deployment Guide – AWS Partner Network. 1 Introduction. 3 Prerequisites and Requirements 3 Time. 3 Product License and Binaries. 3 AWS Account 3 IAM Entity for user 3 IAM Role for EC2. 4 S3 Bucket 4 VPC and Subnets 4 EC2 Key Pair 4 Knowledge Requirements 4 Architecture. 5 Multi-AZ Fault Tolerant Architecture Diagram (Preferred) 5 Single Instance, Single AZ Architecture Diagram (Development and Testing) 6 Deployment 7 Security. 7 Data in Private Subnets. 7 Encrypting IRIS Data at Rest 7 Encrypting IRIS data in transit 8 Secure access to IRIS Management Portal 8 Logging/Auditing/Monitoring. 8 Sizing/Cost 9 Deployment Assets. 10 Deployment Options. 10 Deployment Assets (Recommended for Production) 10 CloudFormation Template Input Parameters 10 Clean Up. 11 Testing the Deployment 11 Health Checks. 11 Failover Test 12 Backup and Recovery. 12 Backup. 12 Instance Failure. 12 Availability-Zone Failure. 12 Region Failure. 12 RPO/RTO.. 13 Storage Capacity. 13 Security certificate expiration. 14 Routine Maintenance. 14 Emergency Maintenance. 14 Support 15 Troubleshooting. 15 Contact InterSystems Support 16 Appendix. 16 IAM Policy for EC2 instance. 16 Introduction InterSystems provides the CloudFormation Template for users to set up their own InterSystems IRIS® data platform according to InterSystems and AWS best practices. This guide will detail the steps to deploy the CloudFormation template. In this guide, we cover two types of deployments for the InterSystems IRIS CloudFormation template. The first method is highly available using multiple availability zones (AZ) and targeted to production workloads, and the second method is a single availability zone deployment for development and testing workloads. Prerequisites and Requirements In this section, we detail the prerequisites and requirements to run and operate our solution. Time The deployment itself takes about 4 minutes, but with prerequisites and testing it could take up to 2 hours. Product License and Binaries InterSystems IRIS binaries are available to InterSystems customers via https://wrc.intersystems.com/. Login with your WRC credentials and follow the links to Actions -> SW Distributions -> InterSystems IRIS. This Deployment Guide is written for the Red Hat platform of InterSystems IRIS 2020.1 build 197. IRIS binaries file names are of the format ISCAgent-2020.1.0.215.0-lnxrhx64.tar.gz and IRISHealth-2020.1.0.217.1-lnxrhx64.tar.gz InterSystems IRIS license key – you should be able to use your existing InterSystems IRIS license key (iris.key). You can also request an evaluation key via the InterSystems IRIS Evaluation Service: https://download.intersystems.com/download/register.csp. AWS Account You must have an AWS account set up. If you do not, visit: https://aws.amazon.com/getting-started/ IAM Entity for user Create an IAM user or role. Your IAM user should have a policy that allows AWS CloudFormation actions. Do not use your root account to deploy the CloudFormation template. In addition to AWS CloudFormation actions, IAM users who create or delete stacks will also require additional permissions that depend on the stack template. This deployment requires permissions to all the services listed in the following section. Reference: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html. IAM Role for EC2 The CloudFormation template requires an IAM role that allows your EC2 instance to access S3 buckets and put logs into CloudWatch. See Appendix “IAM Policy for EC2 instance” for an example of the policy associated with such role. Reference: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html. S3 Bucket Create an S3 bucket called “my bucket”, copy IRIS binaries files and iris.key: BUCKET=<my bucket> aws s3 mb s3://$BUCKET aws s3 cp ISCAgent-2020.1.0.215.0-lnxrhx64.tar.gz s3://$BUCKET aws s3 cp IRISHealth-2020.1.0.217.1-lnxrhx64.tar.gz s3://$BUCKET aws s3 cp iris.key s3://$BUCKET VPC and Subnets The template is designed to deploy IRIS into an existing VPC and Subnets. In regions where three or more Availability Zones are available, we recommend creating three private subnets across three different AZ’s. Bastion Host should be located in any of the public subnets within the VPC. You can follow the AWS example to create a VPC and Subnets with the CloudFormation template: https://docs.aws.amazon.com/codebuild/latest/userguide/cloudformation-vpc-template.html. EC2 Key Pair To access the EC2 instances provisioned by this template, you will need at least one EC2 Key Pair. Refer to this guide for details: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html. Knowledge Requirements Knowledge of the following AWS services is required: Amazon Elastic Compute Cloud (Amazon EC2) Amazon Virtual Private Cloud (Amazon VPC) AWS CloudFormation AWS Elastic Load Balancing AWS S3 Account limit increases will not be required for this deployment. More information on proper policy and permissions can be found here: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html. Note: Individuals possessing the AWS Associate certifications should have a sufficient depth of knowledge. Architecture In this section, we give architecture diagrams of two deployment possibilities, and talk about architecture design choices. Multi-AZ Fault Tolerant Architecture Diagram (Preferred) In this preferred option, mirrored IRIS instances are situated behind a load balancer in two availability zones to ensure high availability and fault tolerance. In regions with three or more availability zones, the Arbiter node is located in the third AZ. Database nodes are located in private subnets. Bastion Host is in a Public subnet within the same VPC. Network Load Balancer directs database traffic to the current Primary IRIS node Bastion Host allows secure access to the IRIS EC2 instances IRIS stores all customer data in encrypted EBS volumes EBS is encrypted and uses the AWS Key Management Service (KMS) managed key For regulated workloads where encryption of data in transit is required, you can choose to use the r5n family of instances, since they provide automatic instance-to-instance traffic encryption. IRIS-level traffic encryption is also possible but not enabled by CloudFormation (see the Encrypting Data in Transit section of this guide) Use of security groups restrict access to the greatest degree possible by only allowing necessary traffic Single Instance, Single AZ Architecture Diagram (Development and Testing) InterSystems IRIS can also be deployed in a single Availability Zone for development and evaluation purposes. The data flow and architecture components are the same as the ones highlighted in the previous section. This solution does not provide high availability or fault tolerance, and is not suitable for production use. Deployment Log into your AWS account with the IAM entity created in the Prerequisites section with the required permissions to deploy the solution Make sure all the Prerequisites, such as VPC, S3 bucket, IRIS binaries and license key are in place Click the following link to deploy CloudFormation template (deploys in us-east-1): https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=InterSystemsIRIS&templateURL=https://isc-tech-validation.s3.amazonaws.com/MirrorCluster.yaml for multi-AZ, fault tolerant deployment In ‘Step 1 - Create Stack’, press the ‘Next’ button In ‘Step 2 - Specify stack details’, fill out and adjust CloudFormation parameters depending on your requirements Press the ‘Next’ button In ‘Step 3 - Configure stack options’, enter and adjust optional tags, permissions, and advanced options Press the ‘Next’ button Review your CloudFormation configurations Press the ‘Create Stack’ button Wait approximately 4 minutes for your CloudFormation template to deploy You can verify your deployment has succeeded by looking for a ‘CREATE_COMPLETE’ status If the status is ‘CREATE_FAILED’, see the troubleshooting section in this guide Once deployment succeeds, please carry out Health Checks from this guide Security In this section, we discuss the InterSystems IRIS default configuration deployed by this guide, general best practices, and options for securing your solution on AWS. Data in Private Subnets InterSystems IRIS EC2 instances must be placed in Private subnets and accessed only via Bastion Host or by applications via the Load Balancer. Encrypting IRIS Data at Rest On database instances running InterSystems IRIS, data is stored at rest in underlying EBS volumes which are encrypted. This CloudFormation template creates EBS volumes encrypted with the account-default AWS managed Key, named aws/ebs. Encrypting IRIS data in transit This CloudFormation does not secure Client-Server and Instance-to-Instance connections. Should data in transit encryption be required, follow the steps outlined below after the deployment is completed. Enabling SSL for SuperServer connections (JDBC/ODBC connections): https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=GCAS_ssltls#GCAS_ssltls_superserver. Durable multi-AZ configuration traffic between IRIS EC2 instances may need to be encrypted too. This can be achieved either by enabling SSL Encryption for mirroring: https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=GCAS_ssltls#GCAS_ssltls_mirroring or switching to the r5n family of instances which provides automatic encryption of instance-to-instance traffic. You can use AWS Certificate Manager (ACM) to easily provision, manage, and deploy Secure Sockets Layer/Transport Layer Security (SSL/TLS) certificates. Secure access to IRIS Management Portal By default, the IRIS management portal is accessed only via Bastion Host. Logging/Auditing/Monitoring InterSystems IRIS stores logging information in the messages.log file. CloudFormation does not setup any additional logging/monitoring services. We recommend that you enable structured logging as outlined here: https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=ALOG. The CloudFormation template does not install InterSystems IRIS-CloudWatch integration. InterSystems recommends using InterSystems IRIS-CloudWatch integration from https://github.com/antonum/CloudWatch-IRIS. This enables collection of IRIS metrics and logs from the messages.log file into AWS CloudWatch. The CloudFormation template does not enable AWS CloudTrail logs. You can enable CloudTrail logging by navigating to the CloudTrail service console and enabling CloudTrail logs. With CloudTrail, activity related to actions across your AWS infrastructure are recorded as an event in CloudTrail. This helps you enable governance, compliance, and operational and risk auditing of your AWS account. Reference: https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-user-guide.html InterSystems recommends monitoring of InterSystems IRIS logs and metrics, and alerting on at least the following indicators: severity 2 and 3 messages license consumption disk % full for journals and databases Write Daemon status Lock Table status In addition to the above, customers are encouraged to identify their own monitoring and alert metrics and application-specific KPIs. Sizing/Cost This guide will create the AWS resources outlined in the Deployment Assets section of this document. You are responsible for the cost of AWS services used while running this deployment. The minimum viable configuration for an InterSystems IRIS deployment provides high availability and security. The template in this guide is using the BYOL (Bring Your Own License) InterSystems IRIS licensing model. You can access Pay Per Hour IRIS Pricing at the InterSystems IRIS Marketplace page: https://aws.amazon.com/marketplace/pp/B07XRX7G6B?qid=1580742435148&sr=0-3 For details on BYOL pricing, please contact InterSystems at: https://www.intersystems.com/who-we-are/contact-us/. The following AWS assets are required to provide a functional platform: 3 EC2 Instances (including EBS volumes and provisioned IOPS) 1 Elastic Load Balancer The following table outlines recommendations for EC2 and EBS capacity built into the deployment CloudFormation template, as well as AWS resources costs (Units $/Month). Workload Dev/Test Prod Small Prod Medium Prod Large EC2 DB* m5.large 2 * r5.large 2 * r5.4xlarge 2 * r5.8xlarge EC2 Arbiter* t3.small t3.small t3.small t3.small EC2 Bastion* t3.small t3.small t3.small t3.small EBS SYS gp2 20GB gp2 50GB io1 512GB 1,000iops io1 600GB 2,000iops EBS DB gp2 128GB gp2 128GB io1 1TB 10,000iops io1 4TB 10,000iops EBS JRN gp2 64GB gp2 64GB io1 256GB 1,000iops io1 512GB 2,000iops Cost Compute 85.51 199.71 1506.18 2981.90 Cost EBS vol 27.20 27.20 450.00 1286.00 Cost EBS IOPS - - 1560.00 1820.00 Support (Basic) - - 351.62 608.79 Cost Total 127.94 271.34 3867.80 6696.69 Calculator link Calculator Calculator Calculator Calculator *All EC2 instances include additional 20GB gp2 root EBS volume AWS cost estimates are based on On-Demand pricing in the North Virginia Region. Cost of snapshots and data transfer are not included. Please consult AWS Pricing for the latest information. Deployment Assets Deployment Options The InterSystems IRIS CloudFormation template provides two different deployment options. The multi-AZ deployment option provides a highly available redundant architecture that is suitable for production workloads. The single-AZ deployment option provides a lower cost alternative that is suitable for development or test workloads. Deployment Assets (Recommended for Production) The InterSystems IRIS deployment is executed via a CloudFormation template that receives input parameters and passes them to the appropriate nested template. These are executed in order based on conditions and dependencies. AWS Resources Created: VPC Security Groups EC2 Instances for IRIS nodes and Arbiter Amazon Elastic Load Balancing (Amazon ELB) Network Load Balancer (NLB) CloudFormation Template Input Parameters General AWS EC2 Key Name Pair EC2 Instance Role S3 Name of S3 bucket where the IRIS distribution file and license key are located Network The individual VPC and Subnets where resources will be launched Database Database Master Password EC2 instance type for Database nodes Stack Creation There are four outputs for the master template: the JDBC endpoint that can be used to connect JDBC clients to InterSystems IRIS, the public IP of the Bastion Host and private IP addresses for both IRIS nodes. Clean Up Follow the AWS CloudFormation Delete documentation to delete the resources deployed by this document Delete any other resources that you manually created to integrate or assist with the deployment, such as S3 bucket and VPC Testing the Deployment Health Checks Follow the template output links to Node 01/02 Management Portal. Login with the username: SuperUser and the password you selected in the CloudFormation template. Navigate to System Administration -> Configuration -> Mirror Settings -> Edit Mirror. Make sure the system is configured with two Failover members. Verify that the mirrored database is created and active. System Administration -> Configuration -> Local Databases. Validate the JDBC connection by following the “First Look JDBC” document: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=AFL_jdbc to validate JDBC connectivity to IRIS via the Load Balancer. Make sure to change the url variable to the value displayed in the template output, and password from “SYS” to the one you selected during setup. Failover Test On the Node02, navigate to the Management Portal (see “Health Check” section above) and open the Configuration->Edit Mirror page. At the bottom of the page you will see This member is the backup. Changes must be made on the primary. Locate the Node01 instance in the AWS EC2 management dashboard. Its name will be of the format: MyStackName-Node01-1NGXXXXXX Restart the Node01 instance. This will simulate an instance/AZ outage. Reload Node02 “Edit Mirror” page. The status should change to: This member is the primary. Changes will be sent to other members. Backup and Recovery Backup CloudFormation deployment does not enable backups for InterSystems IRIS. We recommend backing up IRIS EBS volumes using EBS Snapshot - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSSnapshots.html - in combination with IRIS Write Daemon Freeze: https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=GCDI_backup#GCDI_backup_methods_ext. Instance Failure Unhealthy IRIS instances are detected by IRIS mirroring and Load Balancer, and traffic is redirected to another mirror node. Instances that are capable of recovery will rejoin the mirror and continue normal operations. If you encounter persistently unhealthy instances, please see our Knowledge Base and the “Emergency Maintenance” section of this guide. Availability-Zone Failure In the event of an availability-zone failure, temporary traffic disruptions may occur. Similar to instance failure, IRIS mirroring and Load Balancer would handle the event by switching traffic to the IRIS instance in the remaining available AZ. Region Failure The architecture outlined in this guide does not deploy a configuration that supports multi-region operation. IRIS asynchronous mirroring and AWS Route53 can be used to build configurations capable of handling region failure with minimal disruption. Please refer to https://community.intersystems.com/post/intersystems-iris-example-reference-architectures-amazon-web-services-aws for details. RPO/RTO Recovery Point Objective (RPO) Single node Dev/Test configuration is defined by the time of the last successful backup. Multi Zone Fault Tolerant setup provides Active-Active configuration that ensures full data consistency in the event of failover, with RPO of the last successful transaction. Recovery Time Objective (RTO) Backup recovery for the Single node Dev/Test configuration is outside of the scope of this deployment guide. Please refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-restoring-volume.html for details on restoring EBS volume snapshots. RTO for Multi Zone Fault Tolerant setup is typically defined by the time it takes for the Elastic Load Balancer to redirect traffic to the new Primary Mirror node of the IRIS cluster. You can further reduce RTO time by developing mirror-aware applications or adding an Application Server Connection to the mirror: https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=GHA_mirror#GHA_mirror_set_configecp. Storage Capacity IRIS Journal and Database EBS volumes can reach storage capacity. InterSystems recommends monitoring Journal and Database volume state using the IRIS Dashboard, as well as Linux file-system tools such as df. Both Journal and Database volumes can be expanded following the EBS guide https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-modify-volume.html. Note: both EBS volume expansion and Linux file system extension steps need to be performed. Optionally, after a database backup is performed, journal space can be reclaimed by running Purge Journals: https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=GCDI_journal#GCDI_journal_tasks. You can also consider enabling CloudWatch Agent on your instances to monitor disk space (not enabled by this CloudFormation template): https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html. Security certificate expiration You can use AWS Certificate Manager (ACM) to easily provision, deploy, manage, and monitor expiration of Secure Sockets Layer/Transport Layer Security (SSL/TLS) certificates. Certificates must be monitored for expiration. InterSystems does not provide an integrated process for monitoring certificate expiration. AWS provides a CloudFormation template that can help setup an alarm. Please visit the following link for details: https://docs.aws.amazon.com/config/latest/developerguide/acm-certificate-expiration-check.html. Routine Maintenance For IRIS upgrade procedures in mirrored configurations, please refer to: https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=GCI_upgrade#GCI_upgrade_tasks_mirrors. InterSystems recommends following the best practices of AWS and InterSystems for ongoing tasks, including: Access key rotation Service limit evaluation Certificate renewals IRIS License limits and expiration https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=GCM_dashboard Storage capacity monitoring https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=GCM_dashboard. Additionally, you might consider adding CloudWatch Agent to your EC2 instances: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html. Emergency Maintenance If EC2 instances are available, connect to the instance via bastion host. Note: The public IP of the bastion host may change after an instance stop/start. That does not affect availability of the IRIS cluster and JDBC connection. For command line access, connect to the IRIS nodes via bastion host: $ chmod 400 <my-ec2-key>.pem $ ssh-add <my-ec2-key>.pem $ ssh -J ec2-user@<bastion-public-ip> ec2-user@<node-private-ip> -L 52773:1<node-private-ip>:52773 After that, the Management Portal for the instance would be available at: http://localhost:52773/csp/sys/%25CSP.Portal.Home.zen User: SuperUser, and the password you entered at stack creation. To connect to the IRIS command prompt use: $ iris session iris Consult InterSystems IRIS Management and Monitoring guide: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GCM. Contact InterSystems Support. If EC2 instances are not available/reachable, contact AWS Support. NOTE: AZ or instance failures will automatically be handled in our Multi-AZ deployment. Support Troubleshooting I cannot “Create stack” in CloudFormation Please check that you have the appropriate permissions to “Create Stack”. Contact your AWS account admin for permissions, or AWS Support if you continue to encounter this issue. Stack is being created, but I can’t access IRIS It takes approximately 2 minutes from the moment EC2 instance status turns into “CREATE COMPLETED” to the moment IRIS is fully available. SSH to the EC2 Node instances and check if IRIS is running: $iris list If you don’t see any active IRIS instances, or the message “iris: command not found” appears, then IRIS installation has failed. Check $cat /var/log/cloud-init-output.log on the instance to identify any problems with the IRIS installation during instance first start. IRIS is up, but I can’t access either the Management Portal or connect from my [Java] application Make sure that the Security Group created by CloudFormation lists your source IP address as allowed. Contact InterSystems Support InterSystems Worldwide Response Center (WRC) provides expert technical assistance. InterSystems IRIS support is always included with your IRIS subscription. Phone, email and online support are always available to clients 24 hours a day, 7 days a week. We maintain support advisers in 15 countries around the world and have specialists fluent in English, Spanish, Portuguese, Italian, Welsh, Arabic, Hindi, Chinese, Thai, Swedish, Korean, Japanese, Finnish, Russian, French, German, Hebrew, and Hungarian. Every one of our clients immediately gets help from a highly qualified support specialist who really cares about client success. For Immediate Help Support phone: +1-617-621-0700 (US) +44 (0) 844 854 2917 (UK) 0800615658 (NZ Toll Free) 1800 628 181 (Aus Toll Free) Support email: support@intersystems.com Support online: WRC Direct Contact support@intersystems.com for a login. Appendix IAM Policy for EC2 instance The following IAM policy allows the EC2 instance to read objects from the S3 bucket ‘my-bucket’, and write logs to CloudWatch: { "Version": "2012-10-17", "Statement": [ { "Sid": "S3BucketReadOnly", "Effect": "Allow", "Action": ["s3:GetObject"], "Resource": "arn:aws:s3:::my-bucket/*" }, { "Sid": "CloudWatchWriteLogs", "Effect": "Allow", "Action": [ "logs:CreateLogGroup", "logs:CreateLogStream", "logs:PutLogEvents", "logs:DescribeLogStreams" ], "Resource": "arn:aws:logs:*:*:*" } ] } Hi @Anton.Umnikov excellent work on this (and a lot of it too). I was wondering if you can check the stack into an intersystems github repo so I can suggest some changes and additions to the CF Template through a PR? If not I can create one out of band too but thought it would be nice since its available to have it hosted in CC.

I’m excited to announce that InterSystems will be joining the open source community for InterSystems ObjectScript extension to Visual Studio Code. Early this year I posted that we were on a journey to redefine the future of our IDE strategy, and what came out of that is Visual Studio Code is the IDE that can support that future. It’s fast, stable, feature-rich, and built on a modern technology architecture that affords us the ability to offer you far more functionality around your ObjectScript activities than ever before, particularly in the area of DevOps, continuous development, and collaborative programming. The developer community agrees with us, as for the first time in my memory, a product has captured more than half of the market share for general purpose IDEs. The language story is even more striking, with VS Code being used exponentially more than any other IDE. Other than Java, which is still split very evenly, all other developer communities have chosen VS Code. Innovation only happens where there’s a community to support it, and more and more every year, that place is VS Code. In addition to deciding on VS Code as a platform, we’ve also made the significant decision to, instead of building our own extension from scratch, join the open source community to advance the existing effort created by @Dmitry.Maslennikov, who has done an amazing job building a tool with which many are already doing productive ObjectScript work. Our mission for the project is to develop VS Code support for server-side workflows familiar to long-time InterSystems customers, while also offering a client-centric workflow paradigm more in line with the way mainstream programmers think. To be clear, we are not there yet, and getting the existing tool to that point will take time. But we expect to deliver a version of the VS Code extension to ObjectScript that is production quality and supported by InterSystems by the end of the year. Another important point is, Studio will continue to have an important place in our IDE plans for a long time to come. If Studio suits your needs, you have nothing to worry about. It stays the tool of choice for those with the most sophisticated requirements, such the biggest code bases and low-code editing needs. But our development efforts will focus on VS Code. What happens now? The first order of business is to have you try it out and provide feedback. To make that easier we’ll be working hard to make frequent documentation updates on the GitHub project’s wiki. If you find something that doesn’t work, or a feature you’d like to see, please add it to the GitHub issues board. I know many InterSystems users are not familiar with using GitHub, so we’ll be talking a bit about that here in the coming weeks. This is open source You’ve probably noticed that feedback and communications on this product are all happening in the open. This will continue to be open source software, with InterSystems being a major voice in the community, but far from the only voice. Open source principles will underpin all activities around this project, structured by formal governance principles outlined in the governance.md file in the GitHub repository. Here are the highlights: Anyone can post an issue – which is a bug or feature requestabout Anyone can submit a pull request (PR) to add a feature, fix a bug or enhance documentation Committers can approve PRs The Project Management Committee (PMC) approves committers and prioritizes the issues list, thereby setting the project roadmap The PMC is chaired by @Dmitry.Maslennikov and includes 2 InterSystems members and @John.Murray The PMC strives for consensus but requires a simple majority vote What's next Try out VS Code and get your issues in. We’ll be processing that input over the coming weeks to work out a roadmap that will get us to a version 1.0 production release that InterSystems will formally support through normal channels. Learn more about this work, and modernizing development practices in general. CaretDev featuring @Dmitry.Maslennikov will be offering a webinar on April 14th, and InterSystems will have a webinar focused on IDEs in mid-May. We’ll also be posting articles here on various IDE-related topics, such as continuous integration and testing, leveraging the cloud with services such as Azure DevOps, and managing multi-language projects. It’s going to be a very exciting year for development tools in this community, and I’m looking forward to helping you all take your business to new levels! Important links Installation: https://marketplace.visualstudio.com/items?itemName=daimor.vscode-objectscript Documentation: https://github.com/intersystems-community/vscode-objectscript/wiki Issues: https://github.com/intersystems-community/vscode-objectscript/issues Thank you Raj for high evaluation of my work! I am sure with the community support we will make a perfect solution for coding on ObjectScript. Guys, in case you need any support or want to learn more about the solution, do not hesitate to contact me here or on the website caretdev.com VS code for object script as plugin in MS Visual Studio 2017 1. is it possible to add IS object script as plugin to MS VS2017, so I can use normally C#, C++ , JavaScript ... and additionally as plugin with IS IRIS objectscript with full Debug mode ? 2. Hebrew Fonts in the standard VS2017 the Hebrew letters combined with English are working correctly so I expect accordingly , the IRIS plugin will work OK. 3. now installing another VS Code ... (?) I think may harm the MS VS2017 regards Hi Emmanuel, This particular extension is for Visual Studio Code only, at the moment. Different IDEs I hope will come in the future. And possible for Visual Studio as well. VSCode supports Cyrillic, so, don't see any possible issues with Hebrew. Visual Studio Code and Visual Studio are two completely different projects. There is only one thing between them, both developed by Microsoft. Don't be confused by similar names. So, you should not be worried to use VSCode and Visual Studio on the same machine side by side.

[Background] InterSystems IRIS family has a nice utility ^SystemPerformance (as known as ^pButtons in Caché and Ensemble) which outputs the database performance information into a readable HTML file. When you run ^SystemPerformance on IRIS for Windows, a HTML file is created where both our own performance log mgstat and Windows performance log are included. ^SystemPeformance generates a great report, however, you need to extract log sections manually from a HTML file and paste them to a spreadsheet editor like Excel to create a performance visual graph. Many developers already share useful tips and utilities to do it here (This is a Developer Community great article by @Murray.Oldfield ) Now I introduce a new utiltiy ^mypButtons! [What's new compared to other tools] Download mypButtons.mac from OpenExchange. ^mypButtons combines mgstat and Windows performnace logs in one line. For instance, you can create a graph includes both "PhyWrs" (mgstat) and "Disk Writes/sec" (Win perfmon) in the same time frame. ^mypButtons reads multiple HTML files at once and generates a single combined CSV file. ^mypButtons generates a single CSV file into your laptop so it's much easier to crete your graph as you like. ^mypButtons generates a CSV and it includes columns which I strongly recommend to check as the first step to see the performance of InterSystems product. So everyone can enjoy a peformance graph with this utility so easily! Please Note! If you want to play mypButtons.csv, please load SystemPerformance HTML files with "every 1 second" profile. [How to run] do readone^mypButtons("C:\temp\dir\myserver_IRIS_20230522_130000_8hours.html","^||naka") It reads one SystemPerformance HTML file and store the information into a given global. In this sample, it reads myserver_IRIS_20230522_130000_8hours.html and store it into ^||naka. do readdir^mypButtons("C:\temp\dir","^||naka") It reads all of SystemPerformance HTML files under a given folder and store the information into a given global. In this sample, it reads all HTML files under C:\temp\dir and store it into ^||naka. do writecsv^mypButtons("C:\temp\csv","^||naka") It generates the following three csv files under a given folder from a given global. mgstat.csv perfmon.csv mypButtons.csv Here, mypButtons.csv includes the following columns by default, which I strongly recommend to check first to see the performance: mgstat: Glorefs, PhyRds, Gloupds, PhyWrs, WDQsz, WDphase perfmon: Available MBytes, Disk Reads/sec, Disk Writes/sec, % Processor Time This utility works for InterSystems IRIS, InterSystems IRIS for Health, Caché and Ensemble for Windows. [Example steps to create your IRIS server's performance graph with ^mypButtons] (1) First, run ^SystemPerformance to record both our own performance tool mgstat and Windows peformance monitor perfmon. By default, InterSystems IRIS has some profiles so you can enjoy it soon. Try this from IRIS terminal. %SYS> do ^SystemPerformance Current log directory: c:\intersystems\iris\mgr\ Windows Perfmon data will be left in raw format. Available profiles: 　　1 12hours - 12-hour run sampling every 10 seconds 　　2 24hours - 24-hour run sampling every 10 seconds 　　3 30mins - 30-minute run sampling every 1 second 　　4 4hours - 4-hour run sampling every 5 seconds 　　5 8hours - 8-hour run sampling every 10 seconds 　　6 test - 5-minute TEST run sampling every 30 seconds select profile number to run: 3 Please Note! If you want to play mypButtons.csv, please use "every 1 second" profile. By default, you will see "30 mins" profile which samples every 1 second. If you want to create another profiles, see our documentation for more details. (2) After sampling, one HTML will be generated under irisdir\mgr, whose name is like JP7320NAKAHASH_IRIS_20231115_100708_30mins.html. Open a generated HTML, and you will see a lot of performance comma separated data under mgstat and perfmon section. (3) Load it with ^mypButtons as below. USER> do readone^mypButtons("C:\InterSystems\IRIS\mgr\JP7320NAKAHASH_IRIS_20231115_100708_30mins.html","^||naka") This will load HTML in the first parameter and save the performance data into the global in the second parameter. (4) Generate CSV witl ^mypButtons as below. USER> do writecsv^mypButtons("C:\temp","^||naka") This will output three CSV files under the folder in the first parameter from the global in the second parameter. Open mypButtons.csv in the excel, and you can see mgstat and perfmon is in the same line every second. See this screenshot - yellow highlighted columns are mgstat and blue highlighted columns are perfmon. (5) Let's create a simple graph from this CSV. It's so easy. Choose column B Time and column C Glorefs, select Insert menu, 2-D Line graphs as below. This graph will show you "Global Refernce numbers per second" information. Sorry, there were very few activities in my IRIS instance so my sample graph does not excite you, but I do believe this graph from the production server will tell you a lot of useful information! (6) mypButtons.csv includes selected columns which I think you should check first. Murray's article series will tell you why these columns are important to see the performance. [Edit ^mypButtons for reporting columns] If you want to change columns which are reported into mypButtons.csv, please modify writecsv label manually. It reports columns which are defined in this area. I hope my article and utility will make you encourage to check the performance of InterSystems IRIS. Happy SystemPeformance 😆 Very interesting starting point to understand how to collect performance informations. 💡 This article is considered InterSystems Data Platform Best Practice.

Your may not realize it, but your InterSystems Login Account can be used to access a very wide array of InterSystems services to help you learn and use InterSystems IRIS and other InterSystems technologies more effectively. Continue reading to learn more about how to unlock new technical knowledge and tools using your InterSystems Login account. Also - after reading, please participate in the Poll at the bottom, so we can see how this article was useful to you! What is an InterSystems Login Account? An InterSystems Login account is used to access various online services which serve InterSystems prospects, partners, and customers. It is a single set of credentials used across 15+ externally facing applications. Some applications (like the WRC, or iService) require specific activation for access to be granted by the account. Chances are there is are resources which will help you but you didn't know about - make sure to read about all of the options and try out a new tool to help up your technical game!! Application Catalog You can view all services available to you with your InterSystems Login account by visiting that InterSystems Application Catalog, located at: https://Login.InterSystems.com. This will list only those applications or services to which you currently have access. It remembers your most frequently used applications and lists them at the top for your convenience. Make sure to Bookmark the page for easy access to all of these tools in your InterSystems Login Account toolbox! Application Details Now it's time to get into the details of the individual applications and how they can help you as a developer working with InterSystems technologies! Read on and try to find a new application to leverage for the first time in order to improve your efficiency and skills as a developer.... Getting Started - gettingstarted.intersystems.com Audience Anyone wishing to explore using InterSystems IRIS® data platform Description Learn how to build data-intensive, mission-critical applications fast with InterSystems IRIS. Work through videos and tutorials leveraging SQL, Java, C#/.Net, Node.js, Python, or InterSystems ObjectScript. Use a free, cloud-based, in-browser Sandbox -- IRIS+IDE+Web Terminal—to work through tutorials. How it helps Up Your Technical Game Quickly get oriented with InterSystems technology and see it in action with real working code and examples! Explore the use of other popular programming languages with InterSystems IRIS. Online Learning - learning.intersystems.com Audience All users and potential users of InterSystems products Description Self-paced materials to help you build and support the world's most important applications: Hands-on exercises Videos Online Courses Learning Paths How it helps Up Your Technical Game Learn, learn, learn!! Nothing will help you become a more effective developer faster than following a skilled technical trainer as they walk you through new concepts to use in your InterSystems IRIS projects! Documentation - docs.intersystems.com Audience All users and potential users of InterSystems products Description Documentation for all versions of our products Links where needed to external documentation All recent content, is fed through our new search engine. Search page lets you filter by product, version, and other facets. Certain docs require authorization (via InterSystems Login account): AtScale docs available to Adaptive Analytics customers HealthShare docs are available to HealthShare users Make sure to make use of the new dynamic Upgrade Impact Checklist within the Docs server! How it helps Up Your Technical Game Quickly make use of class reference material and API documentation. Find example code. Read detailed usage documentation for parts of InterSystems IRIS into which you need a deeper dive. Request additional detail or report issues direct from within the documentation pages via the "Feedback" feature. Evaluation - evaluation.intersystems.com Audience Those wishing to download InterSystems software or licenses for evaluation or development use Description Downloads of InterSystems IRIS and InterSystems IRIS for Health. Anybody can download Community Edition kits. Existing customers can also request a powerful license to evaluate enterprise features. Preview versions are available pre-release. Early Access Program packages allow people to provide feedback on future products and features. How it helps Up Your Technical Game Try out Preview versions of software to see how new features can help to accelerate your development. Test run Enterprise features by requesting an evaluation license. Make sure all developers in your organization have the latest version of InterSystems IRIS installed on their machines. Provide feedback to InterSystems Product Management about Early Access Features to ensure that they will meet your team's needs once they are fully released. Developer Community - community.intersystems.com Audience Anyone working with InterSystems technology (InterSystems employees, customers, partners, and prospects) Description Monitor announcements related to InterSystems products and services. Find articles on a variety of technical topics. Ask questions and get answers from the community. Explore job postings or developers available for hire. Participate in competitions featuring $1000’s in cash prizes. Stay up to date concerning all things InterSystems! How it helps Up Your Technical Game With access to the leading global experts on InterSystems technology, you can learn from the best and stay engaged with the hottest questions, trends and topics. Automatically get updates in your inbox on new products, releases, and Early Access Program opportunities. Get help from peers to answer your questions and move past blockers. Have enriching discussions with InterSystems Product Managers and Product Developers - learn from the source! Push your skills to the next level by sharing technical solutions and sharing code and gaining from feedback from others. InterSystems Ideas - ideas.intersystems.com Audience Those looking to share ideas for improving InterSystems technology. Description Post ideas on how to make InterSystems technology better. Read existing reviews and up-vote or engage in discussions. InterSystems will take the most popular ideas into account for future product roadmaps. How it helps Up Your Technical Game See your ideas and needs turned into a reality within InterSystems products or open source libraries. Become familiar with the ideas of your peers and learn to use InterSystems products in new ways. Implement ideas suggested by others, new exploring parts of InterSystems technology. Global Masters - globalmasters.intersystems.com Audience Those wishing to advocate for InterSystems technology and earn badges and swag Description Gamification platform designed for developers to learn, stay up-to-date and get recognition for contributions via interactive content. Users receive points and badges for: Engagement on the Developer Community Engagement on the Open Exchange Publishing posts to social media about InterSystems products and technologies Trade in points for InterSystems swag or free training How it helps Up Your Technical Game Challenges bring to your attention articles or videos which you may have missed on the Developer Community, Learning site or YouTube channel - constantly learning new things to apply to your projects! Open Exchange - openexchange.intersystems.com Audience Developers seeking to publish or make use of reusable software packages and tools Description Developer tools and packages built with InterSystems data platforms and products. Packages are published under a variety of software licenses (mostly open source). Integrated with GitHub for package versioning, discussions, and bug tracking. Read and submit reviews and find the most popular packages. Developers can submit issues and make improvements to packages via GitHub pull requests to help push community software forward. Developers can see statistics of traffic and downloads of the packages they published How it helps Up Your Technical Game Don't reinvent the wheel! Use open source packages created and maintained by the InterSystems Community to solve generic problems, leaving you to focus on developing solutions needed specifically by your business. Contributing to open source packages is a great way to receive constructive feedback on your work and refine your development patterns. Becoming a respected contributor to open source projects is a great way to see demand increase for your skills and insights. WRC - wrc.intersystems.com Audience Issue tracking system for all customer reported problems on InterSystems IRIS and InterSystems HealthShare. Customers with SUTA can work directly with the application. Description Worldwide Response Center application (aka “WRC Direct”). Issue tracking system for all customer reported problems. Open new requests. See all investigative actions and add information and comments about a request. See statistical information about your support call history. Close requests and provide feedback about the support process. Review ad-hoc patch files. Monitor software change requests. Download current product and client software releases. How it helps Up Your Technical Game InterSystems Support Engineers can help you get past any technical blocker you have concerning development or systems management with InterSystems products. Report bugs to ensure that issues are fixed in future releases. iService - iservice.intersystems.com Audience Customers requiring support under an SLA agreement Description A support ticketing platform for our healthcare, cloud and hosted customers. Allows for rule driven service-level agreement (SLA) compliance calculation and reporting. Provides advanced facet search and export functionality. Incorporates a full Clinical Safety management system. How it helps Up Your Technical Game InterSystems Support Engineers can help you get past any technical blocker you have concerning development or systems management with InterSystems healthcare or cloud products. Report bugs to ensure that issues are fixed in future releases. ICR - containers.intersystems.com Audience Anyone who wants to use InterSystems containers Description InterSystems Container Registry A programmatically accessible container registry and web UI for browsing. Community Edition containers available to everyone. Commercial versions of InterSystems IRIS and InterSystems IRIS for Health available for supported customers. Generate tokens to use in CICD pipelines for automatically fetching containers. How it helps Up Your Technical Game Increase the maturity of your SDLC by moving to container-based CICD pipelines for your development, testing and deployment! Partner Directory - partner.intersystems.com Audience Those looking to find an InterSystems partner or partner’s product Partners looking to advertise their software and services Description Search for all types of InterSystems partners: Implementation Partners Solution Partners Technology Partners Cloud Partner Existing partners can manage their service and software listings. How it helps Up Your Technical Game Bring in certified experts on a contract basis to learn from them on your projects. License enterprise solutions based on InterSystems technology so you don't have to build everything from scratch. Bring your products and services to a wider audience, increasing demand and requiring you to increase your ability to deliver! CCR - ccr.intersystems.com Audience Select organizations managing changes made to an InterSystems implementation (employees, partners and end users) Description Change Control Record Custom workflow application built on our own technology to track all customizations to InterSystems healthcare products installed around the world. Versioning and deployment of onsite custom code and configuration changes. Multiple Tiers and workflow configuration options. Very adaptable to meet the specific needs of the phase of the project How it helps Up Your Technical Game For teams authorized for its use, find and reuse code or implementation plans within your organization, preventing having to solve the same problem multiple times. Resolve issues in production much more quickly, leaving more time for development work. Client Connection - client.intersystems.com Audience Available to any TrakCare clients Description InterSystems Client Connection is a collaboration and knowledge-sharing platform for TrakCare clients. Online community for TrakCare clients to build more, better, closer connections. On Client Connection you will find the following: TrakCare news and events TrakCare release materials, e.g. release documentation and preview videos Access to the most up-to-date product guides. Support materials to grow personal knowledge. Discussion forums to leverage peer expertise. How it helps Up Your Technical Game Technical and Application Specialists at TrakCare sites can share questions and knowledge quickly - connecting with other users worldwide. Faster answers means more time to build solutions! Online Ordering - store.intersystems.com Audience Operations users at selected Application partners/end-users Description Allow customers to pick different products according to their contracts and create new orders. Allow customers to upgrade/trade-in existing orders. Submit orders to InterSystems Customer Operations to process them for delivery and invoicing. Allow customers to migrate existing licenses to InterSystems IRIS. How it helps Up Your Technical Game Honestly, it doesn't! It's a tool used by operations personnel and not technical users, but it is listed here for completeness since access is controlled via the InterSystems Login Account ;) Other Things to Know About your InterSystems Login Account Here are a few more useful facts about InterSystems Login Accounts... How to Create a Login Account Users can make their own account by clicking "Create Account" on any InterSystems public-facing application, including: https://evaluation.intersystems.com https://community.intersystems.com https://learning.intersystems.com Alternatively, the InterSystems FRC (First Response Center) will create a Login Account for supported customers the first time they need to access the Worldwide Response Center (WRC) or iService (or supported customers can also create accounts for their colleagues). Before using an account, a user must accept the Terms and Conditions, either during the self-registration process or the first time they log in. Alternative Login Options Certain applications allow login with Google or GitHub: Developer Community Open Exchange Global Masters This is the same InterSystems Login Account, but with authentication by Google or GitHub. Account Profile If you go to https://Login.InterSystems.com and authenticate, you will be able to access Options > Profile and make basic changes to your account. Email can be changed via Options > Change Email. Resolving Login Account Issues Issues with InterSystems Login Accounts should be directed to Support@InterSystems.com. Please include: Username used for attempted login Email Browser type and version Specific error messages and/or screenshots Time and date the error was received Please remember to vote in the poll once you read the article! Feel free to ask questions here about apps that may be new to you. Best part for me is having one spot instead of trying to remember the links to all the pieces. Thanks @Mindy.Caldwell - that is the goal! Glad you find it to be useful :) 💡 This article is considered as InterSystems Data Platform Best Practice.

Hi Developers! We are happy to present the bonuses page for the applications submitted to the InterSystems FHIR and Digital Health Interoperability Contest 2024! Project FHIR Server FHIR SQL Builder Digital Health Interoperability LLM AI or LangChain Embedded Python IRIS For Health Instruqt Survey Find a bug in FHIR Server Find a bug in Interoperability Docker IPM Online Demo Community Idea Implementation First Article on DC Second Article on DC First Time Contribution Video on YouTube Total Bonus Nominal 3 3 4 3 2 2 2 2 2 2 2 4 2 1 3 3 40 FHIR-OCR-AI 3 2 2 2 2 11 iris-fhirfy 3 4 3 2 2 2 2 2 2 1 3 26 HL7-FHIR-Cohort-Population 4 3 7 Patient-PSI-Data 2 3 5 fhirmessageverification 2 2 2 6 ai-query 3 3 3 2 3 3 17 iris-hl7 4 2 2 2 2 2 1 3 18 iris-fhir-lab 3 4 2 2 2 2 2 4 2 1 24 Health Harbour 3 3 2 2 2 2 2 3 3 22 Fhir-HepatitisC-Predict 3 3 2 2 2 1 13 Clinical Mindmap Viewer 3 2 2 2 3 11 IRIS WHIZ - HL7v2 Browser Extension 2 3 5 Please apply with your comments for new implementations and corrections to be made here in the comments or in Discord. Hello @Evgeny.Shvarov ! I comleted IRIS For Health Instruqt Survey. Please add points to Health Harbout team for this criteria @Evgeny.Shvarov Evgeny, please add points to Health Harbout team for IPM also. It has some issues with installation. Please fix it. https://prnt.sc/ENdxmkFwsiDM Hi Evgeny,Thanks for sharing Technological Bonuses Results. Please note that iris-fhir-lab application does contain the following functionality:1-Digital Health Interoperability2-Embedded Python3-IRIS For Health Instruqt Survey completed. 4-Online Demo Thanks HI I think the score for IPM needs to be added to fhirmessageverification It has an error during installation. Please fix it Hi! All points added to your app! Demo doesn't work. Instruct will be added little bit later to all participants who passed it HI， thank you for reminding me that I have updated my package. Please note that it needs to be installed in a namespace with fhir server installed this Thank you! I've checked package and added points to your app. Hi Evgeny, I'm sorry, I used FHIR Serve in the application and published an article, but I didn't receive any bonus points for these two items. I just added another article,Please add points to Fhir Heritage C Predict application. hello In my application FHIR-OCR-AI, I used embedded Python and IPM but did not receive a score, and I also used Intersystem fhir server, which also did not receive a score. Is it my mistake in using it? Looking forward to your reply Found a solution. You just need to install with -dev flag. zpm "install health-harbour -dev". Points were added. Hi! Please read Technology Bonuses article again. You don't set up local FHIR server in your app and don't use cloud FHIR server on aws. Thank you, I saw what you updated your ipm module. Now it works. I've added points to your app. Points for new article were added Hi! Thank you! I've just added ponts for ipm and python. Please read Technology Bonuses article again. You don't set up local FHIR server in your app and don't use cloud FHIR server on aws. Hi! I've added points for survey to you. Sorry, I didn't notice this. Thank you for your answer IRIS-FHIRfy second article https://community.intersystems.com/post/iris-fhirfy-new-era-healthcare-interoperability Thank you, @Henrique ! Can you connect it please? Ah, it's connected in series, nevermind. Hi @Evgeny Shvarov ! I also completed IRIS For Health Instruqt Survey. Please add points to the IRIS-FHIRfy team 🇧🇷 Hi @Evgeny.Shvarov / @Semion.Makarov ! I just added an IRIS Interoperability Production show how to use the code generated by IRIS-FHIRfy to convert a simple CSV into FHIR and persist it to IRIS for Health. Evidences could be found here, here or here. Could you add the points for Digital Health Interoperability bonus to IRIS-FHIRfy, please? Thank you! Bonus has been added to your app. @Evgeny.Shvarov @Semion.Makarov The Youtube video made it for IRIS-FHIRfy Hi @Evgeny Shvarov / @Semion Makarov, sorry to bother you guys. I might be mistaken, but I couldn't spot an online demo bonus for the FHIRfy app. However, it seems to be up and running smoothly at https://iris-fhirfy.demo.community.intersystems.com/csp/fhirfy/index.html Hello, I just completed the survey about the interactive InterSystems IRIS Digital Health Interoperability Instruqt Course. I am also missing bonus points for Video and Second Article for iris-hl7. Thank you for your attention :-) Bonuses were added exclude survey. It will be later. Bonuses for a video, demo and survey were added. Sorry to bother you again. I just finished it survey ,thanks HI,Thank you for the reminder. I have updated the application and added the code for installing the intersystem fhir server, as well as the production class using fhir endpoint. In addition, I have completed the survey about the interactive InterSystems IRIS Digital Health Interoperability Instruct Course. Thank you again Ciao Henry, this URL doesn't open for me can you double check? Looks like a typo, this one works: https://iris-fhirfy.demo.community.intersystems.com/csp/fhirfy/index.html thank you

Hey Community, We have excellent news for you! We have prepared a new Instruqt course for you to sink your teeth into: 👉 InterSystems IRIS for Health Interoperability 👈 Here is what you can expect: hands-on experience with InterSystems IRIS for Health build an interoperability use-case scenario from beginning to end on your own accessible to all skill levels Depending on your level of familiarity and expertise, it will take you between 20 and 40 minutes. Ready to get started? Follow the link!

Hi Developers, We invite you to join InterSystems at the European Healthcare Hackathon in Prague Nov 24-26! You can participate online or come to Prague in-person! Registration closes soon - don't hesitate to register. InterSystems will introduce the "Innovate with FHIR" challenge with $$$ prizes for the best use of InterSystems FHIR services. It will be a weekend full of innovation - looking forward to meeting you there! 🤩

Hello, community! I have been tinkering around with Flutter lately and, as a result, came up with some apps that can use Firebase as a database. When I realized there was an available Python library, I felt the urge to create something for InterSystems IRIS that would communicate with the Firebase RealTime Database and perform CRUD operations. Later, I stumbled upon the following idea from Evgeny in the portal: https://ideas.intersystems.com/ideas/DP-I-146 That is when I got down to work! Are you curious to see my findings? Then buckle up because we’re about to take off! Yet, let’s take it easy, step by step. Step 1 - What in the nerdland is Firebase? Well, Firebase Realtime Database (henceforth RTDB) is a cloud-hosted, NoSQL database service that enables developers to store and synchronize data in real time across users. It provides all connected devices with automatic updates when changes occur within the database. It is perfect for real time applications since alterations made by one user get instantly reflected on other users' devices. Are you still with me on this wild ride? Alright, let the adventure begin then! Step 2 - Let’s whip up our app in Firebase! 🚀🔥 Go to https://console.firebase.google.com/ and log in or register. You will need to have a Google account to do it. Once inside, press the “Add project” button: Let’s give our project a name: Now, you can decide whether or not you want to enable Google Analytics (I disabled it). Wait for a few seconds until the project gets created: After a short wait, it will be completed. Congrats!! Your Firebase Application is finally alive and kicking!! Step 3 - Creating our Realtime Database: At this point, click “Products” and then “Realtime Database”. Ultimately, click “Create Database”. Select the location: Pick the rules. (There are two options: Locked mode, where only authenticated users can make operations, or Test mode, where anyone who knows the URL of the database can perform CRUD operations.) In this case, we will opt for the locked mode. So, make your choice and press Enable. Wait for a few seconds for the database to be ready. Once the database is good to go, copy the URL and save it for later. It's time to set up the rules to admit only authorized connections: These are my rules: With those rules, you will keep unauthorized users at bay The code version would like like the following: { "rules": { "$uid": { ".write": "auth.uid == $uid", ".read": "auth.uid == $uid" } } } We’re almost done here! Only one last step is left in Firebase! Step 4 - Generating our Certification file: Go to the Project Settings section: Then proceed to the tab Service accounts, select Python, and press “Generate new private key”. Save the file because we will need it later. Step 5 - Clone the repository or install IrisFirebase with ZPM: Repository: https://github.com/daniel-aguilar-garcia/irisfirebase ZPM package: iris-firebase Step 6 - Let’s configure Firebase on InterSystems: First, copy your credential file that you downloaded from Firebase in Step 4: If you are using the Docker version, copy the file in the path of the project and update the file name in the Dockerfile file: Once you have performed the steps mentioned above, start the Docker file! On the other hand, if all you want to do is to add the module to your server, make sure you have copied the credential file to a path that the IRIS server can access. Step 7 - Let the magic flow! Now, we are ready to set up the connection with our Firebase App. Open a Terminal and run the following command: do ##class(Firebase.RTDB).ConfigApp(appName,url,credentialFile) Parameters explanation: appName: any random name that popped into your head. (Remember not to forget it) xD URL: your RTDB URL (the one you copied in step 3) credentialFile: your credential file name, including the extension .json Example: do ##class(Firebase.RTDB).ConfigApp("myApp","https://irisfirebaseexample-default-rtdb.firebaseio.com/","irisfirebaseexample.json") Congratulations! That is a wrap! I hope you enjoyed it. Catch you up in my next article! What?.. Not enough?.. Just kidding! Let’s get down to the fun stuff! Step 8 - Creating our first MegaWonderMagic register: In order to create a new register, you will only need 4 following things: Your appName The data you want to save (It is a JSON object) The table (node) name The ID Example: ClassMethod TestCreate() { Set objTest = {} Set objTest.title = "Title the title" Set objTest.detail = "The dummy message" Set id = "00001" Set id=##class(Firebase.RTDB).Create("appNotas",objTest,"notes",id) U 0 w id,! Q id } The result should looks like this: Have you noticed that? There is something familiar… But… What exactly?... What would happen if we presented the information as shown below? ^notes(“00001”,”detail”)=”The dummy message” ^notes(“00001”,”title”)=”Title the title” Exactly! It is a global! As you can see, it seems that the whole world has finally realized that the relational table system has become obsolete, and now everyone is leaning towards an approach similar to our beloved Globals ;-) Step 9 - Reading registers: We can read a single register or a complete node in the following way: Reading a single register would look like this: It’s easy. You only need to call the Read method, indicating the application, table (node), and ID. ClassMethod TestRead() { Set id = "00001" //..TestCreate() Set response=##class(Firebase.RTDB).Read("appNotas","notes",id) U 0 w response.title,! U 0 w response.detail,! } Check out the result below: Now let’s add some extra registers: It is time to read the node notes to get all the details: ClassMethod TestReadFullTable() { Set response = {} Set response=##class(Firebase.RTDB).ReadTable("appNotas","notes") U 0 w response.%ToJSON(),! } Here comes the result: Step 10 - Updating data: Updating a register is a piece of cake!, Simply pass the app name, table name (node), ID, and data object Example: ClassMethod TestUpdate() { Set id = "00001" //..TestCreate() Set objTest = {} Set objTest.title = "Title updated" Set objTest.detail = "Text message updated" Set id=##class(Firebase.RTDB).Update("appNotas","notes",id,.objTest) U 0 w id,! } Take a look at the miraculous result: Great!. Now let’s give those silly grades what they deserve! Step 11 - Deleting registers: We are going to delete the register with the ID “00002” ClassMethod TestDelete() { Set id = "00002" //..TestCreate() Set res=##class(Firebase.RTDB).Delete("appNotas","notes",id) U 0 w res,! } Ready! Now the silly note “00002” is sleeping at the bottom of the ocean. If you wish to send the whole node to uncle Calamardo, you can omit the ID parameter: ClassMethod TestDeleteNode() { Set res=##class(Firebase.RTDB).Delete("appNotas","notes") U 0 w res,! } Goodbye, notes! To sum up: Create register: ##class(Firebase.RTDB).Create("appName",objData,"tableName",id) Update register: ##class(Firebase.RTDB).Update("appName","tableName",id,.objTest) Read a single register: ##class(Firebase.RTDB).Read("appName","tableName",id) Read the whole node: ##class(Firebase.RTDB).ReadTable("appName","tableName") Delete a single register: ##class(Firebase.RTDB).Delete("appName","tableName",id) Delete the whole node: ##class(Firebase.RTDB).Delete("appName","tableName") That is all, folks! (for now) Other interesting Firebase modules could be leveraged by extending this module, including the following: Authentication Cloud Firestone Storage Cloud Messaging … Are you interested in any of them? Please let me know your opinion in the comments (they are always welcome). Did you enjoy the article? Then give me a thumbs-up!! And remember, I will clear all your doubts to the best I can if you write them in the comment section. Thanks for reading!

Hi Community, Thank you for participating in our recent mini-contest! We received many great ideas, and we hope you enjoyed the process. The mastermind of the winning concept will receive 5,000 points, while the astute "investors" in said concept will receive 200 points each. The Winning Concept: Senior people loneliness Loneliness experiences by older people and lack of conversations can negatively impact their mental well-being, concerning their families about difficulties in being able to ask for help on their own. The Mastermind: Marcelo Dotti The astute "investors": Cecilia Brown, Danny, Udo, Lars Barlow-Hansen, Ahmed Tgarguifa, Jimmy N., Dinesh Babu Congratulations to all!

InterSystems announces its fourth preview, as part of the developer preview program for the 2023.2 release. This release will include InterSystems IRIS and InterSystems IRIS for Health. Highlights Many updates and enhancements have been added in 2023.2 and there are also brand-new capabilities, such as Time-Aware Modeling, enhancements of Foreign Tables, and the ability to use Ready-Only Federated Tables. Note that some of these features or improvements may not be available in this current developer preview. Another important topic is the removal of the Private Web Server (PWS) from the installers. This feature has been announced since last year and will be removed from InterSystems installers, but they are still in this first preview. See this note in the documentation. --> If you are interested to try the installers without the PWS, please enroll in its EAP using this form, selecting the option "NoPWS". Additional information related to this EAP can be found here. Future preview releases are expected to be updated biweekly and we will add features as they are ready. Please share your feedback through the Developer Community so we can build a better product together. Initial documentation can be found at these links below. They will be updated over the next few weeks until launch is officially announced (General Availability - GA): InterSystems IRIS InterSystems IRIS for Health Availability and Package Information As usual, Continuous Delivery (CD) releases come with classic installation packages for all supported platforms, as well as container images in Docker container format. For a complete list, refer to the Supported Platforms document. Installation packages and preview keys are available from the WRC's preview download site or through the evaluation services website (use the flag "Show Preview Software" to get access to the 2023.2). Container images for both Enterprise and Community Editions of InterSystems IRIS and IRIS for Health and all corresponding components are available from the new InterSystems Container Registry web interface. For additional information about docker commands, please see this post: Announcing the InterSystems Container Registry web user interface. The build number for this developer preview is 2023.2.0.204.0. For a full list of the available images, please refer to the ICR documentation. Alternatively, tarball versions of all container images are available via the WRC's preview download site.

Hello Community, The Certification Team of InterSystems Learning Services is excited to announce the release of our new InterSystems HL7® Interface Specialist Recertification Project! If you hold the InterSystems HL7 Interface Specialist certification AND your certification's expiration date is within 6 months of today's date, you can get recertified by successfully completing the recertification project. Completing an InterSystems recertification project is one of two options a certification candidate can choose to get recertified (the other option is to take the new version of the exam).The project contains a set of performance-based exercises to complete in a virtual environment (VM), and is open-book, open-internet, etc. The only resource that is not allowed is consulting with another human. Please visit the linked page above to learn more details about the project! The project is now available for purchasing and scheduling in InterSystems Certification's exam catalog. Candidates who successfully complete the project will have the expiration date of their digital certification badge extended by 5 years from the date of successful project completion. To learn more about recertification, please visit the following pages: Renewing InterSystems Certifications for general recertification policy information. InterSystems Recertification Projects for general information about recertification projects, including important details regarding buying and scheduling projects. Please contact us at certification@intersystems.com if you have any questions. Thank you,InterSystems Certification Team

Hello Everyone, The Certification Team of InterSystems Learning Services is developing an InterSystems IRIS Developer Professional certification exam, and we are reaching out to our community for feedback that will help us evaluate and establish the contents of this exam. Note: This exam will replace the current InterSystems IRIS Core Solutions Developer Specialist exam when it is released. Please note from the target role description below that the focus of the new exam will be more on developer best practices and a lot less on the ObjectScript programming language. How do I provide my input? Complete our Job Task Analysis survey (JTA)! We will present you with a list of job tasks, and you will rate them on their importance as well as other factors. How much effort is involved? It takes about 20-30 minutes to fill out the survey. You can be anonymous or identify yourself and ask us to get back to you. How can I access the survey? You can access it here Survey does not work well on mobile devices - you can access it, but it will involve a lot of scrolling Survey can be resumable if you return to it on the same device in the same browser - answers save with the Save/Next button Survey will close on March 8, 2024 What’s in it for me? You get to weigh-in on the exam topics for our new developer exam AND you will be entered in a raffle where 15 lucky winners will be given a $50 Tango* card (Available for US-based participants. InterSystems and VA employees are not eligible). Tango cards are a popular digital reward platform that provides a wide selection of e-gift cards from various retailers. Here are the exam title and the definition of the target role: InterSystems IRIS Developer Professional A back-end software developer who: writes and executes efficient, scalable, maintainable, and secure code on (or adjacent to) InterSystems IRIS using best practices for the development lifecycle, effectively communicates development needs to systems and operations teams (e.g., database architecture strategy), integrates InterSystems IRIS with modern development practices and patterns, and is familiar with the different data models and modes of access for InterSystems IRIS (ObjectScript, Python, SQL, JDBC/ODBC, REST, language gateways, etc.). At least 2 years of experience developing with InterSystems IRIS is recommended. Any code samples that include InterSystems IRIS classes will have methods displayed in both ObjectScript and Python (or SQL).

Hi Community, We're pleased to invite you to join the upcoming InterSystems IRIS 2020.1 Tech Talk: API-First Development on May 5 at 10:00 AM EDT! In this week's InterSystems IRIS 2020.1 Tech Talk, we'll discuss API-first development and how InterSystems is embracing this industry trend with our API Manager, and specifically with our FHIR offerings. First, we'll talk about InterSystems API Manager. This tool controls your web-based API traffic in a single location. You can throttle throughput, configure payload sizes and whitelist/blacklist IPs, among many other features. FHIR stands for Fast Healthcare Interoperability Resources. Release 4 brings this HL7 standard to maturity, and the FHIR R4 support in InterSystems IRIS for HealthTM is big. You'll learn how to work with FHIR data in InterSystems IRIS, and see our developer portal in action, where you can access FHIR resources using the OpenAPI specification. Speakers:🗣 @Patrick.Jamieson3621, Product Manager, Health Informatics Platform🗣 @Craig.Lee, Product Specialist 🗣 @Stefan.Wittmann, Product Manager Date: Tuesday, May 05, 2020Time: 10:00 AM EDT ➡️ JOIN THE TECH TALK! Additional Resources: What is InterSystems API Manager? API Manager: Gummy Bear Factories Using FHIR APIs to View Resources Setting Up RESTful Services Interoperability for Health Overview Code sample: samples-integration-FHIR covid-19-challenge

Hi Community! We are pleased to invite you to the upcoming webinar in Spanish: "How to implement integrations with .NET or Java on InterSystems IRIS" / "Cómo implementar integraciones con .NET o Java sobre InterSystems IRIS" on May 20 at 4:00 PM CEST! What will you learn? PEX (Production EXtension Framework), its architecture and its API, and how to develop an integration with Java or .NET, in order to rich the InterSystems IRIS pre-built components Some simple examples in .NET A more complex example, using PEX to add an existing client library and access to external services Speaker: @Pierre-Yves.Duquesnoy, Sales Senior Engineer, InterSystems Iberia Note: The language of the webinar is Spanish. We are waiting for you at our webinar! ✌🏼 PLEASE REGISTER HERE! Is the video of this webinar available for viewing? Hi David, This webinar recording is already available on InterSystems Developer Community en español. Enjoy watching this video)