What’s a Database Back-End good for when you can’t view the data in any practical way ?
I’ll spare you just how pleased I am that OfaDB now has a proper graphical interface.
Let me go ahead and tell you what it does, and you’ll understand right away.
Did you know that …
- Ofa 3 now seamlessly logs details and hash sums on every log file, source file, input file – even generated and output files, and sends them all to OfaDB.
As you’d expect, level of detail is controlled via Ofa’s astute fine-grained settings management.
- OfaDB stores and crosslinks all those files and details in its tables.
- All (logged) execution variables, warnings and error messages are equally stored, checksummed and cross-linked to the log.
- Data recorded in OfaDB is highly tamper-proof.
You can tell with absolute certainty which exact copy of any logged file was used in a run.
- You can upload all available log files of your ofa 2 batch history.
This will give you starting material for some insight into your operational history like you never knew was possible.
And a sense of the position you’ll be in with the vastly more complete Ofa 3 data …
Okay, then you must have read the previous post about OfaDB.
Now: APEX’ Power
OfaDB’s Data Model is great: it stores every discrete element only once, and ties them together in an efficient, quasi-unfalsifiable way. It should scale big, thanks to all its foreign keys being based on indexed hashsums. As a DBA, I am pleased with the result – yes I am.
To tap into that amazing wealth of valuable information, most obviously an effective interface is needed. And, as far as I’m concerned, one that gives me a straight path to what it’s all about. Therefore, OfaDB’s Data Model was designed with APEX in mind.
APEX is the obvious choice. It’s safe to say that no other application engine lets you slice and dice your data more quickly and efficiently to your heart’s desire. You can knock up an application in a matter of hours that puts the most stunning reports on your data at a mere few clicks of the button.
OfaDB comes with one that should become indispensable from day one:
- View any past period of any and all Ofa jobs, all in one list.
- Filter on status, app, environment, server, you name it.
- Drill down to full logs, sources, warnings, errors, variables, configuration files, input or output data in a few clicks.
- Graph, list, aggregate them.
- Download them raw, as pdf, as csv, or view them right in the browser.
- Know differences, drifts and variations instantly.
- Monitor execution times, error quotes, seasonal peaks and events.
- Save your private custom reports and filters.
- Prove your point, crack the knack, spot the pattern, score the growth.
- The list goes on …
To be honest, OfaDB with APEX brings you as close as you can get to Absolute Traceability.
Pretty close, that is. Closer than anything I’ve seen or heard of.
In your operational environment, nothing much has changed.
A few parameters were set in the core, one job set up for collection.
In- and output files to ship are flexibly set in your scripts’ usual parameter files.
Logs now come out in two formats: XML + plain (post-processed).
Console output and mail stay about the same.
No script needs changes, no performance hit ensues.
The loader hashes, registers and copies (new) source and input files to the queue.
The log checker does the same with output files.
The master collects everything into staging and OfaDB slots them in.
That’s it, no tricks.
You just point your browser at OfaDB, coffee in hand, feet on desk – knowing you have a new instrument at your disposal now for morning meetings, night time fun, trouble shooting, auditor soothing, fact checking, chicks netting – all the while having more time for kiddies, spouse and house… and maybe just maybe, discover new beauty in life.
The story doesn’t end there. Detailed graphical information about OfaDB is due to come soon at www.onobase.ch.
I expect the Ofa revolution to break out any time now – be sure not to miss it.
Olaf, your Ofa Oaf.