WHY DALIL

While for the last 12 years IBM was focusing on promoting its GUI interface to administer WebSphere, it failed to deliver a UNIX command line oriented reporting tool. On the whole, IBM lacked a data warehouse mechanism for a cloud environment that is densely populated by WebSphere. Deriving reports from the IBM scripting tool is neither inductive nor is it coherent, hence managers depend on fuzzy reports that are inconsistently written and often confusing, adding aggrevation and cost to administration.

Dalil solves the problem for administration of cloud computing environment.

We do not to compare Dalil to any other software, since there is no software within its range for it to be compared to.

We list the many advantages of using Dalil:

  • Dalil uses a patented apparatus in comparing XML files and in transforming WebSphere configuration data;
  • Dalil uses an internal report generator that can be customized by user;
  • Dalil uses the command line and depends neither on WebSphere runtime engine nor its JVM;
  • Dalil output can be formatted as plain text, or nroff format hence to support dumb terminal in a data center.

ABOUT DALIL

Creator of Dalil a Programmer and System Integrator

Bassem's Computer Science & Intelligence in Dalil

Bassem W Jamaleddine designed and programmed Dalil. He is a middleware engineer and system integrator with a decade’s contract experience with IBM. In the 90s, his research focused on distributed systems, compiler construction, functional programming for loosely coupled muliprocessors, and fast mathematical exploitation of pattern matching and parallel algorithms. Bassem is a long-time WebSphere system integrator from its earliest version in 1998 until the latest version, 8, of 2011. In the 90s he administered and benchmarked the IBM Super Power Parallel computer SP2. He enjoys restoring old machines like the Heathkit and the micro computer PDP-11, hence the amber screen shots and the nroff formatting that show up from time to time on this site.

ARABIAN COFFEE AND XML INDUCTION

Arabian Coffee and Xml Comparison

It all started two years ago when I was having my morning coffee: I looked at the residue of sediment which formed at the bottom of cup, and the interesting picture it formed. Throughout the Arab world, reading coffee grounds is looked upon as a means of reading one’s future. Though totally incredulous of such divining techniques, I noticed that there is a mathematical aspect in the arrangement of lingering grounds. Looking at the residual layers of the coffee, one thing strikes the mind: would it be possible to compare the residual layering deposited in two separate cups? Thinking of an approach to effect such a comparison, I thought of mapping the layers into numbers, then deriving a function that can produce these numbers -- an approach I think fractal mathematicians could be persuaded to follow. I dismissed this first thought and proceeded with a second approach: what if I were to develop a parser, hence providing grammatical rules that do transformation drawings formed by the layer? "Yes! Grammatical rules; transformation; mapping them into linear form, then comparing the layers by mining them!" Forgetting all about coffee grounds, I directed my attention to the essence of the problem at hand: XML comparison would be much easier to achieve using a well-thought-out approach than to compare the residues formation of coffee. Comparing two XML! And there the answer was, right there at the bottom of a cup of coffee.

AN AMBER EMPIRE STATE

Dalil Works on Amber Terminals

Like Proust and his madelaines, one evening looking at Empire State Building with its top illuminated in amber, I was brought back to graduate school: coding on amber-screened VT320 DEC CRT, VAX terminals strewn across the laboratory’s floor. Snobbish as it may sound, programming on these machines was real programming, requiring concise coding, precise editing, incisive formatting manual pages in nroff: caveman UNIX programming. Even with limited memory and CPU time, we could achieve a task in couple of hours that today would require weeks. Even with thousands of times more memory, supersonic CPUs and unlimited managers available currently, coding was more consistent and less prone to breakage. Until this very day, I keep the style of logging onto the amber terminal, so I can test my programs output is properly formatted for them. Once thing for sure, I will never mess up with the nroff for my manual’s pages.

A RED-AMBER EMPIRE STATE

XML Differences in Red

The Empire State was amber and red the next evening. The amber screen is sufficient to portray a matrix, however, I needed a different color to contrast the contextual differences when comparing data sets. Red is the color to cast XML differences into relief. Whenever red is not available, like on an amber screen, it suffices simply to generate NROFF formatting to replace the red with a bold printing.

DARK EMPIRE STATE

So obvious a child could see it!

There is no light on the top of the Empire State: it is dark. I looked at it for couple of minutes, frozen in concentration. Is there something that I missed? What if there is no light on my amber screen, or, what if one cannot see at all? Once again, something is missing: I missed to account communicating the comparative data to the sightless. But the approach of my "amber screen programming" was already in a place to produce a proper format readily readable to all.