Sun Java Desktop System Configuration Manager, Release 1 - Installation Guide

Bootstrap Information

To access the remote configuration data, the Configuration Agent must be provided with the location of the LDAP server. You can add this location through the YaST2 configuration tool, autoYaST, or by manually editing the policymgr.properties properties file in the /opt/apoc/lib directory. In YaST2, you can add this data in the Network/Advanced section.

Figure 51 Java Desktop System Configuration Agent in YaST

Java Desktop System Configuration Agent in YaST

The following information is required to run the Configuration Agent:


Note

Associated property file keys are indicated in parentheses, where appropriate.



Note

Whenever you change the bootstrap and operational settings, the Configuration Agent must be restarted.


To restart the Configuration Agent on the Desktop, ensure that none of the related client applications are running, log in as root, and type the command /opt/apoc/bin/apocd restart.