Sun Microsystems Network Card JDBC ODBC Adapter User Manual

SUN SEEBEYOND

eWAY™ JDBC/ODBC ADAPTER

USER’S GUIDE

Release 5.1.2

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

Chapter 1

Introducing the JDBC/ODBC eWay

About Java Database Connectivity (JDBC)

JDBC Drivers

Type I: JDBC-ODBC Bridge

Type One Driver

Type II: Partial Java driver

Type Two Driver

Pure Java driver for database middleware

Type Three Driver

Type Four Driver: Direct-to-database pure Java driver

About the JDBC/ODBC eWay

What’s New in This Release

Related Documents

The following Sun documents provide additional information about the Sun Java

Composite Application Platform Suite product:

ƒ Sun SeeBeyond eGate™ Integrator User’s Guide

ƒ Sun Java Composite Application Platform Suite Installation Guide

1.6

Sun Microsystems, Inc. Web Site

The Sun Microsystems web site is your best source for up-to-the-minute product news

and technical support information. The site’s URL is:

http://ww w .sun.com

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 1

Introducing the JDBC/ODBC eWay

Section 1.7

Documentation Feedback

1.7

Documentation Feedback

We appreciate your feedback. Please send any comments or suggestions regarding this

document to:

[email protected]

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 2

Installing the JDBC/ODBC eWay

This chapter describes how to install the JDBC/ODBC eWay.

What’s in this Chapter

ƒ Installing the JDBC eWay on page 17

ƒ ICAN 5.0 Project Migration Procedures on page 19

ƒ Installing Enterprise Manager eWay Plug-Ins on page 21

2.1

Installing the JDBC eWay

The Java Composite Application Platform Suite Installer, referred to throughout this

guide as the Suite Installer, is a web-based application that is used to select and upload

core products, composite applications, and add-on files (eWays) during the installation

process. The following section describes how to install the components required for this

eWay.

Refer to the readme for the latest information on:

ƒ Supported Operating Systems

ƒ System Requirements

ƒ External System Requirements

The JDBC eWay Readme is uploaded with the eWay’s documentation file

(JDBCeWayDocs.sar) and can be accessed from the Documentation tab of the Suite

Installer.

Note: When the Repository is running on a UNIX operating system, the eWays are loaded

from the Suite Installer running on a Windows platform connected to the

Repository server using Internet Explorer.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 2

Installing the JDBC/ODBC eWay

Section 2.1

Installing the JDBC eWay

2.1.1 Installing the JDBC eWay on an eGate supported system

Follow the directions for installing the Sun Java Composite Application Platform Suite

in the Sun Java Composite Application Platform Suite Installation Guide. After you have

installed Core Products, do the following:

1 From the Sun Java Composite Application Platform Suite Installer’s Select Sun

Java Composite Application Platform Suite Products Installed table

(Administration tab), click the Click to install additional products link.

2 Expand the eWay option.

3 Select the products for your Sun Java Composite Application Platform Suite and

include the following:

Š File eWay (the File eWay is used by most sample Projects)

Š JDBCeWay

To upload the JDBC eWay User’s Guide, Help file, Javadoc, Readme, and sample

Projects, expand the Documentation option and select JDBCeWayDocs.

4 Once you have selected all of your products, click Next in the top-right or bottom-

right corner of the Select Sun Java Composite Application Platform Suite

Products to Install box.

5 From the Selecting Files to Install box, locate and select your first product’s SAR

file. Once you have selected the SAR file, click Next. Your next selected product

appears. Follow this procedure for each of your selected products. The Installation

Status window appears and installation begins after the last SAR file has been

selected.

6 Once your product’s installation is finished, continue installing the Sun Java

Composite Application Platform Suite as instructed in the Sun Java Composite

Application Platform Suite Installation Guide.

Adding the eWay to an Existing Sun Java Composite Application

Platform Suite Installation

If you are adding the eWay to an existing Sun Java Composite Application Platform

Suite installation, do the following:

1 Complete steps 1 through 4 above.

2 Once your product’s installation is complete, open the Enterprise Designer and

select Update Center from the Tools menu. The Update Center Wizard appears.

3 For Step 1 of the wizard, simply click Next.

4 For Step 2 of the wizard, click the Add All button to move all installable files to the

Include in Install field, then click Next.

5 For Step 3 of the wizard, wait for the modules to download, then click Next.

6 The wizard’s Step 4 window displays the installed modules. Review the installed

modules and click Finish.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 2

Installing the JDBC/ODBC eWay

Section 2.2

ICAN 5.0 Project Migration Procedures

7 When prompted, restart the IDE (Integrated Development Environment) to

complete the installation.

After Installation

Once you install the eWay, it must then be incorporated into a Project before it can

perform its intended functions. See the eGate Integrator User’s Guide for more

information on incorporating the eWay into an eGate Project.

2.1.2 Extracting the Sample Projects and Javadocs

The JDBC eWay includes sample Projects and Javadocs. The sample Projects are

designed to provide you with a basic understanding of how certain database

operations are performed using the eWay, while Javadocs provide a list of classes and

methods exposed in the eWay.

Steps to extract the Javadoc include:

1 Click the Documentation tab of the Sun Java Composite Application Platform Suite

Installer, then click the Add-ons tab.

2 Click the JDBC eWay Adapter link. Documentation for the JDBC eWay appears in

the right pane.

3 Click the icon next to Javadoc and extract the ZIP file.

4 Open the index.html file to view the Javadoc.

Steps to extract the Sample Projects include:

1 Click the Documentation tab of the Sun Java Composite Application Platform Suite

Installer, then click the Add-ons tab.

2 Click the JDBC eWay Adapter link. Documentation for the JDBC eWay appears in

the right pane.

3 Click the icon next to Sample Projects and extract the ZIP file. Note that the

JDBC_eWay_Sample.zip file contains two additional ZIP files for each sample

Project.

Refer to “Importing a Sample Project” on page 73 for instructions on importing the

sample Project into your repository via the Enterprise Designer.

2.2

ICAN 5.0 Project Migration Procedures

This section describes how to transfer your current ICAN 5.0.x Projects to the Sun Java

Composite Application Platform Suite 5.1.2. To migrate your ICAN 5.0.x Projects to the

Sun Java Composite Application Platform Suite 5.1.2, do the following:

Export the Project

1 Before you export your Projects, save your current ICAN 5.0.x Projects to your

Repository.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 2

Installing the JDBC/ODBC eWay

Section 2.2

ICAN 5.0 Project Migration Procedures

2 From the Project Explorer, right-click your Project and select Export from the

shortcut menu. The Export Manager appears.

3 Select the Project that you want to export in the left pane of the Export Manager and

move it to the Selected Projects field by clicking the Add to Select Items (arrow)

button, or click All to include all of your Projects.

4 In the same manner, select the Environment that you want to export in the left pane

of the Export Manager and move it to the Selected Environments field by clicking

the Add to Select Items (arrow) button, or click All to include all of your

Environments.

5 Browse to select a destination for your Project ZIP file and enter a name for your

Project in the ZIP file field.

6 Click Export to create the Project ZIP file in the selected destination.

Install Java CAPS 5.1.2

1 Install Java CAPS 5.1.2, including all eWays, libraries, and other components used

by your ICAN 5.0 Projects.

2 Start the Java CAPS 5.1.2 Enterprise Designer.

Import the Project

1 From the Java CAPS 5.1.2 Enterprise Designer’s Project Explorer tree, right-click the

Repository and select Import Project from the shortcut menu. The Import Manager

appears.

2 Browse to and select your exported Project file.

3 Click Import. A warning message, “Missing APIs from Target Repository,” may

appear at this time. This occurs because various product APIs were installed on the

ICAN 5.0 Repository when the Project was created that are not installed on the Java

CAPS 5.1.2 Repository. These APIs may or may not apply to your Projects. You can

ignore this message if you have already installed all of the components that

correspond to your Projects. Click Continue to resume the Project import.

4 Close the Import Manager after the Project is successfully imported.

Deploy the Project

1 A new Deployment Profile must be created for each of your imported Projects.

When a Project is exported, the Project’s components are automatically “checked in”

to Version Control to write-protected each component. These protected components

appear in the Explorer tree with a red padlock in the bottom-left corner of each icon.

Before you can deploy the imported Project, the Project’s components must first be

“checked out” of Version Control from both the Project Explorer and the

Environment Explorer. To “check out” all of the Project’s components, do the

following:

A From the Project Explorer, right-click the Project and select Version Control >

Check Out from the shortcut menu. The Version Control - Check Out dialog box

appears.

B Select Recurse Project to specify all components, and click OK.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 2

Installing the JDBC/ODBC eWay

Section 2.3

Installing Enterprise Manager eWay Plug-Ins

C Select the Environment Explorer tab, and from the Environment Explorer, right-

click the Project’s Environment and select Version Control > Check Out from

the shortcut menu.

D Select Recurse Environment to specify all components, and click OK.

2 If your imported Project includes File eWays, these must be reconfigured in your

Environment prior to deploying the Project.

To reconfigure your File eWays, do the following:

A From the Environment Explorer tree, right-click the File External System, and

select Properties from the shortcut menu. The Properties Editor appears.

B Set the inbound and outbound directory values, and click OK. The File External

System can now accommodate both inbound and outbound eWays.

3 Deploy your Projects.

Note: Only projects developed on ICAN 5.0.2 and later can be imported and migrated

successfully into the Sun Java Composite Application Platform Suite.

2.3

Installing Enterprise Manager eWay Plug-Ins

The Sun SeeBeyond Enterprise Manager is a Web-based interface you use to monitor

and manage your Sun Java Composite Application Platform Suite applications. The

Enterprise Manager requires an eWay specific “plug-in” for each eWay you install.

These plug-ins enable the Enterprise Manager to target specific alert codes for each

eWay type, as well as start and stop the inbound eWays.

The Sun Java Composite Application Platform Suite Installation Guide describes how to

install Enterprise Manager. The Sun SeeBeyond eGate Integrator System Administration

Guide describes how to monitor servers, Services, logs, and alerts using the Enterprise

Manager and the command-line client.

The eWay Enterprise Manager Plug-ins are available from the List of Components to

Download under the Sun Java Composite Application Platform Suite Installer’s

Downloads tab.

There are two ways to add eWay Enterprise Manager plug-ins:

ƒ From the Sun SeeBeyond Enterprise Manager

ƒ From the Sun Java Composite Application Platform Suite Installer

To add plug-ins from the Enterprise Manager

1 From the Enterprise Manager’s Explorer toolbar, click configuration.

2 Click the Web Applications Manager tab, go to the Auto-Install from Repository

sub-tab, and connect to your Repository.

3 Select the application plug-ins you require, and click Install. The application plug-

ins are installed and deployed.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 2

Installing the JDBC/ODBC eWay

Section 2.3

Installing Enterprise Manager eWay Plug-Ins

To add plug-ins from the Sun Java Composite Application Platform Suite Installer

1 From the Sun Java Composite Application Platform Suite Installer’s Downloads

tab, select the Plug-Ins you require and save them to a temporary directory.

2 From the Enterprise Manager’s Explorer toolbar, click configuration.

3 Click the Web Applications Manager tab and go to the Manage Applications sub-

tab.

4 Browse for and select the WAR file for the application plug-in that you

downloaded, and click Deploy. The plug-ins is installed and deployed.

2.3.1 Viewing Alert Codes

You can view and delete alerts using the Enterprise Manager. An alert is triggered

when a specified condition occurs in a Project component. The purpose of the alert is to

warn the administrator or user that a condition has occurred.

To View the eWay Alert Codes

1 Add the eWay Enterprise Manager plug-in for this eWay.

2 From the Enterprise Manager’s Explorer toolbar, click configuration.

3 Click the Web Applications Manager tab and go to the Manage Alert Codes sub-

tab. Your installed eWay alert codes display under the Results section. If your eWay

alert codes are not displayed under Results, do the following:

A From the Install New Alert Codes section, browse to and select the eWay alert

properties file for the application plug-in that you added. The alert properties

files are located in the alertcodes folder of your Sun Java Composite Application

Platform Suite installation directory.

B Click Deploy. The available alert codes for your application are displayed under

Results. A listing of the eWay’s available alert codes is displayed in T a ble 2.

Table 2 Alert Codes for the JDBC/ODBC eWay

Alert Code\Description

Description Details

User Actions

DBCOMMON-CONNECT-

Occurs during the

initial database

connection

ƒ Database is down; start your

database.

ƒ External configuration information

is invalid. You may need to verify

the following:

FAILED000001=Failed to connect

to database {0} on host {1}.

Reason: The Pooled connection

could not be allocated: [{2}]

establishment.

Œ Server name

Œ Database name

Œ User

Œ Password

Œ Port

DBCOMMON-CONNECT-

FAILED000002=Operation failed

because of a database

Occurs while

retrieving a

connection from the

database or the

connection pool.

ƒ Verify that the database has not

terminated with unexpected

errors.

connection error. Reason: [{0}]

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 2

Installing the JDBC/ODBC eWay

Section 2.3

Installing Enterprise Manager eWay Plug-Ins

Alert Code\Description

Description Details

User Actions

DBCOMMON-CONNECT-

FAILED000005=Connection

handle not usable. Reason:[{0}]

The connection in the ƒ Probably a database restart

pool is stale and is not

usable.

occurred causing the connection

to be stale, retry the operation

after the database is up.

DBCOMMON-XARESOURCE-

FAILED000001=Unable to get

XAResource for the database.

Reason: [{0}]

Could not obtain

XAResource for the

connection.

ƒ Check if the database supports XA

and has been configured for

Distributed Transaction Support.

DBCOMMON-XACONNECT-

FAILED000001=Failed to connect

to database {0} on host {1}. The

XA connection could not be

allocated: Reason [{2}]

Occurs during the

initial database

connection

ƒ Check if the database is

configured for XA and if the

database is running.

ƒ External configuration information

is invalid. You may need to verify

the following:

establishment.

Œ Server name

Œ Database name

Œ User

Œ Password

Œ Port

DBCOMMON-XASTART-

FAILED000001=Unable to

perform XAStart for the

connection. Reason: [{0}]

A connection error

has occurred which

caused XASTART to

fail.

ƒ Check if the database is running,

and there are no network issues.

DBCOMMON-XAEND-

FAILED000001=XAEnd failed.

Reason: [{0}]

Error occurred during

commit on XA

connection.

ƒ Look for the detailed error

mentioned in the alert for the

appropriate action.

DBCOMMON-CANNOT-GET-

ISOLATION-LEVEL=Unable to

get isolationLevel for the

Could not read

transaction isolation

information of the

connection.

ƒ Transaction isolation is one of the

following constants:

Œ Connection.TRANSACTION_REA

D_UNCOMMITTED

transaction. Reason: [{0}]

Œ Connection.TRANSACTION_REA

D_COMMITTED

Œ Connection.TRANSACTION_REPE

ATABLE_READ

Œ Connection.TRANSACTION_SERI

ALIZABLE

Œ Connection.TRANSACTION_NO

Note: Confirm with the

vendor that the getIsolation()

method of the connection is

implemented correctly.

For information on Managing and Monitoring alert codes and logs, as well as how to

view the alert generated by the project component during runtime, see the Sun

SeeBeyond eGate™ Integrator System Administration Guide.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 2

Installing the JDBC/ODBC eWay

Section 2.3

Installing Enterprise Manager eWay Plug-Ins

Note: An alert code is a warning that an error has occurred. It is not a diagnostic. The user

actions noted above are just some possible corrective measures you may take. Refer

to the log files for more information. For information on Managing and Monitoring

alert codes and logs, see the Sun SeeBeyond eGate Integrator System

Administration Guide.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Setting Properties of the JDBC/ODBC eWay

This chapter describes how to set the properties of the JDBC/ODBC eWay.

What’s In This Chapter

ƒ Creating and Configuring a JDBC eWay on page 25

ƒ Configuring the eWay Connectivity Map Properties on page 25

ƒ Configuring the eWay Environment Properties on page 29

ƒ eWay Connectivity Map Properties on page 30

ƒ eWay Environment Properties on page 31

3.1

Creating and Configuring a JDBC eWay

All eWays contain a unique set of default configuration parameters. After the eWays are

established and a JDBC External System is created in the Project’s Environment, the

eWay parameters are modified for your specific system. The JDBC eWay configuration

parameters are modified from two locations:

ƒ Connectivity Map: These parameters most commonly apply to a specific

component eWay, and may vary from other eWays (of the same type) in the Project.

ƒ Environment Explorer : These parameters are commonly global, applying to all

eWays (of the same type) in the Project. The saved properties are shared by all

eWays in the JDBC External System window.

ƒ Collaboration or Business Process: JDBC eWay properties may also be set from

your Collaboration or Business Process, in which case the settings will override the

corresponding properties in the eWay’s Connectivity Map configuration. Any

properties that are not overridden retain their configured default settings.

3.2

Configuring the eWay Connectivity Map Properties

When you connect an External Application to a Collaboration, Enterprise Designer

automatically assigns the appropriate eWay to the link. Each eWay is supplied with a

list of eWay connections (transaction support levels) from which to choose.

Transaction support levels provided by the JDBC eWay include:

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.2

Setting Properties of the JDBC/ODBC eWay

Configuring the eWay Connectivity Map Properties

ƒ Outbound JDBC eWay

ƒ Outbound JDBC XA eWay

ƒ Outbound JDBC non-Transactional eWay

To configure the eWay properties:

1 On the Enterprise Designer’s Connectivity Map, double-click the JDBC eWay icon.

The eWay Connections window appears.

Figure 5 Connectivity Map with Components

JDBC eWay

2 Select a parameter from the list and click OK.

Figure 6 Template window

The choices to make are as follows:

Š Outbound JDBC non-Transactional eWay: Also referred to as NoTransaction,

this support level indicates that the Collaboration does not support transactions.

This means that when a transaction aborts, there is no ability to roll back any

changes to the previous update.

Š Outbound JDBC XA-eWay: Also referred to as XATransaction, this support

level allows two-phase commit. This means that the transaction, when aborted,

will roll back all changes when one of the updates fails. The update could occur

in the database eWay or other eWays that support XA. Additionally, the

Collaboration can contain only the database eWay, or a combination of database

eWay and other eWays that support XA.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.2

Setting Properties of the JDBC/ODBC eWay

Configuring the eWay Connectivity Map Properties

Š Outbound JDBC eWay: Also referred to as LocalTransaction, this support level

is opposite to NoTransaction, and this means that the transaction, when The

Properties window opens, displaying the default properties for the eWay.

3 The Properties window opens, displaying the default properties for the eWay.

Figure 7 Outbound eWay Properties

3.2.1 Transaction Support Levels Between Different Versions

The types of transaction support levels used in Java CAPS 5.1.0 may be different

from the support levels used in Java CAPS 5.1.2. Projects that are imported from a

Java CAPS 5.1.0 version can potentially display different results, depending on

whether the 5.1.0 Java Collaboration Definition (JCD) included multiple (insert/

update/delete) operations. This only affects non-XA transactions. If you are using

an XA transaction, then you can skip this section.

Example:

In 5.1.0, five new records are to be inserted into a table. If the last record fails to

insert (such as when a duplicate key exists), all previous records will have been

inserted. This is the behavior of NoTransaction support.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.2

Setting Properties of the JDBC/ODBC eWay

Configuring the eWay Connectivity Map Properties

In 5.1.2, five new records are to be inserted into a table. If one of the records fails to

insert (such as when a duplicate key exists), the other four records will not be

inserted. This is the behavior of the LocalTransaction.

In order to achieve the same result as in 5.1.0 versions, you can choose the method

below:

A In the Connectivity Map, delete the link to the database external application,

then reconnect the link and select NoTransaction.

B Fill in the NoTransaction property for the database external system under the

Environment.

C Rebuild the Project.

The following charts identifies what transaction support levels changed between

5.0.5 and 5.1.2, and 5.1.0 and 5.1.2, respectively. Note that there are no changes

when migrating from ICAN version 5.0.5 and Java CAPS 5.1.2.

Figure 8 Transaction Support Levels

ICAN Version 5.0.5

Java CAPS 5.1.2

Outbound Informix eWay

(LocalTransaction)

Outbound Informix eWay

(LocalTransaction)

Outbound Informix XA

eWay

Outbound Informix XA

eWay

(XATransaction)

Java CAPS 5.1.0

Java CAPS 5.1.2

Outbound Informix non-

Transaction eWay

(NoTransaction)

Outbound Informix eWay

(LocalTransaction)

Outbound Informix XA

eWay

Outbound Informix XA

eWay

(XATransaction)

Under the scenario noted above, if you want 5.1.2 behavior for a LocalTransaction,

then set your eWay connection to be Outbound JDBC/ODBC non-Transactional

eWay (NoTransaction).

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.3

Setting Properties of the JDBC/ODBC eWay

Configuring the eWay Environment Properties

3.3

Configuring the eWay Environment Properties

The eWay Environment Configuration properties contain parameters that define how

the eWay connects to and interacts with other eGate components within the

Environment. When you create a new JDBC External System, you may configure the

type of External System required.

Available External System properties include:

ƒ Inbound JDBC eWay

ƒ Outbound JDBC eWay

ƒ Outbound JDBC non-Transactional eWay

ƒ Outbound JDBC XA eWay

To Configure the Environment Properties:

1 In Enterprise Explorer, click the Environment Explorer tab.

2 Expand the Environment created for the JDBC Project and locate the JDBC External

System.

Note: For more information on creating an Environment, see the “Sun SeeBeyond eGate

Integrator Tutorial”.

3 Right-click the External System created for the JDBC Project and select Properties

from the list box. The Environment Configuration Properties window appears.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.4

eWay Connectivity Map Properties

Setting Properties of the JDBC/ODBC eWay

Figure 9 JDBC eWay Environment Configuration

4 Click on any folder to display the default configuration properties for that section.

5 Click on any property field to make it editable.

After modifying the configuration properties, click OK to save the changes.

3.4

eWay Connectivity Map Properties

The eWay Connectivity Map consists of the following properties categories.

Outbound eWay Configuration Sections Include:

ƒ Connectivity Map Outbound eWay Properties on page 31

Outbound non-Transactional eWay Configuration Settings Include:

ƒ Connectivity Map Outbound non-T r ansactional eWay Properties on page 31

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

Outbound XA eWay Configuration Settings Include:

ƒ Connectivity Map Outbound XA eWay Properties on page 31

3.4.1 Connectivity Map Outbound eWay Properties

The Outbound eWay Properties include outbound parameters used by the external

database.

Table 3 Outbound eWay—JDBC Connector Settings

Name

Description

Required Value

A valid string.

The description of the database.

3.4.2 Connectivity Map Outbound non-Transactional eWay

Properties

The Outbound non-Transactional eWay Properties include outbound parameters used

by the external database.

Table 4 Outbound non-Transactional eWay—JDBC Connector Settings

Name

Description

Required Value

Any valid string.

The description of the database.

3.4.3 Connectivity Map Outbound XA eWay Properties

The Outbound XA eWay Properties include outbound parameters used by the external

database.

Table 5 Outbound XA eWay—JDBC Connector Settings

Name

Description

Required Value

Any valid string.

The description of the database.

3.5

eWay Environment Properties

eWay External System properties must be configured from within the Environment.

Until you have successfully configured all eWays for your Java CAPS project, your

project cannot be properly executed. The following list identifies the JDBC eWay

properties. There are four eWay connection types that the JDBC/ODBC eWay

implements.

Property Categories Configured in the Logical Host Environment

ƒ Inbound JDBC eWay Properties on page 32

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

ƒ Outbound JDBC eWay Properties on page 32

ƒ Outbound non-T r ansactional JDBC eWay Properties on page 35

ƒ Outbound XA JDBC eWay Properties on page 37

3.5.1 Inbound JDBC eWay Properties

Before deploying your eWay, you will need to set the Environment properties. The

Inbound JDBC eWay includes the following configuration section:

ƒ Parameter Settings

Details for the Inbound JDBC eWay Parameter Settings are listed in T a ble 6.

Table 6 Inbound JDBC eWay—Parameter Settings

Name

Description

Required Value

A valid string.

The description of the database.

ClassName

Displays the Java class in the JDBC driver

that is used to implement the Driver

Manager interface. Change this as needed

for your driver.

A valid class name.

See JDBC/ODBC Drivers

on page 117 for some of the

popular drivers you can use

with this eWay.

URL

This is the JDBC URL required to gain

access to the database. The URL usually

starts with jdbc; followed by

<subprotocol> and ends with information

that identifies the data source, as follows:

jdbc:<driver>:<data-source-

The applicable JDBC URL.

See JDBC/ODBC Drivers

on page 117 for some of the

popular drivers you can use

with this eWay.

name>[;<attribute-name>=<attribute-

value>]

If you do not select URL in the connection

method this parameter is ignored. For

more information on the JDBC URL,

please consult the documentation of your

specific driver.

User

Specifies the user name the eWay uses to Any valid string.

connect to the database.

Password

Specifies the password used to access the Any valid string.

database.

3.5.2 Outbound JDBC eWay Properties

The Outbound JDBC eWay includes the following configuration sections:

ƒ JDBC Connector Settings

ƒ Connection Retry Settings

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

JDBC Connector Settings

Details for the JDBC Connector Settings used by the external database are detailed in

T a ble 7.

Table 7 Outbound JDBC eWay—JDBC Connector Settings

Name

Description

Required Value

Description

The description of the database.

A valid string. The configured default

is JDBC Connection Pool Datasource.

ClassName

Specifies the Java class in the JDBC

driver that is used to implement the

ConnectionPoolDataSource,

XADataSource interface. Change as

needed for your driver.

A valid class name.

For example:

com.ibm.as400.access.AS400JDBCCon

nectionPoolDataSource

See JDBC/ODBC Drivers on

page 117 for some of the popular

drivers you can use with this eWay.

ClassNamefor

OtherInterfaces

For Sun Java Composite Application

Platform Suite components such as

eTL that do not use

A valid class name.

ConnectionPoolDataSource, use this

entry to enter the name of the driver

class. This entry is not used by the

JDBC eWay.

ServerName

PortNumber

This setting specifies the host name

of the external database server.

Any valid string.

Specifies the I/O port number on

which the server is listening for

connection requests.

A valid port number.

DatabaseName

User

Specifies the name of the database

instance.

Any valid string.

Specifies the user name the eWay

uses to connect to the database.

Any valid string.

Password

Specifies the password used to

access the database.

Any valid string.

DriverProperties The Connection Pool DataSource

Set the driver properties according to

implementation may need to execute driver vendor's instruction. For

additional methods to assure a

successful run. The additional

example:

setDefTdpName#DBSQL##setWorkspa

methods will need to be identified in ce#Navigator##

the Driver Properties. You must

ensure that the driver is installed on

both the Logical Host machine and

the Enterprise Designer machine.

Delimiter

This is the delimiter character to be

used in the DriverProperties prompt.

The default is #.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

Table 7 Outbound JDBC eWay—JDBC Connector Settings (Continued)

Name

Description

Required Value

DataSource

name

Specifies the name of the

XADataSource or

The name of the XADataSource or

ConnectionPoolDataSource

implementation. This property is

Optional. In most cases, leave this box

empty.

ConnectionPoolDataSource

implementation, to which the

DataSource object delegates behind

the scenes when there is connection

pooling or distributed transaction

management being done.

MinPoolSize

Specifies the minimum number of

physical connections the pool

should keep available at all times. 0

(zero) indicates that there is no

maximum.

A valid numeric value. The default is 0.

The pool size you set depends on the

transaction volume and response

time of the application. If the pool

size is too big, you may end up with

too many connections with the

database.

MaxPoolSize

Specifies the maximum number of

physical connections the pool

should keep available at all times. 0

(zero) indicates that there is no

maximum.

A valid numeric value. The default is

10.

If the pool size is too big, you may

end up with too many connections

with the database. The pool size

depends on the transaction volume

and response time.

MaxIdleTime

Specifies the maximum number of

seconds that a physical connection

may remain unused before it is

closed. 0 (zero) indicates that there is

no limit.

A valid numeric value. The default is 0.

Connection Retry Settings

Details for the Connection Retry Settings used by the external database are detailed in

T a ble 8.

Table 8 Outbound JDBC eWay—Connection Retry Settings

Name

Description

Required Value

ConnectionRetries

Specifies the number of retries to

establish a connection upon failure

to acquire one.

A valid numeric value. The

default is 0.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

Table 8 Outbound JDBC eWay—Connection Retry Settings (Continued)

Name

Description

Required Value

ConnectionRetryInterval

Specifies the milliseconds of pause

before each attempt to reaccess the

database. This setting is used in

conjunction with the 'Connection

Retries' setting.

A valid numeric value. The

default is 1000.

For example: In the event that the

eWay cannot connect to the

Database, the eWay will try to

reconnect to the database 10 times

in 5 seconds apart when the

Connection Retries is 10 and the

Connection Retry Interval is 5000

3.5.3 Outbound non-Transactional JDBC eWay Properties

The Outbound non-Transactional JDBC eWay includes the following configuration

sections:

ƒ JDBC Connector Settings

ƒ Connection Retry Settings

JDBC Connector Settings

Details for the JDBC Connector Settings used by the external database are detailed in

T a ble 9.

Table 9 Outbound non-Transactional eWay —JDBC Connector Settings

Name

Description

Required Value

Description

The description of the database.

A valid string. The configured default

is JDBC non-Transactional Connection

Pool Datasource.

ClassName

Specifies the Java class in the JDBC

driver that is used to implement the

ConnectionPoolDataSource/

XADataSource interface. Change as

needed for your driver.

A valid class name.

For example:

com.ddtek.jdbcx.sequelink.SequeLin

kDataSource.

ClassNamefor

OtherInterfaces

For Sun Java Composite Application

Platform Suite components that do

not use ConnectionPoolDataSource,

use this entry to enter the name of

the driver class. This class will not be

used by the eWay.

A valid class name.

ServerName

This setting specifies the host name

of the external database server.

Any valid string.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

Table 9 Outbound non-Transactional eWay —JDBC Connector Settings (Continued)

Name

Description

Required Value

A valid port number.

PortNumber

Specifies the I/O port number on

which the server is listening for

connection requests.

DatabaseName

User

Specifies the name of the database

instance.

Any valid string.

Specifies the user name the eWay

uses to connect to the database.

Any valid string.

Password

Specifies the password used to

access the database.

Any valid string.

DriverProperties The Connection Pool DataSource

Set the driver properties according to

implementation may need to execute driver vendor's instruction. For

additional methods to assure a

successful run. The additional

example:

setDefTdpName#DBSQL##setWorkspa

methods will need to be identified in ce#Navigator##

the Driver Properties. You must

ensure that the driver is installed on

both the Logical Host machine and

the Enterprise Designer machine.

Delimiter

This is the delimiter character to be

used in the DriverProperties prompt.

The default is #.

DataSource

name

Specifies the name of the

XADataSource or

The name of the XADataSource or

ConnectionPoolDataSource

implementation. This property is

Optional. In most cases, leave this box

empty.

ConnectionPoolDataSource

implementation, to which the

DataSource object delegates behind

the scenes when there is connection

pooling or distributed transaction

management being done.

MinPoolSize

Specifies the maximum number of

physical connections the pool

should keep available at all times. 0

(zero) indicates that there is no

maximum.

A valid numeric value. The default is 0.

The pool size you set depends on the

transaction volume and response

time of the application. If the pool

size is too big, you may end up with

too many connections with the

database.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

Table 9 Outbound non-Transactional eWay —JDBC Connector Settings (Continued)

Name

Description

Required Value

MaxPoolSize

Specifies the maximum number of

physical connections the pool

should keep available at all times. 0

(zero) indicates that there is no

maximum.

A valid numeric value. The default is

10.

If the pool size is too big, you may

end up with too many connections

with the database. The pool size

depends on the transaction volume

and response time.

MaxIdleTime

Specifies the maximum number of

seconds that a physical connection

may remain unused before it is

closed. 0 (zero) indicates that there is

no limit.

A valid numeric value. The default is 0.

Connection Retry Settings

Details for the Connection Retry Settings used by the external database are detailed in

T a ble 10.

Table 10 Outbound non-Transactional eWay—Connection Retry Settings

Name

Description

Required Value

ConnectionRetries

Specifies the number of retries to

establish a connection upon failure

to acquire one.

A valid numeric value. The

default is 0.

ConnectionRetryInterval

Specifies the milliseconds of pause

before each attempt to reaccess the

database. This setting is used in

conjunction with the 'Connection

Retries' setting.

A valid numeric value. The

default is 1000.

For example: In the event that the

eWay cannot connect to the

Database, the eWay will try to

reconnect to the database 10 times

in 5 seconds apart when the

Connection Retries is 10 and the

Connection Retry Interval is 5000

3.5.4 Outbound XA JDBC eWay Properties

The Outbound XA JDBC eWay includes the following configuration sections:

ƒ JDBC Connector Settings

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

ƒ Connection Retry Settings

JDBC Connector Settings

Details for the JDBC Connector Settings used by the external database are detailed in

T a ble 11.

Table 11 Outbound XA JDBC eWay—JDBC Connector Settings

Name

Description

Required Value

Description

The description of the database.

A valid string. The configured default

is JDBC XA Datasource.

ClassName

Specifies the Java class in the JDBC

driver that is used to implement the

ConnectionPoolDataSource or

XADataSource interface. Change as

needed for your driver.

A valid class name.

For example:

com.attunity.jdbc.NvXADataSource

ClassNamefor

OtherInterfaces

For Sun Java Composite Application

Platform Suite components that do

not use ConnectionPoolDataSource,

use this entry to enter the name of

the driver class. This class will not be

used by the eWay.

A valid class name.

ServerName

PortNumber

This setting specifies the host name

of the external database server.

Any valid string.

Specifies the I/O port number on

which the server is listening for

connection requests.

A valid port number.

DatabaseName

User

Specifies the name of the database

instance.

Any valid string.

Specifies the user name the eWay

uses to connect to the database.

Password

Specifies the password used to

access the database.

DriverProperties The DataSource implementation may Set the driver properties according to

need to execute additional methods

to assure a successful run. The

additional methods will need to be

identified in the Driver Properties.

You must ensure that the driver is

installed on both the Logical Host

machine and the Enterprise Designer

machine.

driver vendor's instruction. For

example:

setDefTdpName#DBSQL##setWorkspa

ce#Navigator##

Delimiter

This is the delimiter character to be

used in the DriverProperties prompt.

The default is #.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

Table 11 Outbound XA JDBC eWay—JDBC Connector Settings (Continued)

Name

Description

Required Value

DataSource

name

Specifies the name of the

The name of the XADataSource

implementation. This property is

Optional. In most cases, leave this box

empty.

XADataSource implementation, to

which the DataSource object

delegates behind the scenes when

there is connection pooling or

distributed transaction management

being done.

MinPoolSize

Specifies the maximum number of

physical connections the pool

should keep available at all times. 0

(zero) indicates that there is no

maximum.

A valid numeric value. The default is 0.

The pool size you set depends on the

transaction volume and response

time of the application. If the pool

size is too big, you may end up with

too many connections with the

database.

MaxPoolSize

Specifies the maximum number of

physical connections the pool

should keep available at all times. 0

(zero) indicates that there is no

maximum.

A valid numeric value. The default is

10.

If the pool size is too big, you may

end up with too many connections

with the database. The pool size

depends on the transaction volume

and response time.

MaxIdleTime

Specifies the maximum number of

seconds that a physical connection

may remain unused before it is

closed. 0 (zero) indicates that there is

no limit.

A valid numeric value. The default is 0.

Connection Retry Settings

Details for the Connection Retry Settings used by the external database are detailed in

T a ble 12.

Table 12 Outbound XA JDBC eWay—Connection Retry Settings

Name

Description

Required Value

ConnectionRetries

Specifies the number of retries to

establish a connection upon failure

to acquire one.

A valid numeric value. The

default is 0.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 3

Section 3.5

eWay Environment Properties

Setting Properties of the JDBC/ODBC eWay

Table 12 Outbound XA JDBC eWay—Connection Retry Settings (Continued)

Name

Description

Required Value

ConnectionRetryInterval

Specifies the milliseconds of pause

before each attempt to reaccess the

database. This setting is used in

conjunction with the 'Connection

Retries' setting.

A valid numeric value. The

default is 1000.

For example: In the event that the

eWay cannot connect to the

Database, the eWay will try to

reconnect to the database 10 times

in 5 seconds apart when the

Connection Retries is 10 and the

Connection Retry Interval is 5000

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Using the JDBC/ODBC eWay Database

Wizard

This chapter describes how to use the JDBC eWay Database Wizard to build OTDs.

What’s In This Chapter:

ƒ About the Database OTD Wizard on page 41

ƒ Creating a New JDBC OTD on page 41

ƒ Steps to Edit an Existing JDBC OTD on page 56

4.1

About the Database OTD Wizard

The Database OTD Wizard generates OTDs by connecting to external data sources and

creating corresponding Object Type Definitions. The OTD Wizard can create OTDs

based on any combination of Tables and Stored Procedures or Prepared SQL

Statements.

Field nodes are added to the OTD based on the Tables in the external data source. Java

method and parameter nodes are added to provide the appropriate JDBC functionality.

For more information about the Java methods, refer to your JDBC developer’s

reference.

The OTD Wizard allows the addition and removal of columns/nodes in an OTD.

Nodes with the same name and type as existing nodes are allowed by the wizard, but

should not be created, and will result in generic code generation errors upon activation

of the OTD.

Note: Database OTDs are not messagable. For more information on messagable OTDs, see

the eGate Integrator User’s Guide.

4.2

Creating a New JDBC OTD

The following steps are required to create a new OTD for the JDBC Adapter.

ƒ Select Wizard Type on page 42

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

ƒ Connect T o D atabase on page 42

ƒ Select Database Objects on page 43

ƒ Select T a bles/Views/Aliases on page 44

ƒ Select Procedures on page 48

ƒ Add Prepared Statement on page 52

ƒ Specify the OTD Name on page 55

ƒ Review Selections on page 55

4.2.1 Select Wizard Type

Select the type of wizard required to build an OTD in the New Object Type Definition

Wizard.

Steps Required to Select the JDBC Database OTD Wizard Include:

On the Project Explorer tree, right click the Project and select New > Object Type

Definition from the shortcut menu. The Select Wizard Type page appears, displaying

the available OTD wizards. See Figure 10.

Figure 10 OTD Wizard Selection

4.2.2 Connect To Database

1 From the New Object Type Definition Wizard window, select JDBC Database and

click the Next button. The New Wizard - JDBC Database window appears.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

2 Enter the JDBC database connection information in the Connection Information

frame.

Required Database Connection Fields include:

ƒ Driver Jar Files – the location of the driver JAR file.

ƒ Driver Java Class Name – the name of the Driver Manager Class.

ƒ URL Connection String – the URL connection string for the driver.

ƒ User name – a valid JDBC database username.

ƒ Password – a password for the user name noted above.

Figure 11 Database Connection Information

4.2.3 Select Database Objects

Select the type of JDBC database objects you want included in the OTD.

Steps Required to Select Database Objects Include:

1 When selecting Database Objects, you can select any combination of Tables, Views,

Procedures, or Prepared Statements you would like to include in the OTD file.

Click Next to continue. See Figure 12.

Note: Views are read-only and are for informational purposes only.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Figure 12 Select Database Objects

4.2.4 Select Tables/Views/Aliases

Select the types of tables, views, or aliases required in the OTD.

Steps Required to Select Table/Views/Aliases Include:

1 In the Select Tables/Views/Aliases window, click Add. See Figure 13.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Figure 13 Select Tables/Views/Aliases

2 In the Add Tables window, select if your selection criteria will include table data,

view only data, both, and/or system tables.

3 From the Table/View Name drop down list, select the location of your database

table and click Search. See Figure 14.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Figure 14 Database Wizard - All Schemes

4 Select the table of choice and click OK.

The table selected is added to the Selected Tables/Views/Aliases section. See Figure 15.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Figure 15 Selected Tables/Views/Aliases window with a table selected

5 In the Selected Tables/Views/Aliases section, review the table(s) you have selected.

To make changes to the selected Table or View, click Change. If you do not wish to

make any additional changes, click Next to continue.

6 In the Table/View Columns window, you can select or deselect your table columns.

You can also change the data type for each table by highlighting the data type and

selecting a different one from the drop down list. If you would like to change any of

the tables columns, click Change. See Figure 16.

The data type is usually listed as Other when the driver cannot detect the data type.

In these situations we recommend changing the data type to one that is more

appropriate for the type of column data.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Figure 16 Table/View Columns

7 Click Advanced to change the data type, percision/length, or scale. Once you have

finished your table choices, click OK. In general, you will not need to make any

changes. See Figure 17.

Figure 17 Table/View Columns — Advanced

4.2.5 Select Procedures

Select the type of stored procedures required in your OTD.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Steps Required to Select Stored Procedures Include:

1 On the Select Procedures and specify Resultset and Parameter Information

window, click Add.

Figure 18 Select Procedures and specify Resultset and Parameter Information

2 On the Select Procedures window, enter the name of a Procedure or select a schema

from the drop down list. Click Search. Wildcard characters can also be used.

3 In the resulting Procedure Selection list box, select a Procedure. Click OK.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Figure 19 Add Procedures

4 On the Select Procedures and specify Resultset and Parameter Information

window click Edit Parameters to make any changes to the selected Procedure. See

Figure 20.

Figure 20 Procedure Parameters

5 To restore the data type, click Restore. When finished, click OK.

6 To select how you would like the OTD to generate the nodes for the Resultset click

Edit Resultsets.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

7 Click Add to add the type of Resultset node you would like to generate.

Figure 21 Edit Resultset

The DBWizard provides three different ways to generate the ResultSet nodes of a

Stored Procedure. They are "By Executing", "Manually", and "With Assistance"

modes.

By Executing Mode

“By Executing” mode executes the specified Stored

Procedure with default values to generate the

ResultSet(s). Depending on the business logic of the

Stored Procedure, zero or more ResultSets can be

returned from the execution. In the case that there are

multiple ResultSets and "By Executing" mode does not

return all ResultSets, one should use the other modes

to generate the ResultSet nodes.

With Assistance Mode

"With Assistance" mode allows users to specify a query

and execute it to generate the ResultSet node. To

facilitate this operation, the DBWizard tries to retrieve

the content of the specified Stored Procedure and

display it. However, content retrieval is not supported

by all types of Stored Procedures. We can roughly

classify Stored Procedures into two types: SQL and

external. SQL Stored Procedures are created using

CREATE PROCEDURE SQL statements while external

Stored Procedures are created using host languages

(e.g. Java). Since external Stored Procedures do not

store their execution plans in the database, content

retrieval is impossible. When using "Assist" mode,

highlight the execute statement up to and including

the table name(s) before executing the query.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Manually Mode

"Manually" mode is the most flexible way to generate

the result set nodes. It allows users to specify the node

name, original column name and data type manually.

One drawback of this method is that users need to

know the original column names and data types. This is

not always possible. For example, the column name of

3*C in this query.

SELECT A, B, 3*C FROM table T

is generated by the database. In this case, "With

Assistance" mode is a better choice.

If you modify the ResultSet generated by the “Execute”

mode of the Database Wizard you need to make sure

the indexes match the Stored Procedure. This assures

your ResultSet indexes are preserved.

8 On the Select Procedures and specify Resultset and Parameter Information

window click Next to continue.

Note: Not all drivers and databases support stored procedures or stored procedures with

ResultSets. You may contact the driver’s vendor for more information.

4.2.6 Add Prepared Statement

Add a Prepared Statement object to your OTD.

Steps Required to Add Prepared Statements Include:

Note: When using a Prepared Statement, the ‘ResultsAvailable()’ method will always

return true. Although this method is available, you should not use it with a ‘while’

loop. Doing so would result in an infinite loop at runtime and will stop all of the

system’s CPU. If it is used, it should only be used with the ‘if’ statement.

1 On the Add Prepared Statements window, click Add.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Figure 22 Prepared Statement

2 Enter the name of a Prepared Statement or create a SQL statement by clicking in the

SQL Statement window. When finished creating the statement, click Save As giving

the statement a name. This name will appear as a node in the OTD. Click OK. See

Figure 23.

Figure 23 Prepared SQL Statement

3 On the Add Prepared Statement window, the name you assigned to the Prepared

Statement appears. To edit the parameters, click Edit Parameters. You can change

the datatype by clicking in the Type field and selecting a different type from the list.

4 Click Add if you want to add additional parameters to the Statement or highlight a

row and click Remove to remove it. Click OK. Figure 24.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Figure 24 Edit the Prepared Statement Parameters

5 To edit Resultset Columns, click Edit Resultset Columns. The ResultSet Columns

window appears. See Figure 25.

Figure 25 ResultSet Columns

6 Click Add to add a new ResultSet column. Both the Name and Type are editable.

7 Click OK to return to the Add Prepared Statements window.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.2

Creating a New JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

4.2.7 Specify the OTD Name

Specify the name that your OTD will display in the Enterprise Designer Project

Explorer.

Steps Required to Specify the OTD Name:

1 Enter a name for the OTD. The OTD contains the selected tables and the package

name of the generated classes. See Figure 26.

Figure 26 Naming an OTD

2 Click Next.

4.2.8 Review Selections

Review the selections made for the new OTD.

Steps Required to Review Your OTD Selections:

1 View the summary of the OTD. If you find you have made a mistake, click Back and

correct the information.

2 If you are satisfied with the OTD information, click Finish to begin generating the

OTD. See Figure 27.

The resulting OTD appears on the Enterprise Designer’s Project Explorer.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 4

Section 4.3

Steps to Edit an Existing JDBC OTD

Using the JDBC/ODBC eWay Database Wizard

Figure 27 Database Wizard - Summary

4.3

Steps to Edit an Existing JDBC OTD

You can edit any database OTD you create directly from the Enterprise Designer Project

Explorer.

Steps to Edit the OTD from the Enterprise Designer Include:

1 Unlock the OTD. To do this, right-click the OTD in the Project Explorer and select

Version Control > Check Out from the menu.

The Version Control - Check Out window appears.

2 Select the OTD you want to check out, then click Check Out.

3 From the Project Explorer, right-click the OTD again and select Edit from the menu.

The JDBC Database Connection Information wizard appears.

4 Enter the connection information as described in “Connect T o D atabase” on

page 42, and click Next.

5 Step through each of the wizard steps and click Finish to save your changes.

Note: You must verify during project activation or at runtime that no errors are generated

after editing an OTD. Errors could occur if you delete a database object that is

included in a Collaboration.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Database operations in the JDBC eWay are used to access the JDBC database. Database

operations are either accessed through Activities in BPEL, or through methods called

from a JCD Collaboration.

What’s in This Chapter

ƒ JDBC eWay Database Operations (BPEL) on page 57

ƒ JDBC eWay Database Operations (JCD) on page 59

5.1

JDBC eWay Database Operations (BPEL)

Within a BPEL business process, the JDBC eWay uses BPEL Activities to perform basic

outbound database operations, including:

ƒ Insert

ƒ Update

ƒ Delete

ƒ SelectOne

ƒ SelectMultiple

ƒ SelectAll

In addition to these outbound operations, the JDBC eWay also employs the inbound

Activity ReceiveOne within a Prepared Statement OTD.

The ability to perform any of the above methods using a table OTD may not be possible

with all third-party drivers. You have to use a Prepared Statement to perform such an

operation. Check with the respective driver’s vendor for further information. This

feature is known as Updatable ResultSet.

5.1.1 Activity Input and Output

The Sun SeeBeyond Enterprise Designer – Business Rules Designer includes Input and

Output columns to map and transform data between Activities displayed on the

Business Process Canvas.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.1

JDBC eWay Database Operations (BPEL)

Figure 28 displays the business rules between the FileClient.write and

otdJDBC.Db_employeeDelete Activities. In this example, the whereClause appears

on the Input side.

Figure 28 Input and Output Between Activities

The following table lists the expected Input and Output of each database operation

Activity.

Table 13 JDBC.ODBC Operations

eInsight Operations

Activity Input

Activity Output

SelectAll

where() clause (optional)

Returns all rows that fit the

condition of the where()

clause.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

Table 13 JDBC.ODBC Operations (Continued)

eInsight Operations

Activity Input

number of rows

Activity Output

SelectMultiple

Returns the number of rows

specified that fit the condition

of the where() clause, and the

number of rows to be

returned.

where() clause (optional)

For example: If the number of

rows that meet the condition

are 5 and the number of

available rows are 10, then

only 5 rows will be returned.

Alternately, if the number of

rows that meet the condition

are 20, but if the number of

available rows are 10, then

only 10 rows are returned.

SelectOne

where() clause (optional)

Returns the first row that fits

the condition of the where()

clause.

Insert

definition of new item to be inserted

where() clause

Returns status.

Update

Delete

where() clause

5.2

JDBC eWay Database Operations (JCD)

The same database operations are also used in the JCD, but appear as methods to call

from the Collaboration.

Tables, Views, and Stored Procedures are manipulated through OTDs. Methods to call

include:

ƒ insert()

ƒ insertRow()

ƒ update(String sWhere)

ƒ updateRow()

ƒ delete(String sWhere)

ƒ deleteRow()

ƒ select(String where)

The ability to perform any of the above methods using a table OTD may not be possible

with all third-party drivers. You have to use a Prepared Statement to perform such an

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

operation. Check with the respective driver’s vendor for further information. This

feature is known as Updatable ResultSet.

Note: Refer to the Javadoc for a full description of methods included in the JDBC eWay.

5.2.1 The Table

A table OTD represents a database table. It consists of fields and methods. Fields

correspond to the columns of a table while methods are the operations that you can

apply to the OTD. This allows you to perform Query, Update, Insert, and Delete SQL

operations in a table. The ability to update via a ResultSet is called “Updatable

ResultSet”, which is a feature supported by this eWay.

By default, the Table OTD has UpdatableConcurrency and ScrollTypeForwardOnly.

Normally you do not have to change the default setting.

The type of result returned by the select() method can be specified using:

ƒ SetConcurrencytoUpdatable

ƒ SetConcurrencytoReadOnly

ƒ SetScrollTypetoForwardOnly

ƒ SetScrollTypetoScrollSensitive

ƒ SetScrollTypetoInsensitive

The Query (Select) Operation

To perform a query operation on a table:

1 Execute the select() method with the “where” clause specified if necessary.

2 Loop through the ResultSet using the next() method.

3 Process the return record within a while() loop.

For example:

package prjJDBC_JCDjcdALL;

public class jcdTableSelect

{

public com.stc.codegen.logger.Logger logger;

public com.stc.codegen.alerter.Alerter alerter;

public com.stc.codegen.util.CollaborationContext collabContext;

public com.stc.codegen.util.TypeConverter typeConverter;

public void receive(

com.stc.connector.appconn.file.FileTextMessage input,

dtd.otdInputDTD_1394195520.DBemployees otdInputDTD_DBemployees_1,

otdJDBC.OtdJDBCOTD otdJDBC_1, dtd.otdOutputDTD882991309.DBemployee

otdOutputDTD_DBemployee_1,

com.stc.connector.appconn.file.FileApplication FileClient_1 )

throws Throwable

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

{

FileClient_1.setText( "Selecting record(s) from db_employee

table via table select .." );

FileClient_1.write();

otdJDBC_1.getDB_EMPLOYEE().select( input.getText() );

while (otdJDBC_1.getDB_EMPLOYEE().next()) {

otdOutputDTD_DBemployee_1.setEmpNo(

typeConverter.shortToString( otdJDBC_1.getDB_EMPLOYEE().getEMP_NO(),

"#", false, "" ) );

otdOutputDTD_DBemployee_1.setLastname(

otdJDBC_1.getDB_EMPLOYEE().getLAST_NAME() );

otdOutputDTD_DBemployee_1.setFirstname(

otdJDBC_1.getDB_EMPLOYEE().getFIRST_NAME() );

otdOutputDTD_DBemployee_1.setRate(

otdJDBC_1.getDB_EMPLOYEE().getRATE().toString() );

otdOutputDTD_DBemployee_1.setLastDate(

typeConverter.dateToString(

otdJDBC_1.getDB_EMPLOYEE().getLAST_UPDATE(), "yyyy-MM-dd hh:mm:ss",

false, "" ) );

FileClient_1.setText(

otdOutputDTD_DBemployee_1.marshalToString() );

FileClient_1.write();

}

FileClient_1.setText( "Done table select." );

FileClient_1.write();

}

The Insert Operation

To perform an insert operation on a table:

1 Execute the insert() method. Assign a value to a field.

2 Insert the row by calling insertRow()

This example inserts an employee record.

package prjJDBC_JCDjcdALL;

public class jcdInsert

{

public com.stc.codegen.logger.Logger logger;

public com.stc.codegen.alerter.Alerter alerter;

public com.stc.codegen.util.CollaborationContext collabContext;

public com.stc.codegen.util.TypeConverter typeConverter;

public void receive(

com.stc.connector.appconn.file.FileTextMessage input,

com.stc.connector.appconn.file.FileApplication FileClient_1,

dtd.otdInputDTD_1394195520.DBemployees otdInputDTD_DBemployees_1,

dtd.otdOutputDTD882991309.DBemployee otdOutputDTD_DBemployee_1,

otdJDBC.OtdJDBCOTD otdJDBC_1 )

throws Throwable

{

FileClient_1.setText( "Inserting records into db_employee

table .." );

FileClient_1.write();

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

otdInputDTD_DBemployees_1.unmarshalFromString(

input.getText() );

for (int i1 = 0; i1 <

otdInputDTD_DBemployees_1.countX_sequence_A(); i1 += 1) {

otdJDBC_1.getInsert_Ps().setEmp_no(

typeConverter.stringToShort(

otdInputDTD_DBemployees_1.getX_sequence_A( i1 ).getEmpNo(), "#",

false, 0 ) );

otdJDBC_1.getInsert_Ps().setLast_name(

otdInputDTD_DBemployees_1.getX_sequence_A( i1 ).getLastname() );

otdJDBC_1.getInsert_Ps().setFirst_name(

otdInputDTD_DBemployees_1.getX_sequence_A( i1 ).getFirstname() );

otdJDBC_1.getInsert_Ps().setRate( new

java.math.BigDecimal( otdInputDTD_DBemployees_1.getX_sequence_A( i1

).getRate() ) );

otdJDBC_1.getInsert_Ps().setLast_update(

typeConverter.stringToSQLDate(

otdInputDTD_DBemployees_1.getX_sequence_A( i1 ).getLastDate(), "yyyy-

MM-dd hh:mm:ss", false, "" ) );

otdJDBC_1.getInsert_Ps().executeUpdate();

}

FileClient_1.setText( "Done Insert." );

FileClient_1.write();

}

The Update Operation

To perform an update operation on a table:

1 Execute the update() method.

2 Using a while loop together with next(), move to the row that you want to update.

3 Assign updating value(s) to the fields of the table OTD

4 Update the row by calling updateRow().

package prjJDBC_JCDjcdALL;

public class jcdUpdate

{

public com.stc.codegen.logger.Logger logger;

public com.stc.codegen.alerter.Alerter alerter;

public com.stc.codegen.util.CollaborationContext collabContext;

public com.stc.codegen.util.TypeConverter typeConverter;

public void receive(

com.stc.connector.appconn.file.FileTextMessage input,

otdJDBC.OtdJDBCOTD otdJDBC_1, dtd.otdOutputDTD882991309.DBemployee

otdOutputDTD_DBemployee_1, dtd.otdInputDTD_1394195520.DBemployees

otdInputDTD_DBemployees_1,

com.stc.connector.appconn.file.FileApplication FileClient_1 )

throws Throwable

{

FileClient_1.setText( "Update the Rate and Last_update fields

using Prepared Statement.. " );

FileClient_1.write();

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

otdJDBC_1.getUpdate_Ps().setEmp_no(

typeConverter.stringToShort( input.getText(), "#", false, 0 ) );

otdJDBC_1.getUpdate_Ps().executeUpdate();

FileClient_1.setText( "Done Update." );

FileClient_1.write();

}

The Delete Operation

To perform a delete operation on a table:

1 Execute the delete() method.

In this example DELETE an employee.

package prjJDBC_JCDjcdALL;

public class jcdDelete

{

public com.stc.codegen.logger.Logger logger;

public com.stc.codegen.alerter.Alerter alerter;

public com.stc.codegen.util.CollaborationContext

collabContext;

public com.stc.codegen.util.TypeConverter typeConverter;

public void receive(

com.stc.connector.appconn.file.FileTextMessage input,

dtd.otdInputDTD_1394195520.DBemployees otdInputDTD_DBemployees_1,

otdJDBC.OtdJDBCOTD otdJDBC_1, dtd.otdOutputDTD882991309.DBemployee

otdOutputDTD_DBemployee_1,

com.stc.connector.appconn.file.FileApplication FileClient_1 )

throws Throwable

{

FileClient_1.setText( "Delete record .." );

FileClient_1.write();

otdJDBC_1.getDB_EMPLOYEE().delete( input.getText() );

FileClient_1.setText( "Done delete." );

FileClient_1.write();

}

^5.2.2The Stored Procedure

A Stored Procedure OTD represents a database stored procedure. Fields correspond to

the arguments of a stored procedure while methods are the operations that you can

apply to the OTD. It allows you to execute a stored procedure. Remember that while in

the Collaboration Editor you can drag and drop nodes from the OTD into the

Collaboration Editor.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

Executing Stored Procedures

The OTD represents the Stored Procedure “LookUpGlobal” with two parameters, an

inbound parameter (INLOCALID) and an outbound parameter

(OUTGLOBALPRODUCTID). These inbound and outbound parameters are generated

by the Database Wizard and are represented in the resulting OTD as nodes. Within the

Transformation Designer, you can drag values from the input parameters, execute the

call, collect data, and drag the values to the output parameters.

Steps for executing the Stored Procedure include:

1 Specify the input values.

2 Execute the Stored Procedure.

3 Retrieve the output parameters if any.

For example:

package Storedprocedure;

public class sp_jce

{

public com.stc.codegen.logger.Logger logger;

public com.stc.codegen.alerter.Alerter alerter;

public void receive(

com.stc.connector.appconn.file.FileTextMessage

input,com.stc.connector.appconn.file.FileApplication

FileClient_1,employeedb.Db_employee

employeedb_with_top_db_employee_1,insert_DB.Insert_DBOTD insert_DB_1

)

throws Throwable

{

employeedb_with_top_db_employee_1.unmarshalFromString(

input.getText() );

insert_DB_1.getInsert_new_employee().setEmployee_no(

java.lang.Integer.parseInt(

employeedb_with_top_db_employee_1.getEmployee_no() ) );

insert_DB_1.getInsert_new_employee().setEmployee_Lname(

employeedb_with_top_db_employee_1.getEmployee_lname() );

insert_DB_1.getInsert_new_employee().setEmployee_Fname(

employeedb_with_top_db_employee_1.getEmployee_fname() );

insert_DB_1.getInsert_new_employee().setRate(

java.lang.Float.parseFloat(

employeedb_with_top_db_employee_1.getRate() ) );

insert_DB_1.getInsert_new_employee().setUpdate_date(

java.sql.Timestamp.valueOf(

employeedb_with_top_db_employee_1.getUpdate_date() ) );

insert_DB_1.getInsert_new_employee().execute();

insert_DB_1.commit();

FileClient_1.setText( "procedure executed" );

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

FileClient_1.write();

}

Manipulating the ResultSet and Update Count Returned by Stored

Procedure

For Stored Procedures that return ResultSets and Update Count, the following methods

are provided to manipulate the ResultSet:

ƒ enableResultSetOnly

ƒ enableUpdateCountsOnly

ƒ enableResultSetandUpdateCounts

ƒ resultsAvailable

ƒ next

ƒ getUpdateCount

ƒ available

Many drivers do not support manipulating ResultSets in a Stored Procedure. It is

recommended that you use specific eWay Adapters for Oracle, SQL Server, Sybase,

DB2, and so forth, to peform such operations.

JDBC stored procedures do not return records as ResultSets. Instead, the records are

returned through output reference cursor parameters. Reference Cursor parameters are

essentially ResultSets.

The resultsAvailable() method, added to the PreparedStatementAgent class, simplifies

the whole process of determining whether any results, be it Update Counts or

ResultSets, are available after a stored procedure has been executed. Although JDBC

provides three methods (getMoreResults(), getUpdateCount(), and getResultSet()) to

access the results of a stored procedure call, the information returned from these

methods can be quite confusing to the inexperienced Java JDBC programmer and they

also differ between vendors. You can simply call resultsAvailable() and if Boolean true

is returned, you can expect either a valid Update Count when getUpdateCount() is

called and/or the next ResultSet has been retrieved and made available to one of the

ResultSet nodes defined for the Stored Procedure OTD, when that node’s available()

method returns true.

Frequently, Update Counts information that is returned from a Stored Procedures is

insignificant. You should process returned ResultSet information and avoid looping

through all of the Update Counts. The following three methods control exactly what

information should be returned from a stored procedure call. The

enableResultSetsOnly() method, added to the PreparedStatement Agent class allows

only ResultSets to be returned and thus every resultsAvailable() called only returns

Boolean true if a ResultSet is available. Likewise, the enableUpdateCountsOnly()

causes resultsAvailable() to return true only if an Update Count is available. The

default case of enableResultsetsAndUpdateCount() method allows both ResultSets

and Update Counts to be returned.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

Collaboration usability for a stored procedure ResultSet

The Column data of the ResultSets can be dragged-and-dropped from their nodes to

the Business Rules. Below is a code snippet that can be generated by the Collaboration

Editor:

while (getSPIn().getSpS_multi().resultsAvailable())

{

if (getSPIn().getSpS_multi().getUpdateCount() > 0)

{

System.err.println("Updated

"+getSPIn().getSpS_multi().getUpdateCount()+" rows");

}

if (getSPIn().getSpS_multi().getNormRS().available())

{

while (getSPIn().getSpS_multi().getNormRS().next())

{

System.err.println("Customer Id =

"+getSPIn().getSpS_multi().getNormRS().getCustomerId());

System.err.println("Customer Name =

"+getSPIn().getSpS_multi().getNormRS().getCustomerName());

System.err.println();

}

System.err.println("===");

}

else if (getSPIn().getSpS_multi().getDbEmployee().available())

{

while (getSPIn().getSpS_multi().getDbEmployee().next())

{

System.err.println("EMPNO

"+getSPIn().getSpS_multi().getDbEmployee().getEMPNO());

System.err.println("ENAME

"+getSPIn().getSpS_multi().getDbEmployee().getENAME());

System.err.println("JOB

"+getSPIn().getSpS_multi().getDbEmployee().getJOB());

System.err.println("MGR

"+getSPIn().getSpS_multi().getDbEmployee().getMGR());

System.err.println("HIREDATE =

"+getSPIn().getSpS_multi().getDbEmployee().getHIREDATE());

System.err.println("SAL

"+getSPIn().getSpS_multi().getDbEmployee().getSAL());

System.err.println("COMM

"+getSPIn().getSpS_multi().getDbEmployee().getCOMM());

System.err.println("DEPTNO =

"+getSPIn().getSpS_multi().getDbEmployee().getDEPTNO());

System.err.println();

}

System.err.println("===");

}

Note: resultsAvailable() and available() cannot be indiscriminately called because each

time they move ResultSet pointers to the appropriate locations.

After calling "resultsAvailable()", the next result (if available) can be either a ResultSet

or an UpdateCount if the default "enableResultSetsAndUpdateCount()" was used.

Because of limitations imposed by some DBMSs, it is recommended that for maximum

portability, all of the results in a ResultSet object should be retrieved before OUT

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

parameters are retrieved. Therefore, you should retrieve all ResultSet(s) and Update

Counts first followed by retrieving the OUT type parameters and return values.

The following list includes specific ResultSet behavior that you may encounter:

ƒ The method resultsAvailable() implicitly calls getMoreResults() when it is called

more than once. You should not call both methods in your java code. Doing so may

result in skipped data from one of the ResultSets when more than one ResultSet is

present.

ƒ The methods available() and getResultSet() can not be used in conjunction with

multiple ResultSets being open at the same time. Attempting to open more the one

ResultSet at the same time closes the previous ResultSet. The recommended

working pattern is:

Š Open one ResultSet (ResultSet_1) and work with the data until you have

completed your modifications and updates. Open ResultSet_2, (ResultSet_1 is

now closed) and modify. When you have completed your work in ResultSet_2,

open any additional ResultSets or close ResultSet_2.

ƒ If you modify the ResultSet generated by the Execute mode of the Database Wizard,

you need to assure the indexes match the stored procedure. By doing this, your

ResultSet indexes are preserved.

ƒ Generally, getMoreResults does not need to be called. It is needed if you do not

want to use our enhanced methods and you want to follow the traditional JDBC

calls on your own.

The DBWizard Assistant expects the column names to be in English when creating a

ResultSet.

Prepared Statement

A Prepared Statement OTD represents a SQL statement that has been compiled. Fields

in the OTD correspond to the input values that users need to provide.

Prepared statements can be used to perform insert, update, delete and query

operations. A prepared statement uses a question mark (?) as a place holder for input.

For example:

insert into EMP_TAB(Age, Name, Dept No) value(?, ?, ?)

To execute a prepared statement, set the input parameters and call executeUpdate() and

specify the input values if any.

getPrepStatement().getPreparedStatementTest().setAge(23);

getPrepStatement().getPreparedStatementTest().setName(‘Peter Pan’);

getPrepStatement().getPreparedStatementTest().setDeptNo(6);

getPrepStatement().getPreparedStatementTest().executeUpdate();

Batch Operations

To achieve better performance, consider using a bulk insert if you have to insert many

records. This is the “Add Batch” capability. The only modification required is to include

the addBatch() method for each SQL operation and then the executeBatch() call to

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 5

Using JDBC/ODBC Operations

Section 5.2

JDBC eWay Database Operations (JCD)

submit the batch to the database server. Batch operations apply only to Prepared

Statements.

Not all drivers support batch operations. Check with the respective driver’s vendor for

further information.

getPrepStatement().getPreparedStatementTest().setAge(23);

getPrepStatement().getPreparedStatementTest().setName(‘Peter Pan’);

getPrepStatement().getPreparedStatementTest().setDeptNo(6);

getPrepStatement().getPreparedStatementTest().addBatch();

getPrepStatement().getPreparedStatementTest().setAge(45);

getPrepStatement().getPreparedStatementTest().setName(‘Harrison

Ford’);

getPrepStatement().getPreparedStatementTest().setDeptNo(7);

getPrepStatement().getPreparedStatementTest().addBatch();

getPrepStatement().getPreparedStatementTest().executeBatch();

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsytems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Implementing the JDBC/ODBC eWay

Sample Projects

This chapter provides an introduction to the JDBC eWay components, and information

on how these components are created and implemented in a Sun Java Composite

Application Platform Suite Project. Sample Projects are designed to provide an

overview of the basic functionality of the JDBC eWay by identifying how information is

passed between eGate and supported external databases.

It is assumed that you understand the basics of creating a Project using the Enterprise

Designer. For more information on creating an eGate Project, see the eGate Tutorial and

the eGate Integrator User’s Guide.

What’s in This Chapter

ƒ About the JDBC eWay Sample Projects on page 69

ƒ Running the Sample Projects on page 72

ƒ Running the SQL Script on page 73

ƒ Importing a Sample Project on page 73

ƒ Building and Deploying the prjJDBC_JCD Sample Project on page 74

ƒ Building and Deploying the prjJDBC_BPEL Sample Project on page 95

6.1

About the JDBC eWay Sample Projects

The JDBC eWay JDBC_eWay_Sample.zip file contains two sample Projects that

provide basic instruction on using JDBC operations in the Java Collaboration Definition

(JCD), or the Business Process Excecution Language (BPEL) Projects.

The prjJDBC_JCD sample Project uses input files to pass data into Collaborations.

There are four Collaborations that demonstrate the Insert, Update, and Table Select

operations, and two Collaboration to demonstrate Prepared Statements (Select and

Update). Results are written out to an output file.

The prjJDBC_BPEL sample Project uses input files to pass data into business process.

There are four business processes that demonstrate the Insert, Update, Delete, and

Select operations. Results are written out to an output file.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.1

About the JDBC eWay Sample Projects

Implementing the JDBC/ODBC eWay Sample Projects

Figure 29 Database project flow

Both the prjJDBC_JCD and prjJDBC_BPEL sample Projects demonstrate how to:

ƒ Select employee records from a database using a prepared statement.

ƒ Select employee records from the db_employee table.

ƒ Insert employee records into the db_employee table.

ƒ Update an employee record in the db_employee table.

ƒ Delete an employee record from the db_employee table.

In addition to the sample Projects, the JDBC510_SAMPLE_projects.zip file also

includes seven sample input trigger files and nine sample output files, as follows:

Sample input files

ƒ TriggerInsert.in.~in (for JCE projects only)

ƒ TriggerBpPsInsert.in.~in (for BPEL projects only)

ƒ TriggerDelete.in.~in

ƒ TriggerPsUpdate.in.~in (for JCE projects only)

ƒ TriggerBpUpdate.in.~in (for BPEL projects only)

ƒ TriggerPsSelect.in.~in (for JCE projects only)

ƒ TriggerTableSelect.in.~in

Sample output JCD files

ƒ JCE_Insert_output().dat

ƒ JCE_Delete_output().dat

ƒ JCE_PsUpdate_output().dat

ƒ JCE_PsSelect_output().dat

ƒ JCE_TableSelect_output().dat

Sample output BPEL files

ƒ BPEL_PsInsert_output().dat

ƒ BPEL_Delete_output().dat

ƒ BPEL_Update_output().dat

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.1

About the JDBC eWay Sample Projects

Implementing the JDBC/ODBC eWay Sample Projects

ƒ BPEL_TableSelect_output().dat

6.1.1 Sample Project Data

Data used for the sample Projects are contained within a table called db_employee. The

table has the following columns:

Table 14 Sample Project Data - db_employee Table

Column Name

Data Type

INTEGER

Data Length

emp_no

last_name

first_name

rate

VARCHAR

FLOAT

last_update

TIMESTAMP

6.1.2 Operations Used in the JDBC Sample Projects

The following database operations are used in both the JCD and BPEL sample projects:

ƒ Insert

ƒ Update

ƒ Delete

ƒ Select

Assigning Operations in JCD

Database operations are listed as methods in the JCD. Perform the following steps to

access these methods:

1 Create a Collaboration that contains an OTD using JDBC.

2 Right-click the OTD listed in your Collaboration and then select Select Method to

Call from the shortcut menu.

3 Browse to and select a method to call.

Assigning Operations in BPEL

You can associate an eInsight Business Process Activity with the eWay, both during the

system design phase and during runtime. To make this association:

1 Select the desired receive or write operation under the eWay in the Enterprise

Explorer.

2 Drag the operation onto the eInsight Business Process canvas.

The operation automatically changes to an Activity with an icon identifying the

component that is the basis for the Activity.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.2

Running the Sample Projects

Implementing the JDBC/ODBC eWay Sample Projects

At run time, the eInsight engine invokes each step in the order that you defined in the

Business Process. Using the engine’s Web Services interface, the Activity in turn

invokes the eWay. You can open a file specified in the eWay and view its contents before

and after the Business Process is executed.

Note: Inbound database eWays are only supported within BPEL Collaborations.

6.1.3 About the eInsight Engine and eGate Components

You can deploy an eGate component as an Activity in an eInsight Business Process.

Once you have associated the desired component with an Activity, the eInsight engine

can invoke it using a Web Services interface.

Examples of eGate components that can interface with eInsight in this way are:

ƒ Object Type Definitions (OTDs)

ƒ An eWay

ƒ Collaborations

Using the eGate Enterprise Designer and eInsight, you can add an Activity to a

Business Process, then associate that Activity with an eGate component, for example,

an eWay. When eInsight run the Business Process, it automatically invokes that

component via its Web Services interface.

6.1.4 Sample Projects Drivers

Sample Projects included with this eWay were built using the AS/400 JDBC Toolbox

Driver (jt400.jar). You must get this or a different driver from a third-party vendor and

install and configure the eWay as per the vendors specification, using the vendor's

specific driver jar file and appropriate driver specific parameters such as driver class

name, URL connection string, and so forth.

The JAR file for the driver you select must be copied to the following folder:

<JavaCAPS51>\logicalhost\is\domains\domain1\lib

where <JavaCAPS51> is the directory where the Sun Java Composite Application

Platform Suite is installed.

When using any driver to build OTDs, be sure to include the absolute path of the

locally installed JAR file in the Database Connection Information window. See Figure

11 on page 43.

6.2

Running the Sample Projects

The following steps are required to run the sample Projects that are contained in the

JDBCeWayDocs.sar file.

1 Run the SQL script.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.3

Running the SQL Script

Implementing the JDBC/ODBC eWay Sample Projects

The script creates the tables and records required by the sample Project.

2 Import the sample Projects.

3 Build, deploy, and run the sample Projects.

You must do the following before you can run an imported sample Project:

Š Create an Environment

Š Configure the eWays

Š Create a Deployment Profile

Š Create and start a domain

Š Deploy the Project

4 Check the output.

6.3

Running the SQL Script

The data used for both the JCD and BPEL sample Projects are contained within a table

called db_employee. You create this table by using the SQL statement

JDBC_sample_script.sql, that is included in the sample Project. Note that you must use

a database tool to run the script.

Following is the SQL statement designed for the sample Projects.

drop table db_employee

create table db_employee (

EMP_NO int,

LAST_NAME varchar(30),

FIRST_NAME varchar(30),

RATE float,

LAST_UPDATE datetime)

The sample Projects provided with the JDBC eWay use input files to pass predefined

data or conditions into the Collaboration or BPEL business process, which then

transforms the database contents, and delivers the ResultSet.

6.4

Importing a Sample Project

Sample eWay Projects are included as part of the installation CD-ROM package. To

import a sample eWay Project to the Enterprise Designer do the following:

1 Extract the samples from the Sun Java Composite Application Platform Suite

Installer to a local file.

Sample files are uploaded with the eWay’s documentation SAR file, and then

downloaded from the Installer’s Documentation tab. The JDBC_eWay_Sample.zip

file contains the various sample Project ZIP files.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Note: Make sure you save all unsaved work before importing a Project.

2 From the Enterprise Designer’s Project Explorer pane, right-click the Repository

and select Import Project from the shortcut menu. The Import Manager appears.

Figure 30 Import Manager Dialog Box

3 Browse to the directory that contains the sample Project ZIP file. Select the sample

file and click Import.

Click Close after successfully importing the sample Project.

6.5

Building and Deploying the prjJDBC_JCD Sample

Project

This section provides step-by-step instructions for manually creating the prjJDBC_JCD

sample Project.

Steps required to create the sample project

ƒ Creating a Project on page 75

ƒ Creating the OTDs on page 75

ƒ Creating a Connectivity Map on page 76

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

ƒ Creating the Collaboration Definitions (Java) on page 78

ƒ Create the Collaboration Business Rules on page 81

ƒ Binding the eWay Components on page 87

ƒ Creating an Environment on page 88

ƒ Configuring the eWays on page 89

ƒ Creating the Deployment Profile on page 92

ƒ Creating and Starting the Domain on page 93

ƒ Building and Deploying the Project on page 94

ƒ Running the Sample on page 94

6.5.1 Creating a Project

The first step is to create a new Project in the Enterprise Designer.

1 Start the Enterprise Designer.

2 From the Project Explorer tree, right-click the Repository and select New Project. A

new Project (Project1) appears on the Project Explorer tree.

3 Right-click Project1 and select Rename from the shortcut menu. Rename the Project

(for this sample, prjJDBC_JCD).

6.5.2 Creating the OTDs

The sample Project requires three OTDs to interact with the JDBC eWay. These OTDs

include:

ƒ JDBC Database OTD

ƒ Inbound DTD OTD

ƒ Outbound DTD OTD

Steps required to create a JDBC Database OTD:

1 Right-click your new Project in the Enterprise Designer’s Project Explorer, and

select New > Object Type Definition.

The New Object Type Definition Wizard window appears.

2 Select the JDBC Database OTD Wizard from the list of OTD Wizards and click

Next.

3 Enter the connection information for the JDBC database. Connection fields include:

Š Driver Jar Files

Š Driver Java Class Name

Š URL Connection String

Š User name

Š Password

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

4 Click Next, and select the types of database object you want to include in the

sample Project. For our example, select the following:

Š Tables/Views/Aliases

Š Prepared Statements

5 Click Add to select tables from the JDBC database. The Add Tables window

appears.

6 Search for or Type in the name of the database. In this example we use the

DB_EMPLOYEE table. Click Select when the database appears in the Results

selection frame. Click OK to close the Add Tables window

7 Click Next the Add Prepared Statements Wizard appears.

8 Click Add, the Add Prepared Statement window appears. Enter the following:

Š Prepared Statement Name: Select_ps

Š SQL Statement:

select * from db_employee where emp_no > ? order by emp_no

Note: In this example, the SQL statement includes the ? placeholder for input. This

placeholder represents the value for the Where Clause.

9 Click the OK button to close the Prepared Statement window, and then click Next

on the Prepared Statements Wizard window.

10 Enter an OTD name. In this example, use otdJDBC.

11 Click Next and review your settings, then click Finish to create the OTD.

Steps required to create inbound and outbound DTD OTDs include:

1 Right-click your new Project in the Enterprise Designer’s Project Explorer, and

select New > Object Type Definition.

The New Object Type Definition Wizard window appears.

2 Select DTD from the list of OTD Wizards and click Next.

3 Browse to and then select a DTD file. For this example, select one of the following

DTD files from the sample Project, and then click Next.

Š otdInputDTD.dtd

Š otdOutputDTD.dtd

4 The file you select appears in the Select Document Elements window. Click Next.

Click Finish to complete the DTD based OTD. Repeat this process again to create the

second DTD file.

6.5.3 Creating a Connectivity Map

The Connectivity Map provides a canvas for assembling and configuring a Project’s

components.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Steps required to create a new Connectivity Map:

1 From the Project Explorer tree, right-click the new prjJDBC_JCD Project and select

New > Connectivity Map from the shortcut menu.

2 The New Connectivity Map appears and a node for the Connectivity Map is added

under the Project, on the Project Explorer tree labeled CMap1.

Create four additional Connectivity Maps—CMap2, CMap3. CMap4, and

CMap5— and rename them as follows:

Š cmDelete

Š cmInsert

Š cmPsSelect

Š cmTableSelect

Š cmPsUpdate

The icons in the toolbar represent the available components used to populate the

Connectivity Map canvas.

Populating the Connectivity Map

Add the Project components to the Connectivity Map by dragging the icons from the

toolbar to the canvas.

Each Connectivity Map in the prjJDBC_JCD sample Project requires the following

components:

ƒ File External Application (2)

ƒ JDBC External Application

ƒ Service

Any eWay added to the Connectivity Map is associated with an External System. To

establish a connection to JDBC, first select JDBC as an External System to use in your

Connectivity Map.

Steps required to select a JDBC External System:

1 Click the External Application icon on the Connectivity Map toolbar.

2 Select the external systems necessary to create your Project (for this sample, JDBC

and File). Icons representing the selected external systems are added to the

Connectivity Map toolbar.

3 Rename the following components and then save changes to the Repository:

Š File1 to FileClientIN

Š File2 to FileClientOUT

Š JDBC1 to esJDBCOUT

4 Rename each Connectivity Map Service to match the intended operation, as for

example:

Š jcdDelete

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Š jcdInsert

Š jcdPsSelect

Š jcdTableSelect

Š jcdPsUpdate

6.5.4 Creating the Collaboration Definitions (Java)

The next step is to create Collaborations using the Collaboration Definition Wizard

(Java). Since the sample Project includes five database operations, you must create five

separate Collaboration Definitions (Java), or JCDs. Once you create the Collaboration

Definitions, you can write the Business Rules of the Collaborations using the

Collaboration Editor.

JCDs required for the prjJDBC_JCD sample include:

ƒ jcdDelete

ƒ jcdInsert

ƒ jcdPsSelect

ƒ jcdTableSelect

ƒ jcdPsUpdate

jcdDelete Collaboration

Steps required to create the jcdDelete Collaboration:

1 From the Project Explorer, right-click the sample Project and select New >

Collaboration Definition (Java) from the shortcut menu. The Collaboration

Definition Wizard (Java) appears.

2 Enter a Collaboration Definition name (for this sample jcdDelete) and click Next.

3 For Step 2 of the wizard, from the Web Services Interfaces selection window,

double-click Sun SeeBeyond > eWays > File > FileClient > receive. The File Name

field now displays receive. Click Next.

4 For Step 3 of the wizard, from the Select OTDs selection window, double-click

prjJDBC_JCD > otdALL > otdJDBC. The otdJDBC OTD is added to the Selected

OTDs field.

5 Click the Up One Level button twice to return to the Repository. Double-click Sun

SeeBeyond > eWays > File > FileClient. The Selected OTDs field now lists the

FileClient OTD.

6 Click Finish. The Collaboration Editor with the new jcdDelete Collaboration

appears in the right pane of the Enterprise Designer.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

jcdInsert Collaboration

Steps required to create the jcdInsert Collaboration:

1 From the Project Explorer, right-click the sample Project and select New >

Collaboration Definition (Java) from the shortcut menu. The Collaboration

Definition Wizard (Java) appears.

2 Enter a Collaboration Definition name (for this sample jcdInsert) and click Next.

3 For Step 2 of the wizard, from the Web Services Interfaces selection window,

double-click Sun SeeBeyond > eWays > File > FileClient > receive. The File Name

field now displays receive. Click Next.

4 For Step 3 of the wizard, from the Select OTDs selection window, double-click

prjJDBC_JCD > otdALL > otdJDBC. The otdJDBC OTD is added to the Selected

OTDs field.

5 In the same window, double-click otdInputDTD_DBemployees. The

otdInputDTD_DBemployees OTD is added to the Selected OTDs field.

Note: The otdOutputDTD_DBemployees OTD is created from the otdInputDTD.dtd that

is included in the Sample Project.

6 Click the Up One Level button twice to return to the Repository. Double-click Sun

SeeBeyond > eWays > File > FileClient. The Selected OTDs field now lists the

FileClient OTD.

7 Click Finish. The Collaboration Editor with the new jcdInsert Collaboration

appears in the right pane of the Enterprise Designer.

jcdPsSelect Collaboration

Steps required to create the jcdPsSelect Collaboration:

1 From the Project Explorer, right-click the sample Project and select New >

Collaboration Definition (Java) from the shortcut menu. The Collaboration

Definition Wizard (Java) appears.

2 Enter a Collaboration Definition name (for this sample jcdPsSelect) and click Next.

3 For Step 2 of the wizard, from the Web Services Interfaces selection window,

double-click Sun SeeBeyond > eWays > File > FileClient > receive. The File Name

field now displays receive. Click Next.

4 For Step 3 of the wizard, from the Select OTDs selection window, double-click

prjJDBC_JCD > otdALL > otdJDBC. The otdJDBC OTD is added to the Selected

OTDs field.

5 In the same window, double-click otdOutputDTD_DBemployee. The

otdOutputDTD_DBemployee OTD is added to the Selected OTDs field.

Note that the otdOutputDTD_DBemployee OTD is created from the

otdOutputDTD.dtd that is included in the Sample Project.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

6 Click the Up One Level button twice to return to the Repository. Double-click Sun

SeeBeyond > eWays > File > FileClient. The Selected OTDs field now lists the

FileClient OTD.

7 Click Finish. The Collaboration Editor with the new jcdPsSelect Collaboration

appears in the right pane of the Enterprise Designer.

jcdTableSelect Collaboration

Steps required to create the jcdTableSelect Collaboration:

1 From the Project Explorer, right-click the sample Project and select New >

Collaboration Definition (Java) from the shortcut menu. The Collaboration

Definition Wizard (Java) appears.

2 Enter a Collaboration Definition name (for this sample jcdTableSelect) and click

Next.

3 For Step 2 or the wizard, from the Web Services Interfaces selection window,

double-click Sun SeeBeyond > eWays > File > FileClient > receive. The File Name

field now displays receive. Click Next.

4 For Step 3 of the wizard, from the Select OTDs selection window, double-click

prjJDBC_JCD > otdALL > otdJDBC. The otdJDBC OTD is added to the Selected

OTDs field.

5 In the same window, double-click otdOutputDTD_DBemployee. The

otdOutputDTD_DBemployee OTD is added to the Selected OTDs field.

Note: The otdOutputDTD_DBemployee OTD is created from the otdOutputDTD.dtd

that is included in the Sample Project.

6 Click the Up One Level button twice to return to the Repository. Double-click Sun

SeeBeyond > eWays > File > FileClient. The Selected OTDs field now lists the

FileClient OTD.

7 Click Finish. The Collaboration Editor with the new jcdTableSelect Collaboration

appears in the right pane of the Enterprise Designer.

jcdPsUpdate Collaboration

Steps required to create the jcdPsUpdate Collaboration:

1 From the Project Explorer, right-click the sample Project and select New >

Collaboration Definition (Java) from the shortcut menu. The Collaboration

Definition Wizard (Java) appears.

2 Enter a Collaboration Definition name (for this sample jcdPsUpdate) and click Next.

3 For Step 2 of the wizard, from the Web Services Interfaces selection window,

double-click Sun SeeBeyond > eWays > File > FileClient > receive. The File Name

field now displays receive. Click Next.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

4 For Step 3 of the wizard, from the Select OTDs selection window, double-click

prjJDBC_JCD > otdALL > otdJDBC. The otdJDBC OTD is added to the Selected

OTDs field.

5 Click the Up One Level button twice to return to the Repository. Double-click Sun

SeeBeyond > eWays > File > FileClient. The Selected OTDs field now lists the

FileClient OTD.

6 Click Finish. The Collaboration Editor with the new jcdPsUpdate Collaboration

appears in the right pane of the Enterprise Designer.

6.5.5 Create the Collaboration Business Rules

The next step in the sample is to create the Business Rules of the Collaboration using

the Collaboration Editor.

Creating the jcdDelete Business Rules

The jcdDelete Collaboration implements the Input Web Service Operation to read the

TriggerDelete.in file and then delete a record. The Collaboration also writes a message

to JCD_Delete_output0.dat to confirm a deleted record.

Note: The where clause in the business rule reads the trigger value as a placeholder for

input. This permits you to modify the query to select a specific record. Also note that

all records are deleted from the database when the TriggerDelete.in file is empty.

The jcdDelete Collaboration contains the Business Rules displayed in Figure 31.

Figure 31 jcdDelete Business Rules

Creating the jcdInsert Business Rules

The jcdInsert Collaboration implements the Input Web Service Operation to read the

TriggerInsert.in. file. It then unmarshals data from the input data into the

otdInputDTD_DBEmployees OTD, calls the otdJDBC OTD, and inserts records into

the database via a For Loop. The Collaboration also writes a message to

JCD_Insert_output0.dat to confirm an inserted record.

The jcdInsert Collaboration contains the Business Rules displayed in Figure 32.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Figure 32 jcdInsert Business Rules

Sample code from the jcdInsert Includes:

package prjJDBC_JCDjcdALL;

public class jcdInsert

{

public com.stc.codegen.logger.Logger logger;

public com.stc.codegen.alerter.Alerter alerter;

public com.stc.codegen.util.CollaborationContext collabContext;

public com.stc.codegen.util.TypeConverter typeConverter;

public void receive( com.stc.connector.appconn.file.FileTextMessage

input, com.stc.connector.appconn.file.FileApplication FileClient_1,

dtd.otdInputDTD_1394195520.DBemployees otdInputDTD_DBemployees_1,

dtd.otdOutputDTD882991309.DBemployee otdOutputDTD_DBemployee_1,

otdJDBC.OtdJDBCOTD otdJDBC_1 )

throws Throwable

{

\\ Writes out a message stating records are being inserted.

FileClient_1.setText( "Inserting records into db_employee

table .." );

FileClient_1.write();

\\ Unmarshals data from the input XML data into the

otdInputDTD_DBEmployees OTD.

otdInputDTD_DBemployees_1.unmarshalFromString(

input.getText() );

\\ Calls the otdJDBC OTD, and inserts multiple records into the

database via a For Loop. The first insert() method opens the table

ResultSet for insert operations, while the insertRow() method inserts

records into the table ResultSet.

for (int i1 = 0; i1 <

otdInputDTD_DBemployees_1.countX_sequence_A(); i1 += 1) {

otdJDBC_1.getInsert_Ps().setEmp_no(

typeConverter.stringToShort(

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

otdInputDTD_DBemployees_1.getX_sequence_A( i1 ).getEmpNo(), "#",

false, 0 ) );

otdJDBC_1.getInsert_Ps().setLast_name(

otdInputDTD_DBemployees_1.getX_sequence_A( i1 ).getLastname() );

otdJDBC_1.getInsert_Ps().setFirst_name(

otdInputDTD_DBemployees_1.getX_sequence_A( i1 ).getFirstname() );

otdJDBC_1.getInsert_Ps().setRate( new

java.math.BigDecimal( otdInputDTD_DBemployees_1.getX_sequence_A( i1

).getRate() ) );

otdJDBC_1.getInsert_Ps().setLast_update(

typeConverter.stringToSQLDate(

otdInputDTD_DBemployees_1.getX_sequence_A( i1 ).getLastDate(), "yyyy-

MM-dd hh:mm:ss", false, "" ) );

otdJDBC_1.getInsert_Ps().executeUpdate();

\\ Writes a message to confirm the inserted records.

}

FileClient_1.setText( "Done Insert." );

FileClient_1.write();

}

Creating the jcdPsSelect Business Rules

The jcdPsSelect Collaboration implements the Input Web Service Operation to read the

TriggerPsSelect.in file. It then copies the database resultset (as noted in the prepared

statement query) into the otdInputDTD_DBEmployee OTD and selects all available

records from the database. The Collaboration also writes a message to

JCD_PsSelect_output0.dat to confirm when records are selected, or when no records

are available.

The jcdPsSelect Collaboration contains the Business Rules displayed in Figure 33.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Figure 33 jcdPsSelect Business Rules

Sample code from the jcdPsSelect Includes:

package prjJDBC_JCDjcdALL;

public class jcdPsSelect

{

public com.stc.codegen.logger.Logger logger;

public com.stc.codegen.alerter.Alerter alerter;

public com.stc.codegen.util.CollaborationContext collabContext;

public com.stc.codegen.util.TypeConverter typeConverter;

public void receive( com.stc.connector.appconn.file.FileTextMessage

input, otdJDBC.OtdJDBCOTD otdJDBC_1,

dtd.otdOutputDTD882991309.DBemployee otdOutputDTD_DBemployee_1,

com.stc.connector.appconn.file.FileApplication FileClient_1 )

throws Throwable

{

\\ Writes out a message stating records are being selected.

FileClient_1.setText( "Selecting record(s) from db_employee

table via Prepared Statement select .." );

\\ Copies the database resultset into the otdInputDTD_DBEmployee OTD

and selects all available records from the database. The

executeQuery() method executes the prepared statement query, while

the resultsAvailable() method ensures all rows are retrieved in the

while loop.

FileClient_1.write();

otdJDBC_1.getSelect_ps().setEmp_no( Short.parseShort( "0" ) );

otdJDBC_1.getSelect_ps().executeQuery();

if (otdJDBC_1.getSelect_ps().resultsAvailable()) {

while

(otdJDBC_1.getSelect_ps().get$Select_psResults().next()) {

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

otdOutputDTD_DBemployee_1.setEmpNo( Integer.toString(

otdJDBC_1.getSelect_ps().get$Select_psResults().getEMP_NO() ) );

otdOutputDTD_DBemployee_1.setLastname(

otdJDBC_1.getSelect_ps().get$Select_psResults().getLAST_NAME() );

otdOutputDTD_DBemployee_1.setFirstname(

otdJDBC_1.getSelect_ps().get$Select_psResults().getFIRST_NAME() );

otdOutputDTD_DBemployee_1.setRate(

otdJDBC_1.getSelect_ps().get$Select_psResults().getRATE().toString()

);

otdOutputDTD_DBemployee_1.setLastDate(

otdJDBC_1.getSelect_ps().get$Select_psResults().getLAST_UPDATE().toSt

ring() );

FileClient_1.setText(

otdOutputDTD_DBemployee_1.marshalToString() );

FileClient_1.write();

}

} else {

FileClient_1.setText( "No record found!" );

FileClient_1.write();

}

\\ Writes a message to JCD_PsSelect_output0.dat to confirm when

records are selected, or when no records are available.

FileClient_1.setText( "Done Select" );

FileClient_1.write();

}

Creating the jcdTableSelect Business Rules

The jcdTableSelect Collaboration implements the Input Web Service Operation to read

the TriggerTableSelect.in file. It then copies the database resultset into the

otdInputDTD_DBEmployee OTD and selects all available records from the database

that meet a certain criteria. The Collaboration also writes a message to

JCD_TableSelect_output0.dat to confirm when records are selected, or when no

records are available.

Note: The where clause in the business rule reads the trigger value as a placeholder for

input. This permits you to modify the query to select a specific record. Also note that

all records are selected from the database when the TriggerTableSelect.in file is

empty.

The jcdTableSelect Collaboration contains the Business Rules displayed in Figure 34.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Figure 34 jcdTableSelect Business Rules

Sample code from the jcdTableSelect Includes:

package prjJDBC_JCDjcdALL;

public class jcdTableSelect

{

public com.stc.codegen.logger.Logger logger;

public com.stc.codegen.alerter.Alerter alerter;

public com.stc.codegen.util.CollaborationContext collabContext;

public com.stc.codegen.util.TypeConverter typeConverter;

public void receive( com.stc.connector.appconn.file.FileTextMessage

input, dtd.otdInputDTD_1394195520.DBemployees

otdInputDTD_DBemployees_1, otdJDBC.OtdJDBCOTD otdJDBC_1,

dtd.otdOutputDTD882991309.DBemployee otdOutputDTD_DBemployee_1,

com.stc.connector.appconn.file.FileApplication FileClient_1 )

throws Throwable

{

\\ Writes out a message stating records are being selected.

FileClient_1.setText( "Selecting record(s) from db_employee

table via table select .." );

FileClient_1.write();

\\ Copies the database resultset into the otdInputDTD_DBEmployee (XML

OTD) and selects all available records from the database that meet a

certain criteria. Checking the next() method ensures all rows are

retrieved in the while loop.

otdJDBC_1.getDB_EMPLOYEE().select( input.getText() );

while (otdJDBC_1.getDB_EMPLOYEE().next()) {

otdOutputDTD_DBemployee_1.setEmpNo(

typeConverter.shortToString( otdJDBC_1.getDB_EMPLOYEE().getEMP_NO(),

"#", false, "" ) );

otdOutputDTD_DBemployee_1.setLastname(

otdJDBC_1.getDB_EMPLOYEE().getLAST_NAME() );

otdOutputDTD_DBemployee_1.setFirstname(

otdJDBC_1.getDB_EMPLOYEE().getFIRST_NAME() );

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

otdOutputDTD_DBemployee_1.setRate(

otdJDBC_1.getDB_EMPLOYEE().getRATE().toString() );

otdOutputDTD_DBemployee_1.setLastDate(

typeConverter.dateToString(

otdJDBC_1.getDB_EMPLOYEE().getLAST_UPDATE(), "yyyy-MM-dd hh:mm:ss",

false, "" ) );

\\ marshals XML data from the output data into the

otdOutputDTD_DB_Employee_1.marshallToString() method.

FileClient_1.setText(

otdOutputDTD_DBemployee_1.marshalToString() );

FileClient_1.write();

}

\\ Writes a message to confirm when records are selected, or when no

records are available.

FileClient_1.setText( "Done table select." );

FileClient_1.write();

}

Creating the jcdUpdate Business Rules

The jcdUpdate Collaboration implements the Input Web Service Operation to read the

TriggerUpdate.in. file and then update a particular record. The Collaboration also

writes a message to JCD_Update_output0.dat to confirm an updated record.

Note: The where clause in the business rule reads the trigger value as a placeholder for

input. This permits you to modify the query to select a specific record. Also note that

all records are selected from the database when the TriggerUpdate.in file is empty.

The jcdUpdate Collaboration contains the Business Rules displayed in Figure 35.

Figure 35 jcdTableUpdate

6.5.6 Binding the eWay Components

The final step in creating a Connectivity Map is binding the eWay components together.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Steps required to bind eWay components together:

1 Double-click a Connectivity Map—in this example cmDelete—in the Project

Explorer tree. The cmDelete Connectivity Map appears in the Enterprise Designers

canvas.

2 Drag and drop the jcdDelete Collaboration from the Project Explorer to the

jcdDelete Service. The Service icon “gears” change from red to green.

3 Double-click the jcdDelete Service. The jcdDelete Binding dialog box appears.

4 Map the input FileClient (under Implemented Services) to the FileClientIN (File)

External Application. To do this, click on FileSender in the jcdDelete Binding

dialog box, and drag the cursor to the FileClientIN External Application in the

Connectivity Map. A link is now visible between FileClientIN and jcdDelete.

5 From the jcdDelete Binding dialog box, map otdJDBC_1 (under Invoked Services)

to the esJDBCOUT External Application.

6 From the jcdDelete Binding dialog box, map FileClient_1 to the FileClientOUT

External Application, as seen in Figure 36.

Figure 36 Connectivity Map - Associating (Binding) the Project’s Components

7 Minimize the jcdDelete Binding dialog box by clicking the chevrons in the upper-

right corner.

8 Save your current changes to the Repository, and then repeat this process for each of

the other Connectivity Maps.

6.5.7 Creating an Environment

Environments include the external systems, Logical Hosts, Integration Servers and

message servers used by a Project and contain the configuration information for these

components. Environments are created using the Enterprise Designer’s Environment

Editor.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Steps required to create an Environment:

1 From the Enterprise Designer’s Enterprise Explorer, click the Environment

Explorer tab.

2 Right-click the Repository and select New Environment. A new Environment is

added to the Environment Explorer tree.

3 Rename the new Environment to envJDBCProj.

4 Right-click envJDBCProj and select New > JDBC External System. Name the

External System esJDBC. Click OK. esJDBC is added to the Environment Editor.

5 Right-click envJDBCProj and select New > File External System. Name the

External System esFileClient. Click OK. esFileClient is added to the Environment

Editor.

6 Right-click envJDBCProj and select New > Logical Host. The LogicalHost1 box is

added to the Environment and LogicalHost1 is added to the Environment Editor

tree.

7 Right-click LogicalHost1 and select New > Sun SeeBeyond Integration Server. A

new Integration Server (IntegrationSvr1) is added to the Environment Explorer tree

under LogicalHost1. See Figure 37.

Figure 37 Environment Editor - envJDBCProj

8 Save your current changes to the Repository.

6.5.8 Configuring the eWays

eWays facilitate communication and movement of data between the external

applications and the eGate system. Each Connectivity Map in the prjJDBC_JCD

sample Project uses three eWays that are represented as nodes between the External

Applications and the Business Process. See Figure 38.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

You must configure eWay properties in both the Connectivity Map and the

Environment Explorer.

Figure 38 eWays in the cmDelete Connectivity Map

eaJDBCOUT eWay

FileClientIN eWay

FileClientOUT eWay

Configuring the eWay Properties

Steps required to configure the eWay properties:

1 Double-click the FileClientIN eWay on each of the Connectivity Maps and modify

the properties for your system, as seen in T a ble 15. Click OK to close the Properties

Editor.

Table 15 FileClientIN eWay Property Settings

Connectivity Map

cmDelete

Property Name

Input file name

Required Value

TriggerDelete.in

cmInsert

Input file name

TriggerInsert.in

cmPsSelect

cmTableSelect

cmUpdate

TriggerPsSelect.in

TriggerTableSelect.in

TriggerUpdate.in

2 Double-click the FileClientOUT eWay on each of the Connectivity Maps and

modify the properties for your system, as seen in Table 16. Click OK to close the

Properties Editor.

Table 16 FileClientOUT eWay Property Settings

Connectivity Map

cmDelete

Property Name

Output file name

Required Value

JCD_Delete_output%d.dat

JCD_Insert_output%d.dat

JCD_PsSelect_output%d.dat

JCD_TableSelect_output%d.dat

cmInsert

Output file name

cmPsSelect

cmTableSelect

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Table 16 FileClientOUT eWay Property Settings (Continued)

Connectivity Map

cmUpdate

Property Name

Output file name

Required Value

JCD_Update_output%d.dat

Configuring the Environment Explorer Properties

Steps required to configure the Environment Explorer properties:

1 From the Environment Explorer tree, right-click the JDBC External System

(esJDBC in this sample), and select Properties. The Properties Editor opens to the

JDBC eWay Environment configuration.

2 Modify the JDBC eWay Environment configuration properties for your system, as

seen in T a ble 17, and click OK.

Table 17 JDBC eWay Environment Properties

Section

Property Name

ServerName

Required Value

Configuration > Inbound

JDBC eWay > JDBC

Enter the host name of the

database server being used.

Connector settings

DatabaseName

Enter the name of the particular

database that is being used on the

server.

User

Enter the user account name for

the database.

Password

Enter the user account password

for the database.

3 From the Environment Explorer tree, right-click the File External System

(esFileClient in this sample), and select Properties. The Properties Editor opens to

the File eWay Environment configuration.

4 Modify the File eWay Environment configuration properties for your system, as

seen in T a ble 18, and click OK.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Table 18 File eWay Environment Properties

Section

Property Name

Directory

Required Value

Configuration > Inbound

File eWay > Parameter

Settings

Enter the directory that contains

the input files (trigger files

included in the sample Project).

Trigger files include:

ƒ TriggerDelete.in.~in

ƒ TriggerInsert.in.~in

ƒ TriggerPsSelect.in.~in

ƒ TriggerTableSelect.in.~in

ƒ TriggerPsUpdate.in.~in

Configuration > Outbound

File eWay > Parameter

Settings

Directory

Enter the directory where output

files are written. In this sample

Project, the output files include:

ƒ JCD_Delete_output0.dat

ƒ JCD_Insert_output0.dat

ƒ JCD_PsSelect_output0.dat

ƒ JCD_TableSelect_output0.dat

ƒ JCD_PsUpdate_output0.dat

Configuring the Integration Server

You must set your SeeBeyond Integration Server Password property before deploying

your Project.

1 From the Environment Explorer, right-click IntegrationSvr1 under your Logical

Host, and select Properties from the shortcut menu. The Integration Server

Properties Editor appears.

2 Click the Password property field under Sun SeeBeyond Integration Server

Configuration. An ellipsis appears in the property field.

3 Click the ellipsis. The Password Settings dialog box appears.

4 Enter STC as the Specific Value and as the Confirm Password, and click OK.

5 Click OK to accept the new property and close the Properties Editor.

For more information on deploying a Project see the Sun SeeBeyond Java™ Composite

Application Platform Suite Deployment Guide.

6.5.9 Creating the Deployment Profile

A Deployment Profile is used to assign services and message destinations to the

Integration Server and message server. Deployment profiles are created using the

Deployment Editor.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Steps required to create the Deployment Profile:

1 From the Enterprise Explorer’s Project Explorer, right-click the prjJDBC_JCD

Project and select New > Deployment Profile.

2 Enter a name for the Deployment Profile (for this sample dpJDBC_JCD). Select

envJDBCProj as the Environment and click OK.

3 From the Deployment Editor toolbar, click the Automap icon. The Project’s

components are automatically mapped to their system windows. See Figure 39.

Figure 39 Deployment Profile

6.5.10 Creating and Starting the Domain

To build and deploy your Project, you must first create a domain. A domain is an

instance of a Logical Host. After the domain is created, the Project is built and then

deployed.

Note: You are only required to create a domain once when you install the Sun Java

Composite Application Platform Suite.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.5

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_JCD Sample Project

Steps required to create and start the domain:

1 Navigate to your <JavaCAPS51>\logicalhost directory (where <JavaCAPS51> is

the location of your Sun Java Composite Application Platform Suite installation).

2 Double-click the domainmgr.bat file. The Domain Manager appears.

3 If you have already created a domain, select your domain in the Domain Manager

and click the Start an Existing Domain button. Once your domain is started, a

green check mark indicates that the domain is running. Your domain will continue

to run unless you shut it down.

4 If there are no existing domains, a dialog box indicates that you can create a domain

now. Click Yes. The Create Domain dialog box appears.

5 Make any necessary changes to the Create Domain dialog box and click Create. The

new domain is added to the Domain Manager. Select the domain and click the Start

an Existing Domain button. Once your domain is started, a green check mark

indicates that the domain is running.

For more information about creating and managing domains see the eGate Integrator

System Administration Guide.

6.5.11 Building and Deploying the Project

The Build process compiles and validates the Project’s Java files and creates the Project

EAR file.

Build the Project

1 From the Deployment Editor toolbar, click the Build icon.

2 If there are any validation errors, a Validation Errors pane will appear at the bottom

of the Deployment Editor and displays information regarding the errors. Make any

necessary corrections and click Build again.

3 After the Build has succeeded you are ready to deploy your Project.

Deploy the Project

1 From the Deployment Editor toolbar, click the Deploy icon. Click Yes when the

Deploy prompt appears.

2 A message appears when the project is successfully deployed. You can now test

your sample.

6.5.12 Running the Sample

Additional steps are required to run the deployed sample Project.

Steps required to run the sample Project:

1 Rename one of the trigger files included in the sample Project from

<filename>.in.~in to <filename>.in to run the corresponding operation.

The File eWay polls the directory every five seconds for the input file name (as

defined in the Inbound File eWay Properties window). The JCD then transforms the

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

data, and the File eWay sends the output to an Output file name (as defined in the

outbound File eWay Properties window).

The Where Clause defined in the business rule recognizes the trigger as a

placeholder for input, allowing a set condition, such as emp_no = 100, to determine

the type of output data.

You can modify the following input files to view different output.

Š TriggerTableSelect.in

Š TriggerDelete.in

Š TriggerPsUpdate.in

Having no content in these files causes the operation to read all records.

2 Verify the output data by viewing the sample output files. See About the JDBC

eWay Sample Projects on page 69 for more details on the types of output files used

in this sample Project. The output files may change depending on the number of

times you execute the sample Project, the input file, and also the content of your

database table.

6.6

Building and Deploying the prjJDBC_BPEL Sample

Project

The following provides step-by-step instructions for manually creating the

prjJDBC_BPEL sample Project.

Steps required to create the sample project include:

ƒ Creating a Project on page 95

ƒ Creating the OTDs on page 96

ƒ Creating the Business Process on page 97

ƒ Creating the Connectivity Map on page 107

ƒ Creating an Environment on page 109

ƒ Configuring the eWays on page 110

ƒ Creating the Deployment Profile on page 113

ƒ Creating and Starting the Domain on page 114

ƒ Building and Deploying the Project on page 115

ƒ Running the Sample Project on page 115

6.6.1 Creating a Project

The first step is to create a new Project in the Enterprise Designer.

1 Start the Enterprise Designer.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

2 From the Project Explorer tree, right-click the Repository and select New Project. A

new Project (Project1) appears on the Project Explorer tree.

3 Right-click Project1 and select Rename from the shortcut menu. Rename the Project

(for this sample, prjJDBC_BPEL).

6.6.2 Creating the OTDs

The sample Project requires three OTDs to interact with the JDBC eWay. These OTDs

include:

ƒ JDBC Database OTD

ƒ Inbound DTD OTD

ƒ Outbound DTD OTD

Steps required to create a JDBC Database OTD include:

1 Right-click your new Project in the Enterprise Designer’s Project Explorer, and

select New > Object Type Definition.

The New Object Type Definition Wizard window appears.

2 Select the JDBC Database OTD Wizard from the list of OTD Wizards and click

Next.

3 Enter the connection information for the JDBC database. Connection fields include:

Š Driver Jar Files

Š Driver Java Class Name

Š URL Connection String

Š User name

Š Password

4 Click Next, and select the types of database object you want to include in the

sample Project. For this example, select the following:

Š Tables/Views/Aliases

Š Prepared Statements

5 Click Add to select tables from the JDBC database. The Add Tables window

appears.

6 Search for or type in the name of the database. In this example we use the

DB_EMPLOYEE table. Click Select when the database appears in the Results

selection frame. Click OK to close the Add Tables window

7 Click Next the Add Prepared Statements Wizard appears.

8 Click Add, the Add Prepared Statement window appears. Enter the following:

Š Prepared Statement Name: Select_ps

Š SQL Statement:

select * from db_employee where emp_no > ? order by emp_no

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Note: In our example, the SQL statement includes the ? placeholder for input. This

placeholder represents the value for the Where Clause.

9 Click the OK button to close the Prepared Statement window, and then click Next

on the Prepared Statements Wizard window.

10 Enter an OTD name. In this example, we use otdJDBC.

11 Click Next and review your settings, then click Finish to create the OTD.

Steps required to create inbound and outbound DTD OTDs:

1 Right-click your new Project in the Enterprise Designer’s Project Explorer, and

select New > Object Type Definition.

The New Object Type Definition Wizard window appears.

2 Select DTD from the list of OTD Wizards and click Next.

3 Browse to and then select a DTD file. For our example, select one of the following

DTD files from the sample Project, and then click Next.

Š otdInputDTD.dtd

Š otdOutputDTD.dtd

4 The file you select appears in the Select Document Elements window. Click Next.

5 Click Finish to complete the DTD based OTD. Repeat this process again to create

the second DTD file.

6.6.3 Creating the Business Process

Steps required to create the Business Process include:

ƒ Creating the business process flow

ƒ Configuring the modeling elements

Creating the Business Process Flow

The business process flow contains all the BPEL elements that make up a business

process.

Steps to create a business process flow include:

1 Right-click your new Project in the Enterprise Designer’s Project Explorer, and

select New > Business Process from the shortcut menu. The eInsight Business

Process Designer appears and BusinessProcess1 is added to the Project Explorer

tree. Rename BusinessProcess1 to bpelPsInsert.

2 Create three additional business processes and rename them as follows:

Š bpelUpdate

Š bpelDelete

Š bpTableSelect

3 Add the following Activities to the Business Process Designer canvas.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Table 19 Business Process Activities

Business Process

Activity

bpelPsInsert

ƒ FileClient.Receive

ƒ FileClient.Write

ƒ otdInputDTD_DBemployees.unmarshal

ƒ otdJDBC.Insert_PsPSInsert

ƒ FileClient.Write

bpelUpdate

bpelDelete

ƒ FileClient.receive

ƒ FileClient.write

ƒ otdJDBC.DB_EMPLOYEEUpdate

ƒ FileClient.write

ƒ FileClient.receive

ƒ FileClient.write

ƒ otdJDBC.DB_EMPLOYEEDelete

ƒ FileClient.write

bpelTableSelect

ƒ FileClient.receive

ƒ FileClient.write

ƒ otdJDBC.DB_EMPLOYEESelectAll

ƒ otdInputDTD_DBemployees.marshal

ƒ FileClient.write

Configuring the bpelPsInsert Modeling Elements

Business Rules, created between the Business Process Activities, allow you to configure

the relationships between the input and output Attributes of the Activities using the

Business Process Designer’s Business Rule Designer.

Once you have connected the modeling elements together, begin adding the business

processes necessary to facilitate the Insert operation. See Figure 40 for an illustration of

how all the modeling elements appear when connected.

Note: Review the eInsight Business Process Manager User’s Guide for a more detailed

description of the steps required to connect and add business rules to a modeling

elements in a business process.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Figure 40 bpelPsInsert Business Process

Steps required to configure the bpelPsInsert business process:

1 Configure the business rule between the FileClient.receive and FileClient.write

Activities, as seen in Figure 41.

Figure 41 bpelPsInsert Business Rule # 1

2 Configure the business rule between the FileClient.write Activity and

otdInputDTD_DBemployees.unmarshal Activity, as seen in Figure 42.

Figure 42 bpelPsInsert Business Rule # 2

3 Configure the business rule between otdInputDTD_DBemployees.unmarshal and

the otdJDBC.Insert_psPSInsert Activity, as seen in Figure 43.

JDBC/ODBC eWay Adapter User’s Guide

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Figure 43 bpelPsInsert Business Rule # 3

4 Configure the business rule between the otdJDBC.Insert_psPSInsert Activity and

the FileClient.write Activity, as seen in Figure 44.

Figure 44 bpelPsInsert Business Rule # 4

Configuring the bpelUpdate Modeling Elements

The bpelUpdate business process describes how to update a record in the JDBC

database using the Business Process Designer.

Once you have connected the modeling elements together, begin adding the business

processes necessary to facilitate the Update operation. Figure 45 illustrates how all the

modeling elements appear when connected.

Note: The where clause in the business rule reads the trigger value as a placeholder for

input. This permits you to modify the query to select a specific record. Also note that

all records are selected from the database when the TriggerUpdate.in file is empty.

JDBC/ODBC eWay Adapter User’s Guide

100

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Note: Review the eInsight Business Process Manager User’s Guide for a more detailed

description of the steps required to connect and add business rules to a modeling

elements in a business process.

Figure 45 bpelUpdate Business Process

Steps required to configure the bpelUpdate business process:

1 Configure the business rule between the FileClient.receive and FileCleint.write

Activities, as seen in Figure 46.

Figure 46 bpelUpdate Business Rule # 1

2 Configure the business rule between the FileClient.write Activity and

otdJDBC.DB_EMPLOYEEUpdate Activity, as seen in Figure 47.

JDBC/ODBC eWay Adapter User’s Guide

101

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Figure 47 bpelUpdate Business Rule # 2

3 Configure the business rule between otdJDBC.DB_EMPLOYEEUpdate and the

FileClient.write Activity, as seen in Figure 48.

Figure 48 bpelUpdate Business Rule # 3

Configuring the bpelDelete Modeling Elements

The bpelDelete business process describes how to delete a record in the JDBC database

using the Business Process Designer.

Once you have connected the modeling elements together, begin adding the business

processes necessary to facilitate the Delete operation. See Figure 49 for an illustration of

how all the modeling elements appear when connected.

Note: The where clause in the business rule reads the trigger value as a placeholder for

input. This permits you to modify the query to select a specific record. Also note that

all records are selected from the database when the TriggerDelete.in file is empty.

JDBC/ODBC eWay Adapter User’s Guide

102

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Note: Review the eInsight Business Process Manager User’s Guide for a more detailed

description of the steps required to connect and add business rules to a modeling

elements in a business process.

Figure 49 bpelDelete Business Process

Steps required to configure the bpelDelete business process:

1 Configure the business rule between the FileClient.receive and FileClient.write

Activities, as seen in Figure 50.

Figure 50 bpelDelete Business Rule # 1

2 Configure the business rule between the FileClient.write Activity and

otdJDBC.DB_EMPLOYEEDelete Activity, as seen in Figure 51.

Figure 51 bpDelete Business Rule # 2

JDBC/ODBC eWay Adapter User’s Guide

103

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

3 Configure the business rule between the otdJDBC.DB_EMPLOYEEDelete Activity

and the FileClient.write Activity, as seen in Figure 52.

Figure 52 bpelDelete Business Rule # 3

Configuring the bpelTableSelect Modeling Elements

The bpelTableSelect business process is describes how to select all records the JDBC

database using the Business Process Designer.

Once you have connected the modeling elements together, begin adding the business

processes necessary to facilitate the SelectAll operation. See Figure 53 for an illustration

of how all the modeling elements appear when connected.

Note: The where clause in the business rule reads the trigger value as a placeholder for

input. This permits you to modify the query to select a specific record. Also note that

all records are selected from the database when the TriggerTableSelect.in file is

empty.

Note: Review the eInsight Business Process Manager User’s Guide for a more detailed

description of the steps required to connect and add business rules to a modeling

elements in a business process.

Figure 53 bpelTableSelect Business Process

Steps required to configure the bpelTableSelect business process:

1 Configure the business rule between the FileClient.receive and FileCleint.write

Activities, as seen in Figure 54.

JDBC/ODBC eWay Adapter User’s Guide

104

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Figure 54 bpelTableSelect Business Rule # 1

2 Configure the business rule between the FileClient.write Activity and

otdJDBC.DB_EMPLOYEESelectAll Activity, as seen in Figure 55.

Figure 55 bpelTableSelect Business Rule # 2

3 Configure the business rule between the otdJDBC.DB_EMPLOYEESelectAll

Activity and the otdInputDTD_DBemployees.marshal Activity, as seen in Figure

56.

JDBC/ODBC eWay Adapter User’s Guide

105

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Figure 56 bpelSelectTable Business Rule # 3

4 Configure the business rule between the otdInputDTD_DBemployees.marshal

Activity and the FileClient.write Activity, as seen in Figure 57.

Figure 57 bpelTableSelect Business Rule # 4

5 Configure the business rule between the FileClient.write Activity and the

FileClient.write Activity, as seen in Figure 58.

Figure 58 bpelTableSelect Business Rule # 5

JDBC/ODBC eWay Adapter User’s Guide

106

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

6.6.4 Creating the Connectivity Map

The Connectivity Map provides a canvas for assembling and configuring a Project’s

components.

Steps required to create the Connectivity Map:

1 From the Project Explorer tree, right-click the new prjJDBC_BPEL Project and select

New > Connectivity Map from the shortcut menu.

2 The New Connectivity Map appears, and a node for the Connectivity Map is added

under the Project on the Project Explorer tree labeled CMap1.

Create three additional Connectivity Maps—CMap2, CMap3, and CMap4—and

rename them as follows:

Š cmDelete

Š cmPsInsert

Š cmTableSelect

Š cmUpdate

The icons in the toolbar represent the available components used to populate the

Connectivity Map canvas.

Populating the Connectivity Map

Add the Project components to the Connectivity Map by dragging the icons from the

toolbar to the canvas.

Each Connectivity Map in the prjJDBC_BPEL sample Project requires the following

components:

ƒ File External Application (2)

ƒ JDBC External Application

ƒ Business Process

Any eWay added to the Connectivity Map is associated with an External System. To

establish a connection to JDBC, first select JDBC as an External System to use in your

Connectivity Map.

To Select a JDBC External System

1 Click the External Application icon on the Connectivity Map toolbar.

2 Select the external systems necessary to create your Project (for this sample, JDBC

and File). Icons representing the selected external systems are added to the

Connectivity Map toolbar.

3 Rename the following components and then save changes to the Repository:

Š File1 to FileClientIN

Š File2 to FileClientOUT

Š JDBC1 to eaJDBCOUT

JDBC/ODBC eWay Adapter User’s Guide

107

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

To Select a JDBC Business Process

1 Drag a business process from the Enterprise Explorer Project Explorer onto the

corresponding Connectivity Map. For example, drag the dbDelete business process

onto the cmDelete Connectivity Map.

2 Save your changes to the Repository

Binding the eWay Components

The final step in creating a Connectivity Map is binding the eWay components together.

Steps required to bind eWay components together:

1 Open one of the Connectivity Maps and double-click a Business Process, for

example the bpelDelete Business Process in the cmDelete Connectivity Map. The

bpelDelete Binding dialog box appears.

2 From the bpelDelete Binding dialog box, map FileSender (under Implemented

Services) to the FileClientIN (File) External Application. To do this, click on

FileSender in the bpDelete Binding dialog box, and drag the cursor to the

FileClientIN External Application in the Connectivity Map. A link is now visible

between FileClientIN and bpelDelete.

3 From the bpelDelete Binding dialog box, map JDBC_otdJDBC (under Invoked

Services) to the eaJDBCOUT External Application.

4 From the bpelDelete Binding dialog box, map FileReceiver to the FileClientOUT

External Application, as seen in Figure 59.

Figure 59 Connectivity Map - Associating (Binding) the Project’s Components

JDBC/ODBC eWay Adapter User’s Guide

108

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

5 Minimize the bpelDelete Binding dialog box by clicking the chevrons in the upper-

right corner.

6 Save your current changes to the Repository, and then repeat this process for each of

the other Connectivity Maps.

6.6.5 Creating an Environment

Environments include the external systems, Logical Hosts, Integration Servers and

message servers used by a Project and contain the configuration information for these

components. Environments are created using the Enterprise Designer’s Environment

Editor.

Steps required to create an Environment:

1 From the Enterprise Designer’s Enterprise Explorer, click the Environment

Explorer tab.

2 Right-click the Repository and select New Environment. A new Environment is

added to the Environment Explorer tree.

3 Rename the new Environment to envJDBCProj.

4 Right-click envJDBCProj and select New > JDBC External System. Name the

External System esJDBC. Click OK. esJDBC is added to the Environment Editor.

5 Right-click envJDBCProj and select New > File External System. Name the

External System esFileClient. Click OK. esFileClient is added to the Environment

Editor.

6 Right-click envJDBCProj and select New > Logical Host. The LogicalHost1 box is

added to the Environment, and LogicalHost1 is added to the Environment Editor

tree.

7 Right-click LogicalHost1 and select New > Sun SeeBeyond Integration Server. A

new Integration Server (IntegrationSvr1) is added to the Environment Explorer tree

under LogicalHost1. See Figure 60).

JDBC/ODBC eWay Adapter User’s Guide

109

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Figure 60 Environment Editor - envJDBCProj

8 Save your current changes to the Repository.

6.6.6 Configuring the eWays

eWays facilitate communication and movement of data between the external

applications and the eGate system. Each Connectivity Map in the The prjJDBC_BPEL

sample Project use three eWays that are represented as a nodes between the External

Applications and the Business Process, as seen in Figure 61.

You must configure eWay properties in both the Connectivity Map and the

Environment Explorer.

Figure 61 eWays in the cmDelete Connectivity Map

FileClientOUT eWay

FileClientIN eWay

eaJDBCOUT eWay

JDBC/ODBC eWay Adapter User’s Guide

110

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Configuring the eWay Properties

Steps required to configure the eWay properties:

1 Double-click the FileClientIN eWay on each of the Connectivity Maps and modify

the properties for your system, as seen in T a ble 20. Click OK to close the Properties

Editor.

Table 20 FileClientIN eWay Property Settings

Connectivity Map

cmDelete

Property Name

Input file name

Required Value

TriggerDelete.in

cmInsert

Input file name

TriggerBpInsert.in

TriggerTableSelect.in

TriggerUpdate.in

cmTableSelect

cmUpdate

2 Double-click the FileClientOUT eWay on each of the Connectivity Maps and

modify the properties for your system, as seen in Table 21. Click OK to close the

Properties Editor.

Table 21 FileClientOUT eWay Property Settings

Connectivity Map

cmDelete

Property Name

Output file name

Required Value

BPEL_Delete_output%d.dat

BPEL_Insert_output%d.dat

BPEL_TableSelect_output%d.dat

BPEL_Update_output%d.dat

cmInsert

Output file name

cmTableSelect

cmUpdate

Configuring the Environment Explorer Properties

Steps required to configure the Environment Explorer properties:

1 From the Environment Explorer tree, right-click the JDBC External System

(esJDBC in this sample), and select Properties. The Properties Editor opens to the

JDBC eWay Environment configuration.

2 Modify the JDBC eWay Environment configuration properties for your system, as

seen in T a ble 22, and click OK.

JDBC/ODBC eWay Adapter User’s Guide

111

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Table 22 JDBC eWay Environment Properties

Section

Property Name

ServerName

Required Value

Configuration > Inbound

JDBC eWay > JDBC

Enter the host name of the

database server being used.

Connector settings

DatabaseName

Enter the name of the particular

database that is being used on the

server.

User

Enter the user account name for

the database.

Password

Enter the user account password

for the database.

3 From the Environment Explorer tree, right-click the File External System

(esFileClient in this sample), and select Properties. The Properties Editor opens to

the JDBC eWay Environment configuration.

4 Modify the File eWay Environment configuration properties for your system, as

seen in T a ble 23, and click OK.

Table 23 File eWay Environment Properties

Section

Property Name

Directory

Required Value

Configuration > Inbound

File eWay > Parameter

Settings

Enter the directory that contains

the input files (trigger files

included in the sample Project).

Trigger files include:

ƒ TriggerBpPsInsert.in.~in

ƒ TriggerDelete.in.~in

ƒ TriggerTableSelect.in.~in

ƒ TriggerBpUpdate.in.~in

Configuration > Outbound

File eWay > Parameter

Settings

Directory

Enter the directory where output

files are written. In this sample

Project, the output files include:

ƒ BPEL_Delete_output0.dat

ƒ BPEL_PsInsert_output0.dat

ƒ BPEL_TableSelect_output0.dat

ƒ BPEL_Update_output0.dat

JDBC/ODBC eWay Adapter User’s Guide

112

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Configuring the Integration Server

You must set your SeeBeyond Integration Server Password property before deploying

your Project.

1 From the Environment Explorer, right-click IntegrationSvr1 under your Logical

Host, and select Properties from the shortcut menu. The Integration Server

Properties Editor appears.

2 Click the Password property field under Sun SeeBeyond Integration Server

Configuration. An ellipsis appears in the property field.

3 Click the ellipsis. The Password Settings dialog box appears.

4 Enter STC as the Specific Value and as the Confirm Password, and click OK.

5 Click OK to accept the new property and close the Properties Editor.

For more information on deploying a Project see the Sun SeeBeyond Java™ Composite

Application Platform Suite Deployment Guide.

6.6.7 Creating the Deployment Profile

A Deployment Profile is used to assign services and message destinations to the

Integration Server and message server. Deployment profiles are created using the

Deployment Editor.

Steps required to create the Deployment Profile:

1 From the Enterprise Explorer’s Project Explorer, right-click the prjJDBC_BPEL

Project and select New > Deployment Profile.

2 Enter a name for the Deployment Profile (for this sample dpJDBC_BPEL). Select

envJDBCProj as the Environment and click OK.

3 From the Deployment Editor toolbar, click the Automap icon. The Project’s

components are automatically mapped to their system windows, as seen in Figure

62.

JDBC/ODBC eWay Adapter User’s Guide

113

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

Figure 62 Deployment Profile

6.6.8 Creating and Starting the Domain

To build and deploy your Project, you must first create a domain. A domain is an

instance of a Logical Host. After the domain is created, the Project is built and then

deployed.

Note: You are only required to create a domain once when you install the Sun Java

Composite Application Platform Suite.

Steps required to create and start the domain:

1 Navigate to your <JavaCAPS51>\logicalhost directory (where <JavaCAPS51> is

the location of your Sun Java Composite Application Platform Suite installation).

2 Double-click the domainmgr.bat file. The Domain Manager appears.

3 If you have already created a domain, select your domain in the Domain Manager

and click the Start an Existing Domain button. Once your domain is started, a

green check mark indicates that the domain is running. Your domain will continue

to run unless you shut it down.

4 If there are no existing domains, a dialog box indicates that you can create a domain

now. Click Yes. The Create Domain dialog box appears.

5 Make any necessary changes to the Create Domain dialog box and click Create. The

new domain is added to the Domain Manager. Select the domain and click the Start

JDBC/ODBC eWay Adapter User’s Guide

114

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

an Existing Domain button. Once your domain is started, a green check mark

indicates that the domain is running.

Note: For more information about creating and managing domains see the eGate

Integrator System Administration Guide.

6.6.9 Building and Deploying the Project

The Build process compiles and validates the Project’s Java files and creates the Project

EAR file.

Build the Project

1 From the Deployment Editor toolbar, click the Build icon.

2 If there are any validation errors, a Validation Errors pane will appear at the bottom

of the Deployment Editor and displays information regarding the errors. Make any

necessary corrections and click Build again.

3 After the Build has succeeded you are ready to deploy your Project.

Deploy the Project

1 From the Deployment Editor toolbar, click the Deploy icon. Click Yes when the

Deploy prompt appears.

2 A message appears when the project is successfully deployed. You can now test

your sample.

6.6.10 Running the Sample Project

Additional steps are required to run the deployed sample Project.

Steps required to run the sample Project:

1 Rename one of the trigger files included in the sample Project from

<filename>.in.~in to <filename>.in to run the corresponding operation.

The File eWay polls the directory every five seconds for the input file name (as

defined in the Inbound File eWay Properties window). The Business Process then

transforms the data, and the File eWay sends the output to an Output file name (as

defined in the outbound File eWay Properties window).

The Where Clause defined in the business rule recognizes the trigger as a

placeholder for input, allowing a set condition, such as emp_no = 100, to determine

the type of output data.

You can modify the following input files to view different output.

Š TriggerTableSelect.in

Š TriggerDelete.in

Š TriggerBpUpdate.in

Having no content in these files causes the operation to read all records.

JDBC/ODBC eWay Adapter User’s Guide

115

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Chapter 6

Section 6.6

Implementing the JDBC/ODBC eWay Sample Projects

Building and Deploying the prjJDBC_BPEL Sample Project

2 Verify the output data by viewing the sample output files. See About the JDBC

eWay Sample Projects on page 69 for more details on the types of output files used

in this sample Project. The output files may change depending on the number of

times you execute the sample Project, the input file, and also the content of your

database table.

JDBC/ODBC eWay Adapter User’s Guide

116

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Drivers are uniquely different in what they do and the type of functions they support.

The JDBC/ODBC eWay allows you to pick and choose which driver is best suited for

your application environment. There can be significant differences and limitations

between drivers. The performance and functionality of the JDBC/ODBC eWay depends

on the selected driver(s). Certain drivers may not support all JDBC features. Consult

the documentation for your respective drivers for more information.

This appendix provides database configuration information and environment

properties specifications for specific JDBC/ODBC drivers. You should use the

information listed in the included tables to define values for required input parameters.

While any standards compliant JDBC/ODBC database driver may be used, the drivers

covered in this chapter are used more frequently. For runtime, only drivers that support

Connection Pool Data Source and XA Data Source are supported. Connection Pool Data

Source takes advantage of the Integration Service's connection pooling in order to

improve performance. For the OTD Wizard, the driver Manager Class will work.

However, not all drivers support all metadata discovery methods, some of which are

needed to build the OTD. Additionally, not all drivers support Updatable ResultSets,

Stored Procedures, or Stored Procedures with ResultSets. Check with your driver

vendor for what is supported. The ConnectionPoolDataSource should only be used for

Outbound eWays. The Inbound eWay uses native JDBC and must use Driver Manager

(see T a ble 6 on page 32).

It is recommended that you use the Oracle eWay when using the native Oracle driver.

The JDBC eWay does not support some of the functions available in the Oracle eWay

such as creating an OTD from a Prepared Statement, using a Stored Procedure with

ResultSets, and CLOB support.

It is also recommended that you use the SQL Server eWay. The JDBC driver available

for download from the Microsoft web site may not contain the latest version from the

vendor.

Not all drivers support Updatable ResultSets. However, it does allow standard Insert

and Update operations when used with the Prepared Statement feature:

Insert into employee (empno) values(?);

Remember to ensure that the input parameter data types match the data types specified

in the database table targeted by the Prepared Statements as some drivers always

return the data type as a string. Optionally, you may perform the data conversion in the

Collaboration.

JDBC/ODBC eWay Adapter User’s Guide

117

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.1

AS/400 Toolbox Driver

What’s In This Chapter:

ƒ AS/400 T o olbox Driver on page 118

ƒ Attunity Driver on page 119

ƒ MySQL Connector/J Driver on page 121

ƒ PostgreSQL Driver on page 122

ƒ SyBase JConnect Driver on page 124

ƒ Sequelink DataDirect Informix ODBC Driver on page 125

ƒ Sequelink DataDirect MS Access ODBC Driver on page 126

ƒ T e radata Driver on page 128

ƒ Installing JDBC/ODBC Drivers on page 129

ƒ T r oubleshooting on page 130

Refer to the supplied Readme.txt file for information regarding the location of the

required driver files necessary to connect using the JDBC/ODBC eWay.

A.1

AS/400 Toolbox Driver

Configuration Properties:

ƒ OTD Wizard: Database Connection Information on page 118

ƒ Environment Properties on page 119

A.1.1 OTD Wizard: Database Connection Information

To connect to AS/400, use the information provided in T a ble 24 to complete the

Connect to Database step of the JDBC/ODBC OTD Wizard. To access DB2, it is

recommended to use the DB2 eWay Adapter or the DB2 Connect eWay Adapter.

Table 24 AS/400 Database Connection Information

Parameter

Driver Jar Files

Value

jt400.jar

Driver Java Class Name

URL Connection String

com.ibm.as400.access.AS400JDBCDriver

jdbc:as400://<server-name>:<server-port>/

Note: NOTE: Default server port is 446.

User Name

Password

Password associated with the login account name used to

connect to the AS/400 database.

JDBC/ODBC eWay Adapter User’s Guide

118

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.2

Attunity Driver

A.1.2 Environment Properties

Use Table 25 to configure the environment properties for the specified JDBC/ODBC

driver.

Table 25 AS/400 Database Environment Properties

Parameter

Description

Value

JDBC Connection Pool Datasource

ClassName

com.ibm.as400.access.AS400JDBCConnectionPoolDataSource

ClassNamefor

OtherInterfaces

ServerName

PortNumber

Server name of the machine hosting the database.

<server-port>

Note: NOTE: Default server port is 446.

DatabaseName

User

Password

Password associated with the login account name used to

connect to the database.

DriverProperties

Delimiter

The default is #.

DataSourceName

MinPoolSize

MaxPoolSize

MaxIdleTime

The default is 0.

The default is 10.

The default is 0.

A.2

Attunity Driver

Configuration Properties:

ƒ OTD Wizard: Database Connection Information on page 119

ƒ Environment Properties on page 120

A.2.1 OTD Wizard: Database Connection Information

To connect to Attunity, use the information provided in T a ble 26 to complete the

Connect to Database step of the JDBC/ODBC OTD Wizard.

JDBC/ODBC eWay Adapter User’s Guide

119

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.2

Attunity Driver

Table 26 Attunity Driver Database Connection Information

Parameter

Value

Driver Jar Files

nvjdbc2.jar

Driver Java Class Name

URL Connection String

com.attunity.jdbc.NvDriver

jdbc:attconnect://<server-name>;DefTdpName=<database-

logical-name>;OneTdpMode=1

Note: The <database-logical-name> is created in

the Attunity server.

User Name

Password

Leave password field blank. Value configured when the

database entry is created in the Attunity Server.

Leave password field blank. Value configured when the

database entry is created in the Attunity Server.

A.2.2 Environment Properties

Use Table 27 to configure the environment properties for the specified JDBC/ODBC

driver.

Table 27 Attunity Driver Database Environment Properties

Parameter

Description

Value

JDBC Connection Pool Datasource

com.attunity.jdbc.NvXADataSource

ClassName

ClassNamefor

OtherInterfaces

ServerName

PortNumber

Server name of the machine hosting the database.

<server-port>

Note: NOTE: Default server port is 2551.

DatabaseName

User

<database-name>

Leave user field blank. Value configured when the database

entry is created in the Attunity Server.

Password

Leave password field blank. Value configured when the

database entry is created in the Attunity Server.

DriverProperties

setDefTdpName#<database-logical-

name>##setWorkspace#Navigator##

Delimiter

The default is #.

DataSourceName

MinPoolSize

MaxPoolSize

The default is 0.

The default is 10.

JDBC/ODBC eWay Adapter User’s Guide

120

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.3

MySQL Connector/J Driver

Table 27 Attunity Driver Database Environment Properties (Continued)

Parameter

MaxIdleTime

Value

The default is 0.

A.3

MySQL Connector/J Driver

Configuration Properties:

ƒ OTD Wizard: Database Connection Information on page 121

ƒ Environment Properties on page 121

A.3.1 OTD Wizard: Database Connection Information

To connect to MYSQL, use the information provided in T a ble 28 to complete the

Connect to Database step of the JDBC/ODBC OTD Wizard.

Table 28 MySQL Connector/J Driver Database Connection Information

Parameter

Driver Jar Files

Value

mysql-connector-java-3.0.11-stable-bin.jar

com.mysql.jdbc.Driver

Driver Java Class Name

URL Connection String

jdbc:mysql://<server-name>:<server-port>/<database-name>

Note: NOTE: Default server port is 3306

User Name

Password

Password associated with the login account name used to

connect to the database.

A.3.2 Environment Properties

Use Table 29 to configure the environment properties for the specified JDBC/ODBC

driver.

Table 29 MySQL Connector/J Driver Environment Properties

Parameter

Description

Value

JDBC Connection Pool Datasource

ClassName

ccom.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSou

rce

ClassNamefor

OtherInterfaces

JDBC/ODBC eWay Adapter User’s Guide

121

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.4

PostgreSQL Driver

Table 29 MySQL Connector/J Driver Environment Properties (Continued)

Parameter

Value

ServerName

PortNumber

Server name of the machine hosting the database.

<server-port>

Note: NOTE: Default server port is 3306.

DatabaseName

User

<database-name>

Password

Password associated with the login account name used to

connect to the database.

DriverProperties

Delimiter

The default is #.

DataSourceName

MinPoolSize

MaxPoolSize

MaxIdleTime

The default is 0.

The default is 10.

The default is 0.

Note: It is not mandatory to enter driver properties in the Outbound JDBC eWay

Environment properties for MySQL.

A.4

PostgreSQL Driver

Configuration Properties:

ƒ OTD Wizard: Database Connection Information on page 122

ƒ Environment Properties on page 123

A.4.1 OTD Wizard: Database Connection Information

To connect to SQL, use the information provided in T a ble 30 to complete the Connect to

Database step of the JDBC/ODBC OTD Wizard. To access SQL, it is recommended to

use the SQL Server eWay Adapter.

Table 30 PostgreSQL Driver Connection Information

Parameter

Driver Jar Files

Value

postgresql-8.0-310.jdbc3.jar

org.postgresql.Driver

Driver Java Class Name

JDBC/ODBC eWay Adapter User’s Guide

122

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.4

PostgreSQL Driver

Table 30 PostgreSQL Driver Connection Information (Continued)

Parameter

Value

URL Connection String

jdbc:postgresql://<server-name>:<server-port>/<database-

name>

Note: NOTE: Default server port is 5432.

User Name

Password

Password associated with the login account name used to

connect to the database.

A.4.2 Environment Properties

Use Table 31 to configure the environment properties for the specified JDBC/ODBC

driver.

Table 31 PostgreSQL Driver Environment Properties

Parameter

Description

Value

JDBC Connection Pool Datasource

ClassName

org.postgresql.jdbc3.Jdbc3ConnectionPool

ClassNamefor

OtherInterfaces

ServerName

PortNumber

Server name of the machine hosting the database.

<server-port>

Note: NOTE: Default server port is 5432.

<database-name>

DatabaseName

User

Password

Password associated with the login account name used to

connect to the database.

DriverProperties

Delimiter

The default is #.

DataSourceName

MinPoolSize

MaxPoolSize

MaxIdleTime

The default is 0.

The default is 10.

The default is 0.

Note: It is not mandatory to enter driver properties in the Outbound JDBC eWay

Environment properties for PostgreSQL.

JDBC/ODBC eWay Adapter User’s Guide

123

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.5

SyBase JConnect Driver

A.5

SyBase JConnect Driver

Configuration Properties:

ƒ OTD Wizard: Database Connection Information on page 124

ƒ Environment Properties on page 124

A.5.1 OTD Wizard: Database Connection Information

To connect to Sybase, use the information provided in T a ble 32 to complete the Connect

to Database step of the JDBC/ODBC OTD Wizard. To access Sybase, it is recommended

to use the Sybase eWay Adapter.

Table 32 Sybase JConnect Driver Database Connection Information

Parameter

Driver Jar Files

Value

jconn2.jar

Driver Java Class Name

URL Connection String

com.sybase.jdbc2.jdbc.SybDriver

jdbc:sybase:Tds:<server-name>:<server-port>

Note: NOTE: Default server port is 4100.

User Name

Password

Password associated with the login account name used to

connect to the database.

A.5.2 Environment Properties

Use Table 33 to configure the environment properties for the specified JDBC/ODBC

driver.

Table 33 Sybase JConnect Driver Environment Properties

Parameter

Description

Value

JDBC Connection Pool Datasource

ClassName

com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource

ClassNamefor

OtherInterfaces

ServerName

PortNumber

Server name of the machine hosting the database.

<server-port>

Note: NOTE: Default server port is 4100.

<database-name>

DatabaseName

User

JDBC/ODBC eWay Adapter User’s Guide

124

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.6

Sequelink DataDirect Informix ODBC Driver

Table 33 Sybase JConnect Driver Environment Properties (Continued)

Parameter

Value

Password

Password associated with the login account name used to

connect to the database.

DriverProperties

Delimiter

The default is #.

DataSourceName

MinPoolSize

MaxPoolSize

MaxIdleTime

The default is 0.

The default is 10.

The default is 0.

Note: It is not mandatory to enter driver properties in the Outbound JDBC eWay

Environment properties for Sybase.

A.6

Sequelink DataDirect Informix ODBC Driver

Configuration Properties:

ƒ OTD Wizard: Database Connection Information on page 125

ƒ Environment Properties on page 126

A.6.1 OTD Wizard: Database Connection Information

The settings in T a ble 34 describe how to use the DataDirect Sequelink JDBC/ODBC

bridge with the JDBC/ODBC eWay. This information demonstrates how Sequelink can

be used to interface with the ODBC driver. To connect to an Informix database, it is

recommended to use the Informix eWay Adapter.

Table 34 Sequelink DataDirect Informix ODBC Driver Database Connection Information

Parameter

Driver Jar Files

Value

sljc.jar

Driver Java Class Name

URL Connection String

com.ddtek.jdbc.sequelkink.SequeLinkDriver

jdbc:sequelink://<server-name>:<server-port>

Note: NOTE: Default server port is 19996.

User Name

Password

Password associated with the login account name used to

connect to the database.

JDBC/ODBC eWay Adapter User’s Guide

125

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.7

Sequelink DataDirect MS Access ODBC Driver

A.6.2 Environment Properties

Use Table 35 to configure the environment properties for the specified JDBC/ODBC

driver.

Table 35 Sequelink DataDirect Informix ODBC Driver Environment Properties

Parameter

Description

Value

JDBC Connection Pool Datasource

ClassName

com.ddtek.jdbcx.sequelkink.SequeLinkDataSource

ClassNamefor

OtherInterfaces

ServerName

PortNumber

Server name of the machine hosting Sequelink.

<server-port>

Note: NOTE: Default server port is 19996.

DatabaseName

User

Password

Password associated with the login account name used to

connect to the database.

DriverProperties

Delimiter

The default is #.

DataSourceName

MinPoolSize

MaxPoolSize

MaxIdleTime

The default is 0.

The default is 10.

The default is 0.

Note: It is not mandatory to enter driver properties in the Outbound JDBC eWay

Environment properties for Sequelink DataDirect Informix ODBC.

A.7

Sequelink DataDirect MS Access ODBC Driver

Configuration Properties:

ƒ OTD Wizard: Database Connection Information on page 127

ƒ Environment Properties on page 127

JDBC/ODBC eWay Adapter User’s Guide

126

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.7

Sequelink DataDirect MS Access ODBC Driver

A.7.1 OTD Wizard: Database Connection Information

To connect to Microsoft Access, via the Microsoft Access ODBC driver, use the

information provided in Table 36 to complete the Connect to Database step of the

JDBC/ODBC OTD Wizard.

Table 36 MS Access ODBC Driver Database Connection Information

Parameter

Driver Jar Files

Value

sljc.jar

Driver Java Class Name

URL Connection String

com.ddtek.jdbc.sequelink.SequeLinkDriver

jdbc:sequelink://<server-name>:<server-port>

Note: NOTE: Default server port is 19996.

User Name

Password

Password associated with the login account name used to

connect to the database.

A.7.2 Environment Properties

Use Table 37 to configure the environment properties for the specified JDBC/ODBC

driver.

Table 37 MS Access ODBC Driver Environment Properties

Parameter

Description

Value

JDBC Connection Pool Datasource

ClassName

com.ddtek.jdbcx.sequelkink.SequeLinkDataSource

ClassNamefor

OtherInterfaces

ServerName

PortNumber

Server name of the machine hosting Sequelink.

<server-port>

Note: NOTE: Default server port is 19996.

DatabaseName

User

Password

Password associated with the login account name used to

connect to the database.

DriverProperties

Delimiter

The default is #.

DataSourceName

MinPoolSize

The default is 0.

MaxPoolSize

The default is 10.

JDBC/ODBC eWay Adapter User’s Guide

127

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.8

Teradata Driver

Table 37 MS Access ODBC Driver Environment Properties (Continued)

Parameter

MaxIdleTime

Value

The default is 0.

Note: It is not mandatory to enter driver properties in the Outbound JDBC eWay

Environment properties for Sequelink DataDirect MS Access ODBC.

A.8

Teradata Driver

Configuration Properties:

ƒ OTD Wizard: Database Connection Information on page 128

ƒ Environment Properties on page 128

A.8.1 OTD Wizard: Database Connection Information

To connect to Teradata, via the Teradata driver, use the information provided in T a ble

38 to complete the Connect to Database step of the JDBC/ODBC OTD Wizard.

Table 38 Teradata Driver Database Connection Information

Parameter

Driver Jar Files

Value

teradata.jar

Driver Java Class Name

URL Connection String

com.ncr.teradata.TeraDriver

jdbc:teradata://<server-name>:<server-port>/<database-server-

name>

Note: NOTE: Default server port is 6666 for the

Type-3 driver Gateway.

User Name

Password

Password associated with the login account name used to

connect to the database.

A.8.2 Environment Properties

Use Table 39 to configure the environment properties for the specified JDBC/ODBC

driver.

Table 39 Teradata Driver Environment Properties

Parameter

Description

Value

JDBC Connection Pool Datasource

ClassName

com.ncr.teradata.TeraConnectionPoolDataSource

JDBC/ODBC eWay Adapter User’s Guide

128

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.9

Installing JDBC/ODBC Drivers

Table 39 Teradata Driver Environment Properties (Continued)

Parameter

Value

ClassNamefor

OtherInterfaces

ServerName

PortNumber

Server name of the machine hosting the database.

<server-port>

Note: NOTE: Default server port is 6666 for the

Type-3 driver Gateway.

DatabaseName

User

<database-name>

Password

Password associated with the login account name used to

connect to the database.

DriverProperties

setURL#jdbc:teradata://<server-name>:<server-port>/

<database-server-name>##setDSName#<database-

server_name>##

Delimiter

The default is #.

DataSourceName

MinPoolSize

MaxPoolSize

MaxIdleTime

The default is 2.

The default is 10.

The default is 0.

A.9

Installing JDBC/ODBC Drivers

The database drivers specified in your projects need to be installed on both the

Enterprise Designer machine and the Logical host machine. When installing the drivers

on the Enterprise Designer machine, you must specify the absolute path to the driver.

When installing the drivers on the Logical Host, place the driver into the Logical Host

stcisdirectory:

<JavaCAPS51>\logicalhost\is\lib; or

<JavaCAPS51>\logicalhost\is\domains\domain1\lib

where <JavaCAPS51> is the location of your Sun Java Composite Application Platform

Suite installation.

The driver file must be copied to the latter folder if you are running multiple domains

and wish to specify a driver for each domain. Otherwise, you only need to copy the

driver file to the former folder address.

For procedures on how to install database drivers, see “Sample Projects Drivers” on

page 72.

JDBC/ODBC eWay Adapter User’s Guide

129

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Appendix A

JDBC/ODBC Drivers

Section A.10

Troubleshooting

A.10

Troubleshooting

Refer to the following when troubleshooting Driver issues.

ƒ The ReceiveOne operation in BPEL is not supported when using inbound functions

with some drivers.

ƒ Some drivers do not support Updatable ResultSets. If you find this to be the case,

use a Prepared Statement to Update, Insert, and Delete data.

ƒ Not all drivers provide metadata information such as column names and data

types. If your table does not have column names and data types, add them before

saving the OTD.

JDBC/ODBC eWay Adapter User’s Guide

130

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Index

delete(String sWhere) 59

deleteRow() 59

insert() 59

insertRow() 59

select(String where) 59

update(String sWhere) 59

updateRow() 59

Index

database OTD wizard

add prepared statement 52

editing existing OTDs 56

review selections 55

select procedures 48

select tables/views 44

specify the OTD name 55

DataDirect 125, 126

Deployment Profile

Automap 93, 113

activity input and output 57

Add Prepared Statements 52

alert codes, viewing 22

AS/400 Driver 118

Attunity Driver 119

Automap 93, 113

driver class, JDBC 33, 35, 38

Drivers 117

AS/400 118

Attunity 119

installing 129

MySQL Connector/J 121

PostgreSQL Driver 122

Sequelink Informix ODBC 125

Sequelink MS Access ODBC 126

Sybase JConnect 124

Teradata 128

binding

dialog box 88, 109

BPEL operations 57

Delete 57

Insert 57

ReceiveOne 57

SelectAll 57

SelectMultiple 57

SelectOne 57

Update 57

eWay Connectivity Map 25, 30

eWay environment properties 29

eWay plug-ins, installing 21

Collaboration

editor 78

eWay Properties

configuring JDBC eWay 25

connection retry settings, outbound 34, 37, 39

Connectivity Map

Inbound JDBC eWay Properties 32

Outbound JDBC eWay Properties 32, 35, 37

Inbound JDBC eWay Properties 32

Outbound JDBC eWay Properties 32, 35, 37

conventions, text 15

Importing sample Projects 73

Inbound JDBC eWay Properties 32

installation 17

Installing

database operations (BPEL) 57

activity input and output 57

Delete 57

alert codes 22

eWay plug-ins 21

migration procedures 19

Repository on UNIX 17

sample Projects and Javadocs 19

Insert 57

ReceiveOne 57

SelectAll 57

SelectMultiple 57

SelectOne 57

Update 57

Javadocs, installing 19

database operations (JCD) 59

JDBC/ODBC eWay Adapter User’s Guide

131

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Index

JCD operations 59

delete(String sWhere) 59

deleteRow() 59

ResultSet

collaboration usability for a stored procedure 66

ResultSet methods

insert() 59

insertRow() 59

select(String where) 59

update(String sWhere) 59

updateRow() 59

available 65

enableResultSetandUpdateCounts 65

enableResultSetOnly 65

enableUpdateCountsOnly 65

getUpdateCount 65

next 65

JDBC

driver class 33, 35, 38

JDBC eWay Project

building and deploying (BPEL) 95

eInsight and eGate components 72

Importing 73

running sample projects 94, 115

running the SQL script 73

JDBC_BPEL_Sample 69

resultsAvailable 65

sample Projects 73

sample projects, installing 19

Select Database Objects 43

Select Procedures 49

Select Table/Views 44

Sequelink Informix ODBC Driver 125

Sequelink MS Access ODBC Driver 126

Setting Properties

migration procedures 19

MySQL Connector/J Driver 121

configuring JDBC eWay 25

connection retry settings 34, 37, 39

eWay Connectivity Map 25, 30

eWay environment properties 29

outbound eWay 31

operations 57

OTD, editing existing 56

outbound eWay properties 31

Outbound JDBC eWay Properties 32, 35, 37

outbound XA properties 31

SQL 60

SQL operations, table 60

SQL operations, table Delete 63

SQL operations, table Insert 61

SQL operations, table Select 60

SQL operations, table Update 62

Stored Procedure

PostgreSQL Driver 122

prepared statement

batch operations 67

executing 67

executing 64

manipulating ResultSet and update count 65

supporting documents 15

Sybase JConnect Driver 124

Project

importing 73

properties

ConnectionRetries 34, 37, 39

ConnectionRetryInterval 35, 37, 40

DatabaseName 33, 36, 38

Delimiter 33, 36, 38

Description 31, 32, 33, 35, 38

DriverProperties 33, 36, 38

MaxIdleTime 34, 37, 39

MaxPoolSize 34, 37, 39

MinPoolSize 34, 36, 39

Password 32, 33, 36, 38

PortNumber 33, 36, 38

ServerName 33, 35, 38

User 32, 33, 36, 38

Table

SQL operations 60

SQL operations, Delete 63

SQL operations, Insert 61

SQL operations, Select 60

SQL operations, Update 62

Teradata Driver 128

text conventions 15

Transaction Support Levels 27

Troubleshooting 130

JDBC/ODBC eWay Adapter User’s Guide

132

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Index

update count 65

JDBC/ODBC eWay Adapter User’s Guide

133

Sun Microsystems, Inc.

Download from Www.Somanuals.com. All Manuals Search And Download.

Sharp Flat Panel Television LC 13AV1U User Manual
Shure Microphone Model 550L User Manual
Snapper Snow Blower 522E 522E 522E SS5220E ESS5220E User Manual
Snapper Snow Blower 1696004 User Manual
Sony Stereo System ZS YN7L User Manual
SpeakerCraft Stereo Amplifier VST60 User Manual
Speed Queen Washer NetMaster User Manual
SVAT Electronics Security Camera CMOS BW User Manual
Swann Home Security System DB 815 User Manual
Tannoy Speaker 66D User Manual