DevOps and Content Management

By: Raoul Miller – Enterprise Architect

You may have been hearing a lot about DevOps recently and are wondering what it is and whether it’s something applicable to WebCenter or any other form of Content Management technology.

Like many other recent technology concepts, the actual definition is somewhat fluid but the name comes from the conjunction of development and operations.  The idea being that developers, testers and IT staff (operations) need to work much more closely together to accelerate release cycles and make the technical side of the business much more responsive to customer demands and changing markets. The Wikipedia page on DevOps gives some of the history of the concept and provides these helpful illustrations of what it entails:

figure1

Figure 1: DevOps within IT groups

figure 2Figure 2: Agile vs. Waterfall methodology and change cycles

As figure 2 shows, the main idea is that a DevOps approach to software development and management is a direct analog to the agile project approach – in that technical staff can be much more responsive and can lower overall project risk when making rapid small changes rather than infrequent major changes.  The key here is that agility and responsiveness (achieved through automation and aligning the different groups within IT) is a clear competitive advantage in the current dynamic and evolving business environment.  This is why so many large software companies are now using or testing this approach.

So far, so good – but how does this relate to Content Management and how is this different from what you have been doing for many years?  To answer the former, the goal of a Content Management team working in a DevOps setting is to make frequent changes to meet customer demands.  Obviously this must be done cautiously and professionally and within the bounds of the system.  Modifying the metadata and security models within a document management system is not something to be done lightly; while changing user profiles, adding new dropdown choices, updating the UI are all perfect candidates for rapid release cycles in response to user feedback.  A records management system (due to its strict audit controls and external compliance obligations) may gain less from a DevOps approach than a customer experience management system which needs to evolve rapidly to meet changing needs.  So, like so many useful concepts in our evolving world, IT professionals must choose which systems are best suited to the new approach and which tools and aspects of DevOps are suitable to be adopted by their teams and their business.

How is this different from what you’ve been doing? Looking at release and update cycles in a different way and on different time scales forces changes in standard operating procedures.  And this is one of the great advances.  Increased agility and increased pace of release has made the use of automated configuration and deployment tools much more prevalent.  WebCenter has always been scriptable and able to be installed using scripts for many years. But there are now a number of extremely useful tools that allow DevOps teams to manage these processes much more repeatedly and rapidly (essential for consistency between environments and successful loads).

Steve O’Grady of Redmonk wrote an excellent post last week on the relative popularity of the major configuration management tools.  Puppet and Chef are currently the leaders in the space with Ansible and Salt following closely behind and quickly catching up.  All four are open source platforms with enterprise editions and support available.  I’ve worked most directly with Puppet and Chef, and in both cases the additional features available to enterprise users are definitely worth the investment.  Detailed description of how and when to use these configuration management tools is beyond the scope of this post, but I encourage you to download and check out the various applications and versions and find one that works best for you:

There are links to the community versions of each application on the various company pages too.

IBM has a helpful landing page on the topic; regrettably Oracle seems to be a little behind the curve relative to IBM, although there was an article in the Oracle Architect magazine earlier in the year and some internal blog posters are getting up to speed.  Enterprise Manager / Grid Control, especially in 12c versions, does have some of the automation features discussed above, but is in no way a substitute for Puppet or Chef.

My interest in this area was piqued through the excellent writing of the various Redmonk staff and I highly recommend their blog posts and conferences. The applicability of these technologies to Oracle and WebCenter in particular was clearly illustrated by the work of Oracle ACE Edwin Biemond here, here and here.  He is clearly the expert in this field.

Have more questions? Want to have a chat with someone from TEAM? Contact us here.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: