|Oracle® Fusion Middleware Administrator's Guide for Oracle Real-Time Decisions
11g Release 1 (11.1.1)
Part Number E16632-03
|PDF · Mobi · ePub|
JDBC data sources are used by Oracle RTD to access outside data. Data sources are application-server specific, and are used to identify new JDBC data sources that are to be used as suppliers in Inline Services. These data sources can be RDBMS databases, as well as ODBC identified data sources. For information about supported versions for enterprise data sources, see the documents referred to in Section 1.4, "System Requirements and Certification."
This chapter contains the following topics:
If you are running Real-Time Decision Server on WebLogic, follow the steps in this section to configure JDBC data sources so that your Inline Services can access outside data.
This section contains the following topics:
To set the path to JDBC jar files for your data source, you may need to add paths to the Classpath for your Managed Server, if your data source database is different from the Oracle RTD database, and you have not previously edited the Classpath.
If the enterprise data source you want to add is a Teradata data source, copy the files
tdgssconfig.jar to a directory of your choice,
<teradata_jar_files_directory>. You can download these files from the Teradata Web site at
http://www.teradata.com. Make sure that the JDBC driver files you download are compatible with the database version you are using.
Log in to the Administration Console for your Oracle RTD domain.
Navigate the path:
Environment > Servers > managed_server_name > Configuration > Server Start tab.
Add the appropriate path or paths to ClassPath, including Windows or Linux/Unix separators between entries. Do not include spaces between your entries.
Restart the WebLogic Managed Server.
You can use the WebLogic Server Administration Console to create a data source in WebLogic. Before you begin, ensure that WebLogic is started.
To create a data source in WebLogic:
Access the WebLogic Server Administration Console for the WebLogic domain in which Oracle RTD is deployed at the URL
/console. At the login prompt, enter the administrator user name and password.
In the tree on the left, expand Services, then expand JDBC and choose Data Sources.
Click New. You may need to click Lock & Edit first to enable the New button.
The Create a New JDBC Data Source window appears, showing the first page (JDBC Data Source Properties) of a sequence of pages that contain fields you must enter.
On the JDBC Data Source Properties page, follow these steps:
For Name, provide a descriptive name for the data source (for example,
For JNDI Name, enter the same value you provided for Name. This value will appear in Decision Studio when you perform an Import in a data source object.
Set the Database Type.
For Oracle databases, select Oracle.
For SQL Server databases, select MS SQL Server.
For DB2 databases, select DB2.
For other databases, select Other.
Set the Database Driver.
For Oracle databases, select Oracle's Driver (Thin) for Service connections; Versions:9.0.1,9.2.0,10,11.
For SQL Server databases, select Oracle's MS SQL Server Driver (Type 4) Versions:7.0, 2000, 2005, 2008.
For DB2 databases, select Oracle's DB2 Driver (Type 4) Versions:7.X,8.X,9.X.
For other databases, select Other.
On the Transaction Options page:
If you selected a non-XA JDBC driver for the Database Driver, the checkbox Supports Global Transactions appears. Deselect Supports Global Transactions, then click Next.
If you selected an XA JDBC driver for the Database Driver, click Next.
On the Connection Properties page, follow these steps:
For Database Name, enter the name of your database. If you are adding an Oracle BI EE data source, enter any non-empty string; the value does not matter because this property is not used for Oracle BI EE.
For Host Name, enter the name of the computer hosting the database server. If you are adding an Oracle BI EE data source, enter the name of the computer hosting Oracle BI EE.
For Port, enter the port number on the database server used to connect to the database (such as
1433 for SQL Server,
1521 for Oracle Database,
50000 for DB2, or
9703 for Oracle BI EE).
For Database User Name, enter the name of the database run-time user. If you are adding an Oracle BI EE data source, enter the name of an Oracle BI EE user.
For Password, enter the password of the database run-time user. If you are adding an Oracle BI EE data source, enter the password of the Oracle BI EE user. Then, click Next.
On the Test Database Connection page, for Driver Class Name, for Oracle, SQL Server and DB2 databases, accept all default settings. For other databases, enter the full package name of the JDBC driver class used to create the physical database connections in the connection pool (note that this driver class must be in the classpath of any server to which it is deployed):
Oracle BI EE:
For URL, for Oracle, SQL Server and DB2 databases, accept all default settings. For other databases, enter the URL of the database to which you want to connect. The format of the URL varies by data source type:
db_name is missing, the current login user's default database is used. For example, with default database
TMODE=ANSI,CHARSET=ASCII executes as
Oracle BI EE:
Note that the catalog name is required.
In the Properties field, for Oracle, SQL Server and DB2 databases, accept all default settings. For other databases, enter properties and their values required by the JDBC driver. The properties you need to provide vary by data source type:
For Teradata, enter the property
For Oracle BI EE, there are no required properties. Leave the Properties field blank.
Scroll to the bottom of the page. For Test Table, enter the name of an existing table in the database.
Do not test the connection if you are adding an Oracle BI EE or Siebel Analytics Server data source. Instead, skip to Step 12.
Click Test Configuration. If the test fails, go back and check your settings. If the test succeeds, click Next.
Select the server where you want the changes to be made available (for example, RTD_Server). You must perform this step before completing the data source configuration.
Click Activate Changes.
After you add a new enterprise data source, follow the steps in this section to ensure the data source is configured properly. Before you begin, ensure that Oracle RTD is started.
To test a new enterprise data source:
Start Decision Studio by running
\eclipse. Then, create a new Inline Service, or open an existing Inline Service. See the Decision Studio Help for more information about how to do this.
Expand the Service Metadata folder, then right-click Data Sources and select New SQL Data Source.
For Display Label, enter a name for the data source you want to test, then click OK.
Click Import. Then, select the data source you want to test from the JDBC Data Source drop-down list. The list of Tables and Views is updated with tables and view names from that data source.
Select a particular table or view, then click Finish in the Import dialog box. The list of available columns appears in the Output table in the Data Source editor.
Write some basic code to ensure that the actual rows are retrieved from the tables at run time.
If you were not able to complete any of the preceding steps, check your data source configuration settings and try again.