dojoe dashboard

8/14/2019 dojoe dashboard

1/24

dojo.E Dashboarddojo.E Dashboard
http://www.unica.com/


2/24

2

Agenda

What is the Dashboard?

Why Mashups are needed?

Overview of the Dashboard

Look at the architecture Being Successful

Answer Questions
http://www.unica.com/


3/24

3

What is the dojo.E Dashboard?

What it is:

The dojo.E Dashboard is a reference for howto build out a Mashup application.

Demonstration of the capabilities for; dojo,dojo.E, Jaxer

Demonstration of building out an Ajaxapplication including; data binding, screenflow

What it is not: A production application

Something we sell


4/24

4

Why are Mashups needed?


5/24

Enterprise Mashups

Enterprise Services

Connecting People to Services

?????People Service

s


6/24

6

Why are Mashups interesting?

Solve a problem:

Make it easy for people with out IT skills buildcustom screens

Consolidate data services from multiplesources

Quick visualization of data.

Benefits:

Productivity

Agility

Efficiency


7/24

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


8/24

8

Where do Mashups fit inInformation Technology?


9/24

Application Virtualization Trend

App

App

Store Store

App

AppServer

Store

App

AppServer

Mainframe

Client/Server

3 Tiers SOA Mashup

Store

App

AppServer

UIService

BrowserDesktop

Browser Desktop

Browser Desktop

Browser Desktop

Next Gen

App

Browser Desktop

Store

AppServer

UIService

Application

Service

Virtua

lization

Service Service Service

TechnologyProducers(Software/SaaS

Companies)

TechnologyConsumers

(Enterprises)


10/24

Centralized

Formal

Corporate standards

High scalability

Enterprise wideSOA

Browser based Self-service

Situational

Collaborative

LightweightDe-centralized Web 2.0

onvergence o an e .Architectures

Data-CentricLoosely Coupled

Ad Hoc

Composite Applications

Defined security

Interoperable

Source: Enterprise Mashup Webinar


11/24

11

What makes up a Mashup?


12/24

12

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-users application state.

Pub/Sub Eventing Allows the widgets tocommunicate together in a way that doesnt need to be

predefined in the applications. This is a major changefrom the way that the current product works.Information about events and the meta-data that anevent contains must be queryable at runtime.

Event Connector One of the differences in the

Mashup container as compared to iGoogle is that theuser can connect the widgets together so thatinformation from one can drive the display of another.


13/24

13

Mashup Server

Connection to SOA Governance The widgets thatare accessible should be pulled from SOA governanceinfrastructure.

Hot deployable widgets The product needs to allowfor the deploying of widgets without the need toredeploy 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 customizewidgets 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.


14/24

14

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 anddeploy widgets built using any technology.


15/24

15

Lets look at the dojo.E Dashboard


16/24

16


17/24

17

What is in the Dashboard?


18/24

18

High-level Block Diagram

Dojo/dojo.E

Jaxer

Browser

HTML JSON / Jaxer Remoting

Jaxer

Yahoo Pipes GData KapowDatabase What everyou need

Custom Widgets / Data source Handlers / Workflow


19/24

19

High-level Block Diagram J2EE

Dojo/dojo.E

J2EE

Browser

HTML JSON / Seam Remoting

Seam Remoting

Yahoo Pipes GData KapowDatabase What ever

you need

Custom Widgets / Data source Handlers / Workflow

Nexaweb Jboss Seam


20/24

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/24

21

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


22/24

22

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 retrievableby search engine spiders.

Can dojo consume binary data feeds, remote object calls, or is it limitedto 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 logicto "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 youhandle them in dojoE

The more technical, the better.


23/24

Free Lunch and LearnFree Lunch and Learn

session with Bob at yoursession with Bob at your

office *office *

Contact [email protected] [email protected]

* Restrictions apply (of course)* Restrictions apply (of course)

23


24/24

24

Thank you

dojoe dashboard

Documents

Transcript of dojoe dashboard