13-4 Oracle Complex Event Processing Visualizer Users Guide
Figure 13–3 Edit Datasource: Data Source Tab
6.
Configure the DataSource tab as Table 13–1
describes.
7. Click the Global Tx Protocol tab.
The Global Tx Protocol tab appears as Figure 13–4
shows.
Table 13–1 Edit Datasource: Data Source Parameters
Parameter Description
Name The name for this data source configuration.
JNDI Name JNDI path to where this data source will be bound. This is the name your
Oracle CEP application uses to look up the data source in JNDI. Global Tx Protocol
Select the protocol for Oracle CEP to use for the transaction branch when processing a global transaction:
■
OnePhaseCommit Default
■
TwoPhaseCommit
■
LoggingLastResource
■
EmulateTwoPhaseCommit
■
None
Managing Data Sources 13-5
Figure 13–4 Edit Datasource: Global Tx Protocol Tab
8.
Configure the Global Tx Protocol tab as Table 13–2
describes.
9. Click the Connection Pool tab.
The Connection Pool tab appears as Figure 13–5
shows.
Table 13–2 Edit Datasource: Global Tx Protocol Parameters
Parameter Description
Database Type Select the type of JDBC driver to use:
■
Derby
■
Oracle
■
SQL Server 2005
■
Other URL
Specify the database connection URL appropriate for your database. This URL includes the name of the database, the host and port of the computer on
which the database server is running, and so on. Oracle CEP populates a default URL for database types it provides.
Driver Name Specify the name of the driver for the selected database type. Oracle CEP
automatically populates the driver name for types it provides. User Name
Specify database user account name that you want to use for each connection in the data source.
Password Specify database user password that you want to use for each connection in
the data source Use XA
Specify whether or not to use distributed transactions:
■
true : enable distributed transactions.
■
false : disable distributed transactions.
13-6 Oracle Complex Event Processing Visualizer Users Guide
Figure 13–5 Edit Datasource: Connection Pool Tab
10. Configure the Connection Pool tab as
Table 13–3 describes.
11. Click Save.
The datasource is updated in the Oracle CEP server configuration.
13.2 Adding a Data Source
You can add a data source using the Oracle CEP Visualizer.
13.2.1 How to Add a Data Source Configuration
Using the Oracle CEP Visualizer, you can add the data source configuration for a selected Oracle CEP server.
Table 13–3 Edit Datasource: Connection Pool Parameters
Parameter Description
Initial Capacity Specify the number of physical connections to create when creating the
connection pool. Max Capacity
Specify the maximum number of physical connections that this connection pool can contain.
Capacity Increment Specify how many connections to add when all the connections in the
connection pool are in use and the connection pool receives a new connection request.
Test Enter the name of a small table to use in a query if you want to test the
database connection before handing it to the requesting application. The standard query is select 1 from table_name. If you prefer to use a
different query as a connection test, enter SQL followed by a space and the SQL code you want to use to test database connections.
Managing Data Sources 13-7
To add a data source configuration: 1.
In the left pane, click the Domain Server node, where Domain refers to the name of your Oracle CEP domain and Server refers to the name of the server instance.
2. In the right pane, click the DataSource tab.
The DataSource tab appears as Figure 13–6
shows.
Figure 13–6 DataSource Tab
3. Click Add.
The New Datasource dialog appears as Figure 13–7
shows. There are three accordion tabs:
■
Data Source : use this tab to identify the data source and specify whether or
not to use a global transaction protocol.
■
Global Tx Protocol : use this tab to specify connection properties and whether
or not to use XA.
■
Connection Pool : use this tab to specify connection pool properties.
4. Click the Data Source tab.
The DataSource tab appears as Figure 13–7
shows.
13-8 Oracle Complex Event Processing Visualizer Users Guide
Figure 13–7 New Datasource: Data Source Tab
5. Configure the DataSource tab as
Table 13–4 describes.
6. Click the Global Tx Protocol tab.
The Global Tx Protocol tab appears as Figure 13–8
shows.
Table 13–4 New Datasource: Data Source Parameters
Parameter Description
Name The name for this data source configuration.
JNDI Name JNDI path to where this data source will be bound. This is the name your
Oracle CEP application uses to look up the data source in JNDI. Global Tx Protocol
Select the protocol for Oracle CEP to use for the transaction branch when processing a global transaction:
■
OnePhaseCommit Default
■
TwoPhaseCommit
■
LoggingLastResource
■
EmulateTwoPhaseCommit
■
None
Managing Data Sources 13-9
Figure 13–8 New Datasource: Global Tx Protocol Tab
7.
Configure the Global Tx Protocol tab as Table 13–5
describes.
8. Click the Connection Pool tab.
The Connection Pool tab appears as Figure 13–9
shows.
Table 13–5 New Datasource: Global Tx Protocol Parameters
Parameter Description
Database Type Select the type of JDBC driver to use:
■
Derby
■
Oracle
■
SQL Server 2005
■
Other URL
Specify the database connection URL appropriate for your database. This URL includes the name of the database, the host and port of the computer on
which the database server is running, and so on. Oracle CEP populates a default URL for database types it provides.
Driver Name Specify the name of the driver for the selected database type. Oracle CEP
automatically populates the driver name for types it provides. User Name
Specify database user account name that you want to use for each connection in the data source.
Password Specify database user password that you want to use for each connection in
the data source Use XA
Specify whether or not to use distributed transactions:
■
true : enable distributed transactions.
■
false : disable distributed transactions.
