Hello!

Greetings from Chile, I have a question about IAM, I have a client who implements IAM in a QA environment, I configure a workspace and a series of routes (quite a few) and now he wants to export what has been created and take it to production (another server), which is the procedure to do it? Is it possible to export the workspace, routes, plugins, etc.?

Thank you!!

0 2
0 76

Hi everyone!

I am recruiting on a fully remote Intersystems Developer. This role will be a long term contract to begin with high likelihood of extensions or conversion permanent. Please check out the job description down below and feel free to send me an email with your resume: Spencer.Frey@insightglobal.com

0 1
0 168

In this article, I would like to talk about the spec-first approach to REST API development.

While traditional code-first REST API development goes like this:

  • Writing code
  • REST-enabling it
  • Documenting it (as a REST API)

Spec-first follows the same steps but reverse. We start with a spec, also doubling as documentation, generate a boilerplate REST app from that and finally write some business logic.

This is advantageous because:

  • You always have relevant and useful documentation for external or frontend developers who want to use your REST API
  • Specification created in OAS (Swagger) can be imported into a variety of tools allowing editing, client generation, API Management, Unit Testing and automation or simplification of many other tasks
  • Improved API architecture. In code-first approach, API is developed method by method so a developer can easily lose track of the overall API architecture, however with the spec-first developer is forced to interact with an API from the position if API consumer which usually helps with designing cleaner API architecture
  • Faster development - as all boilerplate code is automatically generated you won't have to write it, all that's left is developing business logic.
  • Faster feedback loops - consumers can get a view of the API immediately and they can easier offer suggestions simply by modifying the spec

Let's develop our API in a spec-first approach!

12 6
8 2,358
InterSystems Official
Stefan Wittmann · Feb 16, 2021
IAM 1.5.0.9 is now GA (Generally Available)

The GA release is now published for the 1.5 version of the InterSystems API Manager (IAM).

The container for IAM, including all relevant artifacts to upgrade from earlier versions of IAM can be downloaded from the WRC Software Distribution site in the Components area.

The build number for this release is IAM 1.5.0.9-4.

InterSystems API Manager 1.5 makes it easier to manage your API traffic, integrate with your environment and onboard users of your APIs. It has many new capabilities, including:

  • Improved User Experience
  • Introducing new Developer Portal tools
  • Support for Kafka connectivity
5 6
0 486

Has anyone else seen this error? From the API Manager Catalog, I can select an API and use the "Try it Out" feature. An error is returned - TypeError: Failed to fetch.

The same Curl can be imported into Postman and executed successfully. For us, API Manager is in a container and the container can ping the server. Also, this error is in the Developer Tools/Console -

0 1
0 105

I am working with InterSystems API Manager product and I'm trying to solve an authentication problem. In our implementation, API Manager accepts basic authentication. One of the endpoints accepts OAuth2. The request coming into API Manager is FHIR and needs to have basic auth in the header. The OAuth token is passed to API Manager as a parameter. I want to send FHIR to the endpoint with a Bearer Token in the header instead of the basic auth that came into API Manager. Has anyone used a transformation plug-in to solve a similar issue? I'm trying to solve this problem in API Manager ra

0 4
0 609

InterSystems API Management (IAM) - a new feature of the InterSystems IRIS Data Platform, enables you to monitor, control and govern traffic to and from web-based APIs within your IT infrastructure. In case you missed it, here is the link to the announcement. And here's an article explaining how to start working with IAM.

In this article, we would use InterSystems API Management to Load Balance an API.

In our case, we have 2 InterSystems IRIS instances with /api/atelier REST API that we want to publish for our clients.

There are many different reasons why we might want to do that, such as:

  • Load balancing to spread the workload across servers
  • Blue-green deployment: we have two servers, one "prod", other "dev" and we might want to switch between them
  • Canary deployment: we might publish the new version only on one server and move 1% of clients there
  • High availability configuration
  • etc.
7 3
4 622

Using SOAP Web Services or REST API Resources, if you want to deliver strategic digital assets for your organization, SOA aproach is an excellent option. The InterSystems IRIS supports like a charm the SOA principles with Contract First technique to model services aligned with the business, and create the services from the service contracts (Open API or WSDL).

2 0
2 343