Generate server-side class. It’s pretty similar to the generated code by ^%REST but the added value is the version 3.0 support.
Generate HTTP client classes.
Generate client production (business services, business operation, business process, Ens.Request, Ens.Response) classes.
A web interface to generate and download the code or generate and compile directly on the server.
Convert specification from version 1.x, 2.x to version 3.0.
OpenAPI Suite is split into many packages, and uses different developer community libraries and also public REST services. You can see on the schema below, all packages have been developed, and libraries and web services used:
At InterSystems, we believe in the responsible disclosure of recently discovered security vulnerabilities. We provide timely information to our customers, while keeping it out of the hands of people that may misuse it. We also understand each customer has different requirements related to the resolution of security issues.
We have created a number of REST adapters that extend %CSP.REST and these have been working fine. However, we are now facing a problem with a new one where very large XML documents are being posted. This is the pattern we are following:
InterSystems is pleased to announce the 2022.3 release of InterSystems IRIS Data Platform, InterSystems IRIS for Health, HealthShare Health Connect, and InterSystems IRIS Studio are now Generally Available (GA).
The similarity between JSON objects + arrays and Globals in IRIS or Caché is evident. With small and medium size JSON objects navigation across %Dynamic Objects is comfortable. But with large and/or deep cascaded objects it becomes a challenge.
The presented tool offers 3 variants
loading an already existing %Dyamic object or Array into a global of your choice
loading a %Stream containing a JSON object into a global of your choice
loading an external File containing a JSON object into a global of your choice
In our team, there are several developers working in parallel on different projects. To ensure this distributed collaboration and high-quality code reviews, we rely on version control with Git. Our challenge is to harmonize the unique characteristics of InterSystems products and the possibilities of Git and Docker.
The new $system.external interface (aka "InterSystems External Servers") is used to call/integrate with external language code/libraries, it replace the old gateways (for example Java gateway) that required the import of proxy objects.
Note that the documentation for the old gateways has been removed from IRIS, so only the new $system.external interface is somewhat (i.e. insufficiently) documented.
Regarding the migration from old gateway to new $system.external interface the documentation says:
With the gradual improvement of hospital information construction, there are more and more business interfaces in hospitals. Due to the influence of various factors (network, consumer system, etc.), the data processing of business interface may cause excessive message accumulation and even the situation of interface card congestion, which affects the normal business development in the hospital. Therefore, the monitoring of the queue of business interface components becomes more and more important.
Messages.log file contains lots of useful information about IRIS. Sometimes the file gets big, and it is not easy to get to the data I am interested to review. It would be nice to jump to a specific date and time we suspect a problem may have started.
Usualy, if you want to deploy a solution, you need to add the items, configure your lookup tables and default configuration manually. It's okay if you have all the permissions and privileges to perform these actions. If you want to deploy to a client's production server, and you don't have the permissions, you need to indicate in a document ALL the steps that the deployment manager has to perform.