Organization of Software Resource Files

This section describes how files that contain Access Manager software messages are organized. Access Manager software messages are stored in three file formats:

• Java properties

• XML

• MO

Software messages displayed in the Administration Console (using a browser) are stored in these two formats:

• Java properties

• XML

Software messages displayed in the command-line interface (using a terminal window) are stored in the MO files format.

The next three subsections describe the organization of these three software message formats.

Java Properties Files

Java properties files are resource files that contain most of the software messages to be displayed in the Access Manager Administration Console. Java properties files should be saved in escaped Unicode format. Otherwise, multibyte characters are likely to be incorrectly displayed. To ensure the correct format of Java properties files, after each change, run the native2ascii binary as follows: native2ascii filename

For more information about the native2ascii binary, go to http://java.sun.com/j2se/1.4.2/docs/tooldocs/solaris/native2ascii.html.

Java properties files are located under AM_INS/locale.

Each of the seven supported languages contains 70 Java properties files. The Access Manager Java properties files naming convention is as follows: amfunctionality_locale.properties

This document uses a Dutch (nl) version of Access Manager as an example language.

Java properties files for the Dutch version of Access Manager are under AM_INS/locale.

The following Java properties are for Dutch language:

• amAdminConsole_nl.properties

• amAdminModuleMsgs_nl.properties

• amAgent_nl.properties

• amAuthAD_nl.properties

• amAuthAnonymous_nl.properties

• amAuthApplication_nl.properties

• amAuthCert_nl.properties

• amAuthConfig_nl.properties

• amAuthContext_nl.properties

• amAuthContextLocal _nl.properties

• amAuthDataStore_nl.properties

• amAuthenticationDomainConfig_nl.properties

• amAuth_nl.properties

• amAuthHTTPBasic_nl.properties

• amAuthJDBC_nl.properties

• amAuthLDAP_nl.properties

• amAuthMembership_nl.properties

• amAuthMSISDN_nl.properties

• amAuthnSvc_nl.properties

• amAuthNT_nl.properties

• amAuthRadius_nl.properties

• amAuthSafeWord_nl.properties

• amAuthSAML_nl.properties

• amAuthSecureID_nl.properties

• amAuthUI_nl.properties

• amAuthUnix_nl.properties

• amAuthWindowsDesktopSSO_nl.properties

• amBinarySecurityToken_nl.properties

• amClientData_nl.properties

• amClientDetection_nl.properties

• amCommonUtils_nl.properties

• amConfigurator_nl.properties

• amConsole_nl.properties

• amDelegation_nl.properties

• amDisco_nl.properties

• amEncryption_nl.properties

• amEntrySpecific_nl.properties

• amFederation_nl.properties

• amG11NSettings_nl.properties

• amIdRepo_nl.properties

• amIdRepoService_nl.properties

• amInteraction_nl.properties

• amLDAPv3Repo_nl.properties

• amLibertyDSTService_nl.properties

• amLibertyPersonalProfile_nl.properties

• amLibertySecurity_nl.properties

• amLogging_nl.properties

• amMeta_nl.properties

• amNaming_nl.properties

• amPasswordReset_nl.properties

• amPasswordResetModuleMsgs_nl.properties

• amPlatform_nl.properties

• amPll_nl.properties

• amPolicyConfig_nl.properties

• amPolicy_nl.properties

• amProfile_nl.properties

• amProviderConfig_nl.properties

• amSAML_nl.properties

• amSDK_nl.properties

• amSecurity_nl.properties

• amSession_nl.properties

• amSOABinding_nl.properties

• amSSOProvider_nl.properties

• amUser_nl.properties

• amUtilsMsgs_nl.properties

• amValidation_nl.properties

• amWebAgent_nl.properties

• amWSSecurity_nl.properties

• amWSSProvider_nl.properties

XML Files

Access Manager XML files contain software messages to be displayed in the Administration Console. These XML files are used by the authentication service to display the localized authentication (login) screen based on a particular module type. Save XML files under UTF-8 encoding after each modification. To ensure that an XML file is saved under UTF-8 encoding, the Solaris binary iconv can be used as follows: iconv -f current-file-encoding -t UTF-8 filename

For more information about the iconv binary, go to http://docsun.cso.uiuc.edu/sun_docs/C/solaris_9/SUNWaman/hman1/iconv.1.html.

Access Manager XML files are located under this directory: AM_INS/web-src/services/config/auth/default_locale/

For example, the location of the XML files for the Dutch version of Access Manager is the AM_INS/web-src/services/config/auth/default_nl/ directory.

The following XML files are for the Dutch version of Access Manager:

• AD.xml

• Anonymous.xml

• Application.xml

• Cert.xml

• DataStore.xml

• HTTPBasic.xml

• JDBC.xml

• LDAP.xml

• Membership.xml

• MSISDN.xml

• NT.xml

• RADIUS.xml

• SafeWord.xml

• SAML.xml

• SecurID.xml

• Unix.xml

• WindowsDesktopSSO.xml

MO Files

MO files are resource files that contain software messages to be displayed in the Access Manager CLI. MO files are commonly generated from PO files. MO files are located under AM_INS/locale/locale.UTF-8/LC_MESSAGES/

Generate MO files in UTF-8 encoding by doing the following:

• Adding a charset specification within a PO file that contain localized messages

• Generating the MO file from that PO file using the msgfmt utility

The msgfmt utility is delivered as part of the gettext package. For more information about this package, go to http://www.gnu.org/software/gettext/.

For example, the location of the MO files for the Dutch version of Access Manager is the AM_INS/locale/nl.UTF-8/LC_MESSAGES/ directory.

The MO files for the Dutch version of Access Manager are as follows:

• am_auth_unix_keys.mo

• amhasetup.mo

• amsfoconfig.mo

• backup_restore.mo

• dpscripts.mo

For instructions on how to generate an MO file under UTF-8 encoding, see Hands-on Lab Format.