|
|
|
|
|
|
Creating CORBA C++ Server Applications
This document describes how programmers can implement key features in the BEA WebLogic EnterpriseTM (WLE) product to design and implement scalable, high-performance, C++ server applications that run in a WebLogic Enterprise domain. The C++ examples shown in this book are based on the sample applications described in the Guide to the University Sample Applications.
This document is intended for programmers who are interested in creating secure, scalable, transaction-based server applications. It assumes your are knowledgeable with the BEA Tuxedo® system, CORBA, and C++ programming.
The Entities You Create to Build a WebLogic Enterprise Server Application
The Implementation of the CORBA Objects for Your Server Application
How Interface Definitions Establish the Operations on a CORBA Object
How You Implement the Operations on a CORBA Object
How Client Applications Access and Manipulate Your Application's CORBA Objects
How You Instantiate a CORBA Object at Run Time
Process for Developing WebLogic Enterprise Server Applications
How Client Applications Find Your Server Application's Factories
Creating an Active Object Reference
Application-controlled Deactivation
Reading and Writing an Object's Data
Available Mechanisms for Reading and Writing an Object's Durable State
Reading State at Object Activation
Reading State Within Individual Operations on an Object
Stateless Objects and Durable State
Stateful Objects and Durable State
Your Responsibilities for Object Deactivation
List-Enumerator Design Pattern
Steps for Creating a WebLogic Enterprise Server Application
Summary of the WebLogic Enterprise Server Application Development Process
Step 1: Compile the OMG IDL File for the Server Application
Generating the Skeleton and Implementation Files
Step 2: Write the Methods That Implement Each Interface's Operations
The Implementation File Generated by the IDL Compiler
Step 3: Create the Server Object
Initializing the Server Application
Writing the Code That Creates and Registers a Factory
Releasing the Server Application
Step 4: Define the In-memory Behavior of Objects
Specifying Object Activation and Transaction Policies in the ICF File
Step 5: Compile and Link the Server Application
Step 6: Deploy the Server Application
Development and Debugging Tips
Use of CORBA and M3 Exceptions and the User Log
Client Application View of Exceptions
Server Application View of Exceptions
Detecting Error Conditions in the Callback Methods
Common Pitfalls of OMG IDL Interface Versioning and Modification
Caveat for State Handling in Tobj_ServantBase::deactivate_object()
How You Implement Servant Pooling
Delegation-based Interface Implementation
About Tie Classes in the WebLogic Enterprise System
How to Create Tie Classes in a WebLogic Enterprise Application
Designing and Implementing a Basic WebLogic Enterprise Server Application
How the Basic University Sample Application Works
The Basic University Sample Application OMG IDL
Design Considerations for the University Server Application
Design Considerations for Generating Object References
Design Considerations for Managing Object State
The CourseSynopsisEnumerator Object
Basic University Sample Application ICF File
Design Considerations for Handling Durable State Information
The CourseSynopsisEnumerator Object
How the Basic Sample Application Applies Design Patterns
List-Enumerator Design Pattern
Additional Performance Efficiencies Built into the WebLogic Enterprise System
Preactivating an Object with State
How You Preactivate an Object with State
Usage Notes for Preactivated Objects
Security and WebLogic Enterprise Server Applications
Overview of Security and WebLogic Enterprise Server Applications
Design Considerations for the University Server Application
How the Security University Sample Application Works
Design Considerations for Returning Student Details to the Client Application
Integrating Transactions into a WebLogic Enterprise Server Application
Overview of Transactions in the WebLogic Enterprise System
Designing and Implementing Transactions in a WebLogic Enterprise Server Application
How the Transactions University Sample Application Works
Transactional Model Used by the Transactions University Sample Application
Object State Considerations for the University Server Application
Object Policies Defined for the Registrar Object
Object Policies Defined for the RegistrarFactory Object
Using an XA Resource Manager in the Transactions Sample Application
Configuration Requirements for the Transactions Sample Application
Integrating Transactions in a WebLogic Enterprise Client and Server Application
Making an Object Automatically Transactional
Enabling an Object to Participate in a Transaction
Preventing an Object from Being Invoked While a Transaction Is Scoped
Excluding an Object from an Ongoing Transaction
Opening an XA Resource Manager
Closing an XA Resource Manager
Transactions and Object State Management
Delegating Object State Management to an XA Resource Manager
Waiting Until Transaction Work Is Complete Before Writing to the Database
Notes on Using Transactions in the WebLogic Enterprise System
Wrapping a BEA Tuxedo Service in an Object
Overview of Wrapping a BEA Tuxedo Service
Designing the Object That Wraps the BEA Tuxedo Service
Creating the Buffer in Which to Encapsulate BEA Tuxedo Service Calls
Implementing the Operations That Send Messages to and from the BEA Tuxedo Service
Design Considerations for the Wrapper Sample Application
How the Wrapper University Sample Application Works
Interface Definitions for the Billing Server Application
Additional Design Considerations for the Wrapper Sample Application
Scaling a WebLogic Enterprise Server Application
Overview of the Scalability Features Available in the WebLogic Enterprise System
Scaling a WebLogic Enterprise Server Application
OMG IDL Changes for the Production Sample Application
Replicating Server Processes and Server Groups
Configuring Replicated Server Processes and Groups
Scaling the Application Via Object State Management
How Factory-based Routing Works
Configuring for Factory-based Routing in the UBBCONFIG file
Implementing Factory-based Routing in a Factory
Additional Design Considerations for the Registrar and Teller Objects
Instantiating the Registrar and Teller Objects
Ensuring That Student Registration Occurs in the Correct Server Group
Ensuring That the Teller Object is Instantiated in the Correct Server Group
How the Production Server Application Can Be Scaled Further
Choosing Between Stateless and Stateful Objects
When You Want Stateless Objects
When You Want Stateful Objects
|
|
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|