Skip Links

Network World

  • Social Web 
  • Email 
  • Close

(Comma separation for multiple addresses)
Your Message:

Build an open source and Web 2.0 sandbox

Safe places for trying out new stuff
By Andreas M. Antonopoulos , Network World , 12/05/2006
Andreas Antonopoulos
  • Share/Email
  • Tweet This
  • Comment
  • Print

Open source and Web 2.0 technologies are often appearing in enterprise environments as “skunk-works,” unauthorized projects that rapidly gain popularity.

Tools such as wikis, blogs, content-management systems and discussion forums can be found in many enterprises, despite the lack of official support or sanction. Just like e-mail in the last decade and IM more recently, these technologies are discovered by users outside the enterprise and brought into the enterprise incrementally and without planning.

Some companies are inclined to prohibit or even block these technologies, often with little success. As with e-mail, wireless and IM in the past, most companies eventually realize that the attempts to block technologies that users want to use only lead to uncontrolled deployments, which increase the risks and decrease the benefits.

How can a company experiment with these technologies without spending too many IT resources? Many excellent tools and platforms (both Web 2.0-ish and more “traditional” apps) are available under open-source licenses and built by developer communities (some examples include TWiki, drupal, Zimbra, Alfresco, phBB, SugarCRM, etc.). But building a test bed for these tools can take a lot of time and effort. Corporate IT engineers may have to move beyond their comfort zones and expose themselves to unfamiliar application stacks, operating systems and programming or scripting languages. Is it worth the effort just to try these tools out?

One possible approach is to create a flexible “sandbox” where corporate IT can build small pilot deployments of different applications for testing and evaluation. Let’s say for example that the PR department is willing to try out blogs or wikis for a new campaign. The IT department can deploy some software in the sandbox to allow for some experimentation on a smaller scale.

Building such a sandbox can be easier if companies use open-source tools and virtualization software combined together. Many software vendors and developer communities are now releasing their “wares” as virtual appliances either for VMware or for Xen. Bypassing the cumbersome OS build, customization and fine-tuning, IT engineers can just drop a virtual appliance on a SAN or NAS, boot up a blade server and have a test application up in minutes. By connecting to corporate LDAP or AD directories, IT can quickly enable access controls, user accounts and groups and have the test project ready for experimentation in a matter of days if not hours.

  • Share/Email
  • Tweet This
  • Comment
  • Print
Partner Content

Gartner 2009 Magic Quadrant for Job Scheduling

Gartner has positioned BMC CONTROL-M in the Leaders Quadrant of their "2009 Magic Quadrant for Job Scheduling." The report assesses the ability to execute and completeness of vision of key vendors in the marketplace. Read a full copy today, courtesy of BMC Software.

Download whitepaper

Dell's SMART Approach to Workload Automation

Read a compelling case study by EMA, Inc. to learn how Dell uses BMC CONTROL-M to cut cost and increase productivity with workload automation.

Download whitepaper

Workload Automation Cost Savings 2 Minute Video

A major computer manufacturer uses BMC CONTROL-M and just four people to schedule and run over 85,000 jobs every month. By switching to BMC CONTROL-M, they more than quadrupled the workload without adding a single staff member.  See how in this 2-minute video overview.

Go to video

Comment
Login
Forgot your account info?
Add comment
Anonymous comments subject to approval. Register here for member benefits.
Have a NetworkWorld account? Log in here. Register now for a free account.

Videos

rssRss Feed