· Feb 15, 2020 5m read

Setting Up Your Own InterSystems ObjectScript Package Manager Registry

Hi Developers!

As you know the concept of ObjectScript Package Manager consists of ZPM client - client application for IRIS which helps you to install packages from the registry. And the code which works "on the other side" is  ZPM Registry - server which hosts packages and exposes API to submit, list and install it. Now when you install the ZPM client it installs packages from community package registry, which si hosted on

But what if you want your own registry? E.g. you produce different software packages for your clients and you want to distribute it via private registry?  Also, you may want to use your own registry to deploy solutions with different combinations of packages.

Is it possible? The answer is YES! You can have it if you deploy ZPM registry on your server with InterSystems IRIS.

To make it happen you would need to set up your own registry server.

How to do that?

ZPM Registry can be installed as a package zpm-registry. So you can install zpm-client first (article, video), or take a docker-image with zpm-client inside and install zpm-registry as a package:

zpm: USER>install zpm-registry

When zpm-registry is  installed it introduces the REST end-point on server:port/registry with a set of REST-API routes. Let’s examine it and let's open the GET requests on community registry as an example.


- root entry shows the version of the registry software.




- entry to check the working status. 


- swagger spec entry


- displays all the available packages.



- the set of GET entries for package deployment. ZPM client is using it when we ask it to install a particular package.


- POST entry to publish a new package from the Github repository.

This and all other API you can examine e.g. in full documentation online generated with the help of /_spec entry:


OK! Let's install and test ZPM-registry on a local machine.

1. Run docker container with IRIS 2019.4 and preinstalled ZPM-client (from developer community repo on docker hub).

% docker run --name my-iris -d --publish 52773:52773 intersystemsdc/iris-community:2019.4.0.383.0-zpm
% docker exec -it my-iris iris session IRIS

Node: f40a06bd81b9, Instance: IRIS

USER>zn "%SYS"

%SYS>Do ##class(Security.Users).UnExpireUserPasswords("*")

%SYS>zn "USER"

zpm: USER>install zpm-registry

[zpm-registry]    Reload START
[zpm-registry]    Reload SUCCESS
[zpm-registry]    Module object refreshed.
[zpm-registry]    Validate START
[zpm-registry]    Validate SUCCESS
[zpm-registry]    Compile START
[zpm-registry]    Compile SUCCESS
[zpm-registry]    Activate START
[zpm-registry]    Configure START
[zpm-registry]    Configure SUCCESS
[zpm-registry]    Activate SUCCESS
zpm: USER>

2. Let’s publish a package in our new privately-launched zpm-registry. 

To publish a registry you can make a POST request on registry/package end-point and supply the URL of the repository, which contains module.xml in the root. E.g. let's take the repo of objectscript-math application on Open Exchange by @Peter Steiwer

$ curl -i -X POST -H "Content-Type:application/json" -u user:password -d '{"repository":""}' 'http://localhost:52773/registry/package'

make sure to change the user and password to your credentials.

HTTP/1.1 200 OK
Date: Sat, 15 Feb 2020 20:48:13 GMT
Server: Apache
EXPIRES: Thu, 29 Oct 1998 17:04:19 GMT
PRAGMA: no-cache
Content-Type: application/json; charset=utf-8

As we see, the request returns 200 which means the call is successful and the new package is available in the private registry for installation via ZPM clients. Let’s check the list of packages again:

Open in browser http://localhost:52773/registry/packages/-/all:


Now it shows us that there is one package available.

That’s perfect!

Next question is how to install packages via ZPM client from an alternative repository.

By default when ZPM client is being installed it’s configured to work with public registry

This command shows what is the current registry set up:

zpm: USER>repo -list  

    Enabled?    Yes
    Available?    Yes
    Use for Snapshots?    Yes
    Use for Prereleases?    Yes

zpm: USER>

But this could be altered. The following command changes the registry to your one:

zpm: USER>repo -n registry -r -url http://localhost:52773/registry/ -user usernname -pass password

Change here username and password to what is setup on your server available for /registry REST API.

Let’s check that alternative registry is available:

zpm: USER>repo -list                                                                       

    Source:     http://localhost:52773/registry/
    Enabled?    Yes
    Available?    Yes
    Use for Snapshots?    Yes
    Use for Prereleases?    Yes
    Username:     _SYSTEM
    Password:     <set>

zpm: USER>

So ZPM client is ready to work with another ZPM registry.

So, ZPM registry lets you build your own private registries which could be filled with any collection of packages either from public or from your own.

And ZPM client gives you the option to switch between registries and install from public or from any private registries.

Also check the article by @Mikhail Khomenko which describes how to deploy InterSystems IRIS docker-container with ZPM registry in Kubernetes cloud provided by Google Kubernetes Engine.

Happy coding and stay tuned!

Discussion (1)1
Log in or sign up to continue

Is there any way to have multiple registries enabled at the same time in ZPM, with a priority so that it looks at them in order to find packages. That way you can use public packages from the community repo without having to have them imported/duplicated into your local repo.  Or is the only way to keep switching between repos if you want to source from different places.