That error doesn't indicate that it found the file, it just describes the path where it is looking for the file (per your configuration). If Ensemble can't access a file despite the file existing, this is likely an OS permissions issue. I would check to make sure the OS user Ensemble is using has permission to access the directories/file.
Outside of that, perhaps there would be other helpful evidence in the OS log, Ensemble ^SYSLOG, or the Ensemble event log.
"ccontrol [run | console | cterminal] instname Runs Caché in programmer mode with either no device, the console, or the terminal for $Principal (Windows only)."
Linux Mint is not supported. Dmitriy suggests you might be able to get Caché to run, but you would be on your own if issues cropped up in that environment.
To be clear, SFTP "private key authentication" is really key pair authentication, meaning you need both a private and public key configured. If you just have 1 or the other configured, your service will attempt username authentication instead. The need for both keys is intrinsic to SFTP and is not Caché specific.
"Once you indicate you are using SFTP, you can then configure the SFTPPublicKeyFile and SFTPPrivateKeyFile settings. If you supply values for both SFTP Public Key File and SFTP Private Key File, the adapter attempts key pair authentication. It does this in conjunction with the username and password supplied via the Credentials setting, using the password in the Credentials as the passphrase for the private key."
I'd suggest reviewing the following article for suggestions on how you can debug why the key pair authentication is failing:
I am sure your InterSystems sales team would be happy to have an environment configuration planning discussion with you.
Outside of that, take a look at the following documentation. I am also going to link a developer community article series that covers some topics and best practices for Caché that you can apply to IRIS as well.
There is no supported method to update OpenSSL (thereby getting TLS 1.2 support) other than to upgrade your Caché version. Your current version of Caché is quite old so this would be a great opportunity to get onto something more modern.
The free editions of IRIS are more targeted towards familiarizing yourselves with the basics of IRIS and not for production use. I'm sure an InterSystems rep can answer your licensing questions .
Re: the reliability of your data, the documentation touches on IRIS' data protection mechanisms here:
I have some experience on this with Windows, but if you are on another OS the following won't apply. On Windows, the installer language is controlled by the "Language for non-Unicode programs" Windows setting.
I'd look into confirming that the cbk isn't corrupt for whatever reason. Can you restore it on the original system? Perhaps you can review the checksum? Maybe you can try taking a new online backup or an external backup?
Outside of that, I'd second Robert's suggestion to reach out to the WRC (especially if the problem is urgent). Does the organization you are working with/for have a support contract?
What do you mean by locking resources? I think Call Interval should be appropriate for the behavior you want, but I'm not sure what complication you're referring to.
A common suggestion here might be the Ensemble schedule handler, but I'd not recommend that as per the documentation this isn't intended for specifying specific processing times, but activation windows for the interface. The documentation also discusses creating a more general scheduled task and having it call CreateBusinessService() and ProcessInput() but this would be much more involved than just using Call Interval.
go to post
Hi Joe,
That error doesn't indicate that it found the file, it just describes the path where it is looking for the file (per your configuration). If Ensemble can't access a file despite the file existing, this is likely an OS permissions issue. I would check to make sure the OS user Ensemble is using has permission to access the directories/file.
Outside of that, perhaps there would be other helpful evidence in the OS log, Ensemble ^SYSLOG, or the Ensemble event log.
go to post
Hello Yatin,
That's a known RDP issue that has been fixed in modern versions of Caché. To get around it you can use ccontrol console:
Using Multiple Instances of Caché
"ccontrol [run | console | cterminal] instname Runs Caché in programmer mode with either no device, the console, or the terminal for $Principal (Windows only)."
go to post
Hello Felipe,
You can find the list of supported platforms for Caché 2018.1.4 (and 2018.1.3) here:
https://docs.intersystems.com/latest/csp/docbook/Doc.View.cls?KEY=ISP_technologies#ISP_platforms
Linux Mint is not supported. Dmitriy suggests you might be able to get Caché to run, but you would be on your own if issues cropped up in that environment.
go to post
Hello Vermon,
To be clear, SFTP "private key authentication" is really key pair authentication, meaning you need both a private and public key configured. If you just have 1 or the other configured, your service will attempt username authentication instead. The need for both keys is intrinsic to SFTP and is not Caché specific.
Settings for the FTP Inbound Adapter > SSL Config
"Once you indicate you are using SFTP, you can then configure the SFTPPublicKeyFile and SFTPPrivateKeyFile settings. If you supply values for both SFTP Public Key File and SFTP Private Key File, the adapter attempts key pair authentication. It does this in conjunction with the username and password supplied via the Credentials setting, using the password in the Credentials as the passphrase for the private key."
I'd suggest reviewing the following article for suggestions on how you can debug why the key pair authentication is failing:
https://community.intersystems.com/post/using-and-debugging-netsshsession-ssh-connections
Hope that helps!
go to post
Hello Yuri,
I am sure your InterSystems sales team would be happy to have an environment configuration planning discussion with you.
Outside of that, take a look at the following documentation. I am also going to link a developer community article series that covers some topics and best practices for Caché that you can apply to IRIS as well.
Vertically Scaling InterSystems IRIS
Preparing to Install InterSystems IRIS
https://community.intersystems.com/post/intersystems-data-platforms-capacity-planning-and-performance-series-index
go to post
Hello Rodolfo,
There is no supported method to update OpenSSL (thereby getting TLS 1.2 support) other than to upgrade your Caché version. Your current version of Caché is quite old so this would be a great opportunity to get onto something more modern.
go to post
Hi Fathima,
I'd recommend making a sales inquiry to InterSystems which you can do through this page:
https://www.intersystems.com/who-we-are/contact-us/
The free editions of IRIS are more targeted towards familiarizing yourselves with the basics of IRIS and not for production use. I'm sure an InterSystems rep can answer your licensing questions .
Re: the reliability of your data, the documentation touches on IRIS' data protection mechanisms here:
Introduction to Data Integrity
Hope that helps!
go to post
Hello Eduardo,
I have some experience on this with Windows, but if you are on another OS the following won't apply. On Windows, the installer language is controlled by the "Language for non-Unicode programs" Windows setting.
go to post
For Caché, the restore should just be compatible. I just tested restoring a 2015 cbk to 2017 and confirmed that. For IRIS you'd need additional steps.
Supported Version Interoperability (docs for Caché 2017.2)
I'd look into confirming that the cbk isn't corrupt for whatever reason. Can you restore it on the original system? Perhaps you can review the checksum? Maybe you can try taking a new online backup or an external backup?
Outside of that, I'd second Robert's suggestion to reach out to the WRC (especially if the problem is urgent). Does the organization you are working with/for have a support contract?
go to post
Hello Mikael,
What do you mean by locking resources? I think Call Interval should be appropriate for the behavior you want, but I'm not sure what complication you're referring to.
A common suggestion here might be the Ensemble schedule handler, but I'd not recommend that as per the documentation this isn't intended for specifying specific processing times, but activation windows for the interface. The documentation also discusses creating a more general scheduled task and having it call CreateBusinessService() and ProcessInput() but this would be much more involved than just using Call Interval.