The Security Objects Access (DAO) interface is composed of the following
items:
- jar:
- bttbcaccommon.jar
- bttbcac.jar
- Interface:
- ISecurityObjectManager
This interface defines how to manage the security
objects in the system.
- IDAOFactory
This interface defines how to construct and get the DAO
objects.
- ISecurityRightDAO
This interface defines how to access the Right object
in the system.
- ISecurityRoleDAO
This interface defines how to access the Role object
in the system.
- ISecurityServiceDAO
This interface defines how to access the Service
object in the system.
- ISecurityUserDAO
This interface defines how to access the User object
in the system.
Besides, the following four Java™ classes are provided to represent the
security objects in Java. These Java classes have the corresponding data
field and the simple set or get method.
- jar:
- Class:
- SecurityRight
- SecurityRole
- SecurityService
- SecurityUser
Two ways are provided by BTT Access Control for DAO implementation.
- XML DAO implementation
Located at the
com.ibm.btt.bc.ac.dao.xml package.
The default names of the four repository files are listed as follows. You
can provide the four blank XML files, and tell Access Control about the location
of the files.
- right.xml
- service.xml
- user.xml
- role.xml
- DB2/Oracle/SQLServer 2000/SQLServer 2005 DAO implementation
Located
at the
com.ibm.btt.bc.ac.dao.db2 package. The following diagram illustrates
the schema definitions of the security object in the database. In the diagram,
PK stands for primary key; FK stands for foreign key; the arrow specifies
the foreign key dependency. The definitions are database-specific. DB2®, Oracle and
SqlServer are supported by BTT Access Control in the release. You can find
the different DDL file of the DB file in the ${BTTInstallPackaging}/lib/dbtools/Windows/
:
- createTablesForSecurityManager_DB2.ddl
- createTablesForSecurityManager_Oracle.ddl
- createTablesForSecurityManager_SqlServer2000.sql
- createTablesForSecurityManager_SqlServer2005.sql