The command /usr/ucb/ps -auxww | grep com.sun.directory.wps will list all of the Identity Synchronization for Windows processes running. This table shows which processes should be running.
Table 12–3 Identity Synchronization for Windows Processes
Java Process Class Name |
Component |
When Present |
com.sun.directory.wps.watchdog.server.WatchDog |
System Watchdog |
Always |
com.sun.directory.wps.centrallogger.CentralLoggerManager |
Only where Core is installed |
|
com.sun.directory.wps.manager.SystemManager |
Only where Core is installed |
|
com.sun.directory.wps.controller.AgentHarness |
Connector |
One for each connector installed |
If the expected number of processes are not running, then issue the following commands to restart all Identity Synchronization for Windows processes.
# /etc/init.d/isw stop # /etc/init.d/isw start |
If the WatchDog process is running, but the expected number of java.exe processes are not running, then see the “Examining WatchList.properties” section to verify that all components were installed properly.
Like other system components, the Sun Java System Directory Server Plug-in sends log records over the bus that are managed by the central logger for end-user viewing. However, the Plug-in also logs some messages that may not show up over the bus (for instance when the subcomponent cannot contact the connector). In this case the log messages only show up in the Plug-in’s logs directory on the file system, which should look something like the following:
serverroot/isw/logs/SUBC
Because the Plug-in runs with the Directory Server process, there could potentially be a problem for the Plug-in’s ability to write into its logs directory. This happens if the directory server runs as a different user than the owner of the logs directory. In this case, it may be necessary to give the Plug-in permission explicitly by changing the directories permission or owner using native operating system commands.