Appendix A Installed Product Layout

This appendix describes the directory layout after you install Sun Java™ System Access Manager 6 2005Q1 using the Sun Java System Enterprise installer. These directories include:

Base Installation Directory

The default base installation directory depends on the platform where you are installing Access Manager 6 2005Q1:

In the Access Manager documentation, the AccessManager-base variable is used to represent the base installation directory.

Product Directory

Within the base installation directory, Access Manager 6 2005Q1 packages, shared binary files, command-line tools, and various other files are installed in the /SUNWam directory on Solaris systems and the /identity directory on Linux systems. Therefore, the default product directory also depends on the platform:

The /SUNWam or /identity directory contains the following files and directories:


Note	During installation, you can specify a different base installation directory if you wish; however, do not change the /SUNWam or /identity product directory name.

After installing Access Manager, check the package installation accuracy by using the pkgchk(1M) utility. For example:

/bin Directory

Table A-1 describes the command-line tools and utilities in the /bin directory. For information, see the Access Manager Administration Guide.

Table A-1 Access Manager Command-Line Tools and Utilities
Utility	Description
am2bak	Backs up the Access Manager components.
amadmin	Load XML service files into Directory Server and performs batch administrative tasks on the DIT.
ampassword	Changes passwords for Access Manager administrator or users.
amsamplesilent	Sample installation configuration file for use with the installation and configuration scripts.
amconfig, amutils, amdsconfig, amsdkconfig, amsvcconfig, amas70config, amwas51config, amwl81config, amws61config, and amas81config	Installation and configuration scripts for installing, configuring, and uninstalling Access Manager instances. For information about these scripts, see the Access Manager Administration Guide.
amserver	Start and stops Access Manager instances.
amverifyarchive	Verifies the log archives to detect possible tampering and/or deletion of any files in the archive.
bak2am	Restores Access Manager components backed up by the am2back utility.
ldapmodify	Edits the contents of an LDAP directory, either by adding new entries or by modifying existing ones.
ldapsearch	Issues search requests to an LDAP directory and displays the result as LDIF text.
amsessiondb and amsfopassword	Access Manager session failover scripts.

/amtune Directory

The /amtune subdirectory contains Access Manager tuning scripts: amtune, amtune-as7, amtune-as8, amtune-directory.template, amtune-env, amtune-identity, amtune-os, amtune-prepareDSTuner, and amtune-ws61.

These scripts can sset operating system, Access Manager, web container, and Directory Server parameters to improve performance.

/docs Directory

The /docs directory contains the HTML and related files used for the API Javadocs, including these files: allclasses-frame.html, am_public_javadocs.jar, com directory, deprecated-list.html, help-doc.html, index-all.html, index.html, META-INF directory, overview-frame.html, overview-summary.html, overview-tree.html, package-list, packages.html, serialized-form.html, and stylesheet.css.

/dtd Directory

The /dtd directory contains the Document Type Definition (DTD) files used by Access Manager. A DTD defines the structure for XML files accessed by Access Manager. For more information, see the Access Manager Developer’s Guide. Table A-2 describes the DTD files in the /dtd directory.

Table A-2 Access Manager DTD Files
File	Description
Auth_Module_Properties.dtd	Defines the structure for XML files used by the authentication modules to specify their properties.
amAdmin.dtd	Defines the structure for XML files used to perform batch LDAP operations on the directory tree using the amAdmin command line tool.
amWebAgent.dtd	Defines the structure for XML files used to handle requests from, and send responses to, web agents. This file is deprecated and remains for purposes of backward compatibility.
policy.dtd	Defines the structure for XML files used to store policies in Directory Server.
remote-auth.dtd	Defines the structure for XML files used by the Authentication Service’s remote Authentication API.
server-config.dtd	Defines the structure for serverconfig.xml which details ID, host and port information for all server and user types.
sms.dtd	Defines the structure for XML service files.
web-app_2_2.dtd	Defines the structure for XML files used by the Access Manager deployment container to deploy J2EE applications.

/include Directory

/ldaplib/ Directory

The /ldaplib/ldapsdk subdirectory contains the shared object (.so) files needed to run the LDAP utilities included with Access Manager.

/lib Directory

The /lib directory contains JAR files and additional shared object (.so) files. It also contains a link to the /etc/opt/SUNWam/config/AMConfig.properties file.

/locale Directory

The /locale directory contains the localization properties files. Each properties file includes a corresponding English localization file. For example, amAdminCLI_en.properties. is the corresponding file for amAdminCLI.properties.

/migration Directory

The /migration directory contains the scripts and supporting files used to migrate data from earlier versions of Access Manager. For example, the /opt/SUNWam/migration/61to62/scripts subdirectory contains the Upgrade61DitTo62 script, which is used to migrate a DIT to Access Manager 2005Q1.

For more information about migration, see the Java System Access Manager Migration Guide.

/public_html Directory

The /public_html directory and subdirectories contain the HTML and related files used for the online help.

/samples Directory

The /samples directory contains the following subdirectories: /admin, /appserver, /authentication, /console, /csdk, /liberty, /logging, /phase2, /policy, /saml, /sso, and /um.

Each subdirectory contains samples for the respective functionality, which is indicated by the subdirectory name. For more specific information about these samples, see the Readme.html file.

/share Directory

The /share directory contains a bin/ subdirectory that contains the following additional utilities used internally by Access Manager:

/upgrade Directory

The /upgrade directory contains scripts and other files to upgrade earlier versions of Access Manager.

/web-src Directory

The /web-src directory contains the subdirectories in which Access Manager J2EE web applications are deployed on a web container. It contains the following subdirectories:

The /common directory is where the Access Manager Liberty Common Domain component is deployed. It contains the following subdirectories: /META-INF and /WEB-INF.

The /password directory is where the Access Manager Password Synchronization component is deployed. It contains the index.html file and the following subdirectories: /META-INF, /WEB-INF, and /password.

The /services directory is where Access Manager Core Services are deployed. It contains the index.html file and the following subdirectories: /META-INF, /WEB-INF, /admin, /config, /css, /docs, /fed_css, /fed_images, /images, /js, and /login_images.

/debug, /logs, and /tmp Directories

The default location of the /debug, /logs, and /tmp directories depends on the platform where you are installing Access Manager 2005Q1:

For information about these directories, see the Access Manager Administration Guide.

Configuration (/config) Directory

The default location of the configuration (/config) directory depends on the platform where you are installing Access Manager 2005Q1:

The .version file contains the current version of Access Manager.

The AMConfig.properties file, AMConfig.properties.template, and SSOConfig.properties contain Access Manager configuration attributes.

The serverconfig.xml contains configuration information, including encrypted passwords.

The amdrop.sql, amoraclecreate.sql, amhadbcreate.sql, amProfile.conf, and amhaenv.conf files are used for database operations for session failover.

The map_mime.types file identifies MIME information.

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 (iplanet-am-managed-people-container, etc.) 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 defined by Sun Microsystems’ internal Schema 2 document.

During uninstallation, The ds_remote_schema_uninstall.ldif file removes the Access Manager Access Manager specific LDAP schema object classes and attributes from Directory Server.

The /request subdirectory contains the SunAMClientData.xml and mobileRequest.xml files.

The /ums subdirectory contains XML files, including:

The serverconfig.xml file provides configuration information for the Access Manager for Directory Server.

The ums.xml file provides a set of templates that contain LDAP configuration information for identity-related objects managed using Access Manager.

The /xml subdirectory contains XML files. These XML files are not generally 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 Access Manager Developer’s Guide.

Previous Contents Index Next
Sun Java System Access Manager 6 2005Q1 Deployment Planning Guide