Oracle Data Source Creation JDBC Driver

Figure 19. Data Source Creation Important Third-Party JDBC Drivers with WebLogic Server - Oracle Thin driver 10g11g versions are installed with Oracle WebLogic Server, so you do not need to add these drivers to your CLASSPATH. If you plan to use a third-party JDBC driver that is not installed with WebLogic Server such as MSSQL or DB2, you must install the drivers, which includes updating your CLASSPATH with the path to the driver files. See more at Using Third-Party JDBC Drivers with WebLogic Server [http:download.oracle.comdocscdE13222_01wlsdocs91jdbc_admin third_party_drivers.html] • Domain Configuration - Before you run the Weblogic Server Configuration tools, you must do the following: 1. Setup Third-Party JDBC Drivers as described above. 2. If you use DB2, you must uncomment the Driver element with the className com.ibm.db2.jcc.DB2Driver in WL_SERVER_HOME\server\lib\jdbcdrivers.xml. • Online Server Deployment - You must setup Third-Party JDBC Drivers as described above before running the Oracle Service Registry installer because the data source will be created automatically by the installer. • Manual Deployment - You must setup Third-Party JDBC Drivers as described above before creating the JDBC data source via the Administrator Console of WebLogic. Page 85

4.6. Oracle Data Source Creation

4.7. JDBC Driver

Select the JDBC Driver as shown in Figure 8 .It is not necessary to configure this path for the Oracle database as the JDBC drivers for these databases are installed in the distribution. It is also not necessary if you have already configured this path previously for the selected database. The JDBC drivers are usually supplied by database vendors. Figure 20. Optional JDBC Driver

4.8. Account Backend

If you created a database or schema, you can configure an authentication account provider. Page 86

4.8. Account Backend

Figure 21. Authentication Account Provider Figure 9 allows you to select the authentication account provider. Database All accounts will be stored in the registry database. This is the recommended backend. LDAP Registry accounts integrated with LDAP server. External Registry accounts integrated with other external storage. To integrate Oracle Service Registry, with an external backend, you must implement the interface com.systinet.uddi.account.ExternalBackendApi and add it to the registry installation. For more information about LDAP, Oracle XML and External account backends, please see Section 6, External Accounts Integration

4.9. Multilingual Data

This section describes how Oracle Service Registry supports the storage of UDDI structures in the multilingual data format. There are two types of text fields in UDDI structures: Unicode fields and ASCII fields. Page 87

4.9. Multilingual Data