Tag Archives: SOA

Enterprise 2.0: Top 10 Reasons NOT to Use WOA & APIs

Enterprise 2.0 Strategy for Platform Architecture

Intranet vs Internet

The main goal of a winning Enterprise 2.0 Strategy is to facilitate communication and innovation through collaboration.  The Art of Enterprise Architecture in E 2.0 is to unite people and process.  Thoughts on Enterprise 2.0 Architecture include leveraging the principles of Service-Oriented Architecture (SOA) to support Web-Oriented Architecture (WOA).  This type of Internet architecture for the Intranet makes is possible to support Web 2.0 Apps, Gadgets, & Widgets in the Enterprise.  This strategy reduces the number of resources required for the technical part of Enterprise 2.0 Architecture and provides time to focus on Improving Enterprise 2.0 Adoption Through Gamification.

Many organizations today are supporting employee collaboration through Enterprise 2.0 Platforms.  Vendors are also providing Enterprise 2.0 Solutions that include Social Networking features very similar to Facebook and Twitter.  Some organizations and vendors are missing the biggest success factor behind these popular Social Networking Platforms.  The Application Programming Interface (API) of these platforms contributed heavily to their success.  Using APIs to easily link data is the foundation of how the internet works today.  Enterprise 2.0 platforms should provide a great user experience, enable third-party developers and empowers employees to accomplish their business objectives. This can be accomplished with an Enterprise 2.0 solution that leverages Web-Oriented Architecture (WOA) with open, standards-based, non-proprietary API implementations built on web-based RESTful architecture.

Enterprise 2.0: Top 10 Reasons NOT to Use WOA & APIs

  1. We have endless resources and enjoy spending extra money on integration.
  2. We like to spend our bonus money on infrastructure to support bloated code.
  3. We have no desire to support multiple devices.
  4. We have no plans to share information across multiple environments.
  5. We don’t want a platform that can be extended.
  6. We want to pay top dollar for things most get for free.
  7. We don’t support Standards because we enjoy watching our bug list grow.
  8. We believe code should be rigid and not reusable.
  9. We understand the benefits of WOA & APIs, but that’s not the way we do things here.
  10. We feel trendy when talking about OSGI bundles for the Enterprise Service Bus (ESB).

Data.Gov Demonstrates the Power of WOA and APIs

The next-generation Data.gov platform delivers a fantastic citizen experience, enables developers and empowers agencies to accomplish their mission.  See how this is accomplished in this video.

What Does It Mean to API-Enable Data.Gov?

The Web-Oriented Architecture (WOA) of Data.Gov offers an open, standards-based, non-proprietary API implementation built on web-based RESTful architecture. Learn more here [pdf].

Happy Fav Five Friday!

Favorite 5 Places

Forrester: SOA thriving; but interest in ESBs slips A new survey of 2,165 companies, compiled by a team led by Forrester Research’s Randy Heffner, finds that interest in service oriented architecture remains strong, despite today’s emphasis on cloud computing, mobile applications, and social networking …more

Enterprise 2.0 Roll-up: Welcoming Service Cloud 3 and iPad Remember when Chatter first came out? Salesforce.com’s CEO Marc Benioff couldn’t stop talking about how it was just like Facebook. This week that level of social functionality has been extended to Service Cloud 3, the newest iteration of the company’s social …more

5 recommendations for successfully implementing distributed innovation and shared value The real reason for distributed innovation is simply that you can no longer be self-sufficient. You must bring together more and better resources than you can hope to have inside a single organization. This means that distributed innovation models must address how … more

Becoming an Open Leader Two years ago I posted a short post that picked up from an HBR article on leadership flaws.  I posed the question if Enterprise 2.0 initiatives can thrive in environments where toxic leadership reigns.  My first reaction was no, and then I thought about ways to get to yes.  One of the flaws of flawed leadership is the lack of feedback — to gain self-awareness there is a problem in the first place.  Perhaps the feedback loop E2.0 cultures …more

#E2sday: How to Calculate the ROI of Enterprise 2.0 With enterprise social software platforms starting to gain widespread traction, ROI measurements are now becoming possible with early adopter communities. Many companies are looking for a detailed guide on how to measure the benefits of E2.0 …more [infographic]

Social Business Relationships in Enterprise 2.0

Social Business Strategy & Trends

The SOA Social Graph Love Affair

Saint Valentine’s Day is quickly approaching and it has me thinking more about relationships.  Psychology Today published an interesting article on learning what you need to know to make your relationship last.  A relationship can be defined as an association between two or more people that may range from fleeting to enduring. This association may be based on limerence, love, solidarity, regular business interactions, or some other type of social commitment. Interpersonal relationships are formed in the context of social, cultural and other influences. The context can vary from family or kinship relations, friendship, marriage, relations with associates, work, clubs, neighborhoods, and places of worship. They may be regulated by law, custom, or mutual agreement, and are the basis of social groups and society as a whole.  This article will focus on relationships in Enterprise 2.0 Strategy and the Service-Oriented Architecture (SOA) Social Graph love affair.  The content of the article will include Social Business trends & predictions, Web 2.0 Technologies, and resources to help users integrate systems through Service-Oriented Architecture (SOA) to support relationships between people and data fueling the Social Graph providing context to information for the Enterprise.  This relates to a previous article: Enterprise 2.0 Cloud Computing & Service Oriented Architecture (SOA).

Social Business Forecast: 2011 The Year of Integration

Industry analyst that specializes on customer strategy and  Altimeter Group partner Jeremiah Owyang ( @jowyang ) shares survey information and great insights in this presentation.

Social Business Integration with SOA & WOA

The use of Service-Oriented Architecture leveraging Web-Oriented Architecture (WOA) in Enterprise 2.0 can ease the pain of integration and centralize information management.  This strategy provides the flexibility of sharing information in the proper context while supporting the Social Graph.  Context can be provided by including simple markup in existing solutions.  This markup includes FOAFXFN, and Microformats for events & profiles.  The internet provides many great examples of Web 2.0 Technology integrating SOA and WOA.  Gravatar and DISQUS are two quick examples.  Gravatar provides people a Globally Recognized Avatar that software developers can include through a very simple Application Programming Interface (API) supported by WOA.  DISQUS is a comments platform that helps you build an active community from your website’s audience. It has awesome features, powerful tools, and it’s easy to install.  A solid Enterprise 2.0 Strategy includes much more that providing collaboration tools to employees and includes supporting relationships between everyone and everything connected to the Business.

Social Graph Based Business Models

The audio in this video is low, but there are many great topics covered here.  These topics include “The Super Connector”, “Activity Streams”, “Network Effects”, “Social Graph”, “Facebook”, “Micro Transactions”, and more.  This Social Graph Based Business Models video can be viewed here.

Introduction to the Social Graph API

Google engineer Brad Fitzpatrick gives an introduction to the Social Graph API. The Social Graph API makes information about the public connections between people more easily available. Developers can query this public information to offer their users dramatically streamlined “add friends” functionality and other useful features.  A quick overview of the Social Graph API is available in this video.


Supporting the Social Graph with SocialSite

Understand the importance of Social Networking features in Web applications. Learn about the new OpenSocial standard for plugging into Social Networks. See how Project SocialSite’s Web Services and Widgets make it easy to make your Web Applications social.  Learn more here.

Google’s OpenSocial

Applications that use the OpenSocial APIs can be embedded within a social network itself, or access a site’s social data from anywhere on the internet or intranet.  Learn more here.

Picture 20

Enterprise OpenSocial Whitepaper: Enterprises are collections of people, and thus inherently social. Employees of any organization benefit from social connections, group affiliations and relationships both within their own business and between other businesses. As a result, social networking capabilities have become increasingly popular in business-to-consumer, business-to-business, and internal enterprise collaboration applications. New technologies and standards such as Web 2.0 and OpenSocial [1] are helping software providers better model relationships between people, allowing end-users to benefit from such relationships in day-to-day business processes within their own enterprise, and across business networks. Google’s Enterprise OpenSocial Whitepaper is available here.

Web 2.0 and the Enterprise: A Symbiotic Relationship

Time shifting & place shifting We then discovered that the same type of time shifting happening among consumers was taking place in the workplace too. People were switching between tasks, collaborating and consuming media in completely new ways. Lean more here.

Happy Fav Five Friday!

Fav 5 Places

The Architecture of SocialSite

A quick presentation on the architecture of SocialSite, Sun’s implementation of a OpenSocial compliant Social Networking site using Shindig.  Learn more about SocialSite architecture here. (SocialSite is a Glassfish project now known as “SocialFish“)

Enterprise 2.0 Activity Streams

Activity streams will continue to be a much hyped capability within social platforms. However resulting “stream glut”, interoperability, and security-related issues will threaten benefits unless better user experience design, filtering, standardization, permission models, and back-end analytics are applied. Learn more here.

Social Media is from Mars, Enterprise 2.0 is from Venus

Focus on creating and maintaining genuine relationships with customers.  Learn more here.

The relationship between Enterprise 2.0 and Web 2.0

A topic that is closely related to Enterprise 2.0 is Web 2.0. It is important to note, however, that the concepts are not one and the same, but rather they are two individual areas that are built on top of similar foundations. The term Web 2.0 describes the shift in focus from static and singular media to dynamic, interactive community-oriented social media. Learn more here.

Web 3.0 and Social Business: 2011 Predictions & Recommendations

2011 will mark a turning point in the adoption of digital social technologies because the experimentation phase is drawing to a close, and stakeholder expectations are increasing. Organizations and people will no longer gain attention by executing badly. At the enterprise level, participation will wane in venues and initiatives that have no business strategy, focus, content strategy and commitment.  Learn more here.

Summary

The future of intranets and the internet is all about context, integration, app stores, apps, mashups, widgets, gadgets, and filters.  Integrating Web-Oriented Architecture (WOA) in Enterprise 2.0 supporting Service-Oriented Architecture (SOA) will improve Business success.

The 80-20 Rule for Web 2.0 Architecture in the Enterprise

Enterprise 2.0 Cloud Computing & Service Oriented Architecture (SOA)

Integrating Internet Principals In Your Intranet

80-20-Service-Oriented-Architecture-SOA

You may of heard someone in your office say something like “20% of the people are doing 80% of the work”.  This is known as The Pareto Principle, aka the 80-20 Rule.  This principal will also apply to the future architecture of the internet composed of 80% Consumers and 20% Producers supported by “Linked Data”  This paradigm shift in information architecture will be fuled by the adoption of using widgets, gadgets, and apps to connect information.

Enterprise 2.0 App Stores

  • What if you had an Enterprise 2.0 App created from SharePoint?
  • What if you had an Enterprise 2.0 App for email?
  • What if you had Enterprise 2.0 Apps for your team blog, wiki, graphs, activity streams, …?
  • What if all these apps were displayed as Widgets in your Enterprise 2.0 Dashboard?

Why would you log into all these different areas, when you can see what you want, how you want in a single place.  Navigating to multiple places is time consuming, even with Single Sign On (SSO) solutions in place.  Most Enterprise 2.0 Apps, Widgets, and Gadgets can be created with common web programming languages.  These web programming languages can be as simple as standard HTML, CSS, and JavaScript.  These User Interfaces can easily leverage AJAX and other Web 2.0 Technologies to enhance the User Experience.  The extra benefits of using these standard technologies is lower development cost, shorter time to deployment, and better support across multiple devices such as smart phones, iPads, and standard tablets.

Enterprise 2.0 App Store Architecture

Most organizations have a difficult time measuring the use of their Information Technology.  Some organizations can measure enough to know that moving at least some technology to the cloud makes sense.  Businesses can also realize the benefits from the concept of cloud computing through Enterprise 2.0 App Store Architecture.

What is an Enterprise 2.0 App?

An Enterprise 2.0 App is “a snippet of code that is shared to serve a specific purpose”.  This “App” can be displayed and used on smart phones, mobile devices, desktops, web browsers, dashboards, or other applications.

Where is the App Stored?

Apps can be stored internally or externally.

Internal Apps, Widgets, & Gadgets

Internal apps are hosted and used by the owner, usually in the same domain, therefore the level of trust is higher.

External Apps, Widgets, & Gadgets

External apps are hosted outside the domain and usually by a third party.  The level of trust is lower, therefore the proper security measures should taken.  All developers should know how to build, design and test the security of web applications and web services.

Using a Web Proxy

All modern web browsers impose a security restriction on network connections, which includes calls to XMLHttpRequest. This restriction prevents a script or application from making a connection to any web server other than the one the web page originally came from (Internet Explorer will allow cross-domain requests if the option has been enabled in the preferences). If both your web application and the XML data that application uses come directly from the same server, then you do not run into this restriction.  See the PHP Web Proxy code below and learn more about AJAX Web Proxies here.

<?php
// PHP Proxy example for Yahoo! Web services.
// Responds to both HTTP GET and POST requests
//
// Author: Jason Levitt
// December 7th, 2005
//

// Allowed hostname (api.local and api.travel are also possible here)
define (‘HOSTNAME’, ‘http://search.yahooapis.com/’);

// Get the REST call path from the AJAX application
// Is it a POST or a GET?
$path = ($_POST[‘yws_path’]) ? $_POST[‘yws_path’] : $_GET[‘yws_path’];
$url = HOSTNAME.$path;

// Open the Curl session
$session = curl_init($url);

// If it’s a POST, put the POST data in the body
if ($_POST[‘yws_path’]) {
$postvars = ”;
while ($element = current($_POST)) {
$postvars .= urlencode(key($_POST)).’=’.urlencode($element).’&';
next($_POST);
}
curl_setopt ($session, CURLOPT_POST, true);
curl_setopt ($session, CURLOPT_POSTFIELDS, $postvars);
}

// Don’t return HTTP headers. Do return the contents of the call
curl_setopt($session, CURLOPT_HEADER, false);
curl_setopt($session, CURLOPT_RETURNTRANSFER, true);

// Make the call
$xml = curl_exec($session);

// The web service returns XML. Set the Content-Type appropriately
header(“Content-Type: text/xml”);

echo $xml;
curl_close($session);

?>

You should also see this article: “Restricting Access to your AJAX Services“.

Open Source to the Rescue!

Open Source Libraries and Frameworks to Support Enterprise 2.0  Apps, Widgets, & Gadgets

Creating Enterprise 2.0 Apps, Widgets, and Gadgets can be less time consuming with these free open source libraries and frameworks.

jMaki

jMaki is a lightweight client/server framework for creating JavaScript centric Web 2.0 applications using CSS layouts, widgets widget model, client services such as publish/subscribe events to tie widgets together, JavaScript action handlers, and a generic proxy to interact with external RESTful web services. While jMaki abstracts much of the JavaScript and CSS by providing defaults for widgets, the JavaScript widgets and CSS are made easily accessible so they may be customized by a designer or page developer. jMaki focuses on the aspects of delivering JavaScript to the client allowing the JavaScript to communicate to various server-technologies including PHP, Java (JSP/JSF), and Phobos in a server-technology neutral way. Learn more here.

jmaki-architecture

Google Web Toolkit (GWT)

Google Web Toolkit (GWT) is a development toolkit for building and optimizing complex browser-based applications. Its goal is to enable productive development of high-performance web applications without the developer having to be an expert in browser quirks, XMLHttpRequest, and JavaScript. GWT is used by many products at Google, including Google Wave and the new version of AdWords. It’s open source, completely free, and used by thousands of developers around the world. Learn more here.

Screen shot 2011-01-14 at 2.52.57 AM

Web 2.0 Apps, Gadgets, & Widgets in the Enterprise

Enterprise 2.0 App Stores

Web 2.0 Apps, Gadgets, & Widgets with AJAX, HTML, & CSS

apple-mac-app-store

The interest in Government 2.0 and Enterprise 2.0 “App Stores” is increasing.  This is driven by the popularity of mobile apps and app stores like the “Mac App Store“, which published this press release today:  “Mac App Store Downloads Top One Million in First Day“.  Many tools are available to help users mashup data to create apps.  Some of tools can be reviewed in this previous article: Enterprise 2.0 Strategy For Empowering Employees.

Government 2.0 App Stores

Each Government  Agency is unique, their complex needs require state-of-the-art software to get business done.   The General Services Administration’s Cloud Business Apps provide solutions.   These Business Apps are geared towards the enterprise with cloud software solutions such as analytical, business processes, CRM, tracking and monitoring tools, business intelligence and more. Learn more about Gov 2.0 and Government App Stores in this previous article: Federal Chief Information Officer Vivek Kundra speaks about Government 2.0.

Web 2.0 Apps & Sharable Content Objects

Widget-Security-Challenges

The concept of Web 2.0 Apps, Gadgets, & Widgets is very similar to the “Sharable Content Object Reference Model” (SCORM) as defined by Advanced Distributed Learning (ADL) A “reference model” is something that shows what kinds of services will be needed to solve a particular problem, how they can be put together, the relevant standards that apply, and how they might be used.  The reason for using Enterprise 2.0 App Stores is explained in this article: Enterprise 2.0 Widgets, Mashups, App Stores & Cloud Computing.

The idea of App Stores is nothing new.  The technology used to support app stores is similar to Web Services for Remote Portlets (WSRP) with JSR-168 and JSR-286, except these specifications do not support Web 2.0 technologies (AJAX) very well.  The higher concept of the Producer/Consumer architecture lives on.  New security models will emerge as app stores in the Enterprise continue to grow.  Improving methods for centralizing authentication and authorization will gain more attention as Businesses and Government move toward Federated App Stores hosted in a Cloud Computing Environment.

Web 2.0 Gadgets and Widgets Specifications

Web 2.0 Apps, Gadgets, & Widgets with AJAX, HTML, & CSS

What is the difference between a Web 2.0 App, Gadget, or Widget?  The difference between these terms depends on the context of the conversation and who is involved in the discussion.  Google likes Gadgets, Microsoft likes Widgets, and Apple likes Apps.  People from these organizations seem to use these terms interchangeably.  The high level description of these terms is: “A snippet of code that is shared to serve a specific purpose”.  It is important to know (for security and privacy issues) that the code can be hosted locally or externally.  The good news is apps, gadgets, and widgets can be created with common JavaScript, HTML, and CSS.  Here are a few resources that can help anyone create great apps to be hosted and shared in app stores.

7 Videos & Presentations on Enterprise 2.0 Emergent Architecture

Emergent Architecture of Enterprise 2.0

The adoption of Standards in Enterprise Architecture improves the ability to support enterprise goals, business processes, and organizational behavior.  These technologies include Web Oriented Architecture (WOA), Service-Oriented Architecture (SOA), Enterprise Service Bus (ESB), Virtualization, Cloud Computing, and the Social Graph.

Transforming Software Architecture for the 21st Century

Transforming Software Architecture for the 21st Century Focusing the Power of People and Today’s Network on Opportunity Dion Hinchcliffe

Web Oriented Architecture (WOA)

Web Oriented Architecture (WOA) extends Service-Oriented Architecture (SOA) by using Representational State Transfer (REST) to identify and integrate web resources.

Service-Oriented Architecture (SOA)

Service-Oriented Architecture (SOA) defines how to integrate widely disparate applications for a Web-based environment and uses multiple implementation platforms. You can learn more about Service-Oriented Architecture in this video Service-Oriented Architecture.

Enterprise Service Bus (ESB)

The Enterprise Service Bus (ESB) is a software architecture construct which provides fundamental services for complex architectures via an event-driven and standards-based messaging engine (the bus).  You can learn more about the Enterprise Service Bus in this video IBM WebSphere Enterprise Service Bus 6.2 Video

Virtualization

Virtualization is a process of simulating necessary environments in order to capitalize on available resources.  You can learn more about virtualization in this video What is Virtualization.

Cloud Computing

Cloud computing is a paradigm shift in technology that saves companies money by only paying for resources as needed in the Enterprise.  You can get a quick idea of what cloud computing is in this video Cloud Computing Explained.

The Social Graph

Automatically surfacing how people and things are connected is an easy way of adding intelligence to Enterprise 2.0 Platforms.  You can see how it works in this Google video Introduction to the Social Graph API

Fav Five Faces

Who is on your “Fantasy Innovation Team” this week?

Here are amazing people that have connected me to new friends and new ideas this week. You might be familiar with “Fantasy Football Teams” , well this is my “Fantasy Innovation Team” this week. I recommend following these smart, creative people on Twitter.

byAgah-twitter Entrepreneur, Enterprise 2.0, Social CRM, Europe 2.0, Gov 2.0, New Economic World Order effect in Web 2.0 http://twitter.com/byAgah
2morrowknight-twitter Co-Creator of the #TwitterPowerhouses Series, and #TwitterCharityFacts. Blogger for @Huffingtonpost and @op_editorial, Marketing Strategist, Master Surfer!☮♥ http://twitter.com/2morrowknight
digiphile-twitter Gov2.0 DC Correspondent, @OReillyMedia. Intrigued by technological change, taken with ideas, cooking, the great outdoors, books, dogs, and media, in all forms. http://twitter.com/digiphile
gleonhard-twitter Keynote Speaker, Think-Tank Leader, Futurist, Author & Strategist, Idea Curator, Occasional Heretic, CEO TheFuturesAgency, Visiting Professor FDC Brazil http://twitter.com/gleonhard
bduperrin-twitter Enterprise 2.0 consultant @nextmodernity. Tweeting in French and english about enterprise 2.0, airlines, my life, basketball…and many things http://twitter.com/bduperrin