Sun Java System Access Manager 6 2005Q1 Deployment Planning Guide |
Appendix A
Installed Product LayoutThis 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 DirectoryThe 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 DirectoryWithin 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:
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.
The /SUNWam or /identity directory contains the following files and directories:
After installing Access Manager, check the package installation accuracy by using the pkgchk(1M) utility. For example:
pkgchk -l -p /opt/SUNWam
/bin Directory
Table A-1 describes the command-line tools and utilities in the /bin directory. For information, see the Access Manager Administration Guide.
/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.
/include Directory
The /include directory contains header (.h) files
/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 DirectoriesThe 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) DirectoryThe default location of the configuration (/config) directory depends on the platform where you are installing Access Manager 2005Q1:
The /config directory contains configuration, XML, and LDIF files, including:
- 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 /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.