test

Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide

Configuring DSCC

This section provides the following information about configuring DSCC:

ProcedureTo Change the Common Agent Container Port Number

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.

  1. As root, verify the existing port number for jmxmp-connector-port. 


    $ su 
Password: 
# cacaoadm list-params
...
jmxmp-connector-port=11162
...

  2. 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.

  3. 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.

ProcedureTo Reset the Directory Service Manager Password

To reset the Directory Service Manager password, use DSCC, as described in this procedure.

  1. Access DSCC as described in To Access DSCCTo Access DSCC.

  2. Click the Settings tab, then choose Directory Service Managers.

  3. Click the name of the Directory Service Manager for which you want to change the password.

  4. 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.

ProcedureTo Extend the DSCC Session Automatic Timeout Delay

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.

  1. 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
    ...

  2. Restart Sun Java Web Console.


    # smcwebserver restart
Shutting down Sun Java(TM) Web Console Version 3.0.1 ...
Starting Sun Java(TM) Web Console Version 3.0.1 ...
The console is running.

    For the location of these commands, see Command Locations.

Configuring Failover for DSCC

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:

Troubleshooting DSCC

For information about troubleshooting DSCC, see To Troubleshoot Directory Service Control Center Access in Sun Java System Directory Server Enterprise Edition 6.0 Installation Guide.