Services and integration – Google 2007 JavaOne Advance Conference Guide User Manual

Page 53

technical sessions | track eight : services and integration |

Services and Integration

TS-8544 Integration Gets All Mashed up: Bridging Web 1.0 and

Web 2.0 Applications

Andreas Krohn, Kapow Technologies

Today, using a web browser has become the most dominant way to access
content and applications in the enterprise. It is common for companies
to let their employees, partners, and customers access all kinds of
information and services via the web. However, as the number of web
systems explodes, both inside and outside the firewall, it is not always
easy to get them to work together in an integrated fashion, because they
are often built by different departments and organizations using a variety
of technologies.

The back-end systems behind the web interface, the traditional
integration point, are typically a conglomeration of incompatible
operating environments, data structures, development tools, and
software architectures. Traditional approaches to integration
are costly, brittle, tightly coupled, and largely unsatisfying to IT
organizations and developers.

Developers who attend this session learn about a new approach to
application integration called mashups. Mashups focus on integration
through the web-based front end, using the most common web
interfaces available today: HTML, HTTP, Ajax, REST, SOAP, RSS, ATOM,
and the JavaScript programming language. They enable any application
component with a web interface to be quickly and easily repurposed or
integrated, including web-based content, data, or business logic.

This session demonstrates the use of Swing-based wizards to create
the following mashup styles, each suited to solve specific types of
integration problems:

• Presentation-layer mashups. Presentation-layer mashups extract and

assemble various parts of applications and web sites and other assets
available via HTTP to create internal portals, wikis, and customer-facing
sites. “Clip” content or extract data from any web site, incorporate Ajax
for client-side efficiencies, and deploy as JSR 168- and WSRP-compliant
portlets with a few mouse clicks.

• Logic-based mashups. This class of mashups provides programmatic

access to business logic through existing SOAP interfaces provided
by the source application or by wrapping legacy application logic
as a REST-based service when no service interface exists. These
mashups can be created without changes to the underlying code of
the legacy application and require no control of the source application
environment, providing a cost-effective bridge between Web 1.0 and
Web 2.0 applications.

• data/content-based mashups. These mashups join content from two

or more sources and either combine them into a new data repository or
transfer the data to a new place or application.

The programming model for mashups is different from that of web
applications or web services. Although many of the same Java technology-
based components—such as JavaServer Pages technology, servlets,
portlets, and the JavaScript programming language—are used, the
application platform is the web itself, with the application paradigm
being one of incremental reuse and rapid deployment, as opposed to
development from scratch. Mashups represent the leading edge of
Web 2.0 application development and offer tremendous productivity
advantages for enterprise developers.

TS-8554 Building, Assembling, and deploying Composite

Service Applications

Michael Beisiegel, IBM
Michael Rowley, BEA Systems

Businesses are placing increasing demands on developers to enable
service collaboration across diverse organizations using a variety of
technologies such as Java technology, Microsoft .NET, PHP, Ruby,
and JavaScript technology. Although web services provide protocol
interoperability, developers face a series of challenges in building,
assembling, and deploying applications in distributed service
environments. This session demonstrates how SCA goes beyond web
services to address these challenges. Taking a hands-on approach, it
shows how SCA provides a language-independent service development
model, an assembly model for tying together services written in a variety
of languages, and a deployment model for composite applications.

TS-8612 jPdL: Simplified Workflow for Java Technology

Tom Baeyens, JBoss, a Division of Red Hat

Are you considering developing a homegrown workflow engine? Then
you should definitely attend this session first. Java Process Definition
Language (jPDL) is a language for expressing long-running processes.
Unlike most orchestration technologies, jPDL focuses on plain Java
technology and includes sophisticated task management capabilities.
Attendees learn in which scenarios jPDL is more appropriate than BPEL or
other process languages.

Human tasks and other forms of wait states are typically quite a hassle
in server-side programming. Developers have to think in terms of
requests and manually maintain the user tasks in a database. In the
structure of a server-side application, it’s very hard to get a picture of
the overview. jPDL gives you back that overview. Handling an insurance
claim, submitting and handling an expense note, or going through a
lawsuit are good examples of long-running processes. jPDL allows users to
express the overall execution of these processes in terms of the JavaBeans
architecture, user tasks, and other forms of wait states. These processes
can be edited and viewed graphically. jPDL leverages the unified
expression language (EL) to easily bind your POJOs to the process flow,
and it leverages Hibernate to store the state of the long-running processes
in the users’ database.

On the one hand, jPDL has all the required features for business process
management (BPM), but on the other hand, jPDL is also designed to fit
like a glove on standard and enterprise Java applications. Ease of use for
developers on the Java platform is often neglected in BPM offerings, and
jPDL solves this problem.

TS-8450 Pragmatic Advice for Implementing SOA: Lessons Learned from the Common

Services Team at American Airlines

TS-8459 Service Virtualization: Separating Business Logic from Policy Enforcement

TS-8541 A Step Along the Way: Using Ajax, Portals, and Services to Provide Better

Network Management

TS-8544 Integration Gets All Mashed Up: Bridging Web 1.0 and Web 2.0 Applications

TS-8554 Building, Assembling, and Deploying Composite Service Applications

TS-8612 jPDL: Simplified Workflow for Java Technology

track eight : Services and Integration