Hi Norbert!

This is not the advice on how to uninstall or reinstall, sorry.  I'm on Mac and my advice not to install IRIS but use docker images for Development in IRIS. With this approach, you can use any version of IRIS with your code just changing the line of the image.

There are zillion examples and templates on Open Exchange, but you could start with this one., probably the simplest.

One of the options - don't use USER namespace.

Why bother to deal with USER at all? Much more productive and cleaner approach - build your namespace and base from scratch.

That's why we create a new IRISAPP namespace and database in every template: e.g. objectscript, rest or ZPM package template. 

With this infrastructure-as-a-code approach, you know for sure what is the namespace, mappings, security, database, users are in the namespace because it is you who creates it.

Oh, sorry about that! Here is the valid string:

docker run --name my-iris --publish 9092:52773 -d intersystemsdc/iris-community:2020.

and then 

$ docker exec -it my-iris iris session IRIS

and to run zpm:



IRIS Analytics. (DeepSee) is included even in IRIS Community Version by default so you are welcome to try.

3 easiest ways to try:

1. download IRIS Community version as @Robert Cemper mentioned.

2. Launch Try IRIS instance

3. Docker pull the image

4. Run an instance of IRIS on a cloud you like: Azure, AWS, GCP.

You have IRIS Analytics with Community Edition but you probably want to try something working.

Samples BI is not included but could be installed.

The easiest way to install is to use ZPM.

Or even to launch a docker image with ZPM on board and install Samples-BI with one command.

Also, I can recommend trying AnalyzeThis by @Peter Steiwer  - it's a nice tool to generate a cube+pivot+dashboard vs arbitrary csv file.


Hi Peter!

Thanks for the question.

It makes a lot of sense to test your package before publishing it on ZPM-registry.

You can test it via 'load' and 'publish' commands of ZPM-client.

Suppose, you have IRIS with ZPM client installed and you have the repo folder locally with module.xml in the root. Then you can use following command to test the module.xml loading:

USER:zpm>load /yourfolder/withrepo/

or with -v with more details:

USER:zpm>load -v /yourfolder/withrepo/

It shows the log and if module.xml is not correct you'll see errors in the log. This is the test of resources description.

Then you can test the publisher with 'publish' command. Call:

USER:zpm>packagename publish

or with -v with more details:

USER:zpm>packagename publish -v

This will try to execute all the tests, run web-app settings and call invoke methods locally. This will then refuse to publish cause you don't have the registry locally - which is OK, because you don't want to publish locally, right? All other errors will tell you if something is wrong with your module.xml package. 


Hi Kevin!

The simplest solution is to create a Dimension which filters data upon Users or Roles and then implement %OnGetFilterSpec callback in a cube class where you can set up a filter additional filter for the queries to the cube on this user session upon $USERNAME or $ROLE variables of the logged user.