The default location of the configuration (/config) directory depends on the platform where Access Manager is installed:
Solaris systems: /etc/opt/SUNWam/config
Linux and HP-UX systems: /etc/opt/sun/identity/config
Windows systems: C:\Program Files\Sun\JavaES5\identity\config
The /config directory contains configuration, XML, and LDIF files, including:
The .version file contains the current version of Access Manager.
The AMConfig.properties and SSOConfig.properties files contain Access Manager configuration attributes.
The serverconfig.xml file provides configuration information for the Access Manager for Directory Server.
The /ldif subdirectory contains the LDIF files needed for populating the Directory Server data store when installing Access Manager. For example:
During installation, the ds_remote_schema.ldif file loads the Access Manager specific LDAP schema object classes and attributes (such as the iplanet-am-managed-people-container) needed to store Access Manager data in Directory Server. The sunone_schema2.ldif file loads the Access Manager specific LDAP schema object classes and attributes.
During uninstallation, The ds_remote_schema_uninstall.ldif file removes the Access Manager LDAP schema object classes and attributes from Directory Server.
The /xml subdirectory contains XML files.
The /ums subdirectory contains XML files, including:
The amserveradmin script loads the Access Manager services.
The ums.xml file provides a set of templates that contain LDAP configuration information for objects managed using Access Manager.
The XML files are generally not used for configuration. If they are modified, they must be manually reloaded into the Directory Server data store. (Any changes in the server are not synchronized with these files.) For information about the XML files in this directory, see the Sun Java System Access Manager 7.1 Developer’s Guide.