The LDAP Directory Schema defines object classes and attributes for the information stored in the LDAP directory entries. An object class consists of a set of mandatory and optional attributes. Every entry in the LDAP directory has an object class associated with it.
Before DB2 can store the information into LDAP, the Directory Schema for the LDAP server must include the object classes and attributes that DB2 uses. The process of adding new object classes and attributes to the base schema is called extending the Directory Schema.
Note: | If you are using IBM SecureWay LDAP Directory v3.1, all the object classes and attributes that are required by DB2 are included in the base schema. You do not have to extend the base schema with DB2 object classes and attributes. |
When using the IBM eNetwork Directory Version 2.1, you must extend the base schema with the object classes and attributes that are used by DB2.
Use the following steps to extend the base schema for IBM eNetwork Directory Version 2.1:
include db2.oc
include db2.at
The following tables describe the object classes that are used by
DB2:
Table 153. The eProperty Object Class
Class | eProperty |
---|---|
Description | The eProperty object class is used to specify application specific settings for user preference properties. |
Required Attributes | cn |
Optional Attributes | propertyType
cisProperty (may contain other IBM defined attributes) |
Type | Structural |
OID (object identifier) | 1.3.18.0.2.6.90 |
Special Notes | The eProperty object class is defined in the IBM Directory Schema and may
contain other attributes. The attributes that are used by DB2 UDB
are:
|
Table 154. The eApplicationSystem Object Class
Class | eApplicationSystem |
---|---|
Description | This object class describes application subsystems such as DB2 and CICS as well as systems such as Orion and GSO. An application system may span multiple computer systems or it may reside on a single computer system. |
Required Attributes |
|
Optional Attributes | systemName
(may contain other IBM defined attributes) |
Type | Structural |
OID (object identifier) | 1.3.18.0.2.6.8 |
Special Notes | The eApplicationSystem object class is defined in the IBM Directory Schema and may contain other attributes. The attribute that is used by DB2 UDB is: systemName which is set to "DB2" |
Table 155. The DB2Node Object Class
Class | DB2Node |
---|---|
Description | This object class describes an instance of a DB2 database server. |
Required Attributes | db2nodeName |
Optional Attributes | db2nodeAlias
db2instanceName db2Type host protocolInformation |
Type | Structural |
OID (object identifier) | 1.3.18.0.2.6.116 |
Special Notes | The attributes are used by DB2 as follows:
|
The protocolInformation attribute contains the communication protocol information to bind to the service. It consists of tokens that describe the network protocol supported. Each token is separated by a semicolon. There is no space between the tokens. You may specify an asterisk (*) for an optional parameter.
The tokens for TCP/IP are:
The tokens for APPN are:
The tokens for IPX/SPX are:
The tokens for NetBIOS are:
The tokens for Named Pipe are:
Table 156. The DB2Database Object Class
Class | DB2Database |
---|---|
Description | This object class describes a DB2 database. |
Required Attributes | db2databaseName
db2nodePtr |
Optional Attributes | db2databaseAlias
db2additionalParameters db2ARLibrary db2authenticationLocation db2gwPtr db2databaseRelease DCEPrincipalName |
Type | Structural |
OID (object identifier) | 1.3.18.0.2.6.117 |
Special Notes | The attributes are described as follows:
|
The following table describes the attributes that are used by DB2:
Table 157. The Attribute Specifications
Attribute Name | Syntax | Maximum Length | Multi-Valued | OID |
---|---|---|---|---|
cn | Case Ignored String | 256 | Multi-valued | 2.5.4.3 |
propertyType | Case Ignored String | 64 | Multi-valued | 1.3.18.0.2.4.320 |
cisProperty | Case Ignored String | 250000 | Multi-valued | 1.3.18.0.2.4.309 |
systemName | Case Ignored String | 256 | Single-valued | 1.3.18.0.2.4.329 |
db2nodeName | Case Ignored String | 1024 | Single-valued | 1.3.18.0.2.4.419 |
db2nodeAlias | Case Ignored String | 1024 | Multi-valued | 1.3.18.0.2.4.420 |
db2instanceName | Case Ignored String | 256 | Single-valued | 1.3.18.0.2.4.428 |
db2Type | Case Ignored String | 64 | Single-valued | 1.3.18.0.2.4.418 |
host | Case Ignored String | 256 | Multi-valued | 1.3.18.0.2.4.486 |
protocolInformation | binary | 5000 | Multi-valued | 2.5.4.48 |
db2databaseName | Case Ignored String | 1024 | Single-valued | 1.3.18.0.2.4.421 |
db2databaseAlias | Case Ignored String | 1024 | Multi-valued | 1.3.18.0.2.4.422 |
db2nodePtr | Distinguished Name | 1000 | Single-valued | 1.3.18.0.2.4.423 |
db2gwPtr | Distinguished Name | 1000 | Single-valued | 1.3.18.0.2.4.424 |
db2additionalParameters | Case Ignored String | 1024 | Single-valued | 1.3.18.0.2.4.426 |
db2ARLibrary | Case Ignored String | 256 | Single-valued | 1.3.18.0.2.4.427 |
db2authenticationLocation | Case Ignored String | 64 | Single-valued | 1.3.18.0.2.4.425 |
db2databaseRelease | Case Ignored String | 64 | Single-valued | 1.3.18.0.2.4.429 |
DCEPrincipalName | Case Ignored String | 2048 | Single-valued | 1.3.18.0.2.4.443 |