Skip the navigation

Sidebar: How Orbitz Uses the Jini Architecture

By Carol Sliwa
September 6, 2004 12:00 PM ET

Computerworld - Layer 1: Presentation/State/Persistence
A customer request comes in via a Web application or telephone interactive voice response system. It passes to an Apache Web server and then to a BEA WebLogic Java servlet container, called the Jini client, which is the consumer of the Jini service. That client uses the Jini discovery protocol to find the desired Jini lookup service.
Layer 2: Jini Lookup Services
Redundant instances of Jini lookup services find the Jini service(s) that can meet the customer's request and send a proxy back to the Jini client. The business logic in this layer is responsible for routing, coordination and fail-over to find the best mainframe in Layer 3 to service the request.
Layer 3: Supplier-Specific Services
Third-party mainframes from WorldSpan, Pegasus and Orbitz's internally hosted J2EE-based inventory systems run on the back end, transformed into Jini services through Java-based interfaces that register with the Jini lookup service.

Read more about App Development in Computerworld's App Development Topic Center.



Our Commenting Policies