Marcos Ares Troubleshooting Weblog

When DSEE6 (patchzip version) is installed, the Directory Server Control Center component (aka DSCC) will not be there. This means that there will be no way to administrate through the web the installed instances unless we can register them in a DSCC register running on a different accessible system in the topology (which assumes the customer has at least deployed 1 system with the DSEE6 package version).

I recently installed an in-house lab 100% patchzip, which means no single DSCC component existed in my topology. The following are the steps I took to install a DSCC component on top of one of my patchzip installations.

My machine runs Solaris 10 Sparc.

I went to this SWAN accessible location:

# pwd
/share/builds/nicpgnb6/dsee_deployer61/builds/20070515.1/Common/build/SunOS-sparc-opt/tarball/patch/native/dsee

And installed from it the following packages:

# The 2 packages below are needed by DSCC
# because of /opt/SUNWjdmk/5.1/lib/jmx.jar,
# /opt/SUNWjdmk/5.1/lib/jmxremote.jar,
# /opt/SUNWjdmk/5.1/lib/jmxremote_optional.jar,
# /opt/SUNWjdmk/5.1/lib/sasl.jar,
# /opt/SUNWjdmk/5.1/lib/sunsasl.jar
yes | pkgadd -d . SUNWjdmk-runtime
yes | pkgadd -d . SUNWjdmk-runtime-jmx

# The package below is needed by DSCC
# because of /usr/lib/cacao/lib/cacao_cacao.jar
yes | pkgadd -d . SUNWcacaort

# The package below is needed by DSCC
# because of /opt/SUNWdsee/dsee6/lib/clip.jar
yes | pkgadd -d . SUNWldap-shared

# The package below is needed by DSCC
# because of /opt/SUNWdsee/dps6/lib/dpcfg.jar
yes | pkgadd -d . SUNWldap-proxy-client

# The package below is needed by DSCC
# because of /opt/SUNWdsee/ds6/lib/slapy.jar
yes | pkgadd -d . SUNWldap-directory-client

# The packages below are needed by DSCC
# to be able to create the DSCC Administration DS instance:
yes | pkgadd -d ./SunOS5.10 SUNWicu
yes | pkgadd -d . SUNWldapcsdk-libs
yes | pkgadd -d . SUNWldap-directory

# if Sun Java Web Console (Lockhart) version < 3.0.2
# you can check file /usr/share/webconsole/version.txt
# then you'll need to re-install the SUNWmcon packages:
yes | pkgrm SUNWmcosx SUNWmcos SUNWmcon SUNWmconr SUNWmctag
yes | pkgadd -d ./SunOS5.10 SUNWmctag
yes | pkgadd -d ./SunOS5.10 SUNWmconr
yes | pkgadd -d ./SunOS5.10 SUNWmcon
yes | pkgadd -d ./SunOS5.10 SUNWmcos
yes | pkgadd -d ./SunOS5.10 SUNWmcosx

# Finally, these are the DSCC console packages required:
yes | pkgadd -d . SUNWldap-console-var
yes | pkgadd -d . SUNWldap-console-common
yes | pkgadd -d . SUNWldap-console-cli
yes | pkgadd -d . SUNWldap-console-gui-help
yes | pkgadd -d . SUNWldap-console-gui

The post-install output of SUNWldap-console-gui should look like follows:

## Executing postinstall script.
DSCC Application is not registered in Sun Java(TM) Web Console
Registering DSCC Application in Sun Java(TM) Web Console
Stopping Sun Java(TM) Web Console...
Registration is on-going. Please wait...
DSCC is registered in Sun Java(TM) Web Console
Before using DSCC, you will have to start Sun Java(TM) Web Console using the command:
/usr/sbin/smcwebserver start
.
Installation of was successful.
#

Launching Sun Java(TM) Web Console and checking its logs:

# /usr/sbin/smcwebserver start
Starting Sun Java(TM) Web Console Version 3.0.2 ...
The console is running
#
#
# pwd
/var/log/webconsole/console
# ls -al
total 12
drwxrwxr-x 2 noaccess other 512 May 17 09:26 .
drwxr-xr-x 3 root sys 512 May 17 09:22 ..
-rw-r--r-- 1 root other 2625 May 17 10:01 console_config_log
-rw-r--r-- 1 noaccess root 999 May 17 10:01 console_debug_log

# tail console_debug_log
==============================================================
Java Web Console Version 3.0.2 started on Thu May 17 10:01:21 MEST 2007
==============================================================

# tail console_config_log
17-May-2007 | 10:01:20 | ERROR | Error generating product images for "dccapp" web application: Product name string is empty or null
17-May-2007 | 10:01:20 | INFO | Deployed web application "dccapp".
17-May-2007 | 10:01:21 | INFO | The console instance "console" is starting in user mode.
17-May-2007 | 10:01:41 | INFO | The console is running.

NOTE: a minor ERROR MESSAGE on the console_config_log file, but it does not seem to be important in my test, everything seems to work fine from a DSCC perspective.

Once the commands above run, DSCC should be succesfully installed in your machine. The DSCC application launcher will now accessible from the Sun Java Web Console Login page:

https://hostname:6789 (select root/password as login)

The first time the DSCC app will be launched, you will be prompted for the DSCC admin/password you would like to have, then the ADS will be created and started autommatically. A message of succesful completion should appear, then another one inviting you to logout Sun Java Web Console and use the admin/password you chose in the previous step.

I strongly suggest you to set a bigger timeout for the Web Console to avoid getting logged out too fast. I configured my timeout to 3 hours like this:

# /usr/sbin/wcadmin add -p -a ROOT session.timeout.value=180
Set 1 properties for the ROOT application.
# /usr/sbin/wcadmin list -p
Shared service properties (name, value):
session.timeout.value 180
com.sun.web.console.user noaccess
sun.directory.dcc.path.slapx /opt/SUNWdsee/ds6/bin/dsadm
sun.directory.dcc.path.var /var/opt/SUNWdsee/dscc6
sun.directory.dcc.path.sample.ldif /opt/SUNWdsee/ds6/ldif/Example.ldif
# smcwebserver restart
Restarting Sun Java(TM) Web Console Version 3.0.2 ...