5-4 Oracle Fusion Middleware Administrators Guide for Oracle Real-Time Decisions
9.
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 username=db_user_name
■
For Oracle BI EE, there are no required properties. Leave the Properties field blank.
10. Scroll to the bottom of the page. For Test Table, enter the name of an existing table
in the database.
11. Click Test Configuration. If the test fails, go back and check your settings. If the
test succeeds, click Next. 12.
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.
13. Click Finish.
14. Click Activate Changes.
5.2 Testing a New Enterprise Data Source
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:
1.
Start Decision Studio by running eclipse.exe in RTD_HOME\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.
2. Expand the Service Metadata folder, then right-click Data Sources and select New
SQL Data Source .
3. For Display Label, enter a name for the data source you want to test, then click
OK
.
4. 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.
5. 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.
6.
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.
Note: Do not test the connection if you are adding an Oracle BI EE or
Siebel Analytics Server data source. Instead, skip to Step 12.
6
Clustering and High Availability for Oracle Real-Time Decisions 6-1
6
Clustering and High Availability for Oracle Real-Time Decisions
Oracle RTD may be deployed into a cluster to achieve any of the following objectives:
■
Increased processing power
■
Increased memory, to accommodate more concurrent sessions
■
Increased availability in the event of hardware failures Full details of how to set up and use Oracle RTD clusters, both in general and in a high
availability deployment, appear in the section High Availability for Oracle Real-Time Decisions in Oracle Fusion Middleware High Availability Guide.
6-2 Oracle Fusion Middleware Administrators Guide for Oracle Real-Time Decisions
7
Additional Configuration Settings and Starting Client Tools 7-1
7
Additional Configuration Settings and Starting Client Tools
This chapter describes additional configuration settings for Decision Center and Real-Time Decision Server, and provides information about accessing Oracle RTD
client tools.
This chapter contains the following topics:
■
Section 7.1, Decision Center Browser Configuration
