D
dbeavon
Guest
The oem uses progress vst tables under-the-hood (at least for OE-database-related information). You could access vst's directly (and they are fairly well documented). That is probably the "right" answer. But you can inspect the traffic that is being sent back-and-forth to the browser while you are using OEM. You will find that will often pull up a JSON-formatted data file, before rendering it to HTML for visualization. This JSON stuff is probably NOT well documented, and the JSON is likely to change over time (although not at a rapid pace). However I find it more comforting to use these JSON files than to go get the VST's directly. Sometimes there are obscure tricks to querying the VST's and if you don't do it just right, you will have an inefficient query or worse (negatively affect the server itself). I recall that using certain VST's the wrong way (maybe it was locks?) would cause the database to become unstable in the past. Those kinds of experiences are hard to forget, even after the bugs are fixed.... If OEM is getting its information from VST's, and you are getting your data from OEM, you can be pretty sure that the flow of data has been well-tested and Progress has optimized it to whatever extent they could. Below examples for getting raw JSON from oee/oem. In these URL's you will see references to are "mydatabase" which is a scripted-style database. You may want to inspect your own local traffic as you browse normal OEM pages, and find URL's for the JSON equivalent of each page. Normal OEM page (database connections from scripted database): myserver:9090/.../dbconnections.jsp JSON equivalent of database summary view myserver:9090/.../DatabaseSummaryView JSON equivalent of connections myserver:9090/.../connections JSON equivalent of current user locks myserver:9090/.../DatabaseLocksViewlet Hope this helps.
Continue reading...
Continue reading...