Hi *.*,

I am new to IRIS, IKO and IAM. I have read through a lot of the documentation, but I need clarity on some things that I can't find in the documentation.

• Which Load Balancer does IKO use on the ingress?
  Can it be set to use another one? e.g. nginx-kubernetes + GCP LoadBalancer?
• On a multi-compute and multi-data instances deployment, how do you get to the Management Portal of each instance?
  i.e. The load balancer is the only point of entry into the cluster exposing 1972 and 52773, so how do I route to the individual instances?

IAM 3.2 Release

InterSystems API Manager (IAM) version 3.2.1 is now Generally Available.  In additional to bug fixes and minor improvements IAM 3.2 adds new plug-ins that might be of interest to IRIS customers.

• OAS Validation (oas-validation)
  
  • Validate HTTP requests and responses based on an OpenAPI 3.0 or Swagger API Specification.
• SAML (saml)
  
  • Provides SAML v2.0 authentication and authorization between a service provider (Kong Gateway) and an identity provider (IdP).
• XML Threat Protection (xml-threat-protection)
  
  • This new plugin allows you to reduce the risk of XML attacks by checking the structure of XML payloads. This validates maximum complexity (depth of the tree), maximum size of elements and attributes.
• AppDynamics (app-dynamics)
  
  • Integrate Kong Gateway with the AppDynamics APM Platform.
• JWE Decrypt (jwe-decrypt)
  
  • Allows you to decrypt an inbound token (JWE) in a request.

In this article, I am trying to walk through my deploying step of IAM on my EC2(ubuntu).

What is IAM?

IAM is InterSystems API Manager
you may reference to the link below to get more idea about IAM

https://docs.intersystems.com/components/csp/docbook/Doc.View.cls?KEY=PAGE_apimgr

Before deploying IAM

Check the license of your API host

Enable the User IAM

Deploy IAM

Reference 

https://community.intersystems.com/post/introducing-intersystems-api-manager

Download the image from the following link

https://wrc.intersystems.com/wrc/coDistGen.

IAM 3.0 Release

InterSystems API Manager (IAM) version 3.0.2 is now Generally Available.  IAM 3.

Hey Developers!

Watch this video to get a brief overview of the InterSystems API Manager (IAM) and a deeper dive into new features of IAM 2.3 and 2.8:

⏯ API Management with InterSystems IRIS @ Global Summit 2022

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!!

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 

The Healthcare Integration Developer is responsible for designing, developing, and deploying the complex near real-time and real-time data interoperability solutions using Healthcare industry-standard data formats/specifications (HL7, FHIR, EDI, etc.).

Hi all,

I am trying to test the IAM locally, but I came to a issue. When I turned on the the Basic Authentication, I get an 503 Service Unavailable.
error.

This is the scenario/setup:

• Because I am new to IRIS I need a test sample in IRIS where I can get data from. So I use this tutorial: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=AFL_rest#AFL_rest_exercise. It works, I can make direct calls to IRIS via Postman.
• Because the goal is to test IAM, I setup the IAM with: https://openedx.learning.intersystems.

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!

IAM 2.8.1 Release

InterSystems API Manager (IAM) version 2.8.1 is now Generally Available.  In addition to a spade of performance improvements and bug fixes, this release adds significant new functionality, including:

• Core
  
  • Consumer Groups - Lets you group together consumers to create service tiers
  • Event Hooks - Enables IAM to call a web hook when certain events occur. For example, send a PagerDuty message if an endpoint fails.
  • Improvements to Hybrid Mode - Relaxed version checking; control plane can continue to work if the database is down.

Kong provides an open source configuration management tool (written in Go), called decK (which stands for declarative Kong)

• Check that decK recognizes your Kong Gateway installation via deck ping

deck ping   
Successfully connected to Kong!
Kong version:  2.3.3.2-enterprise-edition

• Export Kong Gateway configuration to a file named "kong.yaml" via deck dump

deck dump

• After modifying the kong.yaml, show the differences via deck diff

deck diff
updating service alerts  {
   "connect_timeout": 60000,
-  "host": "172.24.156.176",
+  "host": "192.10.10.

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

I have performed the suggested steps given in the below link for IAM installation but got an error "docker. errors.NullResource: Resource ID was not provided
[21528] Failed to execute script docker-compose"

https://docs.intersystems.com/components/csp/docbook/Doc.View.cls?KEY=C…

Hey Developers,

Watch as the presenter uses IKO to deploy the WebGateway, SAM, and InterSystems API Manager with the latest version of the InterSystems Kubernetes Operator: 

⏯ IKO: The InterSystems Kubernetes Operator (Version 3.0)

Hi Community,

Enjoy watching the new video on InterSystems Developers YouTube:

⏯ Getting Up to Speed on InterSystems API Manager

Hey Community

A new video is already on InterSystems Developers YouTube

⏯ Best Practices for InterSystems API Manager 
 

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.

Hi Community,

Enjoy watching the new video on InterSystems Developers YouTube:

⏯ Installing InterSystems API Manager

The GA release is now published for the 2.3 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 2.3.3.2-1. 

This release is based on Kong Enterprise version 2.3.3.2.

InterSystems API Manager 2.

How are others deploying API Manager services, routes and plugins from one environment to another?  We plan to use cache object code to deploy.  Is it best to embed curl or is there a better way?

Hi Community,

Enjoy watching the new video on InterSystems Developers YouTube:

⏯ InterSystems API Manager: Gummy Bear Factories

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?

This article contains the materials, examples, exercises to learn the basic concepts of IAM.

You have all resources available on this git : https://github.com/grongierisc/iam-training.

Solutions are in training branch.

This article will cover the following points :

• 1. Introduction
  • 1.1. What is IAM ?
  • 1.2. What is an API Management ?
  • 1.3. IAM Portal
  • 1.4. Flow of this training
• 2. Installation
  • 2.1. What do you need to install?
  • 2.2. How IAM works with IRIS
  • 2.3. Setup
  • 2.4. Install IAM
    • 2.4.1. Iris Image
    • 2.4.2. IAM Image
    • 2.4.3. Update the docker file
    • 2.4.4. Update the docker-compose
    • 2.4.5.

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.

Hi Community!  Today I'd like to share with you a link to some exercises from a workshop about developing REST APIs and how to manage them using InterSystems API Manager.

It includes step by step exercises to:

• Developing REST APIs from OpenAPI specifications.
• Adding the created API in an interoperability production (optional).
• Basic API management in InterSystems API Manager (service, route, auth, consumers, rate limiting, etc.).
• Some other more complex scenarios in InterSystems API Manager like load balancing, or routing by header.

You will find it all here: https://openexchange.intersystems.

I have been using the 

"in": "PATH"

parameter type for at least a year and was working fine for my GET requests.

Now, since this new version, it has stopped compiling. Does someone know why and what's the workaround to make a request like this work

/getmethod/getparam

Regards

Hi someone have tested that ? 

i try, but is not simple, and have no updated documentation about that in kong information.

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).

In 2017, Forbes published an article talking about API Economy (see: https://www.forbes.com/sites/louiscolumbus/2017/01/29/2017-is-quickly-becoming-the-year-of-the-api-economy/). This article was the trigger to popularize the use of API and API Management by large companies. The article published a maturity model. My understanding is that Intersystems IRIS allows you to reach the top of the pyramid with your current technologies. See the figure above.
For this it is important to combine % CSP.