go to post Nikita Savchenko · Mar 14, 2018 Kumar,Does it have the same network configuration (any load balancers/firewalls/etc)?
go to post Nikita Savchenko · Mar 6, 2018 Did you compile them in samples namespace as shown in webapp settings? Also are you sure that nothing unexpected is set up in front of Caché which can prevent normal routing (like load balancers/other routers)?
go to post Nikita Savchenko · Mar 6, 2018 Hello Alexander!Yes, these are definitely the good points to improve the application. But most likely Class Explorer will be rewritten from scratch rather than enhanced with new features. This is because the internal framework choosed for development on the very early stages is very hard to extend.We’ll take a note you mentioned for the future software! Thank you! Maybe you’ll also like my other projects like Caché Visual Editor, check them out.
go to post Nikita Savchenko · Mar 6, 2018 Hello Kumar!Did you compile the classes you’ve imported? Try importing and compiling ClassExplorer.xml once again.
go to post Nikita Savchenko · Jan 29, 2018 Thank you Rich for noticing this. We’ll update the links shortly. This problem is related to WebTerminal repository migration to intersystems-community organization on Github. Follow WebTerminal there!
go to post Nikita Savchenko · Dec 21, 2017 Nice! Thanks! At least I diagnosed the problem: that's because I/O redirection, there's no I/O redirection routines in a new mnespace if the routine performs any writes or reads.We need to find a better way to intercept Caché process I/O. Any help is very welcome!
go to post Nikita Savchenko · Dec 20, 2017 Hi Alexey!This is a known issue I still didn't figure out how to solve. If you can help here in any aspect (for example, how did you figured out that the thing is in DAQ() code?), it is very welcome. Please - continue bug/feature discussions as well as this one on Github.In short, WebTerminal had problems with mnemonics, and what I did to solve them is a bit crazy - I just copied the code from %X364 to let them work here, as that code was utility. Maybe, there is a better solution, but I didn't came to it because of my lack of experience at some point.Alexey, any help is very welcome. Do you know where even to find ^JOBEXAM's code to investigate the problem? Thanks!
go to post Nikita Savchenko · Nov 27, 2017 Thank you very much, Robert! Good to know about MANAGEDEXTENT, I have never heard of it.Do you think it's okay just to copy storage definition/globals as people suggest below? (to duplicate globals data and alter storage definition to use new globals)
go to post Nikita Savchenko · Nov 12, 2017 Thank you Gerd! Paul just posted the same answer a little while ago :)
go to post Nikita Savchenko · Jul 6, 2017 Maybe you just need to update Atelier? I checked mine, and it has everything to export CSP files, both from context menu and project export menu (right click on project -> Export):
go to post Nikita Savchenko · Jun 26, 2017 Joining this question.It would also be nice if someone could describe how to catch and process I/O at this point. Ideally I am looking for something like:set pseudocode = ##class(Any.Util).Execute("cmd") // let's say on Windowsdo pseudocode.Write("ipconfig")// loop may go hereset data = pseudocode.Read()// loop may close here// ... and the data is the stdout of the process! Thanks.
go to post Nikita Savchenko · Jun 26, 2017 Thank you Stephen for your feedback. I will try my best in finding the way to make it all work together.
go to post Nikita Savchenko · Jun 26, 2017 You are welcome! Glad to hear that it works. I hope that functionality WebTerminal v2 has will be enough!
go to post Nikita Savchenko · Jun 26, 2017 Hello Yuval!To install WebTerminal 2.0.0-beta.8 on Caché 2013.1,1. Go to WebTerminal Downloads and download the version 2.0.0-beta.8, which is the XML file. This page also has some instructions about how to set it up.2. Using Studio or whatever you like, import this XML file into the %SYS namespace and compile all imported classes / CSP pages. If you have the "access error" while importing classes, then you need to temporarily enable write access to CACHELIB database, see here how.3. Open <host>:<port>/csp/sys/webterminal/index.CSP page in the browser.The dark part of using v2 is that this version of WebTerminal is very old and have a lot of things that were improved in 2 major releases v3 and v4. Furthermore, despite of it was tested on 2013.1 (some particular version) it may not work there now, as it seems like some changes in WebSockets appeared in InterSystems WebSockets engine, and probably 2013.1 may have a minor release adding them. But anyway, you can try.Versions 3 and 4 of WebTerminal is not compatible with 2013.1 for the only reason — they use %CSP.REST classes. You can try to port WebTerminal resources onto CSP, but this may not be trivial.Let me know if this helps! I will add this instructions to the WebTerminal downloads page. Thanks!
go to post Nikita Savchenko · Jun 16, 2017 Sounds good. I think I need to do a little research on Caché ssh (internal ssh?) to imagine how this can work. Thank you.
go to post Nikita Savchenko · Jun 15, 2017 Once it continues to be web terminal, it can be integrated everywhere, even to Atelier. For example, WebTerminal was easily embedded to Atom COS Studio and Visual Editor projects.
go to post Nikita Savchenko · Jun 15, 2017 Via SSH (putty, etc), am I right that you need to call csession <instance> to enter the Caché terminal? If so, there is no talk about SSH at all. I think there should be a talk about of how to run csession programmatically from Caché ObjectScript. But for remote sessions, without WebTerminal's code installed on the system, it makes sense.
