go to post Fabian Haupt · May 30, 2017 Hard to say anything generic here, but if you are transporting sensitive data (or really any time, actually), you should use both authentication and encryption (ssl on the transport layer) -Fab
go to post Fabian Haupt · May 26, 2017 Why don't you just set the initialexpression to the current date? That's the easiest way in this case.
go to post Fabian Haupt · May 25, 2017 You can do: s ret={} s ret.propa={} s ret.propa.subprop="something" Ok! I have just one more question ... s ret = {} s ret.IdClient= "123" How can i do something like that ?: s ret.client.name = "peter" When i try ...
go to post Fabian Haupt · May 25, 2017 You could create a temporary object and just put in the properties you want: USER>s ret={} USER>s ret.idDate="something" USER>s ret.Datetime="something2" USER>s ret.time="something3" USER>w ret.%ToJSON() {"idDate":"something","Datetime":"something2","time":"something3"} USER>
go to post Fabian Haupt · May 22, 2017 Part of testing with populated data is performance testing. If your data populating utilities can't give a high enough throughput, you can't really test your application under load. And generating meaningfully big sets of data requires a lot of time. So for example, with Caché populate utils it takes 7.891 seconds on my machine to create 1M pairs of , The same takes 0.39s on my machine with a rudimentary go implementation. I very much disagree that performance doesn't matter. In terms of an online service, you could do something like: curl -H "Content-Type: application/json" -X POST --data '{"count":1000000,"headers":false,"fields":[{"name":"Name","type":"name"},{"name":"Age","type":"digits"}]}' http://data.panadadata.com -o data.json (disclaimer, I run that service)
go to post Fabian Haupt · May 22, 2017 If you need a quick intro on how to use Websockets with Caché directly: https://community.intersystems.com/post/asynchronous-websockets-quick-tu...
go to post Fabian Haupt · May 18, 2017 I am not aware of any WS client implementation in COS. Keep in mind that WS would mean a continuous connection, which doesn't really fit with the Operations model for Ensemble.
go to post Fabian Haupt · May 18, 2017 Nikita, he is also asking about cache as websocket CLIENT not as server.
go to post Fabian Haupt · May 17, 2017 Not sure what you are asking? Since you implement the handling method for REST services, you can handle any format? -Fab
go to post Fabian Haupt · May 17, 2017 https://community.intersystems.com/post/lets-write-angular-1x-app-cach%C...
go to post Fabian Haupt · May 17, 2017 What are you trying to do? Where/when are you getting the error? -Fab
go to post Fabian Haupt · May 16, 2017 Do you have any benchmark data comparing this to the populate utils? Cheers, Fab
go to post Fabian Haupt · May 12, 2017 Hi, it depends a little bit what exactly the bottleneck is. If it's the processing, you could possibly split the reading from the processing by inserting a scheduling mechanism and just have the read process queue up things and several worker threads for the processing. If the bottleneck is the reading, there is not much you can do. Reading from the same file in multiple locations is going to make it slower overall. Best, Fab
go to post Fabian Haupt · May 9, 2017 Hi Murali, from looking at both of their websites, it seems they are just web scanners? If so, you don't need to do anything different to run it against your InterSytems powered web pages. You can use them the same as with any other webpage you're scanning. Cheers, Fab
go to post Fabian Haupt · May 8, 2017 Murali, you should check the URL being created (i.e. Request.Location_Path and see if that actually exists and you have access to it. Also keep in mind this code is fairly old, so you might need to adjust it a bit to run with the current json utilities.
go to post Fabian Haupt · May 8, 2017 looks like the code from here: https://github.com/intersystems-ru/CacheGitHubCI/blob/master/CacheGitHub...
go to post Fabian Haupt · May 4, 2017 Hi! A couple of things to note/check on your end: %SYS_Monitor service is enabled (and is not restricting access for your IP) Make sure the iscsnmp.dll is registered. You can run d $ZU(190,5,0) to delete the registry entries and d $ZU(190,5,1) to add them again. Restart SNMP in Cache: zn "%SYS" d stop^SNMP d start^SNMP Make sure there is a SNMP job running in your instance (System -> Processes, filter for SNMP) Make sure the windows firewall allows connections, in doubt you could disable the windows firewall service temporarily For debugging you can set: s ^SYS("MONITOR","SNMP","DEBUG")=1 Which will create a SNMP.log file in your mgr directory. As well as in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intersystems\Cache\SNMP\CurrentVersion (for 64bit) "Debug" = "true" (String value) Which will create a file snmpdbg.log in c:\windows\syswow64\snmpdbg.log Then you can try and get a value directly like this: snmpwalk -r:"localhost" -os:.1.3.6.1.4.1.16563.1.1.1.1.3 -op:.1.3.6.1.4.1.16563.1.1.1.1.4 (or you can use a tool like the iReasoning MIBBrowser..., import the MIB from directory>/SNMP) Hope this helps. Best, Fabian
