Category Archives: Enterprise 2.0

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.

Enterprise 2.0 App Stores: When Good Web 2.0 Apps Go Bad

Custom Dashboards in the Enterprise & Web 2.0 Apps

There’s an app for that!

The success of Apple’s iPhone App Store, Mac apps, and Google’s Marketplace all play a part in driving the trend of Enterprise 2.0 App Stores in business organizations of all sizes.  The idea of providing a solution with “There’s an app for that!” will be common place in the near future.  The App Store market will get very interesting when organizations and Government Agencies harness the true power of Service Oriented Architecture (SOA) & Cloud Computing.  This trend will help fuel the Federated System.  More information about Enterprise 2.0 App Store Architecture can be found here The 80-20 Rule for Web 2.0 Architecture in the Enterprise.

Where Do Apps Come From?

Custom Enterprise 2.0 Dashboards can include apps, widgets, and gadgets that include resources that are internal, external, and a combination of both.

  1. Internal Resources: Apps and their data that are hosted and maintained within the organization. The risk level is low.
  2. Internal and External Resources: There are usually internally created apps that use external data. The risk level is medium.
  3. External Resources: Apps that are hosted by third parties.  The trust relationship is complex and the risk level usually remains high.

How Are Apps Delivered?

Apps are added to devices and dashboards in multiple ways. App code and private data should reside in the client, but this is rarely the case.  Web 2.0 Apps are usually added to Enterprise 2.0 Dashboards by using the following technologies and methods.

What Are Application Security Risks?

Attackers can potentially use many different paths through your application to do harm to your business or organization. Each of these paths represents a risk that may, or may not, be serious enough to warrant attention.  The top 10 application security risks of 2010 can be reviewed on the Open Web Application Security Project (OWASP) web site here.  Additional Web Security information is available from the Open Ajax alliance at Ajax and Mashup Security.  The main rule of thumb is, “Never trust external data”.  Using a Proxy Server to fetch external data can help support the additional security requirements.  A proxy server is also helpful in capturing metrics of external resource usage.  The proxy server can integrated like an Enterprise Service Bus (ESB) to support the complex structure of Enterprise 2.0 App Stores.

What Happens When Good Web 2.0 Apps Go Bad?

How to Detect a Key Logger on Your System

Most people in the Web 2.0 World are familiar with the acronym WYSIWYG, “What You See is What You Get”.  This new acronym WYRIWYR, “What You Requested is What You Received” will be covered here.  The consumer and the producer should be focused on WYRIWYR.  Producers need to trust the consumer’s identity and consumers need to feel secure.

Data can be tampered with on either end and while in transit.

The Open Source Software Community frequently uses checksum to protect software integrity. This same strategy can be used to protect consumers from malicious apps and widgets.  This simplified example will use MD5 in PHP to check the integerity of the app, but MD5 should not be used for sensitive data like passwords in a production environment.  US-CERT of the U. S. Department of Homeland Security said MD5 “should be considered cryptographically broken and unsuitable for further use,” and most U.S. government applications will be required to move to the SHA-2 family of hash functions after 2010.

Simple App

Here is a very simple app that could be part of a custom Enterprise 2.0 Dashboard. The App is reviewed and approved. The reviewer signs the app (creates app MD5 Hash: c15a7308d89afe9218a1b0f60a37f8ad) so changes can be detected when it comes back through the proxy server.

Simple App in Proxy Server before Dashboard Display
Deliver app if new hash and signature match. Disable app and notify Admin if something does not look right.

The Simple App with Key Logger Script Injected

Happy Fav Five Friday!

Fav 5 Places

  1. Google Gadgets For Your Webpage
  2. ‘App store’ makes service orientation real for the business
  3. Global CIO: The Case For Copying Apple’s App Store
  4. Nexuo Enterprise Platform
  5. Enterprise Irregulars: Designing User Experience

The people from Open Social provides a great Introduction To Signed Requests

OpenSocial API provides a method to communicate OpenSocial ID numbers back to your server in a secure way, allowing for the construction of robust web service backed OpenSocial applications, using a portion of the OAuth authorization protocol.  This article will explain the method to make such secure requests from your OpenSocial applications, as well as the server-side process that you need to follow in order to verify that the data passed has not been tampered with.   Learn more here.

Social Business Gets Sexy in Enterprise 2.0

Enterprise 2.0 & the Sexy Side of Integration with SOA

The Social Business Strategy of Enterprise 2.0

Successful Enterprise 2.0 is all about integration.  This integration goes beyond using technology to connect data & systems.  Enterprise 2.0 integration includes a Social Business Strategy.  Some of these strategic integration points include:

  • Integrating Culture
  • Integrating Partners, Customers, & Vendors
  • Integrating Interactive Design Principals
  • Integrating The Dispersed Workforce
  • Integrating Support for Multiple Needs & Devices

Service-Oriented Architecture (SOA) supports using technology to loosely couple systems and social business integration.  Some great guiding principals for Enterprise 2.0 Strategy are defined in the SOA Manifesto.  The SOA Manifesto priorities include:

  • Business value over technical strategy
  • Strategic goals over project-specific benefits
  • Intrinsic interoperability over custom integration
  • Shared services over specific-purpose implementations
  • Flexibility over optimization
  • Evolutionary refinement over pursuit of initial perfection

Great principals for supporting a solid Enterprise 2.0 Strategy can be found in the Guiding Principles section of the SOA Manifesto.

Sexy Enterprise 2.0?

“Enterprise 2.0 Solutions will become very sleek and sexy.” is a statement from this article: Collection of Enterprise 2.0 Predictions & Tech Trends for 2011.

Employers and employees are already seeing the sexy side of Social Business in Enterprise 2.0 with the release of tibbr for the Enterprise.  TIBCO tibbr supports context integration to give people and data more meaning.  The functionality broken down into the simple form allows people to follow people and data.  There is also integration support for Facebook, Twitter, and other Social Networks.  Dennis Howlett wrote a great article about TIBCO tibbr that includes this excerpt “.. it is further eroding the boundaries between siloed operations ..”  You can read his full article here.

What is TIBCO tibbr?

TIBCO tibbr is the first social computing tool specifically built for the workplace that allows the right information to find you.

Unlike social networking applications that focus on the concept of “following people,” tibbr is the first to take an entirely new approach to social computing by allowing you to follow subjects, applications, and social event streams. Learn more here.

tibbr-enterprise-2-0-social-business

Happy Fav Five Friday!

Top 5 Places This Week

  1. What are the distinctions between Social Business and Enterprise 2.0?
  2. Rethinking the Future of Business Part 2: Building the Framework
  3. What Social Media and Enterprise 2.0 Can Bring to HR Processes
  4. What’s The Difference Between Game Mechanics in the Enterprise and Good Management?
  5. How to Build a mobile app on Apple iPhone using Sencha JavaScript Framework

Enterprise 2.0 Social Business Collaboration

Call it “Enterprise 2.0” or “Social Business“, it’s all about building relationships and fostering collaboration.  These conversations around Business Strategy and Social Enterprise reminds me of this presentation “Enterprise 2.0 – Efficient Collaboration and Knowledge Exchange“.

The Enterprise 2.0 Strategy of Gamification

Improving Enterprise 2.0 Adoption Through Gamification

A Gamification Strategy will Continue to Support Perpetual User Engagement

gamification-summit

The Gamification Summit 2011 created a bit of buzz in Enterprise 2.0 circles this week.  This buzz included this great article Trends: 5 Engagement Factors For Gamification And The Enterprise by R Ray Wang, you can connect with him on Twitter at @rwang0

Did you know that Call of Duty: Black Ops generated more than $360 Million Dollars in the first day of sales? Call of Duty: Black Ops is the most beautifully intelligent game I have ever played!  This masterpiece offers amazing game play, stunning graphics, awards, badges, achievements, customization, and takes game mechanics to a whole new level.  Let’s take a look at how we can leverage these success factors for the Enterprise, but first take a look at this funny Call of Duty: Block Ops video.

Call of Duty: Black Ops TV Commercial: “There’s A Soldier In All Of Us”

What is Gamification?

Gamification is the use of game play mechanics for non-game applications, in order to encourage people to adopt the applications. It also strives to encourage users to engage in desired behaviors in connection with the applications.  You can learn more on the Gamification Blog.

How Does Gamification Apply to Enterprise 2.0?

Maslows-Hierarchy-of-Needs

Gamification in Enterprise 2.0 is about Maslow’s hierarchy of needs, a theory in psychology, proposed by Abraham Maslow in his 1943 paper A Theory of Human Motivation.  Most of these needs are met by popular games and should be supported in Enterprise 2.0 platforms to ensure rapid adoption and success.  You will discover some simple methods to “Gamify” your Enterprise 2.0 Platform in this article I wrote last year Game Theory for Enterprise 2.0 Adoption.  That article also includes a few videos about human behavior.  Ideas around the bigger picture of using game mechanics in the Enterprise is coverd in this article Enterprise 2.0 Adoption Patterns: Collective Intelligence.

Gamification Videos & Presentations

The gamification presentations from the Gamification Summit are available to members, but here are a few presentations that will get you thinking differently about using game mechanics in your Enterprise 2.0 Platform to improve user engagement.

Gamification Patterns & Pitfalls

Gabe Zichermann, Gamification Expert and Author discusses some of the main ways that gamification will change your business in this video.

Gamification by Scott Dodson COO, Bobber Interactive

Gamification-by-Scott-Dodson

Gamification by Wanda Meloni, M2 Research

Gamification-by-Wanda-Meloni

Gamification and Its Discontents by Sebastian Deterding

gamification-discontents-Sebastian-Deterding

Engagement through Gamification

Engagement-through-Gamification

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