Home Applications MyOwn Portal

MyOwn Portal

by Murilo Przybyloviecz and 1 others
Community Project
This project is maintained by its author and is not officially supported by InterSystems. For technical support, please contact the project developer.
0
0 reviews
0
Awards
4
Views
0
IPM installs
0
Add to bundle
Details
Releases (1)
Reviews
Issues
Articles (1)
Compact administration portal for InterSystems IRIS and IRIS for Health — React frontend, ObjectScript REST backend, Embedded Python health scoring, and native IRIS Vector Search. Built for the InterSystems Programming Contest.

What's new in this version

Initial Release

MyOwn Portal

MyOwn Portal is a compact, English-language administration interface for InterSystems IRIS and IRIS for Health. It was created for the InterSystems Programming Contest: Build Your Own Management Portal.

The browser application uses React and TypeScript. The REST backend, authorization, auditing, and access to IRIS administration data are implemented in ObjectScript. Vite and Node.js are development and build tools only; the production React bundle is served by the private IRIS web server.

Quick Start

MyOwn Portal has no login of its own — it authenticates directly against the IRIS instance it is installed on. Full explanation in https://github.com/muriloprzy-code/Portal-Iris/blob/master/docs/REFERENCE.md.

The easy way: one double-click

Double-click Instalar.bat at the project root. It figures out the rest on its own:

  • Docker path: if Docker Desktop is installed, it builds and starts the demo container and opens http://localhost:52774/myown/index.html for you. Docker Desktop needs to already be open before you run the installer — if it isn’t running yet, start it first, wait for it to finish starting up, then run Instalar.bat.
  • Local IRIS path: if you already have IRIS installed locally instead, it asks which namespace to install into (press Enter for the default, MYOWN, or type the name of a namespace you already use), builds the frontend (downloading a local copy of Node.js first if needed, no admin rights required for that part), deploys the files, restarts the private web server, and installs the backend — fully automatically, over IRIS’s own Atelier REST API, no terminal to paste into. It asks once for your IRIS username and password for that last step; they are used only in memory and never written to disk. It then opens http://localhost:52773/myown/index.html.
  • If both Docker and a local IRIS are found, it asks once which one you want.

It will ask Windows for administrator permission once (needed only to restart the IRIS private web server on the local-install path) — approve that, and everything else runs by itself. The one thing it cannot do for you is the one-time creation of the namespace if it does not already exist on your IRIS instance; if that is the case, it stops and tells you exactly where to click (Management Portal → System Administration → Configuration → System Configuration → Namespaces → New Namespace) — then just run Instalar.bat again.

Prefer to run the commands yourself, or run outside Windows? (click to expand)

Docker, by hand:

Make sure Docker Desktop is already open, then:

docker compose up --build -d

Open http://localhost:52774/myown/index.html and sign in with _SYSTEM / ChangeMe2026! (the default demo password — see https://github.com/muriloprzy-code/Portal-Iris/blob/master/docs/REFERENCE.md to change it). This spins up a fresh, disposable IRIS just for the demo, with zero risk to any IRIS instance you already have.

Local IRIS, by hand:

  1. If the namespace you want to use does not exist yet, create it once (Management Portal → System Administration → Configuration → System Configuration → Namespaces → New Namespace). The installer’s default is MYOWN, but any existing namespace works — it is only a name.
  2. Build the frontend:
    cd frontend
    npm install
    npm run build
    cd ..
    
    No Node.js on your PATH? Run install-node-local.bat once first (downloads a local copy of Node.js, no admin rights needed), then repeat the commands above.
  3. From the project root, run the installer script directly (this is the same script Instalar.bat runs for the local-IRIS path — running it yourself is only useful if you want to pass explicit parameters, e.g. -IrisInstallDir, -Instance, or -Namespace):
    .\scripts\Install-All.ps1
    
    It deploys the frontend you just built, restarts the private web server, then asks which namespace to use and for your IRIS username/password once — used only for that step, never stored — and installs the backend automatically over IRIS’s built-in Atelier REST API (the same mechanism the VS Code ObjectScript extension uses). The exact HTTP calls it makes are all in https://github.com/muriloprzy-code/Portal-Iris/blob/master/scripts/Install-All.ps1, if you want to see or adapt them.
  4. Open http://localhost:52773/myown/index.html and sign in with _SYSTEM — or grant your own account the MyOwnAdministrator role first, a one-time step explained in https://github.com/muriloprzy-code/Portal-Iris/blob/master/docs/REFERENCE.md.

Everything else — architecture, every install detail, the API reference, and troubleshooting — is in https://github.com/muriloprzy-code/Portal-Iris/blob/master/docs/REFERENCE.md.

Features

  • System overview, operating-system metrics, and active IRIS processes.
  • Embedded Python health scoring with a concise instance-health summary.
  • Native IRIS Vector Search against stored health patterns and recommendations.
  • Users, roles, resources, effective permissions, and controlled role assignment.
  • Web application and REST API inventory with protected enable/disable actions.
  • A bounded local REST API Explorer with an OpenAPI view.
  • Sanitized certificate, OAuth, Secure Wallet, and credential-reference metadata.
  • IRIS Task Manager inventory with protected Run, Suspend, and Resume actions.
  • Sanitized messages.log browsing with search, filters, pagination, and details.
  • Native IRIS role-based access control and audit events for state changes.
  • A demonstration Task Manager task (MyOwn Portal health snapshot) so that Run, Suspend, and Resume can be tried on a fresh instance.
  • Responsive English user interface.

Contest technology bonuses

  • Embedded Python: the instance health score and the host memory and disk metrics are computed in Language = python methods.
  • Vector Search: health patterns are stored in a %Vector property and matched with VECTOR_COSINE.
  • Docker: Dockerfile and compose.yaml build and run the portal on IRIS Community Edition.
  • IPM package: module.xml defines the myown-portal module.

License

MIT

Team

Version
1.0.025 Sep, 2026
Category
Technology Example
Works with
InterSystems IRISInterSystems IRIS for Health
First published
25 Sep, 2026
Last edited
25 Sep, 2026