IAM - InterSystems API Manager is a great tool for monitoring your traffic. If you are trying to use it in your Kubernetes cluster you may have tried doing a deployment similar to this one:
When accessing management portal through IIS the page is not fully rendered and the buttons/links that are displayed don't work.
Management Portal works fine through private web-server.
Have just set up IIS/CSP Gateway to access Ensemble, and accessing the CSP Gateway configuration pages through IIS works fine (screenshot at end of post).
This is the view when accessing management portal through IIS (port 80) - missing images, links don't work, not all content displayed:
When handling a %CSP.REST API response for a custom endpoint, how can I capture or access the response content before it is written to the output buffer and sent through the Web Gateway to the UI?
I'm not so experienced in administering IRIS but as far as I understand IRIS for Health community comes with a web server out-of-the-box while licensed editions require Web Gateway to be deployed.
We have a machine that serves 4 instances of Cache on VMS systems, one of them is password protected and works fine as they all do. we decided we wanted something beefier and copied it to a server, well all but the one you have to login to works so 3 of the 4 do. and the odd part is I can no longer get to the management page from anywhere on any machine, http://localhost/csp/bin/Systems/Module.cxw I get a 404.8 error, I have tried adjusting security and same thing. and a server availability error.
I ran into a situation where VS Code consumed all available web sessions and was unable to get to the Management Console to clear them. I was able to establish a terminal session, though.
Is there a method or routine available through the IRIS terminal that allows one to clear web sessions? I've searched the administration and class documentation and haven't found a solution.
While developing web apps the security practice I consider safe and convenient is to create a special Role (e.g. equal application name) which contains security resources which application will need (SQL tables, priviledges, database access, etc) and assign it to the Web Application. So the user gets this role once it loggs in to the application (via password, no password or delegated).
Convenient, right?
So, the question is, when I deploy the app as an IPM module what should I put as a database access?
In today's rapidly evolving threat landscape, organizations deploying mission-critical applications must implement robust security architectures that protect sensitive data while maintaining high availability and performance. This is especially crucial for enterprises utilizing advanced database management systems like InterSystems IRIS, which often powers applications handling highly sensitive healthcare, financial, or personal data.
While upgrading old Ensemble and Health Connect applications to V 2024.1 we are installing many webgateways since the private webserver is deprecated.
Configuring the "Default Parameters" we can determine the "Event Log Rotation Size" but not the count of preserved logfiles. So even if the webgateway cuts the logs in pieces they could fill up the disk space entirely for there seems to be no cleanup-job for old logfiles.
What is the recommended way to deal with this situation?
In the WRC, we frequently see customers contact us because their Web Gateway is unable to serve web pages. This article will explain a frequent reason why these errors can occur, and explain some tools which can be used to debug the problem. This explanation is focused on the Web Gateway serving InterSystems IRIS instances, but the same explanation should apply to the CSP Gateway serving Caché instances as well.
we're running an Iris installation on SLES 15.5 using the SLES Apache server and web gateway for hosting the management portal on Port 57772 (e.g. http://<host-name>:57772/csp/sys/%25CSP.Portal.Home.zen?$NAMESPACE=HL7TOFHIR) on the same machine. The Iris installation also provides a FHIR Server in a separate namespace which uses the base URL http://<host-name>:57772/fhir/r4 for connections.
Recently, I needed to run WebGateway on an additional port but with a twist - this port should publish only one web application. At first, I thought about configuring Web Gateway to allow only specific web applications (~urls), but Web Gateway configuration is per Apache configuration:
This is like my first post in this community. Let's see how this turns out. I have a question about the Intersystems Kubernetes Operator and the deployment of the webgateways.
I am responsible for the hosting and deployment of the apps. For the future we are planning to host our application in a kubernetes cluster. I am using the IKO for this. I am using webgateways, for external access as separate pods. And sidecar containers for internal access, like the management portal.
I just restarted an AWS instance that have been dormant for 6 months (license still valid) only to find that the web application on there doesn't work and that I cannot connect to the management portal. I can however connect to the web gateway fine but it reports the "Server is currently unavailable".
Well, now we got noPWS container with IRIS, and how to connect to it, simply, without any durable sys or files, using normal peoples way like Environment variables?
Is it possible to use one IIS server to configure Webgateway and external Webserver for management portal when implementing synchronous mirroring with VIP i.e Is it necessary to have two mirror servers(primary and Backup) , one Arbiter server, one Webserver for Webgateway and a sperate webserver for management portal?
If anyone can please point to any documentation on Mirroring with Webgateway and external webserver for management portal will be really helpful.
If you plan on using the nginx server to front end you IRIS instance (as opposed to the standard apache web gateway install) you will need to add a few configuration options into the CSP.conf file in order for all urls to work. It took me a little bit to figure this out but this seems to be the configuration that works.
We recently moved from using the Private Web Server, to using an Apache/Web Gateway setup and moved towards using the built in LDAP functionality within IRIS. Since then, we have 1 user that uses VSCode (/api/atelier) heavily that continues to have issues signing into IRIS through VS Code and the /api/atelier extension.
By update.png)