OAM customization error

Question

I wanted to change the font colour of user manager application to red.To get this done i followed the instructions given in the document.the steps have been done in the process are as below.
2.5.1 Prerequisites to Customizing Styles
Be sure to complete the following prerequisites before you start to customize a style. This enables you to keep the original Classic Style (\style0) intact for reference and in case you need to return to it as a last resort.
To prepare to customize styles
As an Identity Administrator, add your own named style as described in the Oracle Access Manager Identity and Common Administration Guide.
The original style stays in effect until an Identity Administrator makes your style the new system default.
As an Identity Administrator, select the new style as the default style so that you can see the effect of any changes you make.
2.5.2 Customization Facts
Style Updates and Maintenance: Default wrapper files in \style0 and default global stylesheets in \shared are periodically updated to instantiate improvements through patches and product upgrades.
The Release Notes notify you when such updates occur so you can propagate the changes to your custom styles. Oracle recommends that you compare the new file with your custom file and propagate any changes to your custom styles. It is risky to overwrite a default style with a customized style that bears the same name.
Be sure to record the changes you make and the files that are involved so you can more quickly update custom stylesheets when you update default styles.
Custom Directory: Stylesheet customization should occur only within your custom directory. Customized stylesheets must reside in your custom directory and relative pointers in all files must point to the files in your custom directory, not to files in \shared.
Registration Files: As discussed in "General Content of Registration Files", a common registration file and each application's registration file contain the names of the stylesheets and schema files needed to present pages for the application. For example, when you look at the User Manager registration file in identity\oblix\apps\userservcenter\userservcenterreg.xml, you can see the application name and the names of the stylesheets the application calls during the completion of various functions.
Also, given the application and the program name, you can locate the corresponding schema file name in the application's registration file.
Oracle recommends that only experienced developers using extreme care consider editing a registration file. Registration files are covered in more detail at "Registration Files".
Pointers: All wrapper files and stylesheets contain pointers as include statements that call another file. Most of these pointers are relative pointers that indicate where within the directory structure the file is without providing an absolute path name.
For example, when you look at the usc_profile.xsl stylesheet called by User Manager functions, you can see that it contains include statements with relative pointers that call the following files:
./basic.xsl
./selectorinfo.xsl
./usc_searchform.xsl
./usc_navbar.xsl
When you change the location of a file (place a copy of a stylesheet in your custom directory for customization), pointers to this file (whether relative or absolute) must be changed to reflect the new location in every file that calls it. All relative pointers in a stylesheet should point to files in your custom directory.
In addition, many stylesheets contain relative pointers to object files. If Oracle Access Manager cannot instantiate an object when the page is loaded, unexpected behavior may result. All relative pointers to object files should be absolute pointers, as discussed in "Editing Stylesheets".
Wrapper Files: Wrapper files include pointers to actual stylesheets in \shared. However, you cannot be assured that a wrapper file is called before the stylesheet because both the common registration file and the application's own registration file call stylesheets according to an internal ordering. For this reason, all wrapper files in your custom directory must be overwritten by a copy of the corresponding default stylesheet from the \shared directory.
Important:
Customizing stylesheets is an iterative process. Attempting to copy the entire contents of \shared into your custom directory at one time produce an error.
Rather than copying all stylesheets at once, you start by investigating registration files to learn which functions (programs) call which stylesheets. You then selectively copy base stylesheets and a function-related stylesheet into your custom directory to overwrite their wrapper files, as discussed in "Copying Stylesheets to Your Custom Directory". You then customize and test the style for that function. When this returns satisfactory results you repeat the process to customize another function.
2.5.3 Customization Guidelines
The following guidelines should help ensure a successful customization.
Retain all original files in the \style0 and \shared directories in pristine condition and store them safely for future use. Also, make a backup copy of your customized style files so that patches won't disrupt your customization.
Record all changes you make and the files that are affected.
Customize and test your new styles in a non-production environment before migrating them to your production environment.
Important:
Oracle recommends that you do not modify original style files in the \shared or \style0 directories. These may be overwritten by patch updates and product upgrades or you may want to refer to them later.
When you use only one style, consider breaking the dependence on stylesheets in the \shared directory (again, to prevent patch\release updates to \style0 and \shared from disrupting customizations). This means that no stylesheet in your custom directory should inherit from or reference a stylesheet in \shared or \style0.
When you use multiple custom styles, consider the pros and cons of sharing customizations between multiple custom styles with implementing individual customizations for each custom style. For example:
Two styles that share the same stylesheet: When two custom styles (custom_style1 and custom_style2) can share the same stylesheet you may be tempted to customize the stylesheet in the \shared directory despite the risk of having your custom style overwritten by an updated stylesheet in a product patch or upgrade.
Two individual styles: When two custom styles (custom_style1 and custom_style2) require their individually customized stylesheets you use the standard methodology and overwrite the wrapper files in your custom directory with the corresponding stylesheets in \shared.
Consider using parameter stylesheet files for a custom style collection, rather than using hard-coded values (tab id's, attribute names, table/link properties, and so on); this is similar to how program code is written using header files.
2.5.4 Customization Methodology Checklist
As mentioned earlier, customization is an iterative process and more of an art than a science. This Guide does not attempt to give precise instructions for getting the presentation you want. Instead, this section outlines the recommended approach for a minor change.
Important:
Oracle recommends that you focus on stylesheets for one function at a time. Attempting to copy all stylesheets from \shared into your custom style directory results in an error.
Table 2-28 Customization Methodology Checklist
Check Action Description
Add a New Style
See the Oracle Access Manager Identity and Common Administration Guide for details about adding a style and selecting your new style as the default.
Choose a Function to Customize
Decide which function to customize first. Oracle recommends that you customize stylesheets related to one function at a time.
Copy Selected Stylesheets into Your Custom Directory
Copy selected stylesheets from \shared to your custom directory to overwrite corresponding wrapper stylesheets:
Base stylesheets
Stylesheets included in base stylesheets
A function-related stylesheet identified in application registration file
Function-related stylesheets identified in oblixbasereg.xml
Customize Stylesheets in Your Custom Directory
Change relative pointers in copied stylesheets to point to files in your custom directory.
Change relative pointers to objects to absolute pointers.
Complete other changes to implement the function's customization.
Record Your Work
Keep a record of the files you change and the changes you make.
Copy Your Custom Directory Structure to WebPass
Build a custom directory structure on WebPass and copy customized styles and images into it.
Note: On WebPass, stylesheets are used only for client-side processing and are not required for server-side processing.
Test Your Customized Style
Test the customized style and make any alterations you need to the stylesheets in your custom directory.
Record the changes.
Customize Another Function
Repeat this process on a function by function basis:
Choose a function.
Copy related stylesheets from \shared to your custom directory.
Customize pointers and styles.
Record and test your work.
Propagate the Customized Style
When you have copied and customized all stylesheets for the application, copy the custom style directory to all Identity Servers and WebPass hosts in your environment.
2.6 Customizing the Identity System Pages
This example shows a method for changing the way a page looks, without changing what it does. The change is a simple font color alteration for a specific page in one application. After making the change you must verify that the change is successful. When you finish this functional customization, you must create the same custom style directory structure on WebPass and copy all image files into it so WebPass can display the appropriate images in response to queries. You then test the implementation.
The following topics demonstrate one sequence in the "Customization Methodology Checklist". You can complete the following procedures to gain first-hand experience:
Task overview: Customizing Identity System pages includes
Completing Prerequisites
Choosing a Function to Customize
Copying Stylesheets to Your Custom Directory
Editing Stylesheets
Copying Images and Styles to WebPass
Testing Your Customized Style
Propagating Styles
See also:
For details about localizing messages, see "Localizing XSL Files".
2.6.1 Completing Prerequisites
A prerequisite to customizing a style is to add a style and select the new style as the default, as described in the Oracle Access Manager Identity and Common Administration Guide. The resulting files and file structure provide the foundation for your customization.
Suppose you added a new style named Pastel in a directory named Pastel and requested files be copied from Classic Style (in directory \style0).
To confirm the results of adding a new style
Add a style and select it as the default, as described in the Oracle Access Manager Identity and Common Administration Guide.
New Custom Directory: Oracle Access Manager creates a directory that duplicates \style0 for the default language, English. If you have installed a Language Pack for French, Oracle Access Manager also creates a directory that duplicates \style0 in the French language directory.
Locate your new custom directory.
For example:
Identity_install_dir \identity\oblix\lang\en-us\Pastel
Identity_install_dir \identity\oblix\lang\fr-fr\Pastel
Wrapper Stylesheets: Your custom directory contains wrapper stylesheets that point to actual stylesheets in another directory. If you selected the Classic Style to copy from, your custom directory duplicates the content of the \style0 directory.
Open a wrapper stylesheet in your new custom directory, basic.xsl, and review the files that it includes.
For this example:
Identity_install_dir\identity\oblix\lang\en-us\Pastel\basic.xsl
<?xml version="1.0" ?>
- <!-- Copyright (c) 1996-2005, Oracle Inc. All Rights Reserved.
-->
- <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
<xsl:include href="./style.xsl" />
<xsl:include href="../msgctlg.xsl" />
<xsl:include href="../../shared/basic.xsl" />
</xsl:stylesheet>
The basic.xsl wrapper stylesheet includes the following three files:
style.xsl file in your custom directory
msgctlg.xsl, one directory up from your custom directory (in identity\oblix\lang\en-us)
basic.xsl in identity\oblix\lang\shared
Locate and review the content of the basic.xsl stylesheet in \shared.
For example:
Identity_install_dir\identity\oblix\lang\shared\basic.xsl
<?xml version="1.0" ?>
- <!-- Copyright (c) 1996-2002, Oblix Inc. All Rights Reserved. -->
- <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oblix="http://www.oblix.com/">
<xsl:include href="obstringutil.xsl" />
- <!-- xsl:output indent="no"/ -->
<xsl:include href="font.xsl" />
<xsl:include href="title.xsl" />
The basic.xsl stylesheet in the \shared directory includes additional files (font.xsl, title.xsl, obstringutil.xsl) and provides templates to define attributes and status and control display information. See "basic.xsl" for more information.
During your customization process, you copy selected stylesheets from the \shared directory into your custom directory. This overwrites wrapper files with corresponding stylesheets you can then edit in your custom directory.
New Custom XML Document: In addition to the custom directory structure, when you select the new custom style as the default style, Oracle Access Manager creates an XML document (a duplicate of style0.xml) named after the directory you created.
Locate and open the custom xml document that was created when you added the new style.
For this example:
Identity_install_dir\identity\oblix\config\style\Pastel.xml
<?xml version="1.0" ?>
- <ParamsCtlg xmlns="http://www.oblix.com" CtlgName="style0">
- <ValNameList ListName="">
<NameValPair ParamName="styleReady" Value="TRUE" />
</ValNameList>
</ParamsCtlg>
This new file, stored with style0.xml, provides the status of your custom style and the location of the original style directory from which wrapper files were copied. For example, if your custom style directory is named Pastel and you copied from Classic Style, the Pastel.xml file is created when you select Pastel as the default style.
You do not need to edit this file. The original style0.xml remains unchanged. Also, there is a .lck version, Pastel.xml.lck, which is a lock file. No other new files are created when you add a new style.
Updated styles.xml: The styles.xml file is updated to include a new NameValPair that provides both the directory and style names you supplied when creating the style.
Locate and open the styles.xml file to confirm it was updated with your new style information.
For example:
Identity_install_dir\identity\oblix\config\style\styles.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
- <ValNameList xmlns="http://www.oblix.com" ListName="styles.xml">
<NameValPair ParamName="style0" Value="Classic Style" />
<NameValPair ParamName="Pastel" Value="Pastel" />
</ValNameList>
In this example, both the default Classic Style and new custom Pastel style are identified. You do not need to edit this file.
After confirming your custom directory structure, new and updated files, you are ready to choose a function and begin your customization.
2.6.2 Choosing a Function to Customize
The first step in the customization process is to choose a function to customize. For this example, suppose you want to change the font color to red on a specific page of the User Manager without changing anything else.
To identify the function and source information
Log in to the Identity System, as usual.
Navigate to the desired page.
For this example, click:
Identity System Console, User Manager, and then click My Identity
The page appears, as shown in Figure 2-6.
Figure 2-6 Customization Example: A User Manager Page Displays Red Text
The following information on each Identity System application page is useful for customizing styles:
Application Name: The application name, User Manager, appears on a highlighted tab in the top left area of the screen.
Each application's \bin directory contains the registration file that you need to identify functions. See "Registration Files".
Page Name: The page name, in this example it is My Profile, is the first page that you want to customize so you can see text in a red font color.
Registration File Path: The URL for each page includes a path to the application page, for example, identity\oblix\apps\userservcenter\bin\userservcenter.cgi. You can use this to locate the relevant registration file on the Identity Server.
Function Name: The URL for each page also includes a segment, program=view in this case, that you can use to locate the relevant stylesheet name for the function in the registration file.
Record the required information to assist you during the customization.
For this example:
Application: User Manager
Page: User Profile
Registration File Path: Identity_install_dir\identity\oblix\apps\userservcenter\bin\
Function: program=view
2.6.3 Copying Stylesheets to Your Custom Directory
Once you have identified the function you want to customize, your next task in any customization is to copy relevant stylesheets into your custom directory from the \shared directory. This activity overwrites wrapper files in your custom directory with copies of stylesheets you can customize. This also retains the original stylesheets in \shared as well as the original default wrappers in \style0.
Locating and copying relevant stylesheets is an iterative process in itself. In the following procedure you must locate and copy:
Base stylesheets
Stylesheets included in base stylesheets
The specific function-related stylesheet identified for the program in the application's registration file, in this case the stylesheet associated with program=view
Stylesheets included in the function-related stylesheet
Eventually your custom directory must contain all stylesheets, including those identified in the application's registration file and in oblixbasereg.xml. Even if you do not need to edit a stylesheet, it must be copied to your custom directory.
Important:
Copying stylesheets is an iterative process that must be done in a selective manner. Attempting to copy all stylesheets from \shared to you custom directory at one time results in an error.
To locate and copy relevant stylesheets
Copy the base stylesheets to your custom style directory from \shared to overwrite the default wrappers with stylesheets you can customize.
For example:
Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ basic.xsl, font.xsl, searchform.xsl, navbar.xsl, title.xsl
Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\
This retains the original base stylesheets in \shared as well as the original default wrappers in \style0.
Open each base stylesheet in your custom style directory and locate include statements that point to other stylesheets you must copy, as well as any style information you need to customize.
For this example, see Table 2-29:
Table 2-29 Base Stylesheet Pointers and Items to Customize
Base Stylesheets in Custom Directory Pointers to Related Stylesheets and Items to Customize
basic.xsl
Contains implied relative include pointers to other stylesheets you need in your local custom directory:
<xsl:include href="obstringutil.xsl" />
<xsl:include href="font.xsl" />
<xsl:include href="title.xsl" />
Record the names of additional stylesheets you must copy into your custom directory from \shared. In this case, obstringutil.xsl.
font.xsl
Does not contain include pointers to other files.
Does contain color information you can customize:
<xsl:variable name="subHeadingColor">#006699...
<xsl:variable name="contentTitleColor">#000000...
<xsl:variable name="contentTextColor">#000000...
searchform.xsl
Does not contain include pointers to other files.
Does not contain color information to customize. No changes needed to this stylesheet in your custom directory.
navbar.xsl
Does not contain include pointers to other files.
Does contain color information you may customize later.
title.xsl
Does not contain include pointers to other files.
Does contain color information you may customize later. No changes needed to this stylesheet in your custom directory.
Copy stylesheets included in base stylesheets to your custom directory from \shared.
For this example, obstringutil.xsl:
Copy from: Identity_install_dir\identity\oblix\lang\en-us\shared\ obstringutil.xsl
Copy to: Identity_install_dir\identity\oblix\lang\en-us\Pastel\obstringutil.xsl
Record the stylesheets you have copied from \shared to your custom directory so you can track your work.
Locate the required registration files.
For this example, oblixbasereg.xml and userservcenterreg.xml:
Identity_install_dir\identity\oblix\apps\common\bin\oblixbasereg.xml Identity_install_dir\identity\oblix\apps\userservcenter\bin\ userservcenterreg.xml
At some point, you typically need stylesheets included in the common registration file oblixbasereg.xml. However, stylesheets included in oblixbasereg.xml are not needed for this example.
For this example, you must locate only the function-related stylesheet in the userservcenterreg.xml file.
Open the application's registration file and locate the function-related stylesheet you need.
For this example, locate ObProgram name="view":
<?xml version="1.0" ?>
- <ObProgramRegistry>
- <ObApplication name="userservcenter">
- <ObProgram name="front">
<ObStyleSheet name="usc_profile.xsl" />
<ObSchema name="usc_front.xsd" />
</ObProgram>
- <ObProgram name="commonNavbar">
<ObStyleSheet name="usc_profile.xsl" />
<ObSchema name="usc_front.xsd" />
</ObProgram>
- <ObProgram name="view">
<ObStyleSheet name="usc_profile.xsl" />
<ObButton name="initiateDeactivateUser" />
- <!-- ObButton name="manageSubscriptions"/ -->
<ObButton name="userreactivate" />
<ObButton name="wfTicketDelete" />
<ObButton name="userModify" />
<ObSchema name="usc_profile.xsd" />
</ObProgram>
You can see in the registration file that the usc_profile.xsl stylesheet is associated with the function you want to customize (ObProgram name="view"). The usc_profile.xsl stylesheet is also associated with a number of other functions.
Copy the function-related stylesheet, usc_profile.xsl, to your custom style directory from \shared and record the stylesheet name.
For this example:
Copy From: Identity_install_dir\identity\oblix\lang\en-us\shared\ usc_profile.xsl
Copy To: Identity_install_dir\identity\oblix\lang\en-us\Pastel\ usc_profile.xsl
Open the function-related stylesheet and locate include statements that point to other stylesheets you must copy, record any information you plan to customize.
For this example, usc_profile.xsl:
Table 2-30 usc_profile.xsl Pointers and Items to Customize
usc_profile.xsl in Custom Directory Pointers to Related Stylesheets and Items to Customize
usc_profile.xsl
This main stylesheet for the User Manager includes stylesheets that must be copied to your custom directory:
<xsl:include href="./basic.xsl" />
<xsl:include href="./selectorinfo.xsl" />
<xsl:include href="./usc_searchform.xsl" />
<xsl:include href="./usc_navbar.xsl" />
Note: selectorinfo.xsl, usc_searchform.xsl and usc_navbar.xsl should be copied.
Also record pointers to objects that should be customized:
<object id="cenroll" classid= ...
codebase="../../common/bin/xenroll.cab" />
and
<script src="../../common/bin/installCert.vbx" ...
Repeat steps to copy relevant stylesheets, then record their names and details you plan to change.
For this example:
Copy From:
Identity_install_dir\identity\oblix\lang\en-us\shared\selectorinfo.xsl
Identity_install_dir\identity\oblix\lang\en-us\shared\usc_searchform.xsl
Identity_install_dir\identity\oblix\lang\en-us\shared\usc_navbar.xsl
Copy To:
Identity_install_dir\identity\oblix\lang\en-us\Pastel\selectorinfo.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_searchform.xsl Identity_install_dir\identity\oblix\lang\en-us\Pastel\usc_navbar.xsl
These stylesheets do not contain include statements, other stylesheet names, nor parameters you need to change.
You have collected, copied, and recorded relevant stylesheets for this example.
2.6.4 Editing Stylesheets
After copying relevant stylesheets, you may need to edit them. As described in Table 2-29 the information that needs to be customized for this example includes:
Font colors defined in the base stylesheet font.xsl should be changed to red.
Pointers to objects defined in usc_profile.xsl should change from a relative path to an absolute path.
Note:
To help streamline development and testing, consider implementing XSL stylesheet control parameters. See "Caching Considerations".
To edit stylesheets for a simple font color change
Open the font.xsl stylesheet in your custom directory in a text editor.
For example,
Identity_install_dir\identity\oblix\lang\en-us\Pastel\ font.xsl
Edit the stylesheet to change all colors from the default color to red (FF0000), then save the change.
For example,
Change all Default Font Colors From:
... <xsl:variable name="pageHeaderColor">#006699</xsl:variable>
<xsl:variable name="subHeadingColor">#006699</xsl:variable>
<xsl:variable name="contentTitleColor">#000000</xsl:variable>
<xsl:variable name="contentTextColor">#000000</xsl:variable>
and others ...
To Red (#FF0000):
... <xsl:variable name="pageHeaderColor">#FF0000</xsl:variable>
<xsl:variable name="subHeadingColor">#FF0000</xsl:variable>
<xsl:variable name="contentTitleColor">#FF0000</xsl:variable>
<xsl:variable name="contentTextColor">#FF0000</xsl:variable>
and others ...
Record your changes to this file.
If you restarted the Identity Server now you would not yet see your changes. This is because you have not yet customized the function-related stylesheet that identifies where to apply the changes.
Edit the basic.xsl stylesheet in your custom directory as follows to add required include statements that were in the original basic.xml (but were lost when you copied over the basic.xsl from the shared folder).
Locate the line containing the following:
<xsl:include href="obstringutil.xsl"/>
Add the following information so that it precedes the line identified in a):
<xsl:include href="./style.xsl" />
<xsl:include href="../msgctlg.xsl" />
Edit the usc_profile.xsl stylesheet in your custom directory to change the relative path to objects, as shown in the following, then save the changes.
For example:
Change From a Relative Path:
- <head>
...<object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="../../common/bin/xenroll.cab" />
... <script src="../../common/bin/installCert.vbx" language="VBScript" />
</head>
Change To an Absolute Path:
- <head>
... <object id="cenroll" classid="clsid:43F8F289-7A20-11D0-8F06-00C04FC295E1" codebase="/identity/oblix/apps/common/bin/xenroll.cab" />
... <script src="/identity/oblix/apps/common/bin/installCert.vbx" language="VBScript" />
</head>
This concludes the specific function-related change for this example.
Ensure that file system access control for new custom style directories and files is set to match the ownership and permissions of \style0.
Restart the Identity Server.
If you log in to the Identity System now and view the My Identity page, you see the red font color. However, the images supplied by WebPass won't appear until they are included in a corresponding custom style directory structure on the WebPass host.
After doing this i checked user manager application then iam being displayed the following error page.
style shhet error report form.
an error has occured while executing the application.
your browser does not support sending email automatically.
please send email to <a=" "><\a> with the following information.
you name
email adress
make sure to append the trace back in the mail
in the log file errors have been given as below
Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl     
"Failed to compile XSL file."     XSL file:^../../../lang/en-us/pastel2/usc_profile.xsl     
Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl     
"OIS_LOG_PASSED_ERROR"     Error^writer\obhtmlpage.cpp:276: Error: ExXSLTProcessingGeneric: Exception processing stylesheet. Root stylesheet ID: ../../../lang/en-us/pastel2/usc_profile.xsl

Answer 1

Hi Matt,
I think the page you are being redirected to is servererror.jsp, which is deployed within oam-server.ear, within its own ngsso-web.war application. You could deploy your own version of this. I assume you could also modify the ErrorPage setting in oam-config.xml to define your own page, though I have not tested this. This would be a customisation, so you would be responsible for the system behaviour when doing this.
Regards,
Colin