Sun ONE logo      Previous      Contents      Index      Next     

Sun ONE Identity Server Deployment Guide

Appendix A  
Installed Product Layout

This chapter describes the product software layout after a typical installation. It contains the following sections:


The Sun Java Enterprise System 2003Q4 Base Directory

During Identity Server installation, if no directory is specified, the default /opt is used. Because Identity Server installation is now accomplishedd using the Sun Java Enterprise System 2003Q4 installer, any or all products chosen for installation might be installed in this directory. When Identity Server is chosen, the default directory will contain a sub-directory named SUNWam. SUNWam contains all Identity Server shared binary files and command line tools. For a complete listing of sub-directories installed, see the Sun Java Enterprise System 2003Q4 Installation Guide.


The SUNWam Directory

Identity Server packages are installed in in this directory. Brief descriptions of each package are provided following the listing itself.


Note

Directories shown here reflect a product installation for the Solaris Operating Environment. File names and extensions may differ for installations on other platforms. After installing Identity Server, a full list of installed path names for a particular package can be obtained by using the pkgchk(1M) utility, pkgchk -v package-name.


The SUNWam directory contains the following directories and files:

/opt/SUNWam/agents/

This directory contains tools, header files and configuration files specific to Identity Server policy agents. For more information on what is included here, see the Web Policy Agents Guideor the J2EE Policy Agents Guide.

/opt/SUNWam/bin/

This directory contains the command line tools shipped with Identity Server. They are detailed in Table A-1. More information can be found in the Command Line Reference Guide section of the Sun ONE Identity Server Administration Guide.

Table A-1  Identity Server Command Line Utilities 

Utility

What it does

VerifyArchive*

This is the deprecated version of amverifyarchive installed in 6.1 for backward compatibility.

am2bak*

This utility performs a backup of Identity Server components.

amadmin*

amadmin is used to load XML service files into Directory Server and to perform batch administrative tasks on the DIT.

ampassword*

This utility is used to change the passwords set for the Identity Server administrator or users.

amserver*

The amserver command line executable is used to create, start, stop, and delete Identity Server instances.

amverifyarchive*

This utility verifies the log archives. Verification of an archive detects possible tampering and/or deletion of any file in the archive.

bak2am*

This utility performs a restore of the Identity Server components backed-up by the am2back utility.

ldapmodify*

ldapmodify edits the contents of an LDAP directory, either by adding new entries or by modifying existing ones.

ldapsearch*

ldapsearch issues search requests to an LDAP directory and displays the result as LDIF text.

/config ---> /etc/opt/SUNWam/config/

The config directory is a symbolic link to /etc/opt/SUNWam/config. This directory contains the XML service and configuration files detailed in Table A-2. The 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 synched with these files.) Information on all the XML files in this directory can be found in the Sun ONE Identity Server Customization And API Guide.

Table A-2  XML Service and Configuration Files 

Sub-directory

What it contains

ums

  • serverconfig.xml provides configuration information for the Sun™ One Identity Server regarding the Sun ONE Directory Server that is used as its data store.
  • ums.xml provides a set of templates that contain LDAP configuration information for identity-related objects managed using Identity Server.

xml

  • amAdminConsole.xml
  • amAuth.xml
  • amAuthAnonymous.xml
  • amAuthCert.xml
  • amAuthConfig.xml
  • amAuthHTTPBasic.xml
  • amAuthLDAP.xml
  • amAuthMembership.xml
  • amAuthNT.xml
  • amAuthRadius.xml
  • amAuthSafeWord.xml
  • amAuthSecurID.xml
  • amAuthUnix.xml
  • amAuthenticationDomainConfig.xml
  • amClientData.xml
  • amClientDetection.xml
  • amEntrySpecific.xml
  • amDSS.xml
  • amG11NSettings.xml
  • amLogging.xml
  • amNaming.xml
  • amPasswordReset.xml
  • amPlatform.xml
  • amPolicy.xml
  • amPolicyConfig.xml
  • amProviderConfig.xml
  • amSAML.xml
  • amSession.xml
  • amUser.xml
  • amWebAgent.xml

/opt/SUNWam/console.war

console.war is the web application archive (WAR) that contains files pertaining to the Identity Server console application. Information on all WAR files in this directory can be found in the Sun ONE Identity Server Customization And API Guide.

/opt/SUNWam/docs

The docs directory contains the HTML and related files used for the API Javadocs. Following is a list of the included files.

/opt/SUNWam/dtd

The dtd directory contains all the Document Type Definition (DTD) files used by Identity Server. A DTD defines the structure for XML files accessed by Identity Server. More information on the DTD files can be found in the chapter on Service Management in the Sun ONE Identity Server Customization And API Guide. Table A-3 contains a listing of the DTD files.

Table A-3  DTD Files in Identity Server

File

Purpose

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 Identity Server deployment container to deploy J2EE applications.

/opt/SUNWam/ldaplib

ldaplib contains the shared object (.so) files needed to run the LDAP utilities included with Identity Server. Table A-4 details a listing of the files.

Table A-4  Shared Object Files 

Sub-directory

Included files

ldapsdk

  • libicudata.so.2
  • libicui18n.so.2
  • libicuuc.so.2
  • libldap50.so
  • libprldap50.so
  • libsasl.so
  • libssldap50.so

/opt/SUNWam/ldif

The ldif directory contains LDIF files needed for populating the Directory Server data store when installing Identity Server. Table A-5 contains a list of the included LDIF files.

Table A-5  LDIF Files 

File

Purpose

ds_remote_schema.ldif

During installation, this file loads the Identity Server-specific LDAP schema object classes and attributes (iplanet-am-managed-people-container, etc.) needed to store Identity Server data in Directory Server.

ds_remote_schema_uninstall.ldif

This file is used to remove the Identity Server-specific LDAP schema object classes and attributes from Directory Server.

sunone_schema2.ldif

During installation, this file loads the Identity Server-specific LDAP schema object classes and attributes defined by Sun Microsystems’ internal Schema 2 document.

/opt/SUNWam/lib

The lib directory contains JAR files and additional shared object (.so) files. Following is a list of the files and sub-directories.

/opt/SUNWam/locale

The locale directory contains the localization properties files. Following is a list of the included files. Each properties file listed also includes a corresponding English localization file as, for example, amAdminCLI_en.properties.

/opt/SUNWam/migration

The migration directory contains PERL scripts used to migrate data from earlier versions of Identity Server. Following is a list of the migration scripts included with Identity Server. More information on migrating data can be found in the Sun ONE Identity Server Migration Guide.

/opt/SUNWam/password.war

password.war is the web application archive (WAR) that contains files pertaining to the Identity Server password reset application. Information on all WAR files in this directory can be found in the Sun ONE Identity Server Customization And API Guide.

/opt/SUNWam/public_html

The public_html directory contains the HTML and related files used for the online help.

/opt/SUNWam/samples

The samples directory contains the sub-directories listed in Table A-6. These sub-directories hold the samples for the respective functionality. More specific information on the samples themselves can be found in the respective chapter of the Sun ONE Identity Server Customization And API Guide.

Table A-6  Directories For Functional Samples 

Sub-directory Name

Readme.html

admin/

appserver/

authentication/

console/

liberty/

policy/

saml/

sample.css

sso/

sunLogo.gif

um/

/opt/SUNWam/services.war

services.war is the web application archive (WAR) that contains files pertaining to all Identity Server services not included in the previously mentioned WAR files. Information on all WAR files in this directory can be found in the Sun ONE Identity Server Customization And API Guide.

/opt/SUNWam/share

The share directory contains a sub bin/ directory that contains additional utilities used internally by Identity Server.

/opt/SUNWam/web-apps

The web-apps directory contains the directories in which Identity Server J2EE web application are deployed on a web container. It contains the following directories and files.



Previous      Contents      Index      Next     


Copyright 2003 Sun Microsystems, Inc. All rights reserved.