Who Are You Working For?

Before we talk about the details, we need to understand why we are doing what we’re doing.  For me that starts out with defining who we’re doing what for.  So when implementing a web content managment system, even one without an external integration requirement, who is the primary customer?  If you’re thinking the end users or consumers of the site, you’re wrong.  End users are of course important, but as an implementor the primary customer is actually the content contributors.  The often overlook contributor is the first person that should be considered with every requirement or approach.  The reason of course is that a content management implementation is not about implementing a web site, it’s about implementing a tool that allows content contributors to implement and manage a web site.

So what are we looking for in a good contributor-oriented approach?

1. The process should be as simple and straightforward as possible.  Obviously that’s a subjective statement; one person’s simple could also be Lotus Notes.  Contributors vary in skill level and functionality differs with requirements; what we’re striving for though is not necessarily a process that is so simple a child could do it, but one which allows contributors to work as easily and efficiently as possible.
2. Contributors should not need outside assistance or coordination with other groups to contribute content and post it to the site(portal/ external application).  This is a huge no no.  If the contributors need to call developers to move content or have it appear on the site, there’s a huge obstacle to adoption in the way.  Unfortunately this is often one of the first compromises that often happen when integrating with an external application.
3. The basic features of web contribution should be available; images, hyperlinks and basic formatting(bold, underline, italic, bullets, etc) are going to be expected. If have the discussion forums out there support indenting..you’re probably going to need that feature too.
4. Contributors should feel confident that they cannot break their site.  Ideally this means they should not have access to tools or formatting which can break the look and feel of the site.  Workflows should be used to provide an approval process.  We’re looking to empower contributors and ironically nothing breeds creativity like boundaries.  If they feel like they can do no harm, they are more likely to take advantage of the tool.

If you look through that list what you’ll find are some pretty basic requirements for any web content management system.  Every CMS from the Drupal to UCM to Ektron has those basic features and then some, but what if we surface that content through a portal or another application?  How many features will contributors loose right off the bat?

Checklist?  Checkmate…

To sum up what we’re trying to do, the overall the goal is to encourage content contribution by empowering contributors. That’s a goal in every CMS project, but when an external portal/application is included we also need to provide the fundamental contribution features of a CMS in that remote portal or application.

That doesn’t mean just editing text in the portal either.  Contribution is not just about a bunch of words, it’s also about images and tying all that information together with links.  Contributors do not care if it’s a portal, a content management system, a custom site or a magic flashy box.  There are certain fundamental features that are expected and there will be dissatisfaction and lack of adoption if they are not there.  It’s not the contributors faults either…their customers(the end users) have come to expect images and links in what they read.  If it’s boring, hard-to-follow content, why bother reading it?  And if no one is reading it, why keep contributing it?  And then of course what good was that expensive content management project, if no one is going to contribute?

How do we know if we have a good strategy though?  There are a couple of questions I’ve put together which I think help assess a strategy and at the very least identify it’s strengths and weaknesses.

1.  Describe the process for adding and/or editing a page in the integrated environment.  Can the contributor do it on their own(ignoring any workflow)?  Do they need access more than one system to post a single page of content?  If they can’t(do it on their own) or they have to(access more than one system), you might want to head back to the drawing table.  Those are enthusiasm killers for contributors.

2.  How will images be contributed and delivered? Images can be a major pain.  If you’re contributing them in a WYSIWYG editor, typically they head to the CMS or an external repository.  References to images in content need to be preserved, re-written or proxied.  What path will you take and and why?

3.  How will links between pages work? This is usually the question that sends us back to the drawing board.  If you are surfacing content from a CMS on to a portal, how do you link to another page on the portal while using the CMS’s editor?  Relative links are sometimes an options, as are tokens.  It’s important to have a solid approach though as when you are referencing items in two different systems things can get very confusing quickly leaving the site with many broken links.

Even though we’re dealing with some fundamental features, believe it or not once you introduce that separate application very few implementations would get an A+ on all three areas.  At work we’ve taken over some less than successful projects and the #1 problem is not that the site or portal don’t deliver content well, it’s that no one can effectively contribute.  It’s only three general questions to drive a discussion, but I’ve found them to be a very effective check list for separating good ideas from bad ones.

Manifesto or Just Manifest?

The goal of this post is to set up and explain my mindset and strategy for several integration examples on how to approach a portal integration with a CMS(ok they are all UCM/WebCenter examples).  In looking at some of the planned posts, it was clear that they might not makes all that much sense without setting the stage first.

They’ve been up for a couple of weeks and I think the content so far has been excellent.  I know all of the folks who are posting and they really are a very sharp group.  In addition to UCM, there should be some really good .NET and Sharepoint stuff posted.

Under the hood is the technical blog, lots of code and frameworks.  I *think* most of the UCM/Content Management stuff will be found here over all.  Some of you might know Aaron Romaine from OpenWorlds past.  He joined our team a few months ago and has dropped a couple UCM articles out there.

Fit and Finish is the designers, information architects and front end developer blog.  Just looking at the most recent posts though, it looks like there also a good amount of technical information here too.

So give them a read.  I’ll be double posting some of my stuff over there in the coming days.

Fedora the Explorer

When you start out creating a new blank instance, Amazon provides several templates to start with.  As you can see from the list though they all appear to be either Fedora or Windows(towards the bottom). I’m not sure of your experiences, but as far as the elements of a UCM instance(Web server, UCM and the database) go, the database can be the trickiest of all of them.  And also for me to consider this a complete install, I really wanted to have Oracle Text Search running, which requires an 11G database.

I am pretty sure that a Windows VM would have worked for all of this, but it’s more expensive per hour and if I’m honest it felt a bit like cope out since it’s so much easier to work with.  I really wanted this to all run on a Linux box, so rather than take the easy road I decided to give the Fedora install a shot.

Unfortunately Amazon Fedora template my not have been the best choice to begin with.  I’m sure I would have gotten it at some point, but the workarounds combined with the oddities of Amazon’s template kept sending me down some rabbit holes.  It was a lovely Sunday afternoon, surely there’s a better Linux instance for this little proof of concept than Fedora?

So I cheated

It turns out that besides Windows or even Fedora, there is a much, much better option.  And after an hour or so of dealing with my Fedora issues I decided to use a very clever tool to research the best way to do this install.

Oracle, as I soon discovered, is already way ahead of me in setting up their database in the cloud.  There’s a whole bunch of documents about the subject, a FAQ page, a wiki and most importantly several machine images anyone with an EC2 account can use.

You’ll find the Oracle images on the community tab when you create a new instance in the AWS console.  There are a bunch, but if you search for Oracle, you’ll find what you’re looking for.

When you SSH in for the first time, a script runs that will takes you through the DB setup and configuration.  The script seemed a bit light, so I think the VM might really be just intended for demo purposes.  Anyone familiar with the near innumerable number of options in a DB install will find this a bit light.  For folks like myself though who’d rather get on with other things than ASM backup configurations…it’s just about perfect.

How much does a Gazillion processor licenses for Oracle cost?

For a very long time Oracle didn’t really allow customers to licence by virtual procssor.  Organizations who planned on running on virtual machines had to purchase a license for every processor on the host system(the exception being IBM PowerVM as you can isolate processors to an lpar).  That policy, at least towards some vendors like Amazon has changed

For the purposes of licensing Oracle programs in the Cloud environment, customers are required to count each virtual core as equivalent to a physical core. This policy applies to all programs available on a processor metric.

When I saw that right off the first thing I thought when I started down the road of running UCM on an Amazon VM was “Great! pay for one processor license and then run it on the cloud across thousands of servers.  Silly Oracle how could they not have seen that huge loop hole”.  Yeah…not so much.

The thing is that Amazon commoditizes it’s processor power into things called compute units.  Virtual processors are then made up of these compute units.

One EC2 Compute Unit provides the equivalent CPU capacity of a 1.0-1.2 GHz 2007 Opteron or 2007 Xeon processor

So even though you’re running on the cloud, you’re supososably isolated off to your own little share of the processing power.  Besides IO, what’s really the advantage then?  If the processors or the same(or worse really) than anything you’d bring on house, why bother?  Well all is not lost..there definitly are still some serious advantages from a licensing perspective

1. According to the Oracle doc a virtual core is equivalent to a physical core.  Though my little sample VM had only one virtual core with one compute unit, there are a number of hosting packages where virtual cores house as much as 3.25 compute units.
2. Have you tried to purchase a server with one processor lately?  They just aren’t available, even the single processor servers have 2-4 cores.  With Amazon you could run a cluster of four one processor servers and get exactly what you want.
3. UCM is notoriously light and efficient; even more so now that verity is out of it.  Over and over again it’s continually made me look like a genius during load tests on hardware I wouldn’t run this blog on.  I think one of my next posts will be on where I think the real UCM sizing should be.  I just don’t see it needing a ton of processor power.  IO perhaps, which you should have a lot of, but not processor.

In addition to all of that, there should be a huge savings for you from the hosting perspective.  Frankly if you’re budgeting for UCM implementation and planning to run it on Amazon, hosting is effectively free.  To run the current instance I have out there right now, it will cost me $227.50 per year.  For the most expensive instance possible (64bit, 32gb of ram, 13 virtual cores), it would cost $6370 annually.  Bandwidth is even more comically cheap: $.15 per GB for the first 10 Terrabytes, after that it drops to $.11 per GB for the next 40 and so on.

Well can we see it?

I’m going to leave my virtual machine up for a bit.  If you email me I’ll give you the link to take a look…I’m not sure if it still counts as a developer license if I post the URL publicly.

So far there’s no content other than Site Studio; I think I’m going to set up a quick site and run some tests for that follow up post on scaling.  Check back and I’ll share the results.

There was of course some excitement for Solaris, but really it’s pretty clear that Java was the buy:

Java is one of the computer industry’s best-known brands and most widely deployed technologies, and it is the most important software Oracle has ever acquired. Oracle Fusion Middleware, Oracle’s fastest growing business, is built on top of Sun’s Java language and software. Oracle can now ensure continued innovation and investment in Java technology for the benefit of customers and the Java community.

Oracle really isn’t just a database company any more.  They really haven’t been that for some time, but now they are a software company that also sells a database.  The fact is that they now own the language and ultimately the platform of which many of the best selling enterprise applications are built on.  That fact would actually be a little more interesting to think about if they had not already purchased  all of the best selling enterprise applications already.

Who’s Next

I really know nothing about who or what Oracle wants to acquire(in fact I don’t think I could know less), but how much sense does Red Hat make?  Red Hat is just about the gold standard in Linux distros(I don’t want to hear it Ubuntu fans, I’m talking servers), plus they get the last real application server out there that doesn’t have “sphere” in the name and they, like Sun, are major, major proponents of open source technologies.

It’s really crazy…Java.com will be an Oracle site….wow…double wow.

Our session is called “5 Rules to Optimize Your Website for SEO, ROI, and New Site Creation” and is scheduled for 2:30, Tuesday March 31 in room 113A.  You’ll have to attend to find out what the five rules are, but from a high level we’ll be delving in to some of the concepts that can make a large scale enterprise web content management implementation be successful.

If you’re looking for a preview.  Molly and I did a webinar with Oracle for their “Thriving through Expansion” series a few weeks ago.  It’s available for download here.  The password is Oracle1(I hope I’m not giving away a secret with that).

I’ll be at AIIM both Tuesday and Wednesday, so if anyone would like to meet up, please shoot me an email.  I’ll also probably start twittering again(something that only seems to happen at conferences).

Hope to see some of you there.

A little background

In Site Studio there are two types of pages;  Primary pages, which are essentially the landing pages for a folder(think home, search and listing pages).  They are almost always named index.htm and what’s unique about them is that when they are called they only refence specific content items.  Secondary pages, which could be viewed as everything else in a folder differ as they are used in more of traditional templated, delivery fashion, where the content is delivered through a reuseable template.  I butchering those descriptions a little for simplicities sack, but for the most part that’s how they work.

Out of the box, Site Studio lets you reference a content item using it’s content id in the url.  So if you had a content item called 000525, it would be referenced in a folder with it’s content id at the end(http://SiteStudio.com/site/folder/000525 for example).  Since all templates are mapped to thier folder, everything you need to render a page can be found in the URL…it’s all pretty simple.  The thing is, what if you aren’t too crazy about the 000525 name though?  It’s not really all that intuative of a name; you could make the content id friendly or you could use also take advantage of the SSUrlFieldName property in Site Studio.  The SSUrlFieldName property allows you to map a custom metadata field(perhaps one longer than the 30 characters you get for a content id?) as the file name idenifiier used when reference in a URL.

So content item 000525 can also have a metadata field tagged as “autofillthatfriendlyname.htm” and so when refereced as a url, it could look like this: http://SiteStudio.com/site/folder/autofillthatfriendlyname.htm.  That’s pretty cool, right?  There is a bit of a catch though, like the content id the value used in the friendly name field should be unique.  The only problem though is that there’s no automatic validation for the values, so there’s nothing to tell the contributor if they’ve duplicated a value.

What the component does

The code for this component is pretty simple, we’re hooking in to the validateCheckinData event and then basically updating whatever field is identified in the SSUrlFieldName property with a friendly name.  I like the validateCheckinData filter quite bit for situations like this where I need to update or add some metadata at check in or update time.  If I have to kick a process off or do something to a piece of content that has just been checked in, so after it’s in the system, I usually prefer the afterLoadRecordWebChange, but that’s probably for another post.

Getting back on track, once a piece of content is checked in which has a xWebsiteSection value(meaning it’s been assigned a default URL in a web site), it pulls the dDocTitle value out of the binder and makes it friendly(removes any spaces or special characters I could think of).  It then appends a file extension(set in the environmental config) and checks the value against the database.  If the friendly name has been used before on another content item it goes back and adds a 1 to the end of the title part of the file name(I know…not very imaginative).  Each time the component assembles a name it checks it against a max character count also found in the component’s enviornmental config.

Installing this puppy

The install on this component is not really unlike any other.  You of course do need to make sure Site Studio is installed on your content server and that the SSUrlFieldName property has been set in the config.cfg file.  I should note that when you set the SSUrlFieldName property, you need to leave the little x prefixing all custom metadata fields off.  So no xFieldName formats…just FieldName.  You probably will need to tell the component what the size of your friendly name field is.  It’s defaulted to 80 characters, so if you  plan on using less or more, you might want to update it in the component’s environmental config file.

You can download the component here:  Auto Fill Friendly Name

So what have you been working on?

The past couple months have been very fun technology-wise. I’ve actually recived a good amount of interest around the .NET API from a number of clients and even put together several Site Studio/ASP.NET demos. The integration of the two is a little tricky, but you can get the full editor functionality out on an ASP.NET form. This was all prior to the SS 10GR4 release as well, which from my initial tinkering provides quite a few new services around editing and preview(all of which are undocumented, so you have to look at the services file in the component for the list).

I’ve also been doing some work with ALUI…now known as WCI(Web Center Interaction).  ALUI is really my favorite of the Oracle portals(though that could be how often I’ve been running in to it as of late).  From what we’re hearing in Oracle circles UCM will provide content management to all of the WebCenter portals, but the feeling is that ALUI will provide the most functionality and seems to be the one all the demos are being run on.  Please note that I could be totally off on that assessment as Oracle tends to use the word “WebCenter” as a catchall phrase for every product, so it often gets confusing about what product you’re talking about.

It’s a bit of a hobbie but I’ve also been writing some ISAPI and Apache filters.  Most of my projects have been URL-rewriters, which is about the simplest thing you can do in a filter, but I really find them fun to code.  Unless you’re working with IIS7 writing a filter for either web server requires some C code, which is not a language I work in very often.  Really the only thing I do in C is code web security filters for UCM which is really all based on a sample project that takes all the trickery out of the task.  I’ll probably post a couple of my samples soon even though they’re not exactly content management related.  

Plans for ‘09

Despite the bad economy and there’s actually a lot to be excited about when it comes to content management and more specifically Oracle.  I’m not sure how R&D budgets are being affected by the downturn, but it’s pretty clear Oracle had quite a few items in the pipe before things started slowing down.  All of that said, here are some of things I’m hoping to write about this year.

1. Oracle’s recent release of Site Studio 10g4 will have some major benefits and changes to how we approach and when we can do when implementing a WCM project.  I’ve been working with some of it’s new features now for the past week or so and I’m already really, really impressed with what it can do.

2. The hodgepodge of Portals and applications all labeled “WebCenter”.  Most of my portal related posts have to do with capabilities and theory, but nothing all that tangible.  I’ll hopefully be release some samples soon.

3. CMIS.  I haven’t heard a lot about it lately, but it’s still out out there.  Last I checked there hasn’t been much of an update though Alfresco did release a connector for their CMS.

4. More .NET….There’s a lot of interest in anything UCM and .NET.

Ok that’s it.  Thanks to everyone who sent me a “where are you” email, hopefully there won’t be any more extended blogging breaks.

The Questions

Open WCM – Word on the street is that it’s close, very close actually.  In fact I think they may just be waiting for a release date.  When I arrived actually I heard it was not being demoed, but then shortly before leaving I found out it actually was on the demo grounds…doh!

ALUI – When I headed out to OpenWorld what I was hearing was that ALUi would be bundled with UCM.  That unfortunatly is not true.  There is however now a WebCenter suite, which when purchased, has licnesing for ALUI as well as a stripped down version of UCM.  The interesting thing though is that with the WebCenter suite you actually get your choice of portal; WebCenter, ALUI, WebLogic…doesn’t matter the suite gives you licensing for all of them. 

Though I like and have been mostly interested in ALUI, if there was one BEA product that Oracle seemed most interested in, it would have to be Ensamble.  Ensamble came up in just about every session I attended, in addition to the off the cuff discussions in the demo grounds and end of day activities.

My questions around WebCenter were really answered by the ALUI question.  WebCenter is still a portal, however now all the BEA portals(as well as some of the other products) can be licensed as part of the WebCenter suite.  Oracle has plans for all the portals, but strategically it’s WebCenter that they want to lead with long term.

Billy’s book – Got a copy…Got two actually as well as catching thier presentation, which was the best of the conference in my opinion.  I’ll be giving it a read and a review in the next few weeks so check back for that.

Conclusions

I really had a great time out at OpenWorld.  I had a great chance to meet many of you who I normally only talk to online as well as learn a thing or two about what those clever UCM folks are planning for the next year.

Ensamble – The session I did catch yesterday, “The art of the Mash”, was pretty interesting.  The presentation centered around the concept of enterprise mash-ups and specifically how they are implemented using Ensamble, the former BEA product I talked about yesterday.  The big thing I got out of the session was an overview of the security features in Enamble.  It’s pretty interesting actually, I would have assumed it ran in just a simple SSO model, where authenticatoin was handled by ensamble, which then passes the user’s id down to the app for authorisation.  Though it does support that, it also has a number of other trickes for dealing with application that have atypical set ups.