8.2 The sample e-business application: Trade

 < Day Day Up > 



8.2 The sample e-business application: Trade

Trade3 is the third generation of the WebSphere end-to-end benchmark and performance sample application. The new Trade3 benchmark has been re-designed and developed to cover WebSphere's significantly expanding programming model and performance technologies. This provides a real world workload enabling performance research and verification tests of WebSphere's implementation of J2EE 1.3 and Web Services, including key WebSphere performance components and features.

Note 

You can download Trade3 sample business application from

http://www-3.ibm.com/software/webservers/appserv/benchmark3.html

and follow the readme.html to install Trade on a WebSphere Application Server 5.0.1 application server.

Trade3 builds off of Trade2, which is used for performance research on a wide range of software components and platforms, including WebSphere, DB2, Java, Linux, and more. The Trade3 package provides a suite of IBM developed workloads for determining the performance of J2EE application servers.

Trade3's new design enables performance research on J2EE 1.3, including the new EJB 2.0 component architecture, Message Driven Beans, transactions (1-phase and 2-phase commit), and Web Services (SOAP, WSDL, and UDDI).

Trade3 also drives key WebSphere performance components, such as DynaCache, WebSphere Edge Server, AXIS, and EJB caching.

The architecture of the Trade3 application is depicted in Figure 8-1.

click to expand
Figure 8-1: Trade3 architecture

The Trade3 application models an electronic stock brokerage providing Web and Web Services based online securities trading. Trade3 provides a real-world e-business application mix of transactional EJBs, MDBs, servlets, JSPs, JDBC, and JMS data access, adjustable to emulate various work environments. Figure 8-1 shows high-level Trade application components and a model-view-controller topology.

Trade3 implements new and significant features of the EJB 2.0 component specification. Some of these include

CRM

Container Managed Relationships (CRM) provides one-to-one, one-to-many and many-to-many object to relational data managed by the EJB container and defined by an abstract persistence schema. This provides an extended, real world data model with foreign key relationships, cascaded updates/deletes, and so on.

EJB QL

Standardized, portable query language for EJB finder and select methods with container managed persistence.

Local/Remote I/Fs

Optimized local interfaces providing pass-by reference objects and reduced security overhead WebSphere provides significant features to optimize the performance of EJB 2.0 workloads. These features are listed here and leveraged by the Trade3 performance workload. Performance of these features is detailed in Figure 8-1 on page 236.

EJB Data Read Ahead

A new feature of the WebSphere Application Server 5.0 persistence manager architecture for performance is various optimizations to minimize the number of database roundtrips by reading ahead and caching object structures in order to avoid round trips.

Access Intent

Entity bean run-time data access characteristics can be configured to improve database access efficiency (includes access type, concurrency control, read-ahead, collection scope, and so on)

Extended EJB QL

WebSphere provides critical support for extended features in EJB QL, such as aggregate functions (min, max, sum, and so on). The extended addition also provides dynamic query features.

To see the Trade application component details (as shown in Figure 8-2 on page 238), log in to:

click to expand
Figure 8-2: WAS 5.0 Admin console- Install of Trade3 application

https://hostname:9090/admin/

and click Application Enterprise Applications Trade.

In addition to a login page that is used to access the Trade system, a main home page that details the users account information and current market summary information is provided. From the user's home page, the following asynchronous transactions are processed:

  • Purchase order is submitted.

  • New "Open" order is created in DB.

  • The new order is queued for processing.

  • The "open" order is confirmed to the user.

  • The message server delivers the new order message to the TradeBroker.

  • The TradeBroker processes the order asynchronously, completing the purchase for the user.

  • The user receives confirmation of the completed Order on a subsequent request.



 < Day Day Up > 



End-to-End E-business Transaction Management Made Easy
End-To-End E-Business Transaction Management Made Easy
ISBN: 0738499323
EAN: 2147483647
Year: 2003
Pages: 105
Authors: IBM Redbooks

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net