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.
So long Robert! Welcome back... I knew you wouldn't be so far away :-)
Found... I just got to go to add sensors to a group, windows type and snmp library... there it is the oidlib I had just imported!!
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.
Forget it... it doesn't appear in Class Reference (I don't know why), but it's there.
Trying in 2017.1 field test... it seems there is no SYS.Monitor.SystemSensors class... has it disappeared in 2017.1?
Hi, did you check user name and/or password of Demo RestFormsUI? I cannot get access to that page...
I've been unable to install it.... I didn't find kit.zip for Quick Installation ... at least not in GitHub. I've tried the source installation... I installed Python 2.7 and I'm using node.js 7.0.0.... I guess it should be piece of cake.. but I'm getting errors related to node-gyp rebuild... any ideas?
I'm getting some errors compiling the RulesBuilder in the auto-generated class:
Compilando clase Demo.RulesBuilder.ParagraphDomain
Compilando rutina Demo.RulesBuilder.ParagraphDomain.1
Compilando clase Demo.RulesBuilder.ParagraphDomain.Domain
Compilando rutina Demo.RulesBuilder.ParagraphDomain.Domain.1
ERROR: Demo.RulesBuilder.ParagraphDomain.Domain.cls(%CreateDictionaries+33) #1027: Error in SET command : '$zt($p($h,",",2))_": Finished creating ",tProfiles," matching profiles"' : Offset:189 [%CreateDictionaries+28^Demo.RulesBuilder.ParagraphDomain.Domain.1]
TEXT: if pVerbose && ($g(tProfiles)) { if pAsync { set ^CacheTemp.ISC.IK.DomainBuild(+$j,"out",$i(^CacheTemp.ISC.IK.DomainBuild(+$j,"out"))) = $zt($p($h,",",2))_": Finished creating ",tProfiles," matching profiles" } else { write !,$zt($p($h,",",2)),": Finished creating ",tProfiles," matching profiles" } }
ERROR: Demo.RulesBuilder.ParagraphDomain.Domain.cls(%CreateDictionaries+2001) #1026: Invalid command : 'catch' : Offset:8 [%CreateDictionaries+1859^Demo.RulesBuilder.ParagraphDomain.Domain.1]
TEXT: } catch (ex) {
ERROR: Demo.RulesBuilder.ParagraphDomain.Domain.cls(%CreateDictionaries+2005) #1043: QUIT argument not allowed : 'tSC' : Offset:9 [%CreateDictionaries+1863^Demo.RulesBuilder.ParagraphDomain.Domain.1]
TEXT: quit tSC }
ERROR: Demo.RulesBuilder.ParagraphDomain.Domain.cls(%LoadExpressions) #1044: PUBLIC label not allowed : 'public' : Offset:32 [%LoadExpressions^Demo.RulesBuilder.ParagraphDomain.Domain.1]
TEXT: %LoadExpressions(pParams) public {
ERROR: Demo.RulesBuilder.ParagraphDomain.Domain.cls(%LoadExpressions+7) #1043: QUIT argument not allowed : '}' : Offset:11 [%LoadExpressions+7^Demo.RulesBuilder.ParagraphDomain.Domain.1]
TEXT: quit tSC }
ERROR #5123: No se encuentra el punto de entrada para el método '%LoadExpressions' en la rutina 'Demo.RulesBuilder.ParagraphDomain.Domain.1'
6 errores detectados al compilar.
Aren't these "demo tools" useful for general configuration for whatever project? I mean, are they going to appear in future releases or are not so useful in real projects?
I've realized that you can define sets without entities associated and, if that happens, the tabs Table and Sets stop working as there is an internal oref error and no info is produced. To fix it you have to delete the empty set through SQL.
Interesting article and discussion btw :-) Including this new Data Model is a clear and great enhancement to the product imho. I wonder if performance considerations are being taking into account in design and implementation decisions. Are there any numbers about it? How do we compare with our own SQL over relational structures? How do we compare against competitors?
That's great! All major companies have twitter accounts even to give some basic support. Will we provide also that kind of service through twitter?
Great article Alexander! One question. Why is there such difference in performance of $order? How could this affect to the general performance of an application using not Caché Standard for globals and mainly using SQL access to deal with data?
I've tested your ordering routing with Spanish2, 4 and 5 collations and are >4 times slower in inserts and order... !!!
Many thanks!
Great article! I see there is no scenario where the failover members are in different locations. I guess latency factor is the one to blame here, isn't it? Are there any numbers based on your experience that allow others to get an idea about what scenario is more appropiate for them to choose based on expected # of transactions, total volumen of data, required response time, network latency and/or other criteria