There are three kinds of pluggable drivers that an application can provide: authentication, connection, and user community drivers.
BI Beans ships with default implementations for pluggable drivers. The default implementations for connection drivers and for a user community driver are already registered and turned on. If you are satisfied with these default implementations, then you do not have to register any pluggable drivers.
You have the option of using custom pluggable drivers. If you register even one pluggable driver, then you must register all pluggable drivers, including the default drivers that are provided by BI Beans. The following list shows, in order of precedence, the ways that you can register pluggable drivers:
API -- The following three methods of the
BISession
object override all other settings: setAuthenticationProvider
,
setConnectionProvider
, and setUserCommunityProvider
.
Configuration file -- The default settings that BI Beans provides for the connection and user community drivers are present in the BI Beans configuration file that is created in JDeveloper. You can edit this configuration file to reflect custom settings.
Configuration settings are specific to each application, so each application must have its own BI Beans configuration file. The configuration information is stored as XML data in a file named with the xml
extension.
Applications that use the default connection drivers must also have their own set of DAD files, as specified in the configuration file. The BISession
object reads the configuration file upon startup.
To specify a pluggable driver in the configuration file, provide the following information:
Driver type. The values can be a
for an authentication driver, c
for a connection driver, or u
for a user community driver.
Invocation Level. The values differ depending on the type of driver. For a user community driver, the only valid value is session
; the driver is invoked once per session. For an authentication or connection driver, the valid values are bicatalog
for invocation on connection to the BI Beans Catalog or olap
for invocation on connection to an OLAP service.
Required. The values can be true
or false
and indicate whether the driver is invoked. If this value is false
,
then BI Beans applications do not invoke the driver. You cannot set the
connection driver value to false
, because a connection driver
is required by BI Beans.
The following code shows sample pluggable driver settings in the <BISession>
section of a configuration file.
<BISession> <BIUser Username="pmartinez"/> <PluggableDriver DriverType="a" InvocationLevel="olap" Required="true" DriverClass="oracle.dss.appmodule.server.DSSApplicationModuleAuthenticationDriver"/> <PluggableDriver DriverType="c" InvocationLevel="bicatalog" Required="true" DriverClass="oracle.dss.persistence.storagemanager.bi.mapping.ReposConnectionDriver"/> <PluggableDriver DriverType="c" InvocationLevel="olap" Required="true" DriverClass="oracle.dss.connection.server.drivers.mdm.MDMPluggableConnectionDriverImpl"/> <PluggableDriver DriverType="u" InvocationLevel="session" Required="true" DriverClass="oracle.dss.persistence.storagemanager.bi.mapping.ReposUserCommunity"/> </BISession>
You can use the following methods of the BISession
object to override the pluggable driver settings in the configuration file:
setAuthenticationProvider
for authentication drivers.
setConnectionProvider
for connection drivers.
setUserCommunityProvider
for user community drivers.
You can choose to consolidate the implementation of the AuthenticationProvider
, ConnectionProvider
, and UserCommunityProvider
interfaces into a single class where appropriate. You can customize the pluggable drivers as appropriate for the needs of your application.