Hi Rubens!

I'm glad that you are considering it! ZPM is a very powerful and helpful tool.

  • Is ZPM client compatible with Caché 2017.x versions?

it's not at the moment. But it's an open project, you can add this support if you want. And send the PR then.

  • Can we configure a self-hosted registry that doesn't require a GitHub repository link?

Yes you can. You can setup your own registry - here is how.

You can alter the registry in ZPM client, and create, pack, and publish and then install it from the alternative registry, e.g. your corporate registry.

  • Could the ZPM client zip and upload the whole package (all classes, routines, includes) instead of downloading it from a Github link?

YES. 

  • Can we declare a module that specifies classes themselves instead of their package counterpart? e.g. My.Class.CLS instead of My.PKG.

Sure. See the article and an Example.

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.

HTH

Also, there are some analytics tools published in Open Exchange:

Bridge Works VDM , a commercial tool by Bridge Works, tagging @Tony Coffman for details.

OUReports, commercial tool by Yanbor.

Also check the plugins from @Peter Steiwer: Peter recently submitted several DeepSee IRIS Analytics add-ons that enhance/simplify the life of InterSystems BI developer.

HTH

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. 

HTH 

Hi Scott!

There is no need to integrate IRIS with Github. It's more about how the IDE you are using to develop IRIS solutions is integrated with Github. And the majority of modern IDE are integrated with Github already: VSCode goes with Git/Github integration out of the box ( and I believe Visual Studio too (as soon as Github is Microsoft now too).

If the question is how you can develop IRIS solutions having the code managed in Github there are a lot of approaches. You can check these videos made by myself which illustrate:

How to create IRIS Application in Github, develop it in VSCode and commit changes into the repo

How to collaborate and make changes to an already existing project in Github repo using Github Flow

And:

Atelier can be integrated with Git 

Studio also has the integration with Git

Hi, Rubens!

PS: Evgeny, what do you think of adding a Post type called Information? I think the one I used is not adequate, but I had no options since the other types seemed lesser adequate.

Thank you! It's a good idea.  You always can submit a feature request for DC. I would say that this looks like a public discussion around product feature requests, right? To have DC as a sort of idea-portal.

Maybe we'll introduce something like this. But in order to have this more than conversation and to have some follow up on product development, we need to discuss it with Product management.

For now, I think this is more of type Question than Article.