Find

Question
· Jun 21

Where does IRIS Studio save its server connections?

Hi everyone,

I'm preparing to move to a new PC soon and I'm trying to migrate the server connections I use in IRIS Studio to the new environment.

I’ve followed without success an old procedure I've found on a post on the community that involves exporting the registry key from:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Intersystems\Cache\Servers

But I’ve realized that this only includes the entries from the Server Manager and not the actual server connections used within IRIS Studio and shown within the "Server Connections" menu.

As I've done to copy other software configurations, I also checked the following path, but there is no Intersystems or IRIS directory:

C:\Users\<username>\AppData\Roaming\

So I'm wondering where IRIS Studio exactly saves its server connections? Is there a way to export them or copy them to a new machine?

Thanks in advance!

2 Comments
Discussion (2)1
Log in or sign up to continue
Discussion
· Jun 21

CreatedAt and LastUpdated - do you use it?

Hi fellow developers!

Curious if you guys use CreatedAt and LastUpdated properties in your classes?

Created to stamp when the record was created and LastUpdated when it was last updated. Where it can be useful - almost everywhere )) I find it convenient in records sorting (e.g. by creation or last update), in sync (with other systems), and so on, for better analytics.

Do you use it all the time for all the classes?

If don't, why not? What do you use instead?

What property type do you use - %TimeStamp? %DateTime?

What is the best practice to have CreatedAt filled automatically during creation and LastUpdated on every successful save (guess it could be in %OnSave)?

Please share your experience /thoughts?

16 Comments
Discussion (16)3
Log in or sign up to continue
Question
· Jun 21

Business Service Error on Windows 11 machine

Good day 

I am trying to connect a business service to fileZilla using FTP on my local PC Win 11.

I am trying to setup my training after attending the Building HL7 interfaces course with ISC.

The connection is failing. He is the error below

 

ERROR <Ens>ErrOutConnectFailed: FTP Connect failed for localhost:21//SSL=' with error ERROR <Ens>ErrFTPConnectFailed: FTP: Failed to connect to server 'localhost:21//SSL='/' (msg='Missing required argument',code=501)

1 Comment
Discussion (1)2
Log in or sign up to continue
Discussion (0)0
Log in or sign up to continue
InterSystems Official
· Jun 20

InterSystems API Manager (IAM) 3.10 Release Announcement

InterSystems is pleased to announce that IAM 3.10 has been released. IAM 3.10 is the first significant release in about 18 months, so it includes many significant new features that are not available in IAM 3.4, including:

  • Added support for incremental config sync for hybrid mode deployments. Instead of sending the entire entity config to data planes on each config update, incremental config sync lets you send only the changed configuration to data planes.
  • Added the new configuration parameter admin_gui_csp_header to Gateway, which controls the Content-Security-Policy (CSP) header served with Kong Manager. This defaults to off, and you can opt in by setting it to on. You can use this setting to strengthen security in Kong Manager.
  • AI RAG Injector (ai-rag-injector) Added the AI Rag Injector plugin, which allows automatically injecting documents to simplify building RAG pipelines.
  • AI Sanitizer (ai-sanitizer) Added the AI Sanitizer plugin, which can sanitize the PII information in requests before the requests are proxied by the AI Proxy or AI Proxy Advanced plugins.
  • Kafka Consume (kafka-consume): Introduced the Kafka Consume plugin, which adds Kafka consumption capabilities to Kong Gateway.
  • Redirect (redirect): Introduced the Redirect plugin, which lets you redirect requests to another location.
  • … and many more

Customers upgrading from earlier versions of IAM must get a new IRIS license key in order to use IAM 3.10.  Kong has changed their licensing in a way that requires us to provide you with new license keys.  When you are upgrading IAM, you will need to install the new IRIS license key on your IRIS server before starting IAM 3.10.

IAM 2.8 has reached its end-of-life and current customers are strongly encouraged to upgrade as soon as possible.  IAM 3.4 will reach end-of-life in 2026, so start planning that upgrade soon.

 

IAM is an API gateway between your InterSystems IRIS servers and applications, providing tools to effectively monitor, control, and govern HTTP-based traffic at scale. IAM is available as a free add-on to your InterSystems IRIS license.

IAM 3.10 can be downloaded from the Components area of the WRC Software Distribution site

Follow the Installation Guide for guidance on how to download, install, and get started with IAM.  The complete IAM 3.10 documentation gives you more information about IAM and using it with InterSystems IRIS. Our partner Kong provides further documentation on using IAM in the Kong Gateway (Enterprise) 3.10 documentation

IAM is only available in OCI (Open Container Initiative) a.k.a. Docker container format. Container images are available for OCI compliant run-time engines for Linux x86-64 and Linux ARM64, as detailed in the Supported Platforms document.

 

The build number for this release is IAM 3.10.0.2. 

This release is based on Kong Gateway (Enterprise) version 3.10.0.2.

Discussion (0)1
Log in or sign up to continue