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 Lawrence!

Does your issue relates to DeepSee Dashboards UI or to the MDX query performance?

And you are able to redeem the voucher for certification attempt with GM points! See the announcement.

Already 9 available ;)

Hi Sergey! Sounds exciting!

Anything more than picture? E.g. URL, demo, code sample?

For those who participate in ObjectScript Advent of Code 2019: there is an opportunity to receive an attempt for the certification exam for free!

Be one of the top 3 performers in the competition and get a voucher for the certification exam!

The current leaderboard is the following:

And you still have 2 weeks to change the leaderboard!

*The option is not eligible for InterSystems employees so your chances to win are higher! ;)

Advent Of Code 2019 reached its equator!

Here is the current top-20 list:

We decided to raise the odds in the competition and we are adding a new prize for winners - 3 vouchers for InterSystems Certification Exams!

Top-3 participants will get the voucher for any of the two exams available! 

*The option is not eligible for InterSystems employees.

Hi Nikita!

Thanks for the good question!

The answer is on why module.xmlvs installer.cls on projections is quite obvious IMHO.

Compare module.xml and installer.cls which does the same thing.

Examining module.xml you can clearly say what the installation does and easily maintain/support it.

In this case, the package installs:

1. classes from WebTerminal package:

<Resource Name="WebTerminal.PKG" />

2. creates one REST Web app:

 <CSPApplication 
        Url="/terminal"
        Path="/build/client"
        Directory="{$cspdir}/terminal"
        DispatchClass="WebTerminal.Router"
        ServeFiles="1"
        Recurse="1"
        PasswordAuthEnabled="1"
        UnauthenticatedEnabled="0"
        CookiePath="/"
      />

3. creates another REST Web app:

    <CSPApplication 
        Url="/terminalsocket"
        Path="/terminal"
        Directory="{$cspdir}/terminalsocket"
        ServeFiles="0"
        UnauthenticatedEnabled="1"
        MatchRoles=":%DB_CACHESYS:%DB_IRISSYS:{$dbrole}"
        Recurse="1"
        CookiePath="/"
      />

I cannot say the same for Installer.cls on projections - what does it do to my system?

Simplicity, transparency, and installation standard with zpm module.xml approach vs what?

Hi Jeff!

Thanks! When the new release will be available on Docker Hub?

WOW.

Rob, do you plan to share videos on that?

With explanations on all the multi model parts?