Resource Center

Jackopedia™

What does ‘Enterprise Web 2.0’ mean to you? How about ‘Enterprise Mashups’, ‘SOA’ or ‘Ajax’? These terms and many more are loaded with hype but what exactly do they mean? To help you better define these terms, we have created the Jackopedia. If its related to Enterprise Web 2.0, the Jackopedia is your resource. And if you don’t see something that should be here, send us a note!

Enterprise Mashups are a shareable software block created by a user, encapsulating ad-hoc user driven processing of disparate data sources, delivered with a user focused view; enterprise mashups deliver this functionality while adhering to enterprise requirements for security, reliability and service governance.

REA or Rich Enterprise Applications are web-based applications that access enterprise-class services in the form of SOAP, WSDL, legacy systems, and databases while providing a consist set of policies, management, and administration. 

5C Framework is a guide to any of the JackBe Enterprise Mashup Frameworks:

• Consume- A user must be able to consume public and private services on demand. The minimum set of consumable SOA-style services includes: WSDL, REST, RSS and Databases.
• Create - A user must be able to create new mashups made up of consumed services and previously created mashups, preferably in a visual editor.
• Customize A user must be able to customize (filter, for example) existing mashups and create variants which themselves become mashups. Versioning of mashups is also preferred.
• Collaborate- A user must be able to publish and share their mashups publicly and privately, also providing opinions/rating/comments on services and mashups to peers.
• Confidence- All consumption, creation, customization and collaboration must occur in a secured and governed environment that delivers enterprise-grade security (i.e. integrating with single sign-on systems), reliability, and enterprise monitoring/governance systems.

Service Virtualization is the creation of lightweight, standards-based virtual interfaces to less-standardized sources of logic and data. Virtualization is the glue that connects any type of data and services to the desktop and the web, enabling today’s Enterprise 2.0 applications to work efficiently in the browser.

Web 2.0 is a term given to describe a second generation of the World Wide Web that is focused on the ability for people to collaborate and share information online. Web 2.0 basically refers to the transition from static HTML Web pages to a more dynamic Web that is more organized and is based on serving Web applications to users. (http://www.webopedia.com/TERM/W/Web_2_point_0.html)

Enterprise Web 2.0 empowers users to build upon the existing knowledge of others through sharing and collaboration. Enterprise Web 2.0 empowers knowledge workers with web 2.0 technologies like wikis, blogs, and mashups; providing them with the information they need, when they need it and how they need it.

Mashups are web applications that combine data or content from more than one source to create a richer more functional application.
(http://en.wikipedia.org/wiki/Mashup_%28web_application_hybrid%29)

SAAS-Software as a Service (SaaS) is a software application delivery model where a software vendor develops a web-native software application and hosts and operates (either independently or through a third-party) the application for use by its customers over the Internet. Customers do not pay for owning the software itself but rather for using it. (http://en.wikipedia.org/wiki/Software_as_a_service)

Ajax or Asynchronous JavaScript and XML is a web development technique for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user makes a change. This is meant to increase the web page’s interactivity, speed and usability.

SOA or Service Orientated Architecture builds applications out of services. The goal of SOA is to allow fairly large chunks of functionality to be strung together to form ad-hoc applications which are built almost entirely from existing software services.
(http://en.wikipedia.org/wiki/Service-oriented_architecture)

RIAs or Rich Internet Applications transfer the processing necessary for the user interface to the Web client but keep the bulk of the data back on the application server. This allows for Client/Server-like behavior and functionality on the Web.