Another way to catalog many remote databases automatically is through using LDAP as the storage repository to distribute the catalog information.
In DB2 V8, there are 3 LDAP directory servers supported: IBM SecureWay Directory, Netscape LDAP Server and Microsoft Active Directory. Of these, I will briefly talking about some crucial steps to perform to eliminate obstacles as you trying to use Microsoft Active Directory to publish, store and distribute the node and database catalog information.
Assuming your domain is ibm.com and the machine host name is nerdyeddy. IP Address is 10.10.10.1 and LDAP port is listening at 389.
Firstly, fire up a DB2 Command Line Windows (db2cmd).
Execute the following commands:
The above commands are to configure the LDAP connectivity to AD.
Then to register your DB2 Server into AD, do this:
db2 register ldap as MYDB2 protocol tcpip
or if you need to register a remote DB2 server, do this:
db2 register db2 server in ldap as
Note: You shall need to replace the command parameters, these enclosed with square brackets accordingly.
If you was unable to run any or all of the above commands due to maybe SQL3276N eror, SQL3278N error or other funny problems, most probably you haven't run the secret setup yet, :p.
Assumining your DB2 is installed at C:\IBM\SQLLIB
Do this in the command prompt:
Basically, the db2ads.dll and db2schex are to properly configure the schema, metadata and other settings in AD to accomodate for DB2 related object classes and properties.
Ok. If your DB2 server is successfully registered in AD, then for now onwards the new databases that you created will be auto published the catalog information in AD for distribution.
If you need to catalogue previously created databases,
Other related commands include:
REGISTER LDAP AS
REGISTER DB2 SERVER IN LDAP AS
CATALOG LDAP NODE
CATALOG LDAP DATABASE
UNCATALOG LDAP DATABASE
UNCATALOG LDAP NODE
DEREGISTER DB2 SERVER IN LDAP NODE
REFRESH LDAP NODE DIRECTORY
REFRESH LDAP DB DIRECTORY