Skip Headers
Oracle® Fusion Middleware Creating Domains Using the Configuration Wizard
11g Release 1 (10.3.1)
E14140-02
  Go To Documentation Library
Library
Go To Product List
Product
Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

5 Customizing JDBC Data Sources and Component Schema

When you are creating or extending a domain using the Configuration Wizard, you can change the JDBC data source and JDBC component schema settings if they are defined in the domain or template that you selected as the source for the domain that you are creating or extending.

The following topics describe the steps required to change the JDBC settings in your domain:

Configuring JDBC Data Sources

A JDBC data source contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a data source on the JNDI tree, and then request a connection. When the applications no longer need the connections, they return the connections to the connection pool in the data source.

In the Configure JDBC Data Sources screen, you can configure the JDBC data sources defined in your domain source.


Note:

No databases are defined in the wls.jar template; so, if you selected the WebLogic Server template as the basis for the domain, the Configure JDBC Data Sources window and the Run Database Scripts screens are not displayed.

The JDBC data sources associated with the products for which you are creating the domain are listed in the lower half of the screen.


Note:

To configure one or more of the data sources as RAC multi data sources, select the check box adjacent to the name of the required schema, and select the Configure selected data sources as RAC multi data sources in the next panel check box; then, click the Next button.

  1. Select the data source for which you want to specify settings by selecting the check box adjacent to the data source name.


    Note:

    When you select multiple data sources, the text "Varies among data sources" might be displayed in certain fields, indicating that the current values of those fields are different across the selected data sources. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected data sources.

  2. Review the current configuration settings and modify them as required. Table 5-1 describes the fields of the Configure JDBC Data Sources screen.


    Note:

    The default values of data source parameters such as vendor, driver, host name, and port number depend on the values that are specified in the application templates.

    Table 5-1 Configure JDBC Data Sources

    Field Description

    Vendor

    Select the database vendor.

    Driver

    Select the JDBC driver to use to connect to the database. The list includes common JDBC drivers for the selected database vendor.

    Username

    Enter the account login name for connecting to the database.

    Password

    Enter the login password for the specified username.

    DBMS/Service

    Enter a DBMS SID or service name.

    The value that you must enter depends on the driver that you select.

    • If the name of the Oracle driver that you selected contains the words "for Instance connections," you must enter the SID.

    • If the name of the Oracle driver contains the words "for Service connections," you must enter the service name.

    • For information about configuring DataDirect's driver, see the DataDirect documentation.

    Host Name

    Enter the name of the server hosting the database.

    Port

    Enter the port number to be used to connect to the server.


    The values that you specify are displayed in the appropriate columns in the data source list, for the selected data source.

  3. After updating the settings, do one of the following:

    • To test the data source connections to the specified databases, click Test Connections. The Test Data Source Connections screen is displayed. For more information, see Testing JDBC Data Sources.

    • If you do not want to test the connections to the database, click Next.

Configuring RAC Multi Data Source

In this screen of the Configuration Wizard, you configure the data sources (that are included in the domain) as RAC data sources.

The data sources that you opted to configure as RAC data sources in the previous screen of the wizard (Configure JDBC Data Sources) are listed in the lower half of the screen.

  1. Select the data source for which you want to specify data source settings by selecting the check box adjacent to the data source name.


    Note:

    When you select multiple data sources, the text "Varies among data sources" might be displayed in certain fields, indicating that the current values of those fields are different across the selected data sources. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected data sources.

  2. Specify the settings for the RAC data sources.

    Table 5-2 describes the fields in this screen.

    Table 5-2 Configure JDBC Data Sources

    Field Description

    Driver

    Select the JDBC driver to use to connect to the database.

    Service Name

    Enter a database Oracle RAC service name.

    Username

    Enter the account login name for connecting to the database.

    Password

    Enter the login password for the specified username.

    Host Name

    Enter the name of the server hosting the RAC database instances.

    Instance Name

    Enter the name of each Oracle database instance.

    Port

    Enter the port numbers to be used to connect to the server that hosts the database.



    Note:

    You must specify the host name, instance name, and port number of at least one database instance.

    To add a database instance, click Add, and then specify the host name, instance name, and port.

    The values that you specify are displayed in the appropriate columns in the data source list, for the selected data source.

  3. After making the required selections and entries, click the Next button in the wizard to test the connections to the data sources.

Testing JDBC Data Sources

In the Test JDBC Data Sources screen, you can test the configurations that you specified for the data sources in the previous screen.

  1. Select the check boxes adjacent to the names of the data sources to test.

  2. Click Test Connections for the connection to test.

    The wizard tests the configuration for each data source, by attempting to connect to a URL that is constructed by using the driver, host, port, and other information that you specified while configuring the data source.

    The result of the test is indicated in the Status column. Details are displayed in the Connection Result Log pane.

  3. After testing the connections, click the Next button in the wizard.

Running Database Scripts

A domain template might contain a set of SQL files organized by database type. If the domain template contains SQL files, you can run them while creating the domain, in the Run Database Scripts window. Database content for each of the data sources defined in your domain is set up by using pre-existing SQL or database loading files.


Note:

No databases are defined in the wls.jar template; so, if you selected the WebLogic Server template as the basis for the domain, the Configure JDBC Data Sources window and the Run Database Scripts screens are not displayed.

  1. In the Available JDBC Data Sources pane, select the data source for which you want to run the scripts. The scripts that can be executed are displayed in the Available SQL Files and Database Loading Options.

  2. Select the database version from the DB Version drop-down menu.

  3. Click Run Scripts.

    All the scripts displayed in the Available SQL Files and Database Loading Options pane for the selected data source are executed, and the results are displayed in the Results pane. To capture test output in a log file, select the Log File check box and specify the location of the log file.

  4. Repeat steps 1 through 3 for each data source for which you want to execute SQL scripts.

  5. Click Next.

Configuring JDBC Component Schema

For some Fusion Middleware components (for example, SOA and Web Center Spaces), JDBC data sources might be defined as part of the component's database schema, which are loaded (during installation) by using the Repository Creation Utility (RCU).

When you create a domain for such components by using the Configuration Wizard, you can configure the JDBC component schema settings: database driver, schema owner, password, and so on.

The JDBC component schemas associated with the products for which you are creating the domain (for example, SOA) are listed in the lower half of the screen.


Note:

To configure one or more of the schemas as RAC multi data sources, select the check boxes adjacent to the name of the required schemas, and select the Configure selected component schemas as RAC multi data source schemas in the next panel check box; then, click Next.

  1. Select the schemas for which you want to specify data source settings, by selecting the check box adjacent to the schema names.


    Note:

    When you select multiple component schemas, the text "Varies among component schemas" might be displayed in certain fields, indicating that the current values of those fields are different across the selected component schemas. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected component schemas.

  2. Review the current configuration settings and modify them as required. The following table describes the fields in this screen.


    Note:

    The default values of component schema parameters such as vendor, driver, host name, and port number depend on the values that are specified in the application templates.

    Table 5-3 Configure JDBC Data Sources

    Field Description

    Vendor

    Select the database vendor.

    Driver

    Select the JDBC driver to use to connect to the database. The list includes common JDBC drivers for the selected database vendor.

    Schema Owner

    Enter the account login name for connecting to the database.

    Schema Password

    Enter the login password for the specified schema owner.

    DBMS/Service

    Enter a database DBMS name, or service name if you selected a service type driver.

    Host Name

    Enter the name of the server hosting the database.

    Port

    Enter the port number to be used to connect to the server that hosts the database.


    The values that you specify are displayed in the appropriate columns in the schema list, for the selected schemas.

  3. After making the required selections and entries, click the Next button in the wizard to test the component schemas.

Configuring RAC Multi Data Source Component Schema

In this screen of the Configuration Wizard, you configure the component schemas (that are included in the domain) as RAC multi data sources.

The component schemas that you opted to configure as RAC multi data sources in the previous screen of the wizard (Configure JDBC Component Schema) are listed in the lower half of the screen.

  1. In the schema list in the lower half of the screen, select the schemas to configure as RAC multi data sources, by selecting the check box adjacent to the schema names.


    Note:

    When you select multiple data source schemas, the text "Varies among component schemas" might be displayed in certain fields, indicating that the current values of those fields are different across the selected schemas. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected schemas.

  2. Specify the settings for the data sources.

    Table 5-2 describes the fields in this screen.

    Table 5-4 Configure JDBC Data Sources

    Field Description

    Driver

    Select the JDBC driver to use to connect to the database.

    Service Name

    Enter a database Oracle RAC service name.

    Username

    Enter the account login name for connecting to the database.

    Password

    Enter the login password for the specified username.

    Host Name

    Enter the name of the server hosting the RAC database instances.

    Instance Name

    Enter the name of each Oracle database instance.

    Port

    Enter the port numbers to be used to connect to the server that hosts the database.



    Note:

    You must specify the host name, instance name, and port number of at least one database instance.

    To add a database instance, click Add, and specify the host name, instance name, and port.

    The values that you specify are displayed in the appropriate columns in the schema list, for the selected schemas.

  3. After making the required selections and entries, click Next to test the component schemas.

Testing the Component Schema

In the Test Component Schema screen, you can test the configurations that you specified for the data sources in the previous screen.

  1. Select the check boxes adjacent to the names of the schemas to test.

  2. Click Test Connections for the connection to test.

    The wizard tests the configuration for each schema, by attempting to connect to a URL that is constructed by using the driver, host, port, and other information that you specified while configuring the schema.

    The result of the test is indicated in the Status column. Details are displayed in the Connection Result Log pane.

  3. After testing the connections, click the Next button in the wizard.

Configuring JMS File Stores

A JMS file store is a disk-based file in which persistent messages can be saved.

You can modify the JMS file stores that are configured in your domain, in the Configure JMS File Stores screen, which is displayed when you click Next in the Run Database Scripts screen. This step is optional.

  1. Review the current list of JMS file stores. Default values may vary based on the domain source that you selected earlier.


    Note:

    The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

  2. Modify the settings as required for your domain.

    Table 5-1 describes the fields of the Configure JMS File Stores screen.


    Note:

    Fields marked with an asterisk (*) are mandatory fields.

    Table 5-5 Configure JMS File Stores

    Field Description

    Name*

    Enter a name for the JMS file store. The name must be a string of characters and can include spaces.

    The name of the JMS file store must be unique among all component names within the domain.

    Directory

    Enter the path of the directory (in your system) in which the JMS file store resides.

    Synchronous write policy

    From the drop-down list, select one of the following synchronous write policies to determine how the file store writes data to the disk:

    • Cache-Flush: Transactions cannot be completed until all their write operations have been flushed to the disk.

    • Direct-Write: Write operations are performed directly to the disk. This policy is supported on Solaris and Windows. If this policy is active on an unsupported platform, the file store switches automatically to the cache-flush policy.

    • Disabled: Transactions are complete as soon as the writes are cached in memory. When this policy is active, completion of transactions does not depend on waiting for writes to reach the disk.

      This setting affects performance, scalability, and reliability.

    Note: The use of the direct-write policy is reliable in Solaris systems, but Windows systems may leave transaction data in the on-disk cache without writing it to disk immediately. This is considered unreliable, because a power failure can cause loss of on-disk cache data, possibly resulting in lost or duplicate messages. For reliable writes using the direct-write policy on Windows, either disable all write caching for the disk (enabled by default), or use a disk with a battery-backed cache. Some file systems, however, do not allow this value to be changed (for example, a RAID system that has a reliable cache).

    Note: If the JMS file store is used exclusively for paging non-persistent messages to the disk, the synchronous write policy is ignored.


  3. After updating the settings, click Next.

    Review the domain settings and proceed with domain creation as described in Reviewing the Domain Settings and Creating the Domain.

For more information, see Oracle Fusion Middleware Configuring Server Environments for Oracle WebLogic Server.