Another Successful Update

Back in April of this year (2009), I once again updated this BlogEngine.NET installation with version 1.5.0.7, the latest available both then and still now.  Overall the this is the second time I've upgraded BlogEngine.NET and it went very smoothly.  As I had done on both the previous upgrade and original install, for this upgrade I also followed the very easy to understand upgrade instructions provided by Al Nyveldt.

Teaching An Old IT Dog New Tricks

In all my experiences with installing, upgrading, and using BE.NET, which are simultaneously not extensive, and yet not inconsequential, I have been consistently been finding that things work as they described to do and as expected.  With many years experience in corporate and large-scale information technology, I'm very impressed with the stability, ease of use, features and extensibility, and ability to support customization of BlogEngine.NET.

Admittedly, I don't have as of yet, a great deal of experience with blogging platforms, but BE.NET is serving me well in my long and winding journey to learn and understand the technical nuts and bolts of blogging platform alternatives.  That's exactly what this blog is about.  So far, so good with BlogEngine.NET.

Son of Blog(Engine.NET)

Just finished upgrading this BlogEngine.NET blog from 1.3.1 to 1.4.5 and all went fairly smooth.  Followed the upgrade instructions and watched again the screencast just to double check the installation process.  The only catch I came across was the Profiles function threw an exception when I clicked the tab in the Control Panel.  A little staring an the cryptic ASP  server error message, a little poking around the files and a look at the BlogEngine.NET discussion board, and I realized I missed a folder in the upgrade.  As suggested by the upgrade instructions, I replaced the APP_DATA folder in the new install with a backup.  And thus lost the Profiles folder in APP_DATA.  When I copied it in from the upgrade files, the Profiles tab worked just fine.  No harm, no foul so far.

Back In The Blog Saddle 

It' been a good 6 months since I was last here but I'm looking forward to picking up where I left off.  Just highlights of adventures in the IT world in which I work and all other things tech which constantly interest and occupy me.

Suppose I probably should throw a little non-tech writing in there just to mix it a bit.  Life, work, fun, and technology; fortunately it's all good for me.  Been involved in a lot of interesting stuff over last months, so hopefully I'll get some of the details posted here again.

True it's been a mystery lurking on our Data Integrator server for some time.

But more than perplexing, it was really annoying.  As part of the on-going to process to better understand, control and hopefully make use of the web based components installed on a Data Integrator server, I bumped into a vexing, albeit, innocuous security related issue.  As mentioned in the previous post, the Data Integrator installation utilizes Tomcat for web-based admin and management features.  And in the course of exploring the web serving components of that environment, occasionally a login dialog boxed would pop up requesting a user ID and password to proceed.  At first, I didn't even pay attention to exactly what the URL (URI) was that would cause this "oddity". 

Everything important related to the operation of Data Integrator has been working fine and accessing its web admin via the appropriate URL did not cause the login pop-up to appear so there's been no great urgency to find the cause of the mysterious dialog box.  In addition, the DI installation does not use the standard HTTP port of 80 to bring up the main admin page, instead using 28080.  While experimenting with several different Data Integrator URLs, all including the custom port reference, to access different DI admin features, I tried just the server name without any port reference and nothing came up.  Just the standard page not found message.

Knowing that DI was being served via Tomcat as well as the fact that Tomcat use port 8080 as a default , I tried a URL that included the server name and that port such as http://server:8080.  And viola, the mysterious login dialog box showed itself.  Gotcha!  Now we know what ever is throwing the login request is listening on 8080 and it definitely doesn't look like its Tomcat.

But what have I really found out?  What the heck is throwing up this login box?  Data Integrator has its own log in page and it works fine sans the dialog box when accessed through proper URL including the custom port assignment.  Time to get a clue.  And there was one right on the login box: "XDB" was displayed above the text entry fields in the dialog.  But again, now what?  Hmmm... XDB...  XDB...  What's that coming from?  And it looks familiar too.  Wait a minute, I've seen XDB.  It's schema in an Oracle 9iR2 database.

Not only is it a schema in Oracle 9 and higher, it's part of of entire XML feature set now standard with Oracle known as Oracle XDB.  Oracle XDB provides for built-in XML capabilities directly integrated within the Oracle database environment.  After researching I decided that perhaps the dialog box wants the credentials associated with XDB schema (I realize when properly configured other login credentials would likely work as well, but no part of XDB in our installation has been specifically configured at this point other than what goes in as default with database installation).  So I did an ALTER USER on XDB  to unlock the account and reset the password to give it try.

Thinking I've got it figured out and expecting a pleasant outcome I try it.  No dice.  What? This can't be right.  Must be a mistake; I'll try again.  Nope.  The dialog just keeps coming back with every attempt eventually resulting in an "unauthorized" page.  Son of gun...  More reading and a lot of Google uncovers that this is not a particularly unique situation, but the answers as to the cause and the solution are elusive.

Our Data Integrator, like many others, uses Oracle as its back-end repository (not familiar myself if other DBMS can be used for the repository but I suspect so).  And Oracle XDB is part of the Oracle installation by default.  But to further mask the cause in our particular situation, we have another separate Oracle instance running on the same box along with the Oracle instance used by Data Integrator.  It was in this other instance in which I originally changed the XDB login and it turns out this was not the instance listening on 8080, thus no access.

When I opened the XDB login on the Oracle instance used as the repository for Data Integrator it worked!  Up came a directory listing in my browser representing the XML structure residing in and served by the Oracle database serving as the Data Integrator repository.  In finalizing the solution I wanted to now switch from using the Oracle XDB feature in our DI repository to using XDB via the other Oracle database residing on the same box so as not "disturb" the DI repository database.

In the course of researching this situation, I found several options to accomplish this switch.  These included such tactics as disabling the Oracle XDB features completely or changing ports for listening.  What I ended up  doing was leaving everything associated with the Data Integrator repository database as is including XDB enabled on 8080.  I then reconfigured the other Oracle database to listen for the purposes of XDB on 8081 instead (I alse changed the default FTP port from 21 to 2111).   I found the details of these changes on the Internet will put up some links in a follow-up post.

The good news is all seems to be working under our control and now we can put Oracle XDB through a few paces without impacting the Data Integrator installation on the same box.  Mystery solved.  At least until the next one!

Last week I was working with Apache Tomcat off and on, building an understanding of the basics of its operation.  One of the platforms I work with regularly is BusinessObjects' Data Integrator and the version we are using runs on a HP-UX box.  The web administrator for Data Integrator uses Tomcat as its application framework (Oracle is the main Data Integrator repository).

I wanted to get a better understanding of how the web admin is enabled on the back-end and that led me to Tomcat.  As usual I began looking for and reading all the Tomcat related information I could find.  I was quickly scratching my head trying to understand all the pieces that made both Data Integrator and Tomcat do the work they together.  Honestly, I found the "documentation" on the Apache Software Foundation website less than beginner friendly.  A delivery from Amazon of the O'Reilly Tomcat book didn't help much at first.  Both the Apache website and the O'Reilly  book seemed like they will be more useful as my knowledge increases.

But I've stuck with it and have made some good gains in my understanding in the process.  I was able gather from various readings that there are both sample and administration applications as part of a standard Tomcat installation, if they haven't been removed.  Notice the qualifications of "standard" and "haven't been removed".  I wouldn't necessarily call the Data Integrator setup of Tomcat standard.  I don't think it's particularly unique but it's (DI) a commercial, production distribution and I shouldn't expect that everything would be as it described in available documentation on the Tomcat platform.

Fortunately I have worked with Java technology in the past and have a working knowledge of various implementations, including servlets and JSP.  But I couldn't find the Tomcat samples or Manager webapp on our installation.  With some persistence I was able to piece together the required elements and eventually get the Manager app working in our Data Integrator environment.  Let me say that there wasn't any problem with Data Integrator; I merely wanted a better understanding of how Tomcat was used with Integrator and what options we may have for integrating or enhancing other development within the existing DI/Tomcat infrastructure.  I figured implementing the standard Manager webapp, since it wasn't there and it's part of the Tomcat distro, would be a useful exercise.

This has proved to be the case and I now having the Manager webapp working within our Data Integrator installation and the DI portion has not been adversely affected.  I assumed (hoped) this would be the case, as from a "textbook" perspective there doesn't seem to be any reason why this wouldn't be possible.  Not only should it be possible, my understanding is that running this different components (Data Integrator and the Manager webapp) withing the Tomcat framework is exactly what Tomcat was designed to do.  I would guess that Tomcat experts would say, "Of course; what's your point?"  Well I've already mentioned that I wanted to see how this works and in my usual fashion that meant doing it, that's all.  In hindsight not particularly difficult, but then again if you haven't done it before it can be challenging as well.

Gadgets, Widgets and Flakes Oh My: We're not in Kansas Anymore Toto

Spent some time further exploring the "personal page portal" sites of Netvibes, PageFlakes and iGoogle over the last few days.  All pretty interesting as far as the current state and evolution of personalized content.  At first the power of customization seems a little bewildering and had me thinking "Can (should) I really do this?"  You mean I don't just click on a site and sit back and have the content spoon fed to me?  I'm not used to this; will it be work?  I might have to express myself by selecting and interacting with content?  What's going on here?!

Chips Off The Same Block

In some ways, the three sites are very much alike, almost identical in their general function and purpose, and even in some of their basic interface elements.  In some ways..

Yet there are also clear differences in each site's style and "presentation attitude" if you will.  Yes, you customize the content on each in a very similar manner picking from hundreds of chunk-line building blocks of web information, RSS feeds, social network providers and all sorts of other personal and public content.  And while each has a different name for these content building blocks -- on iGoogle they are Gadgets, on Netvibes they're Widgets, and on Pageflakes, they're Flakes, the general idea is the same.  The understanding you develop playing around with one easily translates to the others, making learning curve very portable.

Nuts and Bolts

Each site provides the ability to select from at least hundreds if not thousands of gadgets, widgets and flakes respectively.  Once the blocks of selected content are on the page, you can move them around to your liking, change interface appearances, and hide or remove them.  Each site also provides for customization of the overall page appearance in general, allowing you to select colors, themes, adding text, and etc.  You can create what amounts to multiple pages by adding tabs to organize the content.  I particularly a new Weather Channel radar gadget on iGoogle.

You Go Your Way, I'll Go Mine

Though the three sites have much overall functionality in common, they different quite a bit in presentation and attitude.

I Think Can... iGoogle

iGoogle has Google's typical white with blueish lines appearance by default.  The content gadgets appear in generally plain boxes of fixed width on the page.  Each gadget has controls that are common to all to control appearance, share with others or access content specific settings.  The iGoogle "attitude" is one of having easy going fun in my opinion.  It's a light feel.

Good Netvibrations

Netvibes goes in a distinctly different direction as far as appearance, presenting itself in an ultra modern online style.  Colors are rich and slick by default also with squared content boxes.  It has all the same operation features as iGoogle and 'Flakes but with more adult feel.  If it were a radio station I suspect it's genre would be "Alternative".  Netvibes also makes specific mention of its mobile version for small devices which I did try on a Palm.  I did come up in a greatly slimmed down version.

No Flake Is Alike 

PageFlakes also has all the same functionality as the others presented in an up-to-date, inviting and clean package.  If it wasn't a page in a browser, I wouldn't be able to tell it wasn't a normal and very currently presented application on my system, complete with drop shadows and animated barber-pole progress thermometers.  I also explored the pages that are available from other users and content providers that present almost as mini websites known as PageCasts.  Pageflakes was the only one of the three sites where I quickly found and customized a local cable TV schedule display.  (I believe it came on the public page by default!)

If You Build It (Or Not), They Will Come

Each site provides access for anyone (OK, "developers") to build gadgets, widgets and flakes.  The system on iGoogle was pretty easy to start using with plenty of help and direction available along the way.  I even linked in a little content of my own through the API.  But if "rolling your own" isn't for you, as I've mentioned all sites had a multitude of pre-built modular content from which to select and customize your pages including every major online service and content provider.  Of course, being the tech that I am, I linked in a RSS for a favorite Oracle discussion site and ended going astray from my touring while reading the I-never-get-tired-of-it subject of database performance tuning.

But I guess that's the point of these sites, to get you just where you want to go.  All in all another worthwhile recon mission.

OK, so it may be obvious that I'm new to blogging.  But hey at least I'm doing it which is a step up from where I was at: that would be nowhere.  And it may provide an opening to a bit of humor I enjoy using when I can.  That's when someone offers an unsolicited review of an endeavor usually negative in tone or substance.  This particular comeback requires that the person offering the "advice" isn't themselves doing anything with regard to the subject.

Then I can say, "Well let's take a look at what you're doing.  Oh, that's right, you don't have anything".  Well at least I'm trying something totally new for me.  And I'm not only achieving the goal of giving blogging a test drive, I'm doing it in a way which really suits my technical curiosity by setting up and then using and tinkering with the BlogEngine.NET platform.  SSSSweet.

Don't Get Cocky Kid!

Some may remember that line from Star Wars (oh god, a geek mentioning Star Wars, now I'm really stereo-typing myself).  Perhaps there's a reason it popped into my head just now.  Perhaps I should consider that advice.  On the other hand, can being pleased with actual accomplishment really be construed as arrogance?  This is working out well technically and as added bonus I'm learning and finding that I enjoy the medium to boot.

Baby Step Blogging

Since I've always enjoyed the humorous application of lines from movies, another one comes to mind now from "What About Bob?"  That would be baby stepping.  No doubt I've got a lot to learn about about blogging and Web 2.0 in general, but that's why I'm here.  In a short time, I'm realizing that when done with some thought, it's an engaging creative activity.  Previously I vaguely felt it was self-indulgent at best, if I gave it much thought at all.  Next I need to learn how to write shorter posts! 

(and add "blogging" to the spell check dictionary)

(and my personal holy grail of writing: how to not think faster than I type leaving out words along the way)

Well as part of this on-going experiment to explore both technical and creative aspects of blogging, I'm exploring Technorati.

Though I've been working diligently in technology for over 20 years, I have a lot of updating to do as far as my own knowledge of current tech trends in general, Web 2.0 and social networking specifically.  To this end, within just the last few weeks since setting up this blog, I've follow many interesting leads into these current areas of technology and the Internet.

I've pickup a lot of understanding about social bookmarking and even install another open source platform for server-based personal bookmarking (more on that later).  I've explored Netvibes and Pageflakes.  Very interesting.  I've played around with iGoogle and studied their widget system.  And snooping around Technorati.

After successfully converting dozens of tables in an Oracle data warehouse from uncompressed to compressed without so much as a single glitch, several problems cropped up last week.

We are also using BusinessObjects (now SAP) Data Integrator for ELT operations and have been for over 2 1/2 years also without much issue generally speaking.  The tables in question were just recently converted to compressed and then we started seeing a relatively small number of problems with our Data Integrator loads.

The problem presented itself when we truncated the compressed tables and then subsequently reloaded them.  We then seemed to be having problems with duplicated data.  No errors were given with truncating the tables in question.  It wouldn't seem possible that we'd get a problem with duplication after truncating a table, but nothing is taken for granted.  There was apparently no duplication in the source data used to popuate these tables.

When we switched the tables involved that we had changed back to the original attribute of uncompressed, the problem immediately went away.  And though we have converted dozens of tables to use compression as mentioned, all of which part of Data Integrator load jobs, we've only seen these issues involving a few converted tables.

We still have more investigation to do on this and we're not entirely certain it's related to the use of compression, but it sure seems more than just coincidence.  Also I don't know if I have the facts stated 100% correct but I think my details are pretty accurate nonetheless.  We'll see what we can determine but I'm still satisfied the use of compressed tables is reliable and worth the space we have reclaimed.

An on-going task as part of an Oracle based data warehouse with which I've helped develop is to review and enhance the design of schema objects (tables and indexes for example).  Space utilization and performance are among the primary characteristics to review.  You may suggest, possibly even strongly, that these are factors to be included in the initial design stages.

To that I can respond that they were.  At least to the best knowledge available to the development team at the time of initial design.  The good news is that the data warehouse and the reporting and analysis activities it makes possible has continue to increase both in data available and in use and value to the business overall.  While growth is the majority trend, some data has not been used or does not change as much as initially estimated.

One of things we've been doing is implementing the compression feature of Oracle on tables and indexes were appropriate.  With many months of historical data now available from a substantial and growing list of source systems, we are going back to look for data with a high occurrence of repeated values as candidates for compression.  It turns out this is a majority of the data.  As implemented thus far over several months,  compression has reclaimed upwards of 50% of previously used space without compression.

And the performance hit as been unnoticeable.  In fact daily ELT process may have increased as increased I/O efficiency outweighs slightly increased CPU overhead for compression processing during DML.  The nice thing about this experience with implementing Oracle compression is that it is not a theoretical exercise.  This is our actual experience and we track before and after metrics to observe any positive or negative effects. 

After four or more months of applying compression, the results are only positive.

Several days later since my last and BlogEngine.NET stills seems to be running smoothly.  I installed the spell check function (ieSpell) without a hitch and that seems to work as advertised; very similar to Word.  I was also able to add a nice link button to LinkedIn in the About the Author box.  I'm curious to see the possible effect, if any, of including LinkedIn links may have on search results. 

So, pardon me if they are sprinkled through the content here.