Oracle® Access Manager Upgrade Guide 10g (10.1.4.2.0) Part Number B32416-01 |
|
|
View PDF |
If you started the upgrade process from Oracle Access Manager release 6.5 or 7.x, you can skip this chapter because the directory structure remains the same. However, if you started the upgrade from a release earlier than 6.5, there are important directory structure changes that you need to be aware of.
The installed product directory structure remained constant from Oracle Access Manager release 5.2 to release 6.5. With the introduction of localization for multi-language environments in release 6.5, new directories were added, some directories moved, and some were eliminated. This new directory structure is carried forward with 10g (10.1.4.0.1).
Not all new directories reside on all Oracle Access Manager component hosts. This appendix introduces both the earlier directory structure and the new structure.
Starting with the release 6.5, a new directory structure was introduced to accommodate the addition of Language Packs that enable you to display static information to users in their native language. Oracle Access Manager provides a new directory named \oblix\oracle\nlstrl that is created for each component during with the automatic installation of the Oracle National Language Support Library.
The top level directory structure for 10g (10.1.4.0.1) looks like the following:
OracleAccessManager\access
OracleAccessManager\identity
OracleAccessManager\webcomponent
In addition, 10g (10.1.4.0.1) provides additional Language Packs and support for multibyte character sets such as Japanese and Chinese.
Note:
English language messages require no additional Language Pack. All installations include a \lang directory with an \en-us subdirectory for English language messages.With release 6.5 through 10g (10.1.4.0.1), the location of certain files has changed. For example, the location of message files and stylesheets will differ from earlier releases. See these topics for more information:
The default directory structure for the latest Oracle Access Manager PresentationXML libraries is summarized in the next list. Information here introduces some of these changes, which are explained in detail in the Oracle Access Manager Customization Guide:
IdentityServer_install_dir\identity\oblix\apps\AppName\bin
IdentityServer_install_dir\identity\oblix\lang\langTag
IdentityServer_install_dir\identity\oblix\lang\langTag\style0
IdentityServer_install_dir\identity\oblix\lang\shared
WebPass_install_dir\identity\oblix\lang\langTag
WebPass_install_dir\identity\oblix\lang\langTag\style0
WebPass_install_dir\identity\oblix\lang\shared
WebPass_install_dir\identity\oblix\WebServices\XMLSchema
Starting with release 6.5 and continuing forward, Oracle Access Manager installations include a directory named \lang, which includes a named directory (\langtag) for each installed language. For example, langtag en-us contains English-specific directories and files that is included with every installation by default. When you install a Language Pack a \langtag directory is included and named with a specific language tag. In the example here, the French Language Pack was installed:
Note:
Your installation will be English only unless Oracle-provided Language Packs were installed. You can install Language Packs independently after installing or upgrading, to 10g (10.1.4.0.1) as described in the Oracle Access Manager Installation Guide.Each \langTag subdirectory contains ..XML message catalog files for various applications, which you can customize, as well as other .HTML files. In addition, each \langTag directory contains a \style0 directory.
The \lang\shared directory provides default global stylesheets in all languages. For more information about stylesheets and PresentationXML directories, see "About Custom Items and Upgrades" and the Oracle Access Manager Customization Guide.
Note:
In release 6.5 the \engine directory was removed. Also, in release 6.5 the \orig directory was removed, but returned in release 7.0 and remains in 10g (10.1.4.0.1).This directory contains .pdb files used for debugging crashes on Windows systems.
This directory contains a subdirectory for Crystal Reports that includes samples and templates.
On the computer hosting a WebPass, this directory contains subdirectories for Web Services Description Language files; samples; and XMLSchema. For more information, see the Oracle Access Manager Developer Guide.
The Identity Server was formerly known as the NetPoint or COREid Server. There are several new directories for the Identity Server. Some are new starting with release 6.5 and continuing through10g (10.1.4.0.1) and some are new as of 10g (10.1.4.0.1):
IdentityServer_install_dir\identity\oblix
Table A-1 shows the subdirectories and files that are part of 10g (10.1.4.0.1) located in IdentityServer_install_dir\identity\oblix.
Table A-1 IdentityServer_install_dir\identity\oblix Subdirectories
6.5 to 10g (10.1.4.0.1) | Earlier Subdirectory | File type |
---|---|---|
\apps |
\apps |
Application subdirectories with related files |
\config |
\config |
Configuration files |
\data |
\data |
Runtime-related configuration files |
\data.ldap |
\data.ldap |
LDAP-related configuration files |
\include |
\include |
Include files for third-party integration |
\lang |
Contains the following subdirectories: --\shared directory of default global stylesheets --\en-us (\langtag)language-specific files/directories: -- message files in a specific language --\help directory in a specific language --\style0 (default wrapper stylesheets) |
|
\lib |
\lib |
Library files |
\logs |
\logs |
Log files |
|
|
Mail files |
\obsymbols |
.pdb files used for debugging crashes on Windows systems |
|
\oracle |
Files for the Oracle National Support Library |
|
\orig |
\orig |
Copies of the parameter files with default settings Oracle Customer Care or Professional Services can use these files during troubleshooting to determine if customization of a file is causing a problem. |
\reports |
Crystal reports samples and templates |
|
\scoreboard |
Scoreboard files used by SNMP |
|
\tools |
\tools |
Utility applications (migration_tools and other directories) |
\unsupported |
\unsupported |
Useful tools, utilities, and code examples that have not been tested by Oracle Quality Assurance |
There are several new directories for WebPass, starting with release 6.5 and continuing through 10g (10.1.4.0.1), as shown:
WebPass_install_dir\identity\oblix
Table A-2lists the subdirectories and files that are part of 10g (10.1.4.0.1) located in WebPass_install_dir\identity\oblix:
Table A-2 WebPass_install_dir\identity\oblix Directories
6.5 to 10g (10.1.4.0.1) Subdirectory | Earlier Subdirectory | File type |
---|---|---|
\apps |
\apps |
Application subdirectories and files, including the Identity System Administration files |
\config |
\config |
Configuration files. |
\lang |
Contains the following: --\en-us and other language-specific subdirectories that are not an exact duplicate of those on the Identity Server --\java subdirectory --the \shared directory of default global files that WebPass uses in response to requests |
|
\lib |
\lib |
Library files |
\logs |
\logs |
Log files |
\obsymbols |
.pdb files used for debugging crashes on Windows systems |
|
\oracle |
Files for the Oracle National Support Library |
|
\orig |
\orig |
Copies of the parameter files with default settings Oracle Customer Care or Professional Services can use these files during troubleshooting to determine if customization of a file is causing a problem. |
\tools |
\tools |
Utility applications (migration_tools and other directories) |
\unsupported |
\unsupported |
Useful tools, utilities, and code examples that have not been tested by Oracle Quality Assurance |
\Webservices |
XML schema files for specific applications and more |
|
Release 6.5, 7.0 and 10g (10.1.4.0.1) Files |
Previous Files |
Description |
.apacheconfig |
.apacheconfig |
Directives for Apache Web servers |
.nsconfig |
.nsconfig |
Directives for Sun (formerly Netscape/iPlanet) Web servers to hide files in the Oracle Access Manager system that should not be viewable from a browser |
index.htm |
index.htm |
Startup Web page with .htm extension |
index.html |
index.html |
Startup Web page with .html extension |
The Access System consists of three components (Policy Manager, Access Server, WebGate). The Access System is optional.
Starting with release 6.5 and continuing through 10g (10.1.4.0.1), there are several new directories for the Access System components:
The following subdirectories are included for all Access System components:
The following additional subdirectories are included on the Policy Manager only:
The following additional subdirectories are included on the Access Server and WebGate for use with certain third-party integrations:
The Policy Manager was formerly known as the Access Manager component. Not all directories are available on all Access System components. The following subdirectories and files are part of 10g (10.1.4.0.1) located in the PolicyManager_install_dir\access\oblix:
Table A-3 Policy Manager_install_dir\access\oblix Directories
6.5 to 10g (10.1.4.0.1) Subdirectory | Earlier Subdirectory | File type |
---|---|---|
\apps |
\apps |
Application subdirectories with related files |
\config |
\config |
Configuration files |
\data |
\data |
Runtime-related configuration files |
\data.ldap |
\data.ldap |
LDAP-related configuration files |
\lang |
Contains the following subdirectories: --\en-us and other language-specific subdirectories that contain: --\docs (Web server setup docs) --\help --\style2 --\shared (.js files) |
|
\lib |
\lib |
Library files |
\logs |
\logs |
Log files |
\obsymbols |
.pdb files used for debugging crashes on Windows systems |
|
\orig |
\orig |
A copy of all message and parameter files required for future migration to newer versions of Oracle Access Manager |
\tools |
\tools |
Utility applications (migration_tools and other directories) |
Not all directories are available on all Access System components. The following subdirectories and files in 10g (10.1.4.0.1) are located in the AccessServer_install_dir\access\oblix as:
Table A-4 Access Server_install_dir\access\oblix Directories
6.5-10g (10.1.4.0.1) Subdirectory | Earlier Subdirectory | File type |
---|---|---|
\apps |
\apps |
Application subdirectories with related files |
\config |
\config |
Configuration files |
\data |
\data |
Runtime-related configuration files |
\data.ldap |
\data.ldap |
LDAP-related configuration files |
\engine |
\engine |
Files used to create and audit messages |
\lang |
Contains the following subdirectories (also on the WebGate host): --\en-us and other language-specific subdirectories that contain language-specific message catalogs and: --\docs (Web server setup docs) --\help --\securid subdirectories --\securitybridge subdirectory --\style2 |
|
\lib |
\lib |
Library files |
\logs |
\logs |
Log files |
\obsymbols |
.pdb files used for debugging crashes on Windows systems |
|
\orig |
\orig |
Copies of the parameter files with default settings Oracle Customer Care or Professional Services can use these files during troubleshooting to determine if customization of a file is causing a problem. |
\reports |
Crystal Reports samples and templates (Not on WebGate) |
|
\scoreboard |
Files used by Oracle Access Manager SNMP (Not on WebGate) |
|
\sdk |
\sdk |
Software development kit files (Not on WebGate) |
\tools |
\tools |
Utility applications (migration_tools and other directories) |
In addition to the directories described in"Subdirectories for the Access Server", the directories here are included and WebGate information is added to the WebGate_install_dir\access\oblix:
\_ivmWebGate
\_uninstWebGate
The next discussions identify changes for Oracle Access Manager stylesheets and messages as follows:
PresentationXML Directories with Oracle Access Manager Release 6.5 and Later
PresentationXML Directories Before Oracle Access Manager 6.5
If you have upgraded from release 6.5 or later (or your earlier installation did not include custom images, styles, or JavaScript that you want to use with 10g (10.1.4.0.1)), you can skip this discussion.
Oracle Access Manager default Classic Style stylesheets and the PresentationXML library are now stored as shown here. For more information, see Appendix A, "Oracle Access Manager Directory Structure Changes" and the Oracle Access Manager Customization Guide:
The contents of the default 10g (10.1.4.0.1) directories for the Identity Server are outlined in Table A-5. This directory structure was introduced in Oracle Access Manager release 6.5 and continues through 10g (10.1.4.0.1).
Table A-5 Default PresentationXML Libraries Release 6.5 and Later
Default Oracle Access Manager Directories | Contents |
---|---|
IdentityServer_install_dir\identity\oblix\apps\AppName\bin where AppName can be common, groupservcenter, objservcenter, userservcenter, and so on. |
Registration and parameter files specific to the application. |
IdentityServer_install_dir\identity\oblix\lang\langTag where langTag represents an installed language, such as en-us (English) or fr-fr (French). |
Message files for various applications. |
IdentityServer_install_dir\identity\oblix\lang\langTag\style0 |
|
IdentityServer_install_dir\identity\oblix\lang\shared |
XSL stylesheet templates for various applications |
The contents of the default 10g (10.1.4.0.1) WebPass directories identified earlier are outlined in Table A-6. This directory structure was introduced in Oracle Access Manager 6.5 and continues through 10g (10.1.4.0.1).
Table A-6 Default WebPass PresentationXML Libraries Release 6.5 and Later
Default WebPass Directories | Contents |
---|---|
WebPass_install_dir\identity\oblix\lang\langTag |
Contains message files for various applications |
WebPass_install_dir\identity\oblix\lang\langTag\style0 |
|
WebPass_install_dir\identity\oblix\lang\shared |
|
WebPass_install_dir\identity\oblix\WebServices\XMLSchema |
Contains XML schema files for specific applications |
For more information about directories and their content, see the Oracle Access Manager Customization Guide.
If you have upgraded from release 6.5 or later (or your earlier installation did not include custom images, styles, or JavaScript that you want to use with 10g (10.1.4.0.1)), you can skip this discussion.
The PresentationXML library was provided under two directories and distributed depending upon how the files were likely to be used. For example, stylesheets that define the default Oracle Access Manager Classic Style are maintained in flat files in the file system directory:
For example:
The pre-6.5 Identity Server directory structure IdentityServer_install_dir\identity\oblix\apps\AppName (common, groupservcenter, and so on) is summarized in Table A-7.
Table A-7 Pre-6.5 Identity Server PresentationXML Libraries
\bin | \ui | \xmlschema |
---|---|---|
Dynamically-loadable code for the application, and the registration file, message file(s) and parameter files specific to the application |
Stylesheets for the application(in one or more style directories) |
XML schema files specific to the application |
The pre-6.5 WebPass directory structure is summarized in Table A-8. For example, WebPass_install_dir\identity\oblix\apps\AppName (common, groupservcenter, and so on):
Table A-8 Pre-6.5 WebPass PresentationXML Libraries
\bin | \ui |
---|---|
JavaScript files |
Stylesheets and GIFs specific to the application(in one or more style directories). |
For more information, see the Oracle Access Manager Customization Guide for your earlier release.
Prior to release 6.5, Oracle Access Manager messages were controlled by an XML file for a specific application. For example:
IdentityServer_install_dir/identity/oblix/apps/appname/bin/appnamemsg.xml
where IdentityServer_install_dir is the directory where the Identity Server is installed and appname matches a specific application, as follows:
groupservcenter--Group Manager
objservcenter--Organization Manager
Each appnamemsg.xml file contained multiple paired sets of data, in the form:
<Message MsgTag="the tag name">The tag text</Message>
In 10g (10.1.4.0.1), these message files now reside in specific language directories. For example: IdentityServer_install_dir/identity/oblix/lang/langTag/oblixbasemsg.xml.
For more information, see the Oracle Access Manager Customization Guide.