Respuestas

No, it is not for multiple reasons. We have plans to publish the InterSystems API Manager on Docker Repositories at a later point, but I can't give you an ETA.

Yes. The first release of InterSystems IRIS that supports IAM and is available on all platforms is 2019.1.1.

Alexander has provided the correct answer, you have to unpack the archive first. The reason is that the IAM distribution includes more than just a docker image, but also a readme file and various scripts to make your life easier. That's the reason why the WRC Distribution page lists IAM in the components section and not together with the other containers (like ICM).

I updated the announcement adding a link to the technical introduction which I just published. Enjoy! :)

Hi Vikram,

all answers are perfectly fine, but I would like to add that if you are new to ZEN (and have to build up your knowledge) and want to build a web application, I would advise you to build your APIs via JSON over REST and develop a web application using one of the many popular web frameworks like Angular, React or Vue.js, depending on the requirements of your application and your personal style.

ZEN is not actively enhanced anymore and you might run into undesired behavior with recent browser versions that are hard to control.

Best,

Stefan

Hi Duncan,

great to hear that you find the community edition beneficial! We are currently working on making the IRIS for Health Community Edition available on the docker store as well. I can't give you an exact time window, but it shouldn't be too far away. Stay tuned, it will be announced on the developer community when it is available.

As Sylvain has pointed out, you can always pull the images from the WRC Distribution page if you are a registered partner. The offerings on AWS, Azure or GCP can still be helpful with zero cost, as you often get a voucher when you sign-up for a new account. Enough for playing around for sure.

Best,

Stefan

Hi Juha,

IAM is only available in container format and we have no plans to change that at this point in time. I would like to understand the background of your question. Would you prefer a regular installer and if so, why?

Thanks,

Stefan

You have various options, depending on what you want to achieve:

  1. Added a property of type %DynamicObject or %DynamicArray to a persistent class
  2. Store the JSON content in the Document Data Model
  3. Parse a JSON structure as Eduard indicated and generate the corresponding persistent class(es).
  4. I would not advise to use %Document.Object. Use the Document Model instead.

With option 1) and 2) you don't need to define a schema at all, but can easily persist and manage your JSON content as objects. No SQL access to individual properties of the JSON content for option 1). With the document data model you can add support for SQL queries for individual JSON paths.

Option 3) is work, but doable. Figuring out the correct datatypes will be the greatest challenge. If you have JSON schema instead, your life is much simpler. 

Glad to hear you were able to make it work. Debugging these issues can be really painful. Emulators help as you can easily work with the debugger, but emulators only tell you half the story...

I usually debugged and tested these scenarios on a real device, connected to the IDE on my laptop, which allows you to see exactly what is going on via the output window and the debugger of your IDE.