New post
AllAccepted answers
Jose-Tomas Salvador · Jan 28, 2020

Just in case it gives you any cloud... when I enable the connection it seems that it tries to connect through the terminal or something... because I got an error also:

This is when I just Toggle Disable and then Enable (see the error message in the botton right):

It says: The terminal process command 'docker-compose exec iris /bin/bash -c 'command -v ccontrol >/dev/null 2>&1 && ccontrol session $ISC_PACKAGE_INSTANCENAME -U IRISAPP || iris session $ISC_PACKAGE_INSTANCENAME -U IRISAPP'' failed to launch (exit code: {2})

Jose-Tomas Salvador · Jan 28, 2020

That's what seemed strange to me...  I already did it withing VSCode Terminal directly and it works as if I do it in Powershell ... it fails when it goes through the "Open Terminal in Docker" option...

It works with Windows Powershell and with Powershell core (within VSCode Terminal and in PS Console):

Jose-Tomas Salvador · Jan 28, 2020

Hi Dmitriy,

I'm testing it in Windows 10 Pro... everything works except the terminal... when I try to open it in VSCode

I got the following error:

The terminal process command 'The terminal process command 'docker-compose exec iris /bin/bash -c 'command -v ccontrol >/dev/null 2>&1 && ccontrol session $ISC_PACKAGE_INSTANCENAME -U IRISAPP || iris session $ISC_PACKAGE_INSTANCENAME -U IRISAPP'' failed to launch (exit code: {2})' failed to launch (exit code: {2})

I've tested directly the command within the Powershell console executing:

docker-compose exec iris /bin/bash -c 'command -v ccontrol >/dev/null 2>&1 && ccontrol session $ISC_PACKAGE_INSTANCENAME -U IRISAPP || iris session $ISC_PACKAGE_INSTANCENAME -U IRISAPP'

and it works... but not through the Open terminal in Docker which is what is more user-friendly...

Jose-Tomas Salvador · Apr 5, 2019

We have several partners working on industrial sector that have mentioned that having support for OPC UA in IRIS would be great as it's becoming a de-facto stantard in their sector... I didn't dig much into technical details so far, but, based on your knowledge, would it be worthy to have it natively supported in IRIS or is using Java Business Hosts+external Java Library the better approach in this case?

Jose-Tomas Salvador · Feb 19, 2019

OK. We're improving a bit.

I've changed Cache Terminal to CP850 which is the code page that Windows Powershell uses by default:

Now, any idea how could I make up-down keys work so to see the commands' history? Also, as Robert C. also mentioned… it seems that Ctrl-C quits not only from the command/function in execution but from Caché Terminal itself...

Jose-Tomas Salvador · Dec 21, 2018

Thanks Eduard. You are right. Test() method assumed that the ID refers to an object (world) already defined… but I like more your suggestion. I've uploaded a new release to GitHub. Now, if you execute the Test() and the World doesn't exist, it creates one for you... also we can choose the char to represent alive or dead blocks and get the iteration we're seeing...

Jose-Tomas Salvador · May 22, 2018

Hi Bob,

in Windows, for the key/password it works if you just define a volume where the files are. Then the call would be simpler/smaller:

docker run --name iris3 --detach --publish 52773:52773 \
--volume C:\pmartinez\iris_external:/external \
--volume durable_data:/durable --env ISC_DATA_DIRECTORY=/durable/irissys \
--env ICM_SENTINEL_DIR=/durable iris3:test --key /external/iris.key \
--before "/usr/irissys/dev/Cloud/ICM/changePassword.sh /external/password.txt"

I understand that using a named volume will store the durable %SYS within the Linux VM itself which would avoid issues with Windows FS regarding database files updating, permissions,... but, is there any reason why you choose to mount each file separately instead of this way I include? In the end we just use these 2 files (iris.key and password.txt) once when starting the container.

Jose-Tomas Salvador · Apr 26, 2018

Thanks Robert! Glad you like it! It's a pity many times we include new functionalities that cannot be used for customers because is required a recompilation and a change in their class model... sometimes depending on the feature, can be strictly necessary, but I think it's not the case for exporting/importing mechanisms. 

Jose-Tomas Salvador · Mar 17, 2017

I've installed PRTG on a windows 10 system... enabled SNMP services... I've configured SNMP Service to Community "public" destination "127.0.0.1"... PRTG is able to see and graph the system statistics... OK.

Then I imported ISC-Cache.mib with Paesler MIB Imported, OK, and "Save for PRTG Network Monitor"... everything seems fine, but, then, where is supposed to be? When I go to PRTG NM I cannot see anyhing related to Caché ... no clue about the library that I supposedly just imported...  S of SNMP means Simple... so I'm pretty sure I'm missing something really basic here, but I don't know how to go on.