Oracle® TopLink Examples EJB 2.0 CMP — Advanced Features Example

This example demonstrates how to use the advanced features of TopLink EJB 2.0 container-managed persistence (CMP) entity beans on Oracle Containers for J2EE.

The Java client accesses multiple instances of TopLink-enabled persistent EJB types. The EJBs are stored in a database which is accessed through the server connection facilities. The example demonstrates how to:

Configuration Requirements

Before you build and run the example, follow the minimum configuration requirements for your environment in Configuring the Examples.

Building and Running the Example

Use the following commands to build the example, reset the database, start the server and run the example:

To build the deployable JAR file, execute the build file. For Windows, select the build.cmd file. For UNIX, select the build.sh file. The build file invokes the build.xml ANT script, which retrieves supporting properties from the env.properties file and builds the example.
Ensure the database is running.
To reset database tables for this example, execute the resetDatabase file. For Windows, select the resetDatabase.cmd file. For UNIX, select the resetDatabase.sh file.
Start the OC4J server. When you start the server, set the system property toplink.log.level to "FINE" to turn on logging. For example, java -Dtoplink.log.level="FINE" -jar oc4j.jar.
To deploy the EAR file after server startup, execute the deploy file. For Windows, select the deploy.cmd file. For UNIX, select the deploy.sh file.
To start the client program, execute the runClient file. For Windows, select the runClient.cmd file. For UNIX, select the runClient.sh file

Note:

If you are using Internet Explorer and you change something in the file system, select View > Refresh before double clicking a *.cmd file in the Windows (filesystem) Explorer that IE provided. The *.cmd file will then execute correctly.

Example Files and Directories

Table: Files and Directories Used in this Example lists the supporting directories (and their contents) provided in this example.

Files and Directories Used in this Example

Directory	Contents
config	This directory contains configuration files used by TopLink, including: `toplink-ejb-jar.xml`: the TopLink metadata. The remaining files are J2EE and application server-specific files.
jsp	This directory contains the Java Server Page (JSP) files used in this example.
mw	This directory contains the TopLink Workbench project and supporting files for this example.
src	This directory contains all the supporting `.java` source files for the example. The `.java` files are stored in their respective package hierarchy.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.