Howdy all,

Iain is right that you can get the ODBC driver from the WRC site directly if you are a customer of ours, but the new spot InterSystems hosts drivers for ODBC and so on is here:

https://intersystems-community.github.io/iris-driver-distribution/

edit: I realized this was asking for Cache, not IRIS drivers, so my answer doesn't address it.

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

Hi Smythe,

This should be pretty straightforward! The docs cover a few simple use cases such as setting up Ens.Alert as a router to the email operation, or just having the email operation be Ens.Alert itself. Basically, the system knows to send interoperability alerts to whatever component is called Ens.Alert.

https://docs.intersystems.com/iris20221/csp/docbook/Doc.View.cls?KEY=EGDV_alerts

(These docs are for IRIS but the concept is the same for Ensemble)

To build on Yaron's answer, our documentation is quite helpful to understand the role of journaling and the WIJ. The individual chapters on each item respectively of course go into further detail, but here's a brief section describing the 2.

Differences Between Journaling and Write Image Journaling

I would also echo all of Mario's guidance - and to answer one of your specific questions above, the "warnvalue" is a configurable threshold for when a warning should be thrown, in your case I believe the default of 75% cpu usage. 

Anything else I would say I think has been covered by other commenters.

I might suggest you get the server running and verify that it is happy before trying to get in with Studio. It might be easiest to do it all from the cube - ie you can start iris from there. I mention that because I don't believe you're expected to call irisstart directly. You can call "iris start <instancename>" (distinction is using the iris command to call start).

If the cube fails to start IRIS it should throw an error (likely in the messages.log that the error will tell you to check).

Once you've started IRIS perhaps you can try accessing terminal and the management portal, then Studio. That could narrow down the communication error which may be generic.