Customization examples

Hi everybody,
I would like to request you all for the examples of custom developed info objects, infocubes, ODS objects, infosources and queries etc. and also the situations and environment which led you to do so?
Thanks in advance.
Anita

1. The client had a requirement to implement a new business process in SAP R/3. So new screens, new tables etc. Later, when the requirement cam to report on this data, we had to custom built cubes, ODS and queries in BW.
2. Clients added some more fields to the standard Sales Order header and item tables. So the existing LO Datasources needed to be enhanced to include these new fields.
3. Clients has a standard report that they have been using for years. They wanted the same report to be available after they implemented SAP. So it had to be custom built.
These 3 scenarios and their variations I think covers most of the reasons why client goes for customizations and we earn our bread

Similar Messages

OA framework customization examples

Hi,
I want to customize iprocurement pages. R11i.
How do I go ahead with this.
Cheers

User,
There are lots of blogs available online with examples which talks about OAF Customizations.
Refer:
https://blogs.oracle.com/prajkumar/
Anil's Oracle Application Framework Blog: Extensions in OAF
https://blogs.oracle.com/manojmadhusoodanan/
If you need more details, you need to let us know what exactly you want to do.
Cheers
AJ

Logic GUI Customization - Example

Hello fellow logicians!
I've been using Logic Pro 8 with a custom skin for some time now. And being quite happy with the looks even after longer exposure I'd like to share my experience. You can find a screenshot here:
http://imagebin.org/58243
Tell me what you think. I'm not sure about the legal situation here and if I may just make the customized resources available for everyone. So if you would like to test drive this skin please tell me and I'll see what's possible.
Cheers,
Jazz

I've packed things up and you can download my skin pack from
http://public.me.com/andreastell
Please make sure to leave some feedback
You'll also find a little plugin there that you should give a try if you work a lot with real stereo material.
Cheers,
Jazz

11g JDEV Customization documents and examples ?

All,
We are working on JDEV Customizations(Customizing Applications with MDS) and we are looking for some customization documents and examples as well.
Could anyone share some more documents and customization examples ?
Thanks,
Prabakar.

JDeveloper and OC4J 11g Technology Preview

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

6.1 search engine customization doc error

I'm not sure who to report this to, but there seems to be an error in the documentation for the search engine customization examples.
The page is at http://docs.sun.com/source/817-1831-10/agsearch.html
The section in question says, "The following sample code lists the top ten articles on Java Web Services on a site"
The first line of HTML/JSP says:
<s1ws:search Collection="Articles" Query="Java Web Services" />
Note that "Collection" and "Query" are uppercase.
If you copy that whole example block into a JSP and run it, you get server errors.
On my machine (Win 2000), the error messages say the attributes are invalid according to the TLD. In the TLD, they're lowercase and if I change them to lowercase, the page runs (after having changed the collection to match my local config.)
If that saves anybody any headache time, so be it.
Dave

Thanks for the note, David. It's been forwarded along.

Customizing Convergence 2 (patch 1) - From address

I am looking for some help on customizing something specific in Convergence 2. It is not documented in the Convergence Customization Guide on the Oracle Wiki for CommSuite (http://wikis.sun.com/display/CommSuite/Convergence+2+Customization+Guide).
I would like to be able to disable the "From" feature that becomes enabled in Options after creating a new message. This option only appears when there are multiple Identities (Local Account + any more). The new Identities get created each time an External Account is created.
I have found how to disable the ability to add an External Accounts entirely but this is a bit too extreme for what I want to accomplish.
Also this (http://wikis.sun.com/display/CommSuite/Customization+Example+-DisablingIdentity+Settings+in+Convergence+2) just prevents users from editing the Identity values. But they still get created when an External Account is created.
I think what I am looking to change is contained in js/iwc/widget/mail/CreateMessage.js .. somewhere around this code
//senderId
dojo.forEach(iwc.userPrefs.senderidentities.identity, function(id) {
var label = '<' + id.email + '>';
if (id.displayname)
label = '\"' + id.displayname + '\" ' + label;
this.senderId.addOption({"label": label, "value": id.identityname});
}, this);
I am not a dojo guru and so need a little help on what changes to make to c11n/allDomain/js/customize.js and then c11n/allDomain/js/widget/CreateMessage.js
Solaris X86_64 running Convergence 2-1.01.
Application server GlassFish Enterprise Server v2.1.1 Patch10
Oracle Communications Messaging Exchange Server 7u4-21.01 64bit
Edited by: kmac on Oct 27, 2011 1:21 PM

Oracle has created a customization guide for my specific needs:
http://wikis.sun.com/display/CommSuite/Customization+Example+-RestrictingOutgoing+Mail+by+Only+Allowing+Local+Account+Identity+Parameters

Collapsible Section minimize by default

When I create a section collapsible I see my section expanded.
Is possible to get minimize by default?
Thanks!!

The fact that a section is collapsed is actually a container state as visible in the XML behind a saved customization. The XML storing the definition of the dashboard only contains collapsilble="true" or "false", but not the actual state.
Customization example:
<?xml version="1.0" encoding="utf-8"?>
<sawsel:dashboardSelections xmlns:sawsel="com.siebel.analytics.web/dashselections/v1" xmlns:sawst="com.siebel.analytics.web/state/v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="0.7">
<sawst:envState xmlVersion="200811100"><sawst:container cid="d:dashboard" xsi:type="sawst:topLevelStateContainer">
<sawst:container cid="p:5f17p12grfof9tb1" xsi:type="sawst:page" inDashboardPage="true">
<sawst:container cid="r:or12dfr4au2qvktmj" xsi:type="sawst:report" defaultView="compoundView!1" folder="/shared/something" itemName="something"/>
<sawst:container cid="s:0hq4f94fvkfgpg" xsi:type="sawst:section" minimized="true"/></sawst:container></sawst:container></sawst:envState></sawsel:dashboardSelections>Key part: xsi:type="sawst:section" minimized="true"
Not sure if creating a shared customization valid for all users for each and every single dashboard page would be worth it.

OIM Catalog - hiding certain entries in the catalog for users.

Hi,
I'm trying to hide some entries for the common user in the Catalog. They should be visible for power users.
I'm looking into the filter model of the table-component, which seems like a logical way for me. But it seems that I would have to implement a lot of code? Is there something TableFilterBean
I'm wide open for suggestions on how to implement this. It doesn't have to be a filter Model.
The criteria is that based on the current user some of the catalog-items should be hidden.
[Catalog-customization|http://fusionsecurity.blogspot.no/2012/09/oim-11g-r2-catalog-customization-example.html] . This shows a way to avoid users selecting items, but my requirement is to hide them.
Regards,
Kenneth (Not very experienced with OIM :-) )

In order to hide a component of field, open that field in Web Composer by clicking on Customize link.
Select the component or field you want to hide, click on Edit Component button at the top.
Now you can see a property with the name Show Component.
Click on the Expression builder of the property and Replace "true" with the #{oimcontext.currentUser.roles['SYSTEM ADMINISTRATORS'] != null}
Now in this case if the user is having SYSTEM ADMINISTRATORS role then only the component or field is visible to the user.
You can put the condition with your own role.

Account Generator - Release 11 Asset Module

Does anyone have suggestions on making Acct Generator run faster? We have approx 15,000 active assets and 70,000 retired assets. In test, this program runs for 3 days and then errors out at 15000 records. Oracle keeps saying that the initial run will "take a long time". I cannot accept that as an answer. We have applied all the latest patches to the FA Module as well. HELP!

You can access the information in Metalink via the Technical Libraries, under Financial Apps, under AP and then look at the manuals available. There are manuals on the Account Generators and how to alter them. You must use the Workflow Builder to edit the workflow processes and functions. The functions can be changed via SQL to do what you want.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by jossle:
I am seeking information about the customization of Account Generator, and the interaction of Workflow and Account Generator in Oracle Financials, Rel. 11. My goal is to load account information in Oracle Purchasing and Accounts Payable based on project association.
When I read about Account Generator, there are "further reading" references to Oracle Workflow. However, in the Workflow manual, I do not find any references to Account Generator. There are also references to Flexfields Manual for Release 11 which I do not have.
Can anyone tell me if the Release 11 Flexfields manual has useful information pertaining to the customization of Account Generator?
Does anyone know what is the best instructional source for customizing Account Generator and making it operational? (or should I say "developing a process in Workflow using SQL, and tying it to Account Generator?).
What method is used for Workflow development -- drag and drop, PL-SQL, or a combination of the two?
How are processes edited in Workflow? Are the graphic depictions of processes in Workflow, and in the Customization example in Oracle Projects Manual, editable? How do I access the code?
I know what SQL statements to use in order to retrieve the the account information that is needed. I just don't see where or how to insert it into Workflow (if that is the correct approach).
<HR></BLOCKQUOTE>
null

Oracle9i Report

Hi all:
Have any customize example or suggestion about how to make Jheadstart application with Oracle9i report service cowork ?

You can use a generic JavaScript function:
function doReport(params)
var url = "http://reportservermachine.myweb.nl/cgi-bin/rwcgi60/rwdgi60?" + params;
this.window.location.href=url;
That is called by a report specific JavaScript function:
function preDoReport(reportname, param1, param2)
var params = reportname.value + "&p_param1=" + param1.value + "&p_param2=" + param2.value;
doReport(params);
You can call this for example by using a button.
You also can make it more generic, by parameterizing the URL of the report server, and by changing the functions to pass an array of parameters that can have any size, instead of a fixed number.
Jan Kettenis
JHeadstart Team

Adding web links into FIM pages

Is it possible to add web links or text or even tool tip texts to parts of FIM?
For example, I would like to add a compliance statement for photos in the FIM portal so that when users choose to upload their own photos, they're prompted with a statement about acceptable and professional photos. I haven't seen any customization examples
of this - please advise.
Thanks

Thanks for the tip. I've made some progress, but am not sure if I'm heading in the right direction. I've edited the RCDC Configuration for User Editing as shown below:
<my:Control my:Name="PhotoUpload" my:TypeName="UocFileUpload" my:Caption="Photo - must comply with corporate policy (www.corppolicy.com)." my:Description="" my:RightsLevel="{Binding
Source=rights, Path=Photo}">
        <my:Properties>
          <my:Property my:Name="MaxHeight" my:Value="100"/>
   <my:Property my:Name="MaxWidth" my:Value="100"/>
          <my:Property my:Name="Required" my:Value="{Binding Source=schema, Path=Photo.Required}"/>
          <my:Property my:Name="ContentType" my:Value="Image"/>
        <my:Property my:Name="MaxFileSize" my:Value="12288"/>
          <my:Property my:Name="AllowedFileTypes" my:Value="*.gif; *.jpg; *.jpeg; *.png; *.bmp; *.tif; *.tiff"/>
          <my:Property my:Name="ImageUrl" my:Value="~/_layouts/images/MSILM2/defaultuserphoto.gif"/>
          <my:Property my:Name="Value" my:Value="{Binding Source=object, Path=Photo, Mode=TwoWay}"/>
          <my:Property my:Name="PromptForNoValue" my:Value="%SYMBOL_PhotoPromptForNoValueCaption_END%"/>
          <my:Property my:Name="AlternateText" my:Value="{Binding Source=schema, Path=Photo.DisplayName}"/>
        </my:Properties>
      </my:Control>
This produces an image as shown below:
Ideally I want to have the ability to wrap the highlighted text (as everything just gets pushed along currently) and include a hyperlink to pop-up a new window. Is there a quick and easy way to do this?
Thanks

Looking for Some Examples / Best Practices on User Profile Customization in RDS 2012 R2

We're currently running RDS on Windows 2008 R2. We're controlling user's Desktops largely with Group Policy. We're using Folder Redirection to configure their Start Menus as well.
We've installed a Server 2012 R2 RDS box and all the applications that users will need. Should we follow the same customization steps for 2012 R2 that we used in 2012 R2? I would love to see some articles on someone who has customized a user profile/Desktop
in 2012 R2 to see what's possible.
Orange County District Attorney

Hi Sandy,
Here are some related articles below for you:
Easier User Data Management with User Profile Disks in Windows Server 2012
http://blogs.msdn.com/b/rds/archive/2012/11/13/easier-user-data-management-with-user-profile-disks-in-windows-server-2012.aspx
User Profile Best Practices
http://social.technet.microsoft.com/wiki/contents/articles/15871.user-profile-best-practices.aspx
Since you want to customize user profile, here is another blog for you:
Customizing Default users profile using CopyProfile
http://blogs.technet.com/b/askcore/archive/2010/07/28/customizing-default-users-profile-using-copyprofile.aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Windows 8, set default application for example adobe reader, customize the start screen

I have two questions, Im going to deploy Windows 8 to our company, but have 2 big issues.
1) I need to customize the start screen, but cant find anywhere in the gpo´s? How can I do this without sysprepping etc (deploying with SCCM2012 SP1)
2) I need to set the default programs for adobe reader, mspaint etc, how can I do this? It doesnt work with the GPP and folder options, anyone have done this?
Thanks in advance

Hi,
Thanks for posting your question in the forum. First of all, if you want to deploy customized Windows 8 Start Screen for domain users, I suggest we could refer to the following similar threads
and article.
Group Policy for Windows 8 Start
http://social.technet.microsoft.com/Forums/en-us/winserver8gen/thread/13a13c25-a1b2-4665-ab67-a2f9bc3b9bba
GPO Management for Windows 8 Start Screen?
http://social.technet.microsoft.com/Forums/en-US/W8ITProPreRel/thread/2d4bdcc6-3733-470e-939f-8b6eb0ef4492/
Windows 8 Start Screen Customization with MDT
http://blogs.technet.com/b/deploymentguys/archive/2012/10/26/start-screen-customization-with-mdt.aspx
Regarding the second question, since you want to set the default programs via Group Policy but it didn’t work. Would you please let me know how did you configure the setting? Please refer to
the following steps to configure the GPO setting.
To create a new Open With preference item
Open the
Group Policy Management Console. Right-click the Group Policy object (GPO) that should contain the new preference item, and then click
Edit.
In the console tree under
User Configuration, expand the Preferences folder, and then expand the
Control Panel Settings folder.
Right-click the
Folder Options node, point to New, and select
Open With.
In the
New Open With Properties dialog box, select an Action for Group Policy to perform.
Enter Open With settings for Group Policy to configure or remove.
Click the
Common tab, configure any options, and then type your comments in the
Description box.
Click
OK. The new preference item appears in the details pane.
For details, please refer to the following article.
Configure an Open With Item
http://technet.microsoft.com/en-us/library/cc732272.aspx
In addition, I suggest we could collect the following information to narrow down the cause of the issue.
GPMC.log
==================
a. On domain controller, click Start ->Run, type GPMC.MSC, it will load the GPMC console.
b. Right click on "Group Policy Result" and choose wizard to generate a report for the problematic computer and user account (please place appropriately). (Choose computer and select
the proper user in the wizard)
c. Right click
the resulting group policy result and click the "Save Report…" => save report to save the report to a HTML file.
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback
on our support quality, please send your feedback here.
Andy Qi
TechNet Community Support

Examples of Customizations in real time

Hi,
I don't know this is the right place to ask these questions or not.
Can any one please give me some examples for the following from any of your projects you did:
1. Custom Movement types
2. custom Item catergories - In MM i think this is not possible.
3. Release strategy with workflow otherthan PR approval. If Possible any document on this.
    4. Custom document types
    5. Who will use ERS generally and when?
    6. Any document on EDI setup? For what transactions?
    7. Custom Pricing procedure.
    8. Custom material types?
    9. Any major problems that you faced during the implementaion in MM and possibly the solution.
I greatly appreciate it.
Thanks,
Madhu

1. Custom Movement types
you can create custom Mtype using the existing one from OMJJ tcode. the reason to create that is based on the certain bussiness cenario e.g. if you want give the material as free smaple to your sale rep adn you want accoutn thenm separately then you can create new mivement type so you can keep the track.
2. custom Item catergories - In MM i think this is not possible.
It is possible to create if you authorization - generally not required
3. Release strategy with workflow otherthan PR approval. If Possible any document on this.
YOu can create the Rel Str for PO with wrokflow also and there many diff kind of workflow is there to use for diff purpose see the link below
http://help.sap.com/saphelp_erp2005/helpdata/en/33/4c9a34272a5f2ee10000009b38f83b/frameset.htm
4. Custom document types
Most of the project you need to create custom doc type to handle diff kind of scenario
e.g if you don't want to include certian kind of PO in Release then you need this, for reporting purpose based on the diff bussiness process also you need this etc.
5. Who will use ERS generally and when?
ERS is useful for industry like Dairy, oil etc. the reason is..if you incoming material is not based on the PO means normally it is every day to day process where flow of incoming material can not be handled via PO in those cases you will use ERS to settle the vendor invoice based on the GR of material. or if you same number of qty you receive and you generally settle based on the vendor term then you use ERS to settle the invoice.
6. Any document on EDI setup? For what transactions?
WEDI is main tcode - here oyu will find all kind of config and WE20 is partner profile setup
7. Custom Pricing procedure.
Every company you define your own pricing based on the pricing structure of company by using std sap pricing
8. Custom material types?
IF you want to change the std SAP material type for you company reqs then you need to created custom using std and change as per your reqs or SAP has given e.g. RoH for raw material and you want diff your Raw material more diff way then create custom raw maaterial type more than one and assign them to material based on your reqs.
9. Any major problems that you faced during the implementaion in MM and possibly the solution.
Problems is always there at implemntation side but it vary company to company
check SDN forum it seld wher oyu can see the rreal time problems

Customization examples

Similar Messages

Maybe you are looking for