I have some Services using EnsLib.File.InboundAdapter to go directly to respective operations using EnsLib.File.OutboundAdapter which has a 'File Path' specified.
Using this File Path as a root directory, I'd like to instead pass this through a Router where I could somehow inject a subdirectory to place the file into on the outbound side based off the source service it is coming from. There will likely be several inbound services writing to each outbound operation and I'd like to be able to sort the output into subfolders.
全てのアプリケーションは、IRIS Community Edition 、IRIS for Health Community Edition または、IRIS Cloud SQLで動作する必要があります。MacやWindowsのホスト版をご利用いただく場合は、インストールキットをダウンロードしてください。コンテナを利用する場合は InterSystems Container Registryから pull、または、最新バージョンのイメージ(intersystemsdc/iris-community:latest または intersystemsdc/irishealth-community:latest)をご利用ください。
Currently we are exploring how we can allocate additional disk space to our current environment as we have seen a significant increase in growth of our Database files. Currently we have 3 namespaces, all with 1 IRIS.dat each that contains both the Global and Routines.
Since we have started down the route of everything within a single IRIS.dat file for each namespace, is it logical as we see growth to be able to split the current IRIS.dat for each namespace into a separate IRIS.dat for global and a IRIS.dat with for routines for each namespace in a Mirror environment?
I assume that we would have to take each one of the nodes down at a single time to do this. Is this even logical to do?
Or do we add a LUN and move everything over to that new LUN as is still maintaining the single IRIS.dat per namespace?