In a fresh IRIS Community Edition container if we create a new Database and after we create a new Namespace enabling it for interoperability then we will see the message "ERROR #68: the mounted database count exceeds license limit"
Good News!! You can use now the Free InterSystems IRIS Community Edition in the AWS Cloud
Hello,
It's very common that people new in InterSystems IRIS want to start to work in a personal project in a full free environment. If you are one of this, Good News!! You can use now the Free InterSystems IRIS Community Edition in the AWS Cloud.
Here I’ll walk you through the process of creating a simple Node/Express API and connect it to a InterSystems IRIS instance.
I won't go into much detail about how to work with any of the technologies I will mention in this tutorial but I will leave links, in case you want to learn more.
The objective here is to give you a practical guide on how to set up and connect a node.js back-end API to IRIS.
Before we get our hands dirty, make sure you have Node.js running on your machine. So I'll check:
InterSystems IRIS 2019 is going to introduce new and exciting features. One of the areas with new interesting must-to-know things is the API Management.
I want do to a "simple thing". Show a dynamic log of actions in the browser as we can see on Terminal. For that, I guess to make a simple CSP Page that show a new line every WRITE command is the thing I need.
But how I refresh after each WRITE?
How I can refresh the content automatically?
I made a simple CSP Page and in method OnPage I do this test:
write "Start..",! for i=1:1:10{ hang 1 write "Doing "_i,! }
Usually I recommend to set the global buffer (GB) as large as possible in order to maintain in memory more globals as possible. I don't know if this is a standard recommendation, but I want to discuss what should be the best buffer size for a Ensemble instance that only process messages.
In some project, I found the need to use SMIME format https://www.ietf.org/rfc/rfc3851.txt, basically is an standard used to wrap a message together with its signature using a certificate (usually X509). Ensemble don't have a single class to do that but inside the Ensemble installation we have the openssl utility, so in this example I use the "openssl smime" command to sign or verify a message.
The example has two Business Process that able to sign or verify and in order to test I made a simple production.