Google 2007 JavaOne Advance Conference Guide User Manual

Page 52

| technical sessions | track eight : services and integration | java.sun.com/javaone

* Content subject to change.

TECHNICAL SESSIoNS

| TRACK EIGHT | SERVICES AND INTEGRATION

Services and Integration

TS-8450 Pragmatic Advice for Implementing SoA:

Lessons Learned from the Common Services
Team at American Airlines

Steve Moats, American Airlines
Brian Polster, Credera

In 2004 the American Airlines Customer Technology Group was looking for
a way to better leverage its resources. The group, which was responsible
for all customer-facing systems, such as AA.com, IVR, and airport kiosks,
had systems with similar functionality but different sets of analysts,
developers, and quality assurance teams. AA started a Common Services
team to address the duplication within these systems. The team soon
faced several technical and organizational challenges.

This presentation focuses on the lessons learned by this team over the
past two years, detailing how it dealt with the following issues:

• Service variation—how to handle business rules that vary between

departments

• Service versioning—how often to release services; how to manage

impacts to client systems

• Deploying services—it’s OK not to use web services (some of the time)

TS-8459 Service virtualization: Separating Business Logic from

Policy Enforcement

Michael Gionfriddo, Sun Microsystems, Inc.
Ron Ten-Hove, Sun Microsystems, Inc.

Creating services is only half the battle in providing them to users.
Beyond the core service, a wide variety of policy enforcement mechanisms
is needed to address security, privacy, and manageability concerns.

This session discusses a new approach to service provision: service
virtualization. This separates the core logic of a service from enforcement
of policies by introducing a virtual services layer, allows policies to be
treated as an operational aspect of service delivery, and avoids “code
churn” when policies change. This architecture provides unique features
for addressing some of the most annoying problems encountered in
delivering and evolving services.

TS-8541 A Step Along the Way: using Ajax, Portals, and Services

to Provide Better Network Management

Anton McConville, Nortel

At the 2006 JavaOne conference, Scott McNealy noted that if we could
offer each of the children in Africa a laptop and link them to the internet,
there wouldn’t be enough system administration in the world to support
the resulting network. He challenged us to use web services, thin clients,
and network computing to help.

Supporting our communications networks has become a growing problem
even with the networks we’re building in offices and cities.

• The number of devices that are networked is increasing.
• The range of devices in the network is widening.
• Devices have evolved from dedicated solid-state boxes to programmable

and customizable solutions.

There are currently only limited convenient means of fluidly managing
and relating these interfaces to each other. Network components ship
with their own management tools, the presentation and access of those
tools differ, and they don’t contribute their data to each other.

This problem hasn’t gone unnoticed at Nortel (a major telecom
equipment provider).

This presentation explores how one team leveraged Web 2.0 concepts
within a large corporation with a strong telecom hardware culture and
history to strive toward a more capable management solution.

The presentation tells a story and discusses the ingredients: Enterprise
JavaBeans (EJB) 3.0 architecture, Ajax/portal-based user interface, service-
oriented architecture, and agile development environment. It navigates
through the terminology, cuts through the hype, and shows some bold
decision-making here and there.

The session also demonstrates parts of the solution. A simple service is
built and deployed to show how the technology fits together and how
service orientation can help improve network manageability.

Although this solution doesn’t close the digital divide in any immediate
way, it rises to McNealy’s challenge and hints at how we can grow to
make the network smarter over time. It is a step along the way.

Attendees should be aware of, and interested in, web services, enterprise
Java technology, portals, and Ajax.