Every BI Beans application must use two pluggable connection drivers. One driver handles connections to the BI Beans Catalog, and the other handles connections to the OLAP data source.
As an application developer, you can choose to use the default implementation of a pluggable connection driver that ships with BI Beans, or you can customize the connection driver for your application. You must register and turn on the pluggable connection drivers.
When a user attempts to start an application and make a connection, the authentication driver (if registered), is invoked before the connection driver.
ConnectionProvider
interface specificationThe driver must implement the ConnectionProvider
interface from the oracle.dss.security
package.
public interface ConnectionProvider { public Object connect(Hashtable properties) throws BISecurityException; public void disconnect(Object connection) throws BISecurityException; }
The incoming arguments to the connect
method specify the following:
Properties set by the application developer.
Properties set inside the authenticate
method.
The BIUser
object, retrieved either from the BISession
object or from the BIUser
information that is provided in the BI Beans configuration file.
The connect
method establishes the specified connection and passes
the Connection
object to the caller.
The default implementation of the connection driver for the BI Beans Catalog involves a pluggable connection driver, which is implemented in the oracle.dss.persistence.storagemanager.bi.mapping.ReposConnectionDriver
class. This class implements methods that throw a BISecurityException
to indicate an error. The methods are as follows:
connect
method: This method establishes a JDBC connection
to the BI Beans Catalog, using the Oracle database user name and password.
The default implementation first looks in the incoming properties for the
user name and password. If the user name and password are not available
in the incoming properties, then the default implementation looks in the
DAD file. If the DAD file is not available, then the default implementation
throws a BISecurityException
, which indicates that the connection
cannot be established. If the connection is established successfully, then
the connect
method returns the java.sql.Connection
object as a Java object to the caller.
After the database connection is made, the BIUser
user name
controls scoping for Catalog operations. The user name is obtained either
from the settings in the BI Beans configuration file or from the application
through method calls on the BISession
object. If the application
uses the Oracle Application Server Single Sign-On (SSO) authentication system,
then it can retrieve the user name from SSO. The application can supply
the user name that is retrieved from SSO as the BIUser
or the
application can obtain the appropriate user name by any other means that
it chooses to use.
disconnect
method: This method disconnects the specified
java.sql.Connection
object.
The default implementation of the connection driver for an OLAP data source
involves a pluggable connection driver, which is implemented in the oracle.dss.connection.server.drivers.mdm.MDMPluggableConnectionDriverImpl
class. This class implements methods that throw a BISecurityException
to indicate an error. The methods are as follows:
connect
method: This method establishes a JDBC connection
to the OLAP data source, using the RDBMS user name and password. The default
implementation first looks in the incoming properties for the user name
and password. If the user name and password are not available in the incoming
properties, then the default implementation looks in the DAD file. If the
DAD file is not available, then the default implementation throws a BISecurityException
,
which indicates that the connection cannot be established. If the connection
is established successfully, then the connect
method returns
the java.sql.Connection
object as a Java object to the caller.
disconnect
method: This method disconnects the specified
Connection
object.