SAM was built as a "gateway" to proper custom Prometheus/Grafana setup for cases when you only need to monitor IRIS. If you are building more complex solution, with non-InterSystems sources, I would recommend to set up Prometheus separately from SAM and just add SAM monitoring endpoints there.

Hi Michael,

You should have one top-level dispatch class which will dispatch individual API calls to separate endpoint classes.

This is true for this particular version of Ensemble, but in IRIS this behaviour has changed -- even Embedded queries are using Dynamic SQL now. See discussion here https://community.intersystems.com/post/what-happened-embedded-sql

Hi Tom,

You need to contact TRC for this one, since it will depend slightly on the Version and Edition you are using, and will most probably involve some custom code to map your AD role structure into TrakCare's security groups. They will be able to guide you in the right direction.

Cheers
Sergei Shutov
Banksia Global
https://banksiaglobal.com

Hi Evgeny, this is very much dependent on how you log in :)

If you are using "basic auth" method directly from browser (where it will prompt you for login/password once), you can change username by using "username@" in address bar, for example

http://userB@127.0.0.1/my/api/

Hope this helps!
=Sergei Shutov
Banksia Global | https://banksiaglobal.com

In your case sigalg will be RS256 instead of HS256 and you'll need to call ##class(%OAuth2.JWKS).AddX509 instead of ##class(%OAuth2.JWKS).AddOct to use your private RSA keys.

It's definitely a bit of a challenge, but should be doable!

Hi Muhammad,

You should look at csvgen package by @Evgeny Shvarov https://github.com/evshvarov/csvgen

There are a few examples of importing data from GitHub on the home page. You can have a look at the source code to see how it's done if you need more flexibility.

Hi Sai Sai,

One thing you might look into in regards to distribution and deployment is ZPM Package Manager https://github.com/intersystems-community/zpm . It's still under active development, but is already very usable at the moment, you can use it with a self-hosted open source private registry https://github.com/intersystems-community/zpm-registry/ and my consultancy is currently developing a commercial hosted version which will be announced at Virtual Summit next month.

There is an example of an Interoperability packaging at GitHub: https://github.com/intersystems-community/iris-interoperability-template

In terms of deployment, unless you have MASSIVE productions, I would recommend to deploy the whole thing at once even if not everything has changed -- it's just a lot less moving parts and options for errors this way, and you can test deployments on your test server as many times as you like.

Hope this helps!

Sergei Shutov
Managing Director, Banksia Global
https://banksiaglobal.com

You can use %IGNOREINDEX and %NOINDEX keywords, have a look here in documentation

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...

Did you try to rebuild indices and purge cached queries?

Also, have a look at the execution plan in the Management portal -- it will tell you which indices it uses and how it builds a result.