This window allows you to set up the console so that it can communicate with other directory servers using the Secure Sockets Layer (SSL) encryption, if necessary.
From this window you can:
You can find more detailed help on the following elements of this window:
Specify the keystore database path and file name in the Keystore field. This is the fully qualified file specification of the keystore database file. The file must exist on the computer where the IBM Tivoli Directory Integrator Administration and Monitoring Console is installed.
Specify the keystore password in the Keystore password field. If a password stash file is not being used, the password for the keystore database file must be specified here.
Enter the fully qualified path to a trusted Certification Authority (CA) certificates database file. This is the fully qualified file specification of the Truststore database file. The file must exist on the computer where the IBM Tivoli Directory Integrator Administration and Monitoring Console is installed.
Enter the password for the Truststore file.
The Administration and Monitoring Console provides a way for you to authenticate users to an LDAP backend. If LDAP authentication is enabled, you must configure the properties of the LDAP server to which you want to authenticate.
To configure LDAP properties:
You can find more detailed help on the following elements of this window:
Specify the host name or IP address of the server on which the LDAP server is running. localhost is the default host name.
Enter the port number of the LDAP server. 389 is the default port number.
Enter the admin ID of the LDAP administrator.
Enter the LDAP administrator password.
Select one of the following types of servers from the Server type menu:
Enter the ID that will be used to bind to the LDAP server.
Enter the password for the LDAP bind ID. This password is encrypted using PKI encryption and is stored in the .amc properties.
Enter the suffix of the LDAP server.
JDBC properties are used to define the connections settings to the CloudScape database. The CloudScape database is used to store the Administration and Monitoring Console's configuration information, connection details, and Action Manager rules and results.
From this window you can:
You can find more detailed help on the following elements of this window:
Enter the JDBC URL, for example: jdbc:db2://hostname:port/dbname.
Enter the desired user name. Only the tables available to this user are shown.
Enter the password for the user.
Enter the JDBC driver class name. The default value of sun.jdbc.odbc.JdbcOdbcDriver addresses the JDBC-ODBC bridge, which is not recommended for production use. For IBM DB2, the type 2 or type 4 driver you would typically specify is com.ibm.db2.jcc.DB2Driver.
This window allows you to set general properties such as refresh rates and session timeouts for the Administration and Monitoring Console.
From this window you can:
You can find more detailed help on the following elements of this window:
Set Monitor Status as the start up page
Select the authentication mode from the menu.
Select Monitor Status if you want the Monitor Status window to be the default window that appears after you log on to the Administration and Monitoring Console. By default Monitor Status is not selected.
Enter the amount of time in minutes that must expire between Monitor Status window refreshes. For example, if you enter 10, the Monitor Status window refreshes every ten minutes.
Enter the amount of time in days that must expire between Action Manager log rotations.