Evgeny already mentioned just released preview version of IRIS 2018.2. And fortunately documentation from this version already available online,  and they offer to use new dialect  org.hibernate.dialect.InterSystemsIRISDialect. You can try to use it.

Very interesting question. Actually, it mostly depends on your application and how do you work with private data there. 

You can make application for any number of customers working in one database, with good security which does not allow to access data from one customer by another.  But in this case mostly means, that your application should be designed so, from the beginning.

Another and maybe simplest way is making separate databases for each customer. In Caché you can create multiple namespaces with different databases for each customer, but with the same database for a code of your application. So, you can update all sites at the same time.

Nowadays, I would recommend looking at containerization of application. And with kubernetes you can very fast deploy any new site with completely separate code and data between customers. But it means some work on how to prepare your application to be deployable with kubernetes.

%CacheObject was replaced with %Compiler.Type.Object. But this class was and still for internal use, how do you use it?

Silent install uses exactly the same manifest file, as for interactive. And it will install all components. But you can choose which one you really need with ISC_PACKAGE_CLIENT_COMPONENTS parameter and when this parameter empty will be installed all components.

This rouitine should be available from %SYS namespace, and stored in CACHESYS database. All routines and globals which starts with Z,z from %SYS namespace, or %Z,%z  from any namespace will be stored there.

Caché cube icon available only for Windows. But there is an external project Cube, but it was not developed so long.

I have configured automatic deployment of the application to Kubernetes with Helm from GitLab as a part of CI/CD process.

I would not say that I had some specific issues, just well configured Kubernetes cluster with the right storage driver. Any InterSystems products supports devicemapper and aufs right now, yet. So, of course, better to have devicemapper available server, and use this possibility. AUFS already deprecated by Docker and will disappear in the next major release.

Do not forget that $lb is just a list, concatenated list of single $lb, and $lb is a string in binary format.. So, just $replace, will work

USER>set list = $lb("stri,ng", $c(0), 2)

USER>set list = $replace(list, $lb($c(0)), $lb())

USER>zw list
list=$lb("stri,ng",,2)

I made such an example years ago, you can look at GitHub. This example maybe not so correct by this time, but can be useful. When you have to run only ECP clients, it becomes a bit easier. You should not care about volumes, in most cases, all the data stored in ECP-client is temporal. So, you mostly should care only about buffers. In my example, you can find how to configure instance during docker build to work as ECP-client.

You can specify /nodelete qualifier when you run your tests.

Do ##class(%UnitTest.Manager).RunTest("testspec","/nodelete")

Look at the documentation for other options.

You can find detailed information in the documentation

Well, there is mostly only one reason, why you can't mount your database and this issue mostly happens when anybody tries to migrate between different versions on different machines. And it is different localization settings. Like, your database uses some national global collation, and you try to copy it to the instance with different settings, where this collation does not supported. You should find mention about  wrong collation in cconsole.log. So, then, you should set the same NLS, as in the first system and try to mount again.

Another possible reason is different blocksize in the Database. By default Caché uses 8KB blocks, but it is possible to have different block size, and instance should be configured for this particular blocksize, as well. cconsole.log should also contain error in this case.

Some other issues, which you can face, but they do not prevent database to be mounted.

• 8-bit or Unicode, when you install Caché you still able to choose it, when Ensemble, HealthShare, and IRIS is Unicode only. In this case, if your data not in English, possible data should be converted from 8-bit codepage to Unicde.
• cache.lck file next to CACHE.DAT, it is a lock file, prevents to mount database with exclusive access. But Database in this case should be mounted in read-only mode.

Function $zf(-1) just executes a command passed as the second argument, you passed only file name. it is not complete, you should add command del  for Windows.

set status = $zf(-1, "del c:\sys\text.txt")

it should return 0 if the command was successful.

If you want just delete a file, you can use %File class, useful for many different operations with files and folders.

set result = ##class(%File).Delete("c:\sys\text.txt")

I successfully use atelier on Mac. Could you add some errors you faced?

Yes, it also works as expected, because

Write "123",456

Outputs

123456

Without any quotes, but it doesn't mean that there are no difference between "123" and just 123. You can see it if you would try to work with $zhex. Try by yourself

Write $zhex(32)

Write $zhex("32")

If you think you know exact column which fails this query, you can try to CAST it to another type which Cache will understand.

I would recommend to use more suitable class for it. %Stream.FileCharacter when you can set TranslateTable property

Set stream=##class(%Stream.FileCharacter).%New()
Set sc=stream.LinkToFile("c:\myfile.txt")
Set stream.TranslateTable = "UTF8"
While 'stream.AtEnd {
	Set line=stream.Read()
	; Process the chunk here
}

And you don't need any conversions after that

It looks like you are going the wrong way. If it fails if even classes have not changed and have not recompiled.

Could you show exact error, which fails to run your reports?

I think, the issue may be in SQL cache, so, you can try to purge it

Do $SYSTEM.SQL.Purge()

Collation 20 is Portuguese2. Looks like windows was localized in Portuguese or regional settings when Ensemble was installed. But later changed locale definition to something else. You should return back because the database was created with this collation, and if you want to use new collation you should create a new one and move all data to the new database.

I think your original locale was ptbw, so, you should choose it and press install, and in confirmation press install again.