#InterSystems API Manager (IAM)

1 Follower · 68 Posts

The InterSystems API Manager (IAM) enables you to monitor and control traffic to and from your web-based APIs. If you are building service-oriented application layers, you are very likely to find the number of APIs you are using quickly rise. The more distributed your environment the more critical it becomes to properly govern and monitor your API traffic. The API Manager enables you easily route all your traffic through a centralized gateway and forward API request to appropriate target nodes.

Additional Resources: 
Documentation
Introducing InterSystems API Manager [Article] 
What is InterSystems API Manager [Video] 
InterSystems API Manager Introduction [Video] 
InterSystems API Manager: Gummy Bear Factories Demo [Video] 

InterSystems staff + admins Hide everywhere
Hidden post for admin
Job Ratnesh Shrivastava · Jan 27

Job Title: InterSystems Developer / Specialist (IRIS / HealthShare)
Location: New York City, NY (Hybrid / Remote)
Duration: Contract (2+ years)
Experience: Min. 8 Years 

Job Summary

We are looking for an experienced InterSystems Developer / Specialist with expertise in InterSystems IRIS / HealthShare to support healthcare integration and interoperability initiatives. The ideal candidate should have hands-on experience in ObjectScript development, healthcare data standards, and integration protocols supporting EHR/HIE environments.

Key Skills Required

0
0 74
Article Sylvain Guilbaud · Jan 23 5m read

 

A question that quickly arises when configuring IAM (aka Kong Gateway) is how many routes should be created to reach all the business objects in an IRIS API.

A common mistake is to create one route per business object, unnecessarily multiplying the number of routes.

Let's take the example of the Supply Chain Orchestrator Data Model API:

0
0 10