Guide to CORBA University Sample Applications

Introduction

This topic describes the University sample applications provided for the CORBA environment in the BEA Tuxedo product. The sample applications provide client and server programmers with the basic concepts of developing distributed client/server applications using the CORBA environment and introduces many of the more advanced CORBA features of the BEA Tuxedo product.

This topic includes the following sections:

Notes: The BEA Tuxedo CORBA Java client and BEA Tuxedo CORBA Java client ORB were deprecated in Tuxedo 8.1 and are no longer supported. All BEA Tuxedo CORBA Java client and BEA Tuxedo CORBA Java client ORB text references, associated code samples, should only be used to help implement/run third party Java ORB libraries, and for programmer reference only.

Technical support for third party CORBA Java ORBs should be provided by their respective vendors. BEA Tuxedo does not provide any technical support or documentation for third party CORBA Java ORBs.

An Overview of the University Sample Applications

The BEA Tuxedo software kit includes a CORBA sample application suite based on client and server applications implemented at a university. Each University sample application demonstrates a new set of CORBA features while building on the experience obtained from the previous examples. The University sample applications are intentionally simplified to demonstrate only the steps and processes associated with using a particular CORBA feature of the BEA Tuxedo product.

Table 1-1 describes the University sample applications.

Table 1-1 The University Sample Applications

University Sample Application	Description
Basic	Describes how to create CORBA client and server applications, configure a CORBA application, and build and run the client and server applications included in the Basic sample application. CORBA C++ client applications are provided as well as a CORBA C++ server application.
Security	Adds application-level security to the CORBA client applications in the Basic sample application and to the configuration of the CORBA application.
Transactions	Adds transactional objects to the CORBA client and server applications in the Basic sample application. The Transactions sample application demonstrates how to use the Implementation Configuration File (ICF) to define transaction policies for CORBA objects.
Wrapper	Demonstrates how to wrap an ATMI application as a CORBA object.
Production	Demonstrates replicating CORBA server applications, creating stateless CORBA objects, and implementing factory-based routing in CORBA server applications.

Use the University sample applications in conjunction with the following manuals:

Getting Started with BEA Tuxedo CORBA Applications

Naming Conventions Used in the University Sample Applications

The naming conventions listed and described in Table 1-2 are used in the code of the University sample applications.

Table 1-2 Naming Conventions Used in the University Sample Applications

Convention	Description
`crs`	The abbreviation for course.
`syn`	The abbreviation for synopsis.
`det`	The abbreviation for details.
`lst`	The abbreviation for list.
`enum`	The abbreviation for enumerator.
`stu`	The abbreviation for student.
`num`	The abbreviation for number.
`cur`	The abbreviation for current.
`_oref`	A `CORBA::Object` reference.
`_ref`	A typed object reference.
`p_`	The abbreviation for ptr.
`v_`	The abbreviation for var.
`s_`	The abbreviation for file static data.
`m_`	The abbreviation for class member data.
Method names and variable names	Use all lowercase letters for the name and underscores to separate words within the method name (for example, `m_v_crs_syn_list` is member data that is a var holding a course synopsis list).
Type names	Start with an uppercase letter and use an uppercase letter to separate words with a type name. Type names do not use abbreviations. An example of a type name is `UniversityB::CourseSynopsisEnumerator_var`.