Discoverer 9i stylesheet customization ?

We are attempting customization of Discoverer Viewer 9i interface.
We need to add a "Confidentiality" message to the page footer of each screen.
We can see how to do this in gui_components.xsl ...make the mods, add an additional text string to resources/en.xml (call func_build_resource_string) ...but cannot get the modified stylesheet/xml file - gui_components.xsl and the resource file en.xml - to get picked up by Discoverer.
How does one force Discoverer to detect and pick up mods in the stylesheets? Where do we have to put files to force such a change? The only changes we have been able to effect are the logo and basic presentation options in ui_config.xml. IS caching prevent us from seeing the changes?
Any help or suggestions appreciated,

Hello
Are you asking whether the application server can be installed on Windows7, whether you can use Discoverer Plus/Viewer on Windows7 or whether you can install Discoverer Admin/Desktop on Windows7?
I cannot give you a definitive answer on any of these as I have not tried installing 9i any time recently. I can tell you about some of them with Discoverer 10 though.
Using Discoverer 10.1.2 or 10.1.3 I have seen Discoverer Plus/Viewer running successfully on Windows7. However, you cannot use IE8 so you either have to use IE7 or use Firefox. Someone also told me that Google Chrome works ok too.
Using Discoverer 10.1.2 or 10.1.3 I have also seen Discoverer Admin/Desktop successfully installed onto Windows7.
Unfortunately, I have not seen or heard of anyone installing Discoverer Application Server on Windows7. This does not mean that it won't work and I'm sure if anyone reading this has been able to do it that they will let you know. The Application Server is always the most complicated to install.
If you have a Windows7 machine to hand and already have Discoverer 9i up and running I'd just give it a go and see if you can launch a Plus or Viewer window. If you cannot you have not lost anything.
Best wishes
Michael

Similar Messages

OAM customization error

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" ?>
- 
- <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" ?>
- 
- <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: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="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

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

BackUp Procedure for OAM

how can we backup OAM? What are all the things that are to be backed up as a routine process?
What iam trying to achieve is :
Everyday a backup process runs and everything in the backup folder is backed up.
So what and how will I push to this folder so that backup of the same can happen.

A complete OAM installation would have -
1) Install directories for the various components,
2) Web server configuration mods, and
3) Configuration and policy data.
For 1, just back up once after your initial install is done. Typically you would not be changing things around a whole lot in the installation directories - mainly files inside the config directory and logs written by OAM. You can selectively back up those pieces and also any other files (e.g. stylesheet customizations etc.) where you do make changes. While patching/migrating, OAM creates backups before upgrading the installs.
For 2, OAM itself (usually) creates backups of the web server configuration before adding in its edits and if you have webpass, policy manager and webgate on the same web server, you might have up to 3 versions of the configuration files. If your web server is IIS, you need to create the backup yourself.
For 3, you can use snapshots using Configuration Manager (http://download.oracle.com/docs/cd/B28196_01/idmanage.1014/b32392/overview.htm) - that you can restore from later.
Hope that helps.
-Vinod

Customization Of Discoverer Viewer

I Want to Modify Viewer_Config.xml to customize Discoverer Viewer.
I am referring Oracle "Configuration Guide For Oracle 9i Application Server"
In the quick Customization Steps it is written that
Change section <look name = "Corporate Look " > according to your preferred Template name
change the various component values to true or false as required.
And paste the changed one before </layout_templates>
But after doing this i did not get changed reflected in the Discoverer Viewer.
I have restarted Http and discoverer 4i services also
Have any of you have modified the Discoverer 4i Viewer
Pls help
Regards
Awtar

Hello..
Sorry for posting my question here again..
Dear friends..
I need help to customize our discoverer viewer.
We are creating work sheets in arial font size 8.
But, when it's viewing through discoverer viewer it's coming big size.
If we saw the source code by right click, it's taking some scipt where
the font size is mentioned as 8. not 8px.
How I can modify the work sheets in viewer.
Exactly which tag I should modify for this.
And the other thing is the heading section is coming something as
jung.
Like this...
&nb12.09.52 PM 27-OCT-02; 27-OCT-02 &n12.09.52 PM12.09.52 PM
From: 01-JAN-2002 To: 30-DEC-2002o Page :1 / 1
How we will correct this ?
Please reply me as the earliest.
With Thanks & Regards,
Sheeja
[email protected]

Customize Discoverer 10.1.2.48.18 Viewer

We want to customize the Viewer page something like limit the no of export types and also remove the save option which viewer 10.1.2.48.18 gives when the workbook layout is changed or condition formating has been done. We dont want the user to be prompted for save. How can i achieve this ideal case would be to have export such a way that it exports to excel by default when user clicks export. Can this be done ?

Greetings,
Yes it can be done. I have modified our Discoverer View & Plus to have only the Connect To, Username, Password and Database fields. I have not removed the database field. I use the url to pass the Connect To (lm=applications) and the database (db= <database>).
Oracle Metalink note 342255.1 goes into detail on how to modify the page to remove End User Layer. A search on Metalink using UIX will return a several detailed notes on how to modify Discoverer pages.
The notes say that any modification is not supported so make a backup of all files!!!
Best regards,
Con O'Keeffe

Customize Print Quote stylesheet ASOPRINT.xsl

Hi,
I have a requirement where I need to check if we can use the existing Print Quote functionality to generate custom Quote Reports. As i see we can create new XML templates by making changes to the standard style sheet ASOPRINT.XSL. According to what is mentioned in the oracle quoting guide we can add company logo, change height width etc.. of the report by modifying this style sheet. I need to know how do we cusomize the style sheet to include static text or add new tables etc.. I am very new to XSL so do not have much idea as to where is the data fetched from and where is the static text present.
Thnaks
AM

Hi,
Thanks a lot for the response. I went through the documents and they mainly talk about customizing the Quote report by including the company logo, Title and disclaimer. How can we add static text to the ASOPRINT.XSl style sheet in order to customize it and attach it to a custom tempalate. I am very new to this so do not have much idea. can we add the static test directly in the style sheet or is it fetched from somewhere?
Regard
AM

Can i Customize the Discoverer Reports

Hello,
I mean to say that like we make a report in Report Builder and can write text on the report.
So can we write any thing on the report in discoverer?
Regards
Mustafa Ali Qizilbash

Hi
You cannot do this in any of the current production versions. However, in the next release, codenamed Drake, this feature is available in the Plus (web) version.
My sources tell me that the release of Drake, which is really, 10g release 2, is imminent and we should expect to see the software being available on OTN sometime during the month of January.
Hope this helps
Regards
Michael

Discoverer 10G customization

Hi All,
I have customized up my discoverer viewer (10.1.2.55.26) as much as I can using the Oracle docs - but I still have a few questions.
1. How to hide the "Connect To" on the login page but have it default to "OracleBI Discoverer". I have read this article 312463.1 . . close but didn't hit it exactly. This - 400638.1 is the most promising but an OHS re-write rule, so that URLs like:
http://hostname:port/discoverer/viewer
is"re-written" as:
http://hostname:port/discoverer/plus?lm=discoverer
. . . . scares me! Does anyone have the exact steps and code to achieve this.
2. How to hide the "Locale" on the login page
3. How to increase the number of rows retrieved by default from a LOV in Viewer.
Many Thanks

Hi Robert
Hmmm - yes and no is my opinion of that advice. If you have an existing Discoverer Administrator set up on your machine you can add the Desktop component to the same home. You do this by re-inserting or running the original installer. You use the same Oracle Home then select the Custom option. From the Custom screen you can then check Desktop. It will be added as another tool.
If you are using a stand-alone Desktop installer then yes, I agree that you can't use the same Oracle Home as the stand-alone Desktop installler does not have the Administration components and you could, aka more than likely will, mess things up.
Best wishes
Michael

Discoverer - Customize or add new file export

Hi all,
i need to have a file export of worksheets for my customers, i already do this, but some of my customers asked for example to have special characters/dividers in the export files (like csv).
Is there a way to change the divider character ( " ) to another one or better to add and customize the exports and have a second file, like csv2(custom) in the lov exports?
thanks
Alex

I've never tried to alter the separation character but agree that Michael's solution sounds like the correct choice.
The idea of a csv (comma delimited) or a tab delimited file will have a comma or a tab as the delimiter by definition.
After you export as a comma delimited file, as Michael suggests, I bet there will be a freebie program on the net to alter all commas to a different delimiter (so you don't have to edit the output, change the delimiter and maybe change the filetype by editing (seen this happen)).
Russ

How can I customize the stylesheet of webdynpro applications?

Hello experts,
how can I customize the Look & Feel (e.g. background color) of webdynpro applications?
I refer e.g. to UWL which is opened by a task link in an email and opens as as webdynpro application in a separate window. It appears in the typical SAP blue. I would like to change the color.
The portal´s customization does not affect webdynpro applications.
Thanks in advance for any hint.
Thomas

Hi Avi
Yep, that's what you get with AIR output. You have to live
with the skins the AIR layout provides. I suppose if you are a FLEX
developer you might be able to change the skins. But it is what it
is.
You might consider submitting a Wish Form to ask the
development team to allow us more flexibility with AIR skins. Or to
even create a way for the AIR app to use elements of the WebHelp
skins.
Click
here to visit the Wish Form.
Cheers... Rick

Portlet Customizations - Oracle BI 10g (Discoverer + Portal)

on Portal, Discoverer Portlet, how to remove dotted line after worksheet / gauges ???

Hi, I intend to enroll for the Oracle BI 10G course, and need to study and see what are the eligibility criteria for it?
Would appreciate if you can get back directly on my email [email protected]
Intending to enroll and study for this . Thanks for your help
Abhishek

Oracle Portal and Discoverer Integration

Portal Version: 9.0.2.0.1
RDBMS Versjion: 9.0.1.3
OS/Vers. Where Portal is Installed:: Suse 7 SLES
Error Number(s)::
Oracle Portal and Discoverer Integration
We're trying to integrate Discoverer with Portal unsuccessfully.
We made many things in accordance with oracle's documentation until add discoverer portlets (worksheet and list of workbooks) in a test page.
In view mode, the worksheet portlet shows the error:
"The portlet has not been defined. The publisher must define the portlet by clicking on Edit Defaults for the portlet on the edit mode of this page. Please contact the publisher of this page."
We think we have to edit properties before. Is this? Anyway edit worksheet portlet crashes between step 1 and 2. The error is: "The listener returned the following Message: 500 Internal Server Error".
We have a public conection created in EM and a discoverer application which can be viewed using plus or viewer.
Furthermore, it's not possible delete the added portlets neither the page that contain it. The error at delete is:
Error: An unexpected error occurred: User-Defined Exception (WWC-44082)
(WWC-00000)
An unexpected error has occurred in portlet instances: User-Defined Exception (WWC-
44846)
An unexpected error occurred: User-Defined Exception (WWC-43000)
The following error occurred during the call to Web provider:
oracle.portal.provider.v2.PortletNotFoundException
at oracle.portal.utils.v2.ContainerException.fillInStackTrace(Unknown Source)
at java.lang.Throwable.<init>(Throwable.java:78)
at java.lang.Exception.<init>(Exception.java:29)
at oracle.portal.utils.v2.ContainerException.<init>(Unknown Source)
at oracle.portal.provider.v2.PortletException.<init>(Unknown Source)
at oracle.portal.provider.v2.PortletNotFoundException.<init>(Unknown Source)
at oracle.disco.portlet.provider.DiscoPortletPersonalizationMgr.destroy
(DiscoPortletPersonalizationMgr.java:65)
at oracle.portal.provider.v2.DefaultPortletInstance.deregister(Unknown Source)
at oracle.webdb.provider.v2.adapter.soapV1.ProviderAdapter.deregisterPortlet
(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at oracle.webdb.provider.v2.utils.soap.SOAPProcessor.doMethodCall(Unknown Source)
at oracle.webdb.provider.v2.utils.soap.SOAPProcessor.processInternal(Unknown Source)
at oracle.webdb.provider.v2.utils.soap.SOAPProcessor.process(Unknown Source)
at oracle.webdb.provider.v2.adapter.SOAPServlet.doSOAPCall(Unknown Source)
at oracle.webdb.provider.v2.adapter.SOAPServlet.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at com.evermind.server.http.ResourceFilterChain.doFilter
(ResourceFilterChain.java:59)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
at com.evermind.server.http.ServletRequestDispatcher.invoke
(ServletRequestDispatcher.java:523)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal
(ServletRequestDispatcher.java:269)
at com.evermind.server.http.HttpRequestHandler.processRequest
(HttpRequestHandler.java:735)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:151)
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
(WWC-43147)
Edit properties for portlet List of Workbook works but in view mode we have the error in the portlet area:
"Failed to refresh portlet. Please verify that the information used to create the
portlet instance or customization is still valid. Otherwise, please contact your
iAS administrator. oracle.discoiv.controller.FatalControllerException:
DiscoNetworkException - Nested exception: org.omg.CORBA.OBJECT_NOT_EXIST: minor
code: 0 completed: No null"
Any ideas?
Thanks

Hi there,
Have you applied any patches to 9ias since it was first installed? We had the same problem and had to apply a couple of patches to get the portlets working.
1. Apply the 9.0.2.53.16 one-off patch for Oracle 9iAS Discoverer which takes Discoverer up to 9.0.2.53.16. This patch appears to be password protected and you need to get someone at Oracle support to give you a password.
2. Apply the Discoverer Portlet Provider: 9.0.2.53.00c patch (patch no. 2595444) which gives you a new discportal.xsl file that actually works. It's this second step that solves your problem but you need to do step 1 before this. This is password protected as well.
3. As you've upgraded Disco on the server to 9.0.2.53, you'll need to upgrade Disco Admin & Desktop within your 9iDS installation using patch no. 2555265. This is because Disco 9.0.2.53 uses an upgraded EUL that Disco Admin & Desktop need to be patched to use.
This was the course of action Oracle support advised us about nine months ago. Of course they may have released a further patch to Disco that does 1 & 2 in one go, but we regularly carry out steps 1 and 2 on servers we use and we can use the Disco portlets successfully.
Hope this helps
Mark Rittman
[email protected]

Can I use stylesheets to create multiple button styles?

I am trying to create a custom look-and-feel within UIX to get it as close as possible to
our existing application's look-and-feel.
As part of this, I customized the UIX button by overriding the following named style:
ButtonServerText
and also by providing my own icons for:
buttonStart
buttonEnd
buttonTopBackground
buttonBottomBackground
The good news is that I was able to get the button component to look exactly like our existing
application buttons.
The bad news is that we have different types of buttons in our application
for different purposes. (i.e. the image used for the button can be completely different based on the context e.g.
yellow button for important actions and light-blue buttons for secondary actions)
It seems like there is no way in which I can use this stylesheet mechanism to create different types of buttons
and use them within my application. (sometimes different types of buttons can appear on the same page)
Please let me know if there is a way.
This is in fact a general question regarding overriding a stylesheet for customizing look-and-feel.
Lets say I customize the "contentContainer" component using the stylesheet. This change would then be global.
But I do want to have different types of contentContainers in the application. I would be forced to create my own custom
UIX elements similar to contentContainer and write my own renderers.
(I know contentContainer does have the light, medium and dark styles. I used this just as an example.)
Please let me know what my options are.
Thanks,
Jayesh Kapoor

Hi Jayesh -
The good news is that I was able to get the button
component to look exactly like our existing
application buttons.Cool - I'm glad to hear you were able to get this working!
The bad news is that we have different types of
buttons in our applicationRight. This is a fundamental limitation of our look and feel customization functionality - we only support global customizations, not instance-specific customizations. I agree that there are many cases where instance-level customization would be useful, but this just instance supported yet.
The only solution that I can think of for your button dilemma would be to use static images. It's pretty easy to wire up an image to behave like a button - just embed the image in a link and use <fireAction> as the link's primaryClientAction.
Obviously, the downside of this approach is that you need to create the button images manually - which also isn't ideal if you are planning to translate your applications. One possible solution here might be to use UIX to pre-generate your button images. The idea would be to create custom LAFs for each style of button, then create a UIX page for each button style, including <button> instances for each translated value. Then, you could configure UIX to run in the desired look and feel, hit the corresponding page, and UIX will generate the required buttons into your image cache. Again, not ideal, but this might be easier than creating the buttons by hand.
This is in fact a general question regarding
overriding a stylesheet for customizing
look-and-feel.
Lets say I customize the "contentContainer" component
using the stylesheet. This change would then be
global.
But I do want to have different types of
contentContainers in the application. I would be
forced to create my own custom
UIX elements similar to contentContainer and write my
own renderers.Right - this is a generic problem. But for some components, like content containers, an easier solution might be to leverage UIX's templating mechanism. Remember, you can embed arbitrary HTML contents in a UIX page/template by setting the namespace to "http://www.w3.org/TR/REC-html40". You can then reference these templates from your other UIX contents as if they were in fact UIX components. I'd recommend that you explore UIX's template support to see if this will meet your needs.
Andy

How to do Grouping of Workbooks using XSL in Discoverer Viewer?

Hello Discoverer Experts,
My question is related to grouping of workbook names using XSL in Discoverer Viewer. This is a sample xml data file which contains 6 workbooks.
<eul>
     <workbooks>
          <workbook>
               <wb_name>Purchasing Workbook 1</wb_name>
               <worksheets>
                    <worksheet>
                         <ws_name>A</ws_name>
                    </worksheet>
                    <worksheet>
                         <ws_name>B</ws_name>
                    </worksheet>
               </worksheets>
          </workbook>
          <workbook>
               <wb_name>Purchasing Workbook 2</wb_name>
               <worksheets>
                    <worksheet>
                         <ws_name>C</ws_name>
                    </worksheet>
                    <worksheet>
                         <ws_name>D</ws_name>
                    </worksheet>
               </worksheets>
          </workbook>
          <workbook>
               <wb_name>Manufacturing Workbook 1</wb_name>
               <worksheets>
                    <worksheet>
                         <ws_name>E</ws_name>
                    </worksheet>
                    <worksheet>
                         <ws_name>F</ws_name>
                    </worksheet>
               </worksheets>
          </workbook>
          <workbook>
               <wb_name>Manufacturing Workbook 2</wb_name>
               <worksheets>
                    <worksheet>
                         <ws_name>G</ws_name>
                    </worksheet>
                    <worksheet>
                         <ws_name>H</ws_name>
                    </worksheet>
               </worksheets>
          </workbook>
          <workbook>
               <wb_name>CEO Workbook 1</wb_name>
               <worksheets>
                    <worksheet>
                         <ws_name>I</ws_name>
                    </worksheet>
                    <worksheet>
                         <ws_name>J</ws_name>
                    </worksheet>
               </worksheets>
          </workbook>
          <workbook>
               <wb_name>CEO Workbook 2</wb_name>
               <worksheets>
                    <worksheet>
                         <ws_name>K</ws_name>
                    </worksheet>
                    <worksheet>
                         <ws_name>L</ws_name>
                    </worksheet>
               </worksheets>
          </workbook>
     </workbooks>
</eul>
The XSL is generating a List of Workbooks in <table> by using <xsl:for-each select="eul/workbooks/workbook">
<table>
<tr><td>Purchasing Workbook 1</td></tr>
<tr><td>Purchasing Workbook 2</td></tr>
<tr><td>Manufacturing Workbook 1</td></tr>
<tr><td>Manufacturing Workbook 2</td></tr>
<tr><td>CEO Workbook 1</td></tr>
<tr><td>CEO Workbook 2</td></tr>
</table>
Now my question is:
1. The client want to see this report in Groups i.e
<table>
<tr><th>Group Name: Purchasing</th></tr>
<tr><td>Purchasing Workbook 1</td></tr>
<tr><td>Purchasing Workbook 2</td></tr>
</table>
<table>
<tr><th>Group Name: Manufacturing</th></tr>
<tr><td>Manufacturing Workbook 1</td></tr>
<tr><td>Manufacturing Workbook 2</td></tr>
</table>
<table>
<tr><th>Group Name: CEO</th></tr>
<tr><td>CEO Workbook 1</td></tr>
<tr><td>CEO Workbook 2</td></tr>
</table>
How can I achieve this grouping using XSL ? Has anybody tried customizing the XSL file to achieve grouping of workbooks by name?
Any help is highly appreciated.
Thanks in advance.
Warm Regards,
Pranav Desai

Hi Friends..
This is not the reply.
I have also some question..
Some related topic I found on this.
That's why I am posting the same question here also..
Dear friends..
I need help to customize our discoverer viewer.
We are creating work sheets in arial font size 8.
But, when it's viewing through discoverer viewer it's coming big size.
If we saw the source code by right click, it's taking some style sheets where
the font size is mentioned as 8. not 8px.
How I can modify the work sheets in viewer.
Exactly which tag I should modify for this.
And the other thing is the heading section is coming something as
jung.
Like this...
&nb12.09.52 PM 27-OCT-02; 27-OCT-02 &n12.09.52 PM12.09.52 PM
From: 01-JAN-2002 To: 30-DEC-2002o Page :1 / 1
How we will correct this ?
Please reply me as the earliest.
With Thanks & Regards,
Sheeja
[email protected]

How to run "Standard Purchase Order Stylesheet" in EBS

Hi again,
Please, anybody can give some clue for this?
In a r12 instance I have the "Standard Purchase Order Data Source" Data Definitio.
Related to this Data Definition there are 2 Templates
- Standard Purchase Order Stylesheet
- Standard Purchase Order Stylesheet with Logo
my question is... how and were in Oracle Applications (EBS) can I run this report?
where are defined the parameters?
I have searched in the concurrent programs, but I have not been able to find it?
Thanks and regards.
Juanje

The two purchase order stylesheets can be used by the "PO Output for Communication" (POXPOPDF) process found under the Purchasing Responsibilities.
To designate which template you want the "PO Output for Communication" process to use, you can select the template from Purchasing Super User Responsibility > Setup > Purchasing > Document Types. Then select the document type you want to change the template for (i.e. Standard PO) and change the template in the LOV.
This template is designed in the XSL-FO format, not RTF, so it is substantially more difficult to customize than normal XML Publisher templates unless you're proficient at working with code (it works a lot like HTML once you get used to it).
I suggest reading the white paper posted under note: 387670.1 at Metalink ("Oracle Purchasing Document Printing and Communication"). It is a decent document about how the Purchase Order PDF process works and how you can approach customizing the template if desired.
Also, these two (and many other) R12 templates do work in 11.5.10 if you upload them. However, I have not found any good reason to use the R12 template in this case over the 11.5.10 version. There is a lot of extra code specific to R12 functionality that just creates extra overhead (and no notable enhancements for 11i users).
Regards,
-Brian

Discoverer 9i stylesheet customization ?

Similar Messages

Maybe you are looking for