Can you explain what section of the portal you are looking at? Do you mean interoperability system default settings?

Hi Andy,

This can be done via mappings.

Hello Abhishek,

Please see the following course on HL7 > FHIR.

https://learning.intersystems.com/course/view.php?id=1744

Hi Scott,

I would suggest using the %SYS.LDAP APIs to test each method individually or the LDAP test configuration page which will show additional logging.

https://docs.intersystems.com/iris20233/csp/docbook/DocBook.UI.Page.cls?KEY=ROARS_iam_ldap#ROARS_iam_ldap_unixapicertdebug

For posterity, the solution WRC proposed was to implement a CreateRS method allowing for the sort order to be modified by changing the SQL query.

No, that will not work. I'd suggest following the server migration guide.

https://docs.intersystems.com/iris20232/csp/docbook/Doc.View.cls?KEY=AMIG

Documentation shows that Java 8 and 11 are supported.

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=ISP_technologies#ISP_ejb

11 support was added briefly before Java 17 LTS was released (early 2021 I believe), but it seems InterSystems' Java support has not been updated in the past 2 years. This is something we are working on, however I don't know when that change might be released.

The garbage collector is somewhat an internal process which is why I believe it is sparsely documented. I'd echo Dmitry that understanding your concern would help.

I think what is documented generally covers a high level understanding - that being that there is a GARCOL process. And that blocks are marked freed after a large kill by this process, to be freed in the background.

You could use %Dictionary.ClassDefinition to open the class definitions, use %ConstructClone and then save to another namespace.

I agree with Lorenzo and Pietro as well! Since I believe you're looking to run tasks/code that has to do with your mirror failing over, I suppose it might be worth taking a higher level look at the scenarios you are hoping to address. Probably most of the things you want to do can be put in your ZMIRROR so that when your new primary takes over it can do whatever miscellaneous non-IRIS failover tasks you want.

What procedures do you need to be concerned about in a clean failover via shutting down the instance (triggering ZSTOP) vs in an unclean failover for whatever reason, in which case you would only expect your ZMIRROR to run?

In that case, I'd recommend reviewing the service user documentation I linked above. If you prefer to not set the service user for whatever reason, then using an admin command prompt would be a perfectly acceptable short term alternative.

Hi Scott, that doc is here:

Improving Restarts for Productions with Large Queues

That being said - I thought the move from suspended back to the queue was automatic generally, and wouldn't require a manual resubmit?

"By default, when a production is stopped, any asynchronous messages on the ^Ens.Queue global queue are moved to the ^Ens.Suspended queue. When the production is restarted, they are moved back."

I'm not aware of a sample in our modern documentation but I've put in a request for that. Since pretty much any arbitrary code can be run in ZMIRROR, I don't think there's much guideline for coding ZMIRROR besides the documented tags.

I do think that something like the stubs we document for ZSTART/ZSTOP might be helpful, if that's what you had in mind.

If you're an existing customer, you can access the distributions through the WRC application. Otherwise Michael's link will let you get a preview copy to test with and review.

I would check the audit log and review the login failures. Access denied is a generic error, the audit log knows more.

Hi David,

%Operator / the %Admin_Operate resource only give access to the system operation pages so that might be what you want to start with. From there, you can use custom resources to restrict individual pages.

No idea about custom menus!

It's already been reported, I meant! Rest assured.

Smythe,

Did you have a chance to review the replies on your other post? Are you trying to use the managed alert framework? If so, I'd suggest reviewing that documentation to make sure your configuration is appropriate. It sounds to me you may just want a regular router, and not to use the AlertManager, in which case a simple business rule can do that routing (or if you don't need routing, you can just make the email operation the Ens.Alert component.)

I think the following Google page explains the SMTP settings you need:

https://support.google.com/a/answer/176600?hl=en

Have you checked the CSP Gateway log / IIS logs?

Hi Thembelani,

If I'm understanding your question right, I think you just need to change the settings on the IRIS web application for your REST service, modifying the allowed authentication methods so "password" is enabled.