Transaction Commit Options
|
|
- Steven Johnson
- 6 years ago
- Views:
Transcription
1 Transaction Commit Options Entity beans in the EJB container of Borland Enterprise Server by Jonathan Weedon, Architect: Borland VisiBroker and Borland AppServer, and Krishnan Subramanian, Enterprise Consultant Borland Software Corporation June 2002 Introduction This paper provides an overview of the transaction commit options defined in the Enterprise JavaBeans (EJB ) specification and how the EJB container in Borland Enterprise Server, AppServer Edition handles those options. The various transaction commit options defined in the EJB specification are applicable to entity beans only. This paper enumerates the behavior and performance of entity beans running within the EJB container of Borland Enterprise Server when using each of the transaction commit options. Entity beans reviewed Entity beans provide an object view of data. The data is usually stored in a relational database, although it is also possible for an entity bean to provide an object view of an existing (legacy) application. To maintain data integrity, entity beans usually are accessed in the scope of a transaction. Contents Introduction 1 Instance life cycle 2 Transaction commit options 4 Conclusion 9 The EJB container of the Borland Enterprise Server manages the synchronization among concurrent invocations from multiple client threads; the bean provider need not be concerned with this fact. To support concurrency, the EJB container creates as many instances of entity beans as there are simultaneous transactions; this is one of the strengths of EJB container implementation (for both EJB 1.1 and EJB 2.0) by Borland. Some vendors serialize access to a single entity bean instance, limiting scalability.
2 Clients Figure 1: Serializing access to an entity bean. EJB container Single entity bean instance As the preceding figure shows, some vendors attempt to solve the problem of synchronizing concurrent client access to entity beans by serializing access to a single entity bean instance. However, this solution is not scalable since a single entity bean instance cannot efficiently service requests when the number of clients increases. Note also that this solution is imperfect when the EJB container is clustered. EJB container of Borland Enterprise Server Instance life cycle The EJB 1.1 and EJB 2.0 specifications define three states for an entity bean instance: Does not exist Pooled state Ready state In the following sections, we discuss each of these states and how the container moves entity beans among the various states. Does not exist The does not exist state is not particularly interesting, as this is the state an entity bean is in before it is instantiated. This state is analogous to nothingness. Pooled state The pooled state is where an entity bean s life starts, when the EJB container instantiates the entity bean. After creating an instance, the container then invokes the setentitycontext(entitycontext) method to pass the created instance a reference to the EntityContext interface. The pooled state is where an entity bean instance is not associated with a primary key. Clients Figure 2: How the EJB container of Borland Enterprise Server handles simultaneous client requests. As the above figure shows, the EJB container of Borland Enterprise Server creates as many instances of entity beans as there are simultaneous transactions. That is, these instances run in parallel, servicing client requests more efficiently. ejbfind (args) ejbselect (args)* ejbhome (args)* * EJB 2.0 only Figure 3: Pooled state. DOES NOT EXIST Step 1: newinstance() Step 2: setentitycontext(ec) 2
3 Beans in this state can be used to execute methods in the home interface. Note that a call to methods in the home interface will result in the instance remaining in the pooled state. The property ejb.maxbeansinpool controls the number of bean instances in this state, with a default setting of When the container starts up (or is restarted), there are no instances in the pooled state. That is, the pool is filled lazily in the Borland Enterprise Server. The number of entity bean instances in this state increases as required, depending on access by various clients. Ready state An entity bean is in the ready state when the instance is associated with a specific object identity. In other words, the given entity bean instance is associated with a primary key. Let s extend this aspect of the EJB specification with our own visualization for the sake of clarity. Assume there are two sub-classifications of bean instances in the ready state: Cached state Transactional state Cached state The cached state is where an entity bean instance is associated with a primary key. Depending on the transaction commit option (discussed in the next section), the bean instance might also be associated with state (state means the persisted fields other than the primary key). The size of this cache is governed by the ejb.maxbeansincache property, with a default setting of As in the pooled state, the number of entity bean instances in the cached state is filled lazily as new primary keys are encountered. If the application uses a small table or a few rows from a given table, often far fewer than 1000 beans are typically in use. For performance reasons, you may want to increase the size of this cache since it increases the likelihood of a cache hit (i.e., the given item could be retrieved from the cache). Caveat: Too many entity bean instances in memory may start to impact garbage collection, although this depends on the configuration of the Java Virtual Machine (JVM ) and hardware. Figure 4: Cached without state. Transactional state ejbactivate() CACHED WITHOUT STATE The transactional state is where entity bean instances actually execute business methods. Beans in this state are always associated with a transaction and typically return to the cached or pooled state at the end of the transaction. ejbpassivate() ejbactivate() CACHED WITHOUT STATE Figure 5: Transactional state. ejbload() ejbstore() As seen in the figure above, the entity bean instance in the Cached without state knows only about its primary key and not the values of its persisted fields. The value of these persisted fields needs to be synchronized with those in the database; this is accomplished via a call to the ejbload() method. Once the ejbload() is performed, the entity bean will have all the persisted fields in sync with those in the database (for that transaction) and can then execute business methods. 3
4 ejbpassivate(): This disassociates the bean from its primary key, i.e., the bean instance returns to the ejbpassivate() ejbactivate() ejbremove() pooled state. CACHED WITHOUT STATE ejbload() ejbstore() business methods ejbselect (args)* * EJB 2.0 only Step 1: ejbactivate() Step 2: ejbload() Step 4: ejbstore() Step 5: ejbpassivate() Figure 6: Transactional state transitions. Transaction commit options There are three transaction commit options defined by the EJB 1.1 and EJB 2.0 specifications. These are commit options A, B, and C. We start with option C, as it is the simplest behavior. Option C In option C, the cache is not used, that is, the property ejb.maxbeansincache is ignored. Entity bean instances in this pool wait for something to do. If a call on the home interface occurs, the entity bean executes against an instance from this pool which is in fact the behavior for all commit options. If a business method is invoked by a client, the following sequence of calls is made: ejbactivate(): This associates the bean instance with a primary key. ejbload(): This associates the bean instance with the state in the database i.e., the persisted fields in the entity bean are synchronized with those in the database. Following the above two calls, the business methods are executed in the scope of that transaction. When the transaction ends (i.e., the transaction commits), the following sequence of calls are made: ejbstore(): This updates the database with the changed values (if any) of the entity bean instance s persisted fields. Step 3: business method(s) Figure 7: Option C bean states. Option B Option B is the default behavior of Borland Enterprise Server. Here, bean instances are kept in the cache: the bean instances are associated with a primary key, but the state of an entity bean s persisted fields are not synchronized with the values in the database. When a client invokes a business method, the EJB container checks its cache to see whether a corresponding bean instance (identified by its primary key) exists. If so, then that cached instance is taken out and used. The ejbload() is invoked on this cached instance to synchronize its state (persisted fields) with those in the database. If the cache does not contain an instance associated with that primary key (either because the bean associated with that primary key has not been accessed previously or because some other concurrent transaction has already taken the bean instance out of the cache for its own use), then a bean instance is transitioned out of the pooled state. In this case, the ejbactivate() is called to first associate the bean instance with a primary key, then followed by a call to ejbload() to synchronize the state of the entity bean with the state in the database. 4
5 Client business method EJB container in Borland Enterprise Server PK=2 PK=8 PK=5 Cached without state Pooled state As indicated by the figure above, once the entity bean in the transaction ready state executes the business method(s), the container calls the ejbstore() and sends the bean back to the cache. It is possible that the bean instance enters the pooled state after ejbstore() is called by calling ejbpassivate(): this would happen if there already existed an entity in the cache for the given primary key. Figure 8: Option B client invokes business method In the preceding figure, assume that the cache of the EJB container holds three instances of an entity bean, each with its own primary key (the entity bean instances only know their primary keys). Assume that there are a number of bean instances in the pooled state; these instances are not associated with any primary key. Option A Option A provides optimized data access in cases where the EJB container has exclusive access to the database or where the underlying data is either read only, or insert only. In other words, this option provides optimized data access in cases where existing rows in the database are not modified (though new ones could be inserted over time). The following sequences of events occur in the EJB container of Borland Enterprise Server when a client invokes a business method on an Option B entity bean: Does the entity bean referenced by the client exist in the cache? ejbload() Yes, so get it out of the cache CACHED WITHOUT STATE execute business method(s) ejbstore() ejbactivate() ejbpassivate() No, so get any instance out of the pool In this case, the container uses a cache to hold the beans associated with a primary key. However, when Option A is used, the entity beans are also associated with the state in the database. In other words, the entity bean instance not only holds the primary key field but also the values for all its persisted fields. The handling of Option A by the Borland Enterprise Server is very similar to the handling of entity beans using Option B. As with Option B, when a client invokes a business method, the EJB container first looks in the cache. If the entity bean instance matching that primary key identity is found, the instance is taken out from the cache and used. It should be noted that if the cache does contain the required entity bean instance, then a call to the ejbload() can be avoided because the state of the bean is known to be consistent with the state from the last committed transaction. If the entity bean instance cannot be found in the cache, then the EJB container gets an instance from the pool and calls the ejbload() to load the state from the database. Figure 9: Option B handling request internally by the container. 5
6 Client business method EJB container in Borland Enterprise Server PK=2 PK=8 PK=5 Cached with state Figure 10: Option A client invokes business method. Pooled state In the figure above, the cache contains three entity bean instances. These instances are associated with their primary key and with their state in the database. The pooled state contains entity bean instances that are not associated with any particular primary key. The following sequences of events occur in the EJB container of Borland Enterprise Server when a client invokes a business method on an Option A entity bean: Does the entity bean referenced by the client exist in the cache? Yes, so get it out of the cache No, so get any instance out of the pool Combining the facts that (a) Option A can suppress reads from the database (when that instance is present in the cache), and (b) the difference detection engine in the Borland implementation for CMP eliminates writes to the database (i.e., eliminates updates in the ejbstore() method) when no fields were modified, demonstrates how our product provides entity bean support with no database access. In other words, a pure middle-tier data cache! Putting Option A beans back into the cache can be a bit tricky. The Borland Enterprise Server uses a first out, last in algorithm the first transaction that wants to use the bean instance gets it from the cache. If a subsequent transaction(s) requests the same bean instance from the cache, we get a cache miss because the first transaction has already removed the bean instance from the cache. The cache miss implies that a bean instance has to be retrieved from the pool, then is followed by a call to ejbactivate() (to associate the instance with its primary key) and more importantly an ejbload(). That is, only the first transaction needing a particular bean can avoid an ejbload(). Concurrent transactions must get that bean from the database. execute business method(s) Step 1: ejbactivate() Step 2: ejbload() Figure 11: Option A handling request internally by the container. Subsequently, the last transaction to complete successfully puts the bean back in the cache. The implementation of Transaction Commit Option A by Borland provides the benefits of exclusive database access without the need to serialize entity bean access. Serializing entity bean access implies that a single entity bean instance (in the ready state) services client requests in a serial manner. As mentioned in the beginning of this paper, this is not a scalable option. 6 The following figure shows how the EJB container handles Option A entity beans accessed by concurrent transactions, labeled T1 and T2. The contents of the cache and the state of the entity bean are shown. Also illustrated is the way the last transaction to complete successfully puts the state associated with that entity bean instance back in the cache.
7 T1 get bean: 2 modify state (x) to z commit transaction T2 get bean: 2 not found, get from DB modify state (x) to y commit transaction Cache empty Figure 12: Option A writing back to the cache from multiple transactions. bean state (in cache) State = x State = y State = z The EJB 1.1 and 2.0 specifications actually suggest that Option A can only be used by serializing access to a single entity bean instance. The fact that the Borland Enterprise Server, AppServer Edition provides concurrent access to Option A beans (i.e. without the need for serializing access) correctly is cool! So far we have discussed only the settings in the EJB container of the AppServer Edition to limit the number of bean instances in the pooled state or cached state. As we have discussed, the EJB specification mentions the three states possible for an entity bean. The last state, the ready state, is split into two: cached state and transactional state. So, in effect, there are four states possible from our perspective: 7 Does not exist Pooled Cached (may be with or without state, i.e., with state when Option A is used and without state when Option B is used) Transactional state In the following section, we discuss an interesting feature of entity bean support that limits the number of entity bean instances in a transaction. The ejb.maxbeansinpools and the ejb.maxbeansincache properties control the pooled state and cached state, as mentioned above. The flag ejb.maxbeansintransactions governs the number of bean instances possible in the transactional state. Typically, you would use this flag when you run a batch-style operation, such as if you were running through a large number of entity beans in a single transaction. For reasons of performance and isolation, you might want to run such batch-style operations in a single transaction. Until now, we have seen cases where beans were returned to the cache or pool only upon transaction completion. The most common concern when running batch transactions that access a large number of entity beans is the resource usage in terms of memory increasing substantially. The property ejb.maxbeansintransactions controls the number of entity bean instances in the transactional state that are actually allocated to active transactions. The default size is 500, which is half the default size of the bean instances in the pool/cache. So if the default sizes of the pool/cache were changed, then the ejb.maxbeansintransactions value should probably be adjusted accordingly. The way this property works is as follows: when a transaction accesses an entity bean, the entity bean instance is usually allocated to that given transaction. However, before the entity bean instance is allocated to that transaction, a check is made to see whether the number of entity bean instances in the transactional state exceeds the
8 ejb.maxbeansintransactions value. If so, then other beans in the current transaction are moved to the cache/pool by calling ejbstore() or ejbpassivate(), depending on the commit option selected. In effect, the ejbstore() or ejbpassivate() is not called at the end of a transaction but rather when the number of entity bean instances exceeds the limit set by the ejb.maxbeansintransactions property. As the following figure shows, the elements that are light in color represent the number of beans in the cached state (the default limit is 1000). The elements within the smaller window, in a darker shade, represent the number of bean instances in the transactional state. The number of bean instances in the transactional state (the size of the smaller window) is governed by the ejb.maxbeansintransactions property. In effect, the EJB container dynamically slides the window of active beans as well as the window of cached beans across the total items in the data set. For example, your session façade could initiate a transaction and call an entity bean s finder method that returned 100,000 rows. The session bean would then iterate through the finder collection, get the data from the entity bean, put these in some kind of a data structure, and return them to the client. Instead of instantiating 100,000 objects (as many vendors do) the EJB container instantiates only 500 objects (or whatever the size of the ejb.maxbeansintransactions is set to be) and caches a subset of the total rows (the subset has a default of 1000 instances associated with the primary key, not the state). Instances are moved from the transaction state to the cached state, based on the Least Recently Used (LRU) algorithm. Large-scale performance tests have shown that this implementation provides a good space/time tradeoff. The strategy is extremely effective at keeping batch-style operations running in a controlled amount of memory without impacting the performance of other types of transactions that do not exceed their transactional limits. Total rows (e.g. result of a finder method) Bean instances in transactional state Bean instances in cached state. "window" size governed by ejb.maxbeansintransactions value "window" size governed by ejb.maxbeansincache value Figure 13: Use of ejb.maxbeansintransactions property. In the CMP 1.1 engineof Borland Enterprise Server, we read all the results from the JDBC ResultSet at one time. That is, if there were 100,000 records, we would read all 100,000 records from the ResultSet immediately, but only instantiate as many entity bean instances as there are set by the ejb.maxbeansinpool property. In the 5.x version of Borland Enterprise Server, which supports the EJB 2.0 specification, we lazy-load from the ResultSet also. That is, we do not scroll through the ResultSet returned by a SQL query when the finder executes. Rather, we scroll through the ResultSet as and when the caller requests more items. 8
9 Conclusion So, what should you do to optimize your application? The first question is to determine whether your EJB container can use Option A. The answer would be based on whether it is possible to have exclusive access to the database or whether certain tables (or beans) are either read only or insert only. The next consideration is to determine which kinds of memory constraints you might have in your deployment environment. If your deployment environment provides only a small amount of memory, you might want to reduce the size of the cache and pool, likewise reducing the number of beans in transactions. Option C will consume less memory than Option B due to the fact there is only a pool and no cache. Note that caches are effective only if there is a high likelihood of a cache hit (i.e., an item can be found in the cache). So, if your application exhibits locality of reference as do most real world applications, then Option B is preferable to Option C. Benchmarking clients typically access entities at random, in which case Option C might be preferred. And, of course, if you have batch operations, you might want to consider the impact of ejb.maxbeansintrasanctions property. The Java ECperf benchmarking exercise conducted on the AppServer Edition has demonstrated that the default entity bean configuration in the EJB container of Borland Enterprise Server is quite effective. Borland used the default configuration for all entity beans in the ECperf test and found excellent results. We did try changing a number of variables, including trying Option C instead of Option B (Option A is disallowed by ECperf run rules), and varying the pool/cache sizes. In all cases, we found that such changes either hurt performance or had no measurable impact. So, unless there are significant memory constraints or unless Option A can be used, it is recommended that the default configuration be used as a starting point for performance optimization. 100 Enterprise Way Scotts Valley, CA Made in Borland Copyright 2002 Borland Software Corporation. All rights reserved. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other marks are the property of their respective owners. Corporate Headquarters: 100 Enterprise Way, Scotts Valley, CA Offices in: Australia, Brazil, Canada, China, Czech Republic, France, Germany, Hong Kong, Hungary, India, Ireland, Italy, Japan, Korea, the Netherlands, New Zealand, Russia, Singapore, Spain, Sweden, Taiwan, the United Kingdom, and the United States
Integrating CaliberRM with Mercury TestDirector
Integrating CaliberRM with Mercury TestDirector A Borland White Paper By Jenny Rogers, CaliberRM Technical Writer January 2002 Contents Introduction... 3 Setting Up the Integration... 3 Enabling the Integration
More informationStarTeamMPX Server. Publish/Subscribe Technology for StarTeam. By the Development Resources Platform Team. March, A Borland White Paper
Publish/Subscribe Technology for StarTeam A Borland White Paper By the Development Resources Platform Team March, 2003 Contents ebusiness Challenges... 3 /Server Challenges... 3 The StarTeam Solution...
More informationEnterprise JavaBeans. Layer:07. Entity
Enterprise JavaBeans Layer:07 Entity Agenda Build entity beans. Describe the bean's lifecycle. Describe the server's free pool. Copyright (C) 2001 2 Entity Beans Purpose Entity beans represent business
More informationStored Procedures and UDFs with Borland JDataStore
Stored Procedures and UDFs with Borland JDataStore Increase application capability and get encapsulation of business logic by Jens Ole Lauridsen Borland Software Corporation August 2002 Contents Introduction
More informationTOPLink for WebLogic. Whitepaper. The Challenge: The Solution:
Whitepaper The Challenge: Enterprise JavaBeans (EJB) represents a new standard in enterprise computing: a component-based architecture for developing and deploying distributed object-oriented applications
More informationJBuilder. Getting Started Guide part II. Preface. Creating your Second Enterprise JavaBean. Container Managed Persistent Bean.
Getting Started Guide part II Creating your Second Enterprise JavaBean Container Managed Persistent Bean by Gerard van der Pol and Michael Faisst, Borland Preface Introduction This document provides an
More informationA Look at Borland C#Builder from the Delphi Developers View
A Look at Borland C#Builder from the Delphi Developers View A Borland White Paper August 2003 By Corbin Dunn, Research and Development Engineer, Borland Software Corporation Contents Introduction... 3
More informationUsing the Transaction Service
15 CHAPTER 15 Using the Transaction Service The Java EE platform provides several abstractions that simplify development of dependable transaction processing for applications. This chapter discusses Java
More informationEnterprise JavaBeans: BMP and CMP Entity Beans
CIS 386 Course Advanced Enterprise Java Programming Enterprise JavaBeans: BMP and CMP Entity Beans René Doursat Guest Lecturer Golden Gate University, San Francisco February 2003 EJB Trail Session Beans
More informationImproving Data Access of J2EE Applications by Exploiting Asynchronous Messaging and Caching Services
Darmstadt University of Technology Databases & Distributed Systems Group Improving Data Access of J2EE Applications by Exploiting Asynchronous Messaging and Caching Services Samuel Kounev and Alex Buchmann
More informationEnterprise JavaBeans. Layer:08. Persistence
Enterprise JavaBeans Layer:08 Persistence Agenda Discuss "finder" methods. Describe DataSource resources. Describe bean-managed persistence. Describe container-managed persistence. Last Revised: 11/1/2001
More informationJBuilder. JBuilder 6 features and benefits. Developer productivity Support for the latest Java standards
Developer productivity Support for the latest Java standards High-productivity development environment Advanced, state-of-the-art JBuilder AppBrowser IDE Develop Java applications with no proprietary code
More informationPerformance Tuning EJB -based Applications
Performance Tuning EJB -based Applications Optimizing Enterprise JavaBeans applications A Borland White Paper By Borland Enterprise Server team January 2003 Contents Introduction... 3 The application...
More informationUNIT-III EJB APPLICATIONS
UNIT-III EJB APPLICATIONS CONTENTS EJB Session Beans EJB entity beans EJB clients EJB Deployment Building an application with EJB. EJB Types Types of Enterprise Beans Session beans: Also called business
More informationPower Analyzer Firmware Update Utility Version Software Release Notes
Power Analyzer Firmware Update Utility Version 3.1.0 Software Release Notes Contents General Information... 2... 2 Supported models... 2 Minimum system requirements... 2 Installation instructions... 2
More informationENHANCED INTERIOR GATEWAY ROUTING PROTOCOL STUB ROUTER FUNCTIONALITY
APPLICATION NOTE ENHANCED INTERIOR GATEWAY ROUTING PROTOCOL STUB ROUTER FUNCTIONALITY OVERVIEW Enhanced Interior Gateway Routing Protocol (EIGRP).Stub Router functionality, which Cisco introduced in Cisco
More informationUnderstanding and Designing with EJB
Understanding and Designing with EJB B.Ramamurthy Based on j2eetutorial documentation. http://java.sun.com/j2ee/tutorial/1_3-fcs/index.html 3/31/2003 1 Review Request/Response Model Distributed Objects:
More informationWeb Services Designer puts you in control.use the new Web Services designer to visually create, validate, import, and export Web Services.
General Questions What is Borland JBuilder? Borland JBuilder accelerates your Java development with the leading next-generation, cross-platform environment for building industrial-strength enterprise Java
More informationBorland InterBase and MySQL
Borland InterBase and MySQL A technical comparison A Borland White Paper By Bill Todd, The Database Group March 2004 Contents Executive summary... 3 Introduction... 3 Choosing the right database for your
More informationSCBCD EXAM STUDY KIT. Paul Sanghera CX JAVA BUSINESS COMPONENT DEVELOPER CERTIFICATION FOR EJB MANNING. Covers all you need to pass
CX-310-090 SCBCD EXAM STUDY KIT JAVA BUSINESS COMPONENT DEVELOPER CERTIFICATION FOR EJB Covers all you need to pass Includes free download of a simulated exam You will use it even after passing the exam
More informationEntity Beans 02/24/2004
Entity Beans 1 This session is about Entity beans. Understanding entity beans is very important. Yet, entity bean is a lot more complex beast than a session bean since it involves backend database. So
More informationIt Is a Difficult Question! The Goal of This Study. Specification. The Goal of This Study. History. Existing Benchmarks
It Is a Difficult Question! J2EE and.net Reloaded Yet Another Performance Case Study The Middleware Company Case Study Team Presented by Mark Grechanik How to compare two functionally rich platforms? Benchmarks?
More informationInnovative Fastening Technologies
Innovative Fastening Technologies Corporate Overview 2011 Update Infastech is one of the world s largest producers of engineered mechanical fasteners with revenues exceeding USD500 million and an industry
More informationLab2: CMP Entity Bean working with Session Bean
Session Bean The session bean in the Lab1 uses JDBC connection to retrieve conference information from the backend database directly. The Lab2 extends the application in Lab1 and adds an new entity bean
More informationTopexam. 一番権威的な IT 認定試験ウェブサイト 最も新たな国際 IT 認定試験問題集
Topexam 一番権威的な IT 認定試験ウェブサイト http://www.topexam.jp 最も新たな国際 IT 認定試験問題集 Exam : 1D0-442 Title : CIW EnterprISE SPECIALIST Vendors : CIW Version : DEMO Get Latest & Valid 1D0-442 Exam's Question and Answers
More informationTraffic Offload. Cisco 7200/Cisco 7500 APPLICATION NOTE
APPLICATION NOTE Cisco 700/Cisco 700 Traffic offload allows exchange carriers to offload their telephony traffic to a packet network from the Public Switched Telephone Network (PSTN). By doing so, carriers
More informationClient/Server-Architecture
Client/Server-Architecture Content Client/Server Beginnings 2-Tier, 3-Tier, and N-Tier Architectures Communication between Tiers The Power of Distributed Objects Managing Distributed Systems The State
More informationCisco Aironet In-Building Wireless Solutions International Power Compliance Chart
Cisco Aironet In-Building Wireless Solutions International Power Compliance Chart ADDITIONAL INFORMATION It is important to Cisco Systems that its resellers comply with and recognize all applicable regulations
More informationOracle9iAS TopLink. 1 TopLink CMP for BEA WebLogic Server. 1.1 EJB 2.0 Support. CMP-Specific Release Notes
Oracle9iAS TopLink CMP-Specific Release Notes Release 2 (9.0.3) August 2002 Part No. B10161-01 These release notes include information on using Oracle9iAS TopLink Release 2 (9.0.3) with the following CMPs:
More informationSupports 1-1, 1-many, and many to many relationships between objects
Author: Bill Ennis TOPLink provides container-managed persistence for BEA Weblogic. It has been available for Weblogic's application server since Weblogic version 4.5.1 released in December, 1999. TOPLink
More informationConception of Information Systems Lecture 8: J2EE and EJBs
Conception of Information Systems Lecture 8: J2EE and EJBs 3 May 2005 http://lsirwww.epfl.ch/courses/cis/2005ss/ 2004-2005, Karl Aberer & J.P. Martin-Flatin 1 1 Outline Components J2EE and Enterprise Java
More informationMulti-tier architecture performance analysis. Papers covered
Multi-tier architecture performance analysis Papers covered Emmanuel Cecchet, Julie Marguerie, Willy Zwaenepoel: Performance and Scalability of EJB Applications. OOPSLA 02 Yan Liu, Alan Fekete, Ian Gorton:
More informationEJB ENTERPRISE JAVA BEANS INTRODUCTION TO ENTERPRISE JAVA BEANS, JAVA'S SERVER SIDE COMPONENT TECHNOLOGY. EJB Enterprise Java
EJB Enterprise Java EJB Beans ENTERPRISE JAVA BEANS INTRODUCTION TO ENTERPRISE JAVA BEANS, JAVA'S SERVER SIDE COMPONENT TECHNOLOGY Peter R. Egli 1/23 Contents 1. What is a bean? 2. Why EJB? 3. Evolution
More informationthese methods, remote clients can access the inventory services provided by the application.
666 ENTERPRISE BEANS 18 Enterprise Beans problems. The EJB container not the bean developer is responsible for system-level services such as transaction management and security authorization. Second, because
More informationENTERPRISE beans are the J2EE components that implement Enterprise Java-
18 Enterprise Beans ENTERPRISE beans are the J2EE components that implement Enterprise Java- Beans (EJB) technology. Enterprise beans run in the EJB container, a runtime environment within the J2EE server
More informationIBM. Enterprise Application Development with IBM Web Sphere Studio, V5.0
IBM 000-287 Enterprise Application Development with IBM Web Sphere Studio, V5.0 Download Full Version : http://killexams.com/pass4sure/exam-detail/000-287 QUESTION: 90 Which of the following statements
More informationEND-OF-SALE AND END-OF-LIFE ANNOUNCEMENT FOR THE CISCO MEDIA CONVERGENCE SERVER 7845H-2400
END-OF-LIFE NOTICE, NO. 2566 END-OF-SALE AND END-OF-LIFE ANNOUNCEMENT FOR THE CISCO MEDIA CONVERGENCE SERVER 7845H-2400 Cisco Systems announces the end of life of the Cisco Media Convergence Server 7845H-2400.
More informationCisco Extensible Provisioning and Operations Manager 4.5
Data Sheet Cisco Extensible Provisioning and Operations Manager 4.5 Cisco Extensible Provisioning and Operations Manager (EPOM) is a Web-based application for real-time provisioning of the Cisco BTS 10200
More informationTesting JDBC Applications Using DataDirect Test for JDBC
Testing JDBC Applications Using DataDirect Test for JDBC Introduction As a major designer of the JDBC specification, DataDirect Technologies has used its expertise to develop the first Pure Java JDBC testing
More informationThe Developer s Guide to Understanding Enterprise JavaBeans. Nova Laboratories
The Developer s Guide to Understanding Enterprise JavaBeans Nova Laboratories www.nova-labs.com For more information about Nova Laboratories or the Developer Kitchen Series, or to add your name to our
More informationIntroducing Borland Delphi 8
Introducing Borland Delphi 8 for the Microsoft.NET Framework A product overview A Borland White Paper January 2004 Contents Introduction... 3 Windows development today... 4 The Microsoft.NET Framework...
More informationU85026A Detector 40 to 60 GHz
Operating and Service Manual U85026A Detector 40 to 60 GHz Serial Numbers This manual applies directly to U85026A detectors with serial numbers 100 and above. For additional information on serial numbers,
More informationCisco Voice Services Provisioning Tool 2.6(1)
Data Sheet Cisco Voice Services Provisioning Tool 2.6(1) The Cisco Voice Services Provisioning Tool (VSPT) provides a GUI for the creation, modification, and execution of signaling connections, trunks,
More informationGlobal entertainment and media outlook Explore the content and tools
www.pwc.com/outlook Global entertainment and media outlook Explore the content and tools A comprehensive online source of global analysis for consumer/ end-user and advertising spending 5-year forecasts
More informationImplementing a Web Service p. 110 Implementing a Web Service Client p. 114 Summary p. 117 Introduction to Entity Beans p. 119 Persistence Concepts p.
Acknowledgments p. xvi Introduction p. xvii Overview p. 1 Overview p. 3 The Motivation for Enterprise JavaBeans p. 4 Component Architectures p. 7 Divide and Conquer to the Extreme with Reusable Services
More informationJ2EE Access of Relational Data
J2EE Access of Relational Data Direct JDBC Direct SQL calls, uses rows and result sets directly Object view Accessed as objects or components, transparent that the data is stored in relational database
More informationOverview. ❶ Short introduction to the company. ❶ Short history of database and DBMS. ❶ What is the next DBMS s generation? ❶ Introduction to Tamino
❶ The XML Company Overview ❶ Short introduction to the company ❶ Short history of database and DBMS ❶ What is the next DBMS s generation? ❶ Introduction to Tamino Enterprise Transaction Suite High-Performance
More informationProgramming Note. Agilent Technologies Quick Reference Guide For the 8757D/E Scalar Network Analyzer
Programming Note Agilent Technologies Quick Reference Guide For the 8757D/E Scalar Network Analyzer Manufacturing Part Number: 08757-90130 Printed in USA Print Date: July 1992 Agilent Technologies, Inc.
More informationEnterprise JavaBeans (I) K.P. Chow University of Hong Kong
Enterprise JavaBeans (I) K.P. Chow University of Hong Kong JavaBeans Components are self contained, reusable software units that can be visually composed into composite components using visual builder
More informationE-Seminar. Voice over IP. Internet Technical Solution Seminar
E-Seminar Voice over IP Internet Technical Solution Seminar Voice over IP Internet Technical Solution Seminar 3 Welcome 4 Objectives 5 Telephony in Business 6 VoIP and IP Telephony 7 Traditional Telephony
More informationChapter 6 Object Persistence, Relationships and Queries
Prof. Dr.-Ing. Stefan Deßloch AG Heterogene Informationssysteme Geb. 36, Raum 329 Tel. 0631/205 3275 dessloch@informatik.uni-kl.de Chapter 6 Object Persistence, Relationships and Queries Object Persistence
More informationJ2EE Application Server. EJB Overview. Java versus.net for the Enterprise. Component-Based Software Engineering. ECE493-Topic 5 Winter 2007
Component-Based Software Engineering ECE493-Topic 5 Winter 2007 Lecture 24 Java Enterprise (Part B) Ladan Tahvildari Assistant Professor Dept. of Elect. & Comp. Eng. University of Waterloo J2EE Application
More informationEfficient Object-Relational Mapping for JAVA and J2EE Applications or the impact of J2EE on RDB. Marc Stampfli Oracle Software (Switzerland) Ltd.
Efficient Object-Relational Mapping for JAVA and J2EE Applications or the impact of J2EE on RDB Marc Stampfli Oracle Software (Switzerland) Ltd. Underestimation According to customers about 20-50% percent
More informationPRODUCT DATA. Reporting Module Type 7832
PRODUCT DATA Reporting Module Type 7832 Reporting Module Type 7832 provides dedicated Data Management and Reporting for Brüel & Kjær Noise Monitoring Systems. It has never been easier to create great looking
More informationEnterprise JavaBeans Benchmarking 1
Enterprise JavaBeans Benchmarking 1 Marek Procházka, Petr T ma, Radek Pospíšil Charles University Faculty of Mathematics and Physics Department of Software Engineering Czech Republic {prochazka, tuma,
More informationAppendix A - Glossary(of OO software term s)
Appendix A - Glossary(of OO software term s) Abstract Class A class that does not supply an implementation for its entire interface, and so consequently, cannot be instantiated. ActiveX Microsoft s component
More informationServer Virtualisation Assessment. Service Overview
Server Virtualisation Assessment Service Overview Our Server Virtualisation Assessment helps organisations reduce server total cost of ownership and make informed decisions around capacity planning by
More informationEnterprise Java Beans
Enterprise Java Beans Objectives Three Tiered Architecture Why EJB? What all we should know? EJB Fundamentals 2 Three Tiered Architecture Introduction Distributed three-tier design is needed for Increased
More informationApplication Servers G Session 11 - Sub-Topic 2 Using Enterprise JavaBeans. Dr. Jean-Claude Franchitti
Application Servers G22.3033-011 Session 11 - Sub-Topic 2 Using Enterprise JavaBeans Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences
More informationSafety. Introduction
KickStart Guide Safety Introduction Safety precautions Before using this product, see the safety precautions associated with your instrument. The instrumentation associated with this software is intended
More informationPurchasing. Operations 3% Marketing 3% HR. Production 1%
Agenda Item DOC ID IAF CMC (11) 75 For Information For discussion For decision For comments to the author IAF End User Survey results (October 211) This report summarises the total responses to the IAF
More informationConfiguring DHCP for ShoreTel IP Phones
Configuring DHCP for ShoreTel IP Phones Network Requirements and Preparation 3 Configuring DHCP for ShoreTel IP Phones The ShoreTel server provides the latest application software and configuration information
More informationN2753A and N2754A Windows XP to Windows 7 Upgrade Kits. For Infiniium 9000, 90000, and X-Series Oscilloscopes
N2753A and N2754A Windows XP to Windows 7 Upgrade Kits For Infiniium 9000, 90000, and 90000 X-Series Oscilloscopes All new Infiniium 9000, 90000, and 90000-X oscilloscopes now ship standard with Microsoft
More informationCISCO IP PHONE 7970G NEW! CISCO IP PHONE 7905G AND 7912G XML
Q & A CISCO IP PHONE 7970G NEW! CISCO IP PHONE 7905G AND 7912G XML GENERAL QUESTIONS Q. What is the Cisco IP Phone 7970G? A. The 7970G is our latest state-of-the-art IP phone, which includes a large color,
More informationCisco CallManager 4.0-PBX Interoperability: Lucent/Avaya Definity G3 MV1.3 PBX using 6608-T1 PRI NI2 with MGCP
Application Note Cisco CallManager 4.0-PBX Interoperability: Lucent/Avaya Definity G3 MV1.3 PBX using 6608-T1 PRI NI2 with MGCP Introduction This is an application note for connectivity of Lucent/Avaya
More informationBorland Application Server Certification. Study Guide. Version 1.0 Copyright 2001 Borland Software Corporation. All Rights Reserved.
Borland Application Server Certification Study Guide Version 1.0 Copyright 2001 Borland Software Corporation. All Rights Reserved. Introduction This study guide is designed to walk you through requisite
More informationStep 1: New Portal User User ID Created Using IdentityIQ (IIQ)
Rockwell Automation PartnerNetwork Portal Single Sign-on (SSO) Login to Rockwell Automation PartnerNewtork Portal for Commercial Programs Participants Scope: This job aid provides instructions on how to
More informationCisco 2651XM Gateway - PBX Interoperability: Avaya Definity G3 PBX using Analog FXO Interfaces to an H.323 Gateway
Application Note Cisco 2651XM Gateway - PBX Interoperability: Avaya Definity G3 PBX using Analog FXO Interfaces to an H.323 Gateway Introduction This note describes the interoperability between the Avaya
More informationTraining Notes Unity Real Time 2
Training Notes Unity Real Time 2 For Customers Using SPC (Westgard) Rules Log on to Unity Real Time 2 1 Double-click the Unity Real Time 2 shortcut located on your computer desktop. 2 Select your user
More informationaddendum Uptime Cisco customer interactive solutions
addendum Uptime Cisco customer interactive solutions What makes Uptime tick? Uptime is made up of a number of service elements, which all work together to minimise downtime and assure business continuity.
More informationMANUAL VOICE/DATA SIMCARD CANADA
MANUAL VOICE/DATA SIMCARD CANADA Copyright 2018. All rights reserved. The content of this document may not be copied,replaced,distributed,published,displayed, modified,or transferred in any form or by
More informationSupplier Responding to New Products RFP Event
This presentation contains instructions focused on the required steps needed for suppliers to respond to a RFP request made from the New Products group. For more general information on how to respond to
More informationStrategic IT Plan Improves NYCHA Resident Services While Reducing Costs US$150 Million
C U S T O M E R C A S E S T U D Y Strategic IT Plan Improves NYCHA Resident Services While Reducing Costs US$150 Million Executive Summary CUSTOMER NAME New York City Housing Authority (NYCHA) INDUSTRY
More informationMulti-Site Parallel Testing with the S535 Wafer Acceptance Test System APPLICATION NOTE
Multi-Site Parallel Testing with the S535 Wafer Acceptance Test System In semiconductor wafer production, minimizing the cost of test has been identified as the number one challenge. The biggest factor
More informationOn Performance of Enterprise JavaBeans
On Performance of Enterprise JavaBeans Radek Pospíšil, Marek Procházka, Vladimír Mencl 1 Abstract Enterprise JavaBeans (EJB) is a new-sprung technology for Java-based distributed software components. During
More informationTHE POWER OF A STRONG PARTNERSHIP.
THE POWER OF A STRONG PARTNERSHIP. Now you can harness a network of resources. Connections, knowledge, and expertise. All focused on your success. The Cisco Channel Partner Program. BE CONNECTED. Great
More informationUpgrading Luminex IS 2.3 to Bio-Plex Manager 6.1 Software. For technical support, call your local Bio-Rad office, or in the US, call
Upgrading Luminex IS 2.3 to Bio-Plex Manager 6.1 Software For technical support, call your local Bio-Rad office, or in the US, call 1-800-424-6723. Bio-Rad Laboratories, Inc., 2000 Alfred Nobel Drive,
More informationBEA WebLogic. Server. Programming WebLogic Enterprise JavaBeans
BEA WebLogic Server Programming WebLogic Enterprise JavaBeans Release 7.0 Document Revised: February 18, 2005 Copyright Copyright 2005 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This
More informationINTERDIGITAL. 4 th Quarter 2013 Investor Presentation. invention collaboration contribution InterDigital, Inc. All rights reserved.
INTERDIGITAL 4 th Quarter 2013 Investor Presentation invention collaboration contribution 1 2013 InterDigital, Inc. All rights reserved. Forward-Looking Statements 2 2013 InterDigital, Inc. All rights
More informationeconsent Landscape Assessment: 2016
e Landscape Assessment: 2016 e Landscape Assessment: Overview The intention of the e Landscape Assessment is to share the collected, aggregated, and blinded survey data on global experience with e. The
More information<<Interface>> EntityBean (from ejb) EJBHome. <<Interface>> CountHome. (from entity) create() findbyprimarykey() <<Interface>> EJBObject.
Count BMP Entity EJB Count BMP Entity EJB EJBHome (from ejb) EntityBean (from ejb) CountClient main() CountHome create() findbyprimarykey() EJBObject (from ejb) Count getcurrentsum() setcurrentsum() increment()
More informationTroubleshooting Ethernet Problems with Your Oscilloscope APPLICATION NOTE
Troubleshooting Ethernet Problems with Your Oscilloscope Introduction Ethernet is a family of frame-based computer networking technologies for local area networks (LANs), initially developed at Xerox PARC
More informationAllianz SE Reinsurance Branch Asia Pacific Systems Requirements & Developments. Dr. Lutz Füllgraf
Allianz SE Reinsurance Branch Asia Pacific Systems Requirements & Developments Dr. Lutz Füllgraf Technology and Innovation for Insurance Conference 2007, Sydney 22 March 2007 Contents 1 Importance of a
More informationEventBuilder.com. International Audio Conferencing Access Guide. This guide contains: :: International Toll-Free Access Dialing Instructions
EventBuilder.com International Audio Conferencing Access Guide TM This guide contains: :: International Toll-Free Access Dialing Instructions :: ATFS (Access Toll-Free Service) Dialing Instructions ::
More informationHybrid Wide-Area Network Application-centric, agile and end-to-end
Hybrid Wide-Area Network Application-centric, agile and end-to-end How do you close the gap between the demands on your network and your capabilities? Wide-area networks, by their nature, connect geographically
More information[ PARADIGM SCIENTIFIC SEARCH ] A POWERFUL SOLUTION for Enterprise-Wide Scientific Information Access
A POWERFUL SOLUTION for Enterprise-Wide Scientific Information Access ENABLING EASY ACCESS TO Enterprise-Wide Scientific Information Waters Paradigm Scientific Search Software enables fast, easy, high
More informationCustomers want to transform their datacenter 80% 28% global IT budgets spent on maintenance. time spent on administrative tasks
Customers want to transform their datacenter 80% global IT budgets spent on maintenance 28% time spent on administrative tasks Cloud is a new way to think about your datacenter Traditional model Dedicated
More informationVOICE/DATA SIMCARD USA UNLIMITED
VOICE/DATA SIMCARD USA UNLIMITED Copyright 2018. All rights reserved. The content of this document may not be copied,replaced,distributed,published,displayed, modified,or transferred in any form or by
More informationAC : EXPLORATION OF JAVA PERSISTENCE
AC 2007-1400: EXPLORATION OF JAVA PERSISTENCE Robert E. Broadbent, Brigham Young University Michael Bailey, Brigham Young University Joseph Ekstrom, Brigham Young University Scott Hart, Brigham Young University
More informationQuintiles vdesk Welcome Guide
Quintiles vdesk Welcome Guide Dear Quintiles Clinical ASP User, Quintiles is pleased to announce vdesk, an unique solution part of the Clinical ASP platform offer. Quintiles vdesk, is a virtual desktop
More informationFast 3D EMC/EMI Scan with Detectus Scanning System and Tektronix Real Time Spectrum Analyzers CASE STUDY
Fast 3D EMC/EMI Scan with Detectus Scanning System and Tektronix Real Time Spectrum Analyzers Fast 3D EMC/EMI Scan with Detectus Scanning System and Tektronix Real Time Spectrum Analyzers Customer Solution
More informationOracle 10g: Build J2EE Applications
Oracle University Contact Us: (09) 5494 1551 Oracle 10g: Build J2EE Applications Duration: 5 Days What you will learn Leading companies are tackling the complexity of their application and IT environments
More informationTektronix Logic Analyzer Probes P5900 Series Datasheet
Tektronix Logic Analyzer Probes P5900 Series Datasheet Applications Digital hardware validation and debug Monitoring, measurement, and optimization of digital hardware performance Embedded software integration,
More informationCisco ONS SDH 12-Port STM-1 Electrical Interface Card
Data Sheet Cisco ONS 15454 SDH 12-Port STM-1 Electrical Interface Card The Cisco ONS 15454 SDH 12-Port STM-1 Electrical Interface Card (STM-1E) provides a cost-effective, high-speed electrical interface
More informationDigital Opportunity Index. Michael Minges Telecommunications Management Group, Inc.
Digital Opportunity Index Michael Minges Telecommunications Management Group, Inc. Digital Opportunity Index (DOI) Why How Preliminary results Conclusions WSIS Plan of Action E. Follow-up and evaluation
More informationHL7: Version 2 Standard
HL7: Version 2 Standard John Quinn (HL7 CTO) HIMSS 2010 Agenda HL7 Version 2.0 2.5.1 History & Use Basic Tenets Elements & Structures HL7 Version 2.6 October 2007 HL7 Version 2.7 How we got here HL7 Version
More informationNAVIGATING TECHNOLOGY CHOICES FOR SAS DATA ACCESS FROM MULTI-TIERED WEB APPLICATIONS
NAVIGATING TECHNOLOGY CHOICES FOR SAS DATA ACCESS FROM MULTI-TIERED WEB APPLICATIONS Ricardo Cisternas, MGC Data Services, Carlsbad, CA Miriam Cisternas, MGC Data Services, Carlsbad, CA ABSTRACT There
More informationiclass SE multiclass SE 125kHz, 13.56MHz 125kHz, 13.56MHz
Date created: 11 July 2016 Last update: 18 August 2016 READERS REGULATORY CERTIFICATION BY COUNTRY. The following table consists of the current regulatory certifications for the readers. HID Global is
More informationNetBeans IDE Field Guide
NetBeans IDE Field Guide Copyright 2005 Sun Microsystems, Inc. All rights reserved. Table of Contents Extending Web Applications with Business Logic: Introducing EJB Components...1 EJB Project type Wizards...2
More informationMicrosoft Dynamics 365 for Finance and Operations. Table of contents
Microsoft Dynamics 365 for Finance and Operations Product localization and translation availability guide April 2018 update 1 Dynamics 365 for Finance and Operations Product localization and translation
More information