This section provides the following information about configuring DSCC:
The default common agent container port number is 11162. The common agent container defines the DSCC agent port as jmxmp-connector-port. If for administrative reasons you need to use a different port number for the DSCC agent and common agent container, use the following procedure.
You cannot use DSCC to perform this task. Use the command line, as described in this procedure.
As root, verify the existing port number for jmxmp-connector-port.
$ su Password: # cacaoadm list-params ... jmxmp-connector-port=11162 ... |
Change the DSCC agent port number.
The common agent container must be stopped when changing the DSCC agent port number.
# cacaoadm stop # cacaoadm set-param jmxmp-connector-port=new-port # cacaoadm start |
For the location of this command, see Command Locations.
In DSCC, unregister your servers, and then reregister them using the new DSCC agent port number.
In addition, when you create a new server, you must specify the non-default DSCC agent port number.
To reset the Directory Service Manager password, use DSCC, as described in this procedure.
Access DSCC as described in To Access DSCC.
Click the Settings tab, then choose Directory Service Managers.
Click the name of the Directory Service Manager for which you want to change the password.
In the properties screen, enter the new password.
Confirm the new password by typing it again in the Confirm Password field. Click OK to save your changes.
After a period of time, your DSCC session will time out, and you will be logged out of DSCC. Use this procedure to extend the timeout delay. Note that this procedure extends the timeout for DSCC and for all other applications in Sun Java Web Console.
You cannot use DSCC to perform this task. Use the command line, as described in this procedure.
As root, extend the timeout delay.
# wcadmin add -p -a ROOT session.timeout.value=mm |
where mm is the number of minutes before timeout.
For example, to set the timeout to two hours, type:
$ su Password: # wcadmin add -p -a ROOT session.timeout.value=120 Set 1 properties for the ROOT application. # wcadmin list -p Shared service properties (name, value): session.timeout.value 120 ... |
Restart Sun Java Web Console.
# smcwebserver restart Shutting down Sun Java(TM) Web Console Version 3.0.2 ... Starting Sun Java(TM) Web Console Version 3.0.2 ... The console is running. |
For the location of these commands, see Command Locations.
DSCC displays the servers that you have registered in DSCC.
If the machine on which you have installed DSCC fails, you can install DSCC on another machine and then reregister your servers. However, this can be time-consuming. If you want to have immediate access to your servers through DSCC, you can configure DSCC failover.
To configure DSCC failover, take the following considerations into account:
All information for registered servers is stored in the DSCC registry. This registry is a Directory Server instance. You can use the administration commands dsadm and dsconf to manage the registry.
The DSCC registry has the following default characteristics:
Solaris — /var/opt/SUNWdsee/dscc6/dcc/ads
Linux and HP-UX — /var/opt/sun/dscc6/dcc/ads
Windows — C:\Program Files\Sun\DSEE\var\dscc6\dcc\ads
cn=dscc
LDAP 3998, LDAPS 3999
After you have installed DSCC on two or more machines, you can set up replication between the DSCC registry suffixes. Use the replication command-line procedures described in Chapter 10, Directory Server Replication. Alternatively, for an example of setting up a simple replication configuration, dsconf(1M) man page.
After replication is set up, you can access the same servers that are registered in DSCC from different machines. For example, if you set up replication between the DSCC registry suffixes on host1 and host2, you can manage the same servers using DSCC on either https://host1:6789 or https://host2:6789. In case of host failure, access DSCC from the other host.
For information about troubleshooting DSCC, see To Troubleshoot Directory Service Control Center Access in Sun Java System Directory Server Enterprise Edition 6.2 Installation Guide.