Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
WebLogic Enterprise Doc Home   |   Sample Applications   |   Previous Topic   |   Next Topic   |   Contents   |   Index

This topic describes the University sample applications provided with the WebLogic Enterprise software. The sample applications provide client and server programmers with the basic concepts of developing distributed client/server applications using the WebLogic Enterprise software and introduces many of the more advanced features of the WebLogic Enterprise product.

This topic includes the following sections:

• An Overview of the University Sample Applications

• Naming Conventions Used in the University Sample Applications

The WebLogic Enterprise software includes a sample application suite based on client and server applications implemented at a university. Each University sample application demonstrates a new set of WebLogic Enterprise 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 feature of the WebLogic Enterprise 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 WebLogic Enterprise client and server applications, configure the WebLogic Enterprise application, and build and run the client and server applications included in the Basic sample application. CORBA C++, CORBA Java, and ActiveX client applications are provided as well as a C++ server application.
Security	Adds application-level security to the client applications in the Basic sample application and to the configuration of the WebLogic Enterprise application.
Transactions	Adds transactional objects to the 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 existing BEA Tuxedo application as a CORBA object.
Production	Demonstrates replicating server applications, creating stateless objects, and implementing factory-based routing in server applications.

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

• Getting Started

• Creating Client Applications

• Creating C++ Server 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.