You are on page 1of 24

dojo.

E Dashboard
Agenda

• What is the Dashboard?


• Why Mashups are needed?
• Overview of the Dashboard
• Look at the architecture
• Being Successful
• Answer Questions

2
What is the dojo.E Dashboard?

• What it is:
– The dojo.E Dashboard is a reference for how
to build out a Mashup application.
– Demonstration of the capabilities for; dojo,
dojo.E, Jaxer…
– Demonstration of building out an Ajax
application including; data binding, screen
flow…
• What it is not:
– A production application
– Something we sell

3
Why are Mashups needed?

4
Enterprise Mashups
Connecting People to Services

Enterprise Services

?????
People Service
s
Why are Mashups interesting?

• Solve a problem:
– Make it easy for people with out IT skills build
custom screens
– Consolidate data services from multiple
sources
– Quick visualization of data.
• Benefits:
– Productivity
– Agility
– Efficiency

6
Who is the User, Who is the Creator?

• Everyone can be a User


• Is the creator IT or not IT?
• What are people good at?
– Create content
– Consumer content
– Make Decisions
Where do Mashups fit in
Information Technology?

8
Application Virtualization Trend
Ap
 Browser
 Desktop

p
 Browser

Ap
 Desktop

p
 Browser

Ap

Virtualization
 Desktop
Applicatio
n
 Browser

Ap
 Desktop p Service

 Browser UI UI

Ap
 Desktop
p Service Service

Ap p Service Service Service

p App
Server
App
Server
App
Server
App
Server

Store Store Store Store Store

Mainfra Client/Ser 3 Tiers SOA Mashup Next Gen


me ver Technology
Technology
Consumers Producers
(Software/SaaS
(Enterprises)
Companies)
Convergence of SOA and Web 2.0
Architectures…

Corporate standards
Enterprise wide
SOA
Centralized
Interoperable
High scalability
Defined security Ad Hoc
Formal
Loosely Coupled Data-Centric Situational

Composite Applications
Collaborative

Web 2.0
De-centralized Lightweight

Browser based Self-service

* Source: Enterprise Mashup Webinar


What makes up a Mashup?

11
Mashup Container
• WebTop – UI simlar to iGoogle, pageflake that allows
users to add and remove widgets and organize them.
• Personalization – Allows for the storage of settings
related to the end-user’s application state.
• Pub/Sub Eventing – Allows the widgets to
communicate together in a way that doesn’t need to be
predefined in the applications. This is a major change
from the way that the current product works.
Information about events and the meta-data that an
event contains must be queryable at runtime.
• Event Connector – One of the differences in the
Mashup container as compared to iGoogle is that the
user can connect the widgets together so that
information from one can drive the display of another.

12
Mashup Server
• Connection to SOA Governance – The widgets that
are accessible should be pulled from SOA governance
infrastructure.
• Hot deployable widgets – The product needs to allow
for the deploying of widgets without the need to
redeploy the application or restart the server.
• Integration with authentication – integrate with
standard authentication infrastructure
• Role-based Access – need to be able to control use
access to widgets and provide means to customize
widgets based on access
• Federated Mashup Repository – allows users to pull
widgets from any number of servers
• Portal – Widgets can be accessed and deployed into a
JSR 168 compliant portal server.

13
Widget Creator
• Creation - Allow developers to create Service-
enable widgets
• Versioning – Need to allow the versioning of
the widgets
• Describe - events and meta-data associated
with events
• Publish - widgets to the Mashup server
• Customization - of the Mashup interface
• Open – Need to allow developers to build and
deploy widgets built using any technology.

14
Let’s look at the dojo.E Dashboard

15
16
What is in the Dashboard?

17
High-level Block Diagram
Custom Widgets / Data source Handlers / Workflow

Dojo/dojo.E Jaxer

Browser

HTML JSON / Jaxer Remoting

Jaxer

Database Yahoo Pipes GData Kapow What ever


you need

18
High-level Block Diagram – J2EE
Custom Widgets / Data source Handlers / Workflow

Dojo/dojo.E Seam Remoting

Browser

HTML JSON / Seam Remoting

Nexaweb Jboss Seam

J2EE

Database Yahoo Pipes GData Kapow What ever


you need

19
Steps to success

• Production
– Need services to feed into the Mashup
– Leverage companies like Kapow, Mashery,
StrikeIron

• Consumption
– Look at complete platforms
– Standards, Open, Mission Critical

• Proof of Concepts

20
Steps to success

• Production
– Need services to feed into the Mashup
– Leverage companies like Kapow, Mashery,
StrikeIron

• Consumption
– Look at complete platforms
– Standards, Open, Mission Critical

• Proof of Concepts

21
Questions that were asked
• Sortable grid with paged, dynamic data.
• Using dojo.data with Tree widget?
• Dashboard creation automation.
• Anything related to database driven product webpages that are fully retrievable
by search engine spiders.
• Can dojo consume binary data feeds, remote object calls, or is it limited
to text/xml formatted data?
• examples for yahoo and google
• multimedia and/or photo album type application. Also grid control
• How easy it might be to create real-time integration abd business logic
to "join" these Disparate services.
• Event set up and communications between portlets.
• Performance optimization
• Perhaps an overview of how dojo fits into Struts2/Webwork
• Interested in knowing how the composition works?
• What types of changes do you expect to see (futuristic) and how do you
handle them in dojoE
• The more technical, the better.

22
Free “Lunch and Learn”
session with Bob at your
office *
Contact events@nexaweb.com
* Restrictions apply (of course)

23
Thank you

24