Oracle® TopLink Examples |
Enterprise Information System (EIS) - Session Broker Example
10g Release 3 (10.1.3)
January 2006
This example demonstrates how to use TopLink Session Broker to integrate data from both an Enterprise Information System (EIS)/XML data store and a relational database into a single object model. It uses TopLink to access a relational database through JDBC and it uses TopLink EIS/XML to access integrated XML data through the Attunity Connect JDBC driver.
This example uses the OrderSys example bundled with the Attunity Connect, version 3.5. Each time an Order is created, the example logs a record of the order transaction in the relational database. As a result, the user searches for transactions as opposed to placed orders.
The example demonstrates how to:
Place an Order
Search for a Transaction
View an Order
Before you build and run the example, you must:
Follow the minimum configuration requirements for your environment in Configuring the Examples.
|
Note: This example requires a database. It runs from both an XML data store created as part of the demo and a relational database.Oracle does not recommend running this example with a Sybase database |
Download a free evaluation copy of Attunity Connect, version 3.5 from: http://www.attunity.com/products/ApplicationConnect.Asp.
Select the "Download" link.
Fill in the registration information.
Choose your platform.
Download the Attunity kit.
Install Attunity Connect.
Accept the option to run the server by default.
Accept the option to create the demo data source.
Wait for the Attunity Connect Evaluation License e-mail.
After you receive the Attunity Connect Evaluation License e-mail, save it as license.txt. Use the nav_util application in the <ATTUNITY_HOME>/bin directory to register the license as follows: nav_util register license.txt.
Follow the instructions in the <ATTUNITY_HOME>/Connect/Samples/Adapters/Ordersys/readme.txt file and configure the OrderSys adapter.
Follow the instructions in the readme.txt file to ensure that the adapter is functioning properly.
Start and stop the Attunity server. Refer to the Attunity Connect documentation for details.
Extract the <ATTUNITY_HOME>/Connect/Java/attunityResourceAdapter.zip file into the <ATTUNITY_HOME>/Connect/Java directory.
To ensure the Attunity server and adapter function properly, enter run ordersample from the <ATTUNITY_HOME>/Connect/Java/Samples directory.
Copy the <ATTUNITY_HOME>/Connect/Java/lib/attunityResourceAdapter.jar to the <OC4J_INSTALL>/toplink/jlib directory.
If the server is installed on a different computer than the example or if you are using different settings, modify the following constants in the sessions.xml file:
Set serverName property to the URL of the machine where the Attunity server is running (default: localhost).
Set portNumber property to the port number on which Attunity server listens for connections (default: 2551).
Do not change the eisName property. It must remain the name of the demo Attunity adapter.
Use the following commands to build the example, reset the database, start the server and run the example:
Ensure the Attunity Connect server is running. Refer to the Attunity Connect documentation for details.
To build the deployable EAR 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.
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.
Double click the startClient.htm file or start a browser and point it to http://localhost:8888/sessionbean_eis_sessionbroker/mainPage.jsp.
|
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. |
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 |
|---|---|
|
This directory contains configuration files used by TopLink, including.
The remaining files are J2EE and application server-specific files. |
|
|
This directory contains the Java Server Page (JSP) files used in this example. |
|
|
This directory contains the TopLink Workbench project and supporting files for this example. |
|
|
This directory contains all the supporting |
Oracle TopLink Examples, 10g Release 3 (10.1.3)
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.