Chromosomes and genes in portal look and feel

Hi everybody.
Has anyone experimented succesfully the use of genes and chromosomes in bea portal 9.2?
I have troubles with look and feel editor, that doesn't show inlined css, and runtime also, that seems to always
get the default.chromosome file instead of the one i configured in the .laf file.
Any point? Thank you.

In regard to your chromosome not working: if you created your .portal file first, and then changed the .laf file, you'll need to reload the markup from Workshop. See the second bullet item on this link: http://edocs.bea.com/wlp/docs92/portals/develop_portals.html#wp1011140
If you want, before you do the above, you can check the markup of your .portal file to see if it's correct. Open your .portal as XML, and find the <netuix:lookAndFeel> element. It should have a attributes for skinChromosome and skeletonChromosome that equal your new .chromosome file's name.
I don't believe that the Look and Feel editor supports inlined CSS rules at this time, but that is an optimization in scope for the next release.
George

Similar Messages

WebDynPro ABAP iViews not picking the portal look and feel

Hi,
In our case , WebDynPro ABAP iViews not picking the portal look and feel.
Is there any way to provide the custom developed portal theme link or css file to the WebDynPro application.
Can it be done programmatically in the WD ABAP application.
Best Regards
Sid

Look at the below link, it will answer your question:
Re: EP 7 Portal stylesheet with WD ABAP
Raja T

Portal look and feel?

Hi,
Can someone please direct me to threads/wiki/blog/sap help for customising portal look and feel like company branding logo and colour themes etc.. I have to a requirement to match SAP Portal interface to look like existing company intranet web site.
Also please let me know how can I transport these portal setting once configured to different environment (QA and PRD).
Thanks
Praveen.

Hi Praveen,
The questions you asked have been posted many a times before. Do search and if you dont get any good results then you may always post.
As for know do refer to the following links:
MastHead Change & Portal Desktop
Portal Customizations Intro - Login Part 1
Portal Customizations Intro - Login Part 2
Portal Customizations Intro - Look&Feel Part 3
http://wiki.sdn.sap.com/wiki/display/EP/LookandFeel
For more information of Themes, Transporting themes - http://help.sap.com/saphelp_nw70/helpdata/en/f4/bb7a3b688d3c1de10000000a11402f/frameset.htm
Thanks,
GLM

Change Portal Look and Feel

Experts,
How to Change Portal Look and Feel u2013 Branding. (Basic Knowledge of JSP and HTMLB required) ?...
Please provide me some link i will be thankful to you guys.
Thanks
Nityanand Arya

Hi
refer to the following links:
[MastHead Change & Portal Desktop|MastHead Change & Portal Desktop]
[Portal Customizations Intro - Login Part 1|MastHead Change & Portal Desktop]
[Portal Customizations Intro - Login Part 2|Portal Customizations Intro - Login Part 2]
[Portal Customizations Intro - Look&Feel Part 3|Portal Customizations Intro - Look&Feel Part 3]
For Portal Themes refer this[http://help.sap.com/saphelp_nw70/helpdata/en/f4/bb7a3b688d3c1de10000000a11402f/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/f4/bb7a3b688d3c1de10000000a11402f/frameset.htm]
Cheers
Chinmaya

Instant Portal Look'n'Feel

Hi,
is there any easy way to transfer the Instant Portal Look'n'Feel into Enterprise Portal?
Are there specific stylesheets that could be plugged into Enterprise Portal?
Any info would be much appreciated?
Thanks,
Peter

Hi
I tried to personalize the instant portal look and feel but it drove me crazy.
Styles are very complex and generated by a stored proc that you can't modify.
In standart portal, it is easy to manage with UI templates, but in instant portal you simply cant' modify them.
If you find a way to do so, let me know.

Wireframes to portal look and feel

hi,
i am working on a webcenter portal application.
as usual, we have got wireframes (html prototypes) from customer which has html, js and css files.
now i have to produce same kind of look and feel on webcenter portal.
please suggest what shall i do?
is this recommended way?
i copy content of css file which i got as part of wireframes into portal-skin.css file, now i use html components (div, ul, li, p etc) in page template and other jspx pages (reference could be the html files which i got in wireframes).
please suggest.

Hi.
You can select two ways:
- Continue with your HTML + CSS and create templates based directly on wireframes. Faster and easier solution for non-adf people.
- Translate your wireframes to a ADF Templates and use ADF Skinning to achieve the styles. Slower and hard if you don't have much experience with it.
About the solution of maintain HTML + CSS:
- Maintain your structure of CSS, images and JS in separated folders of skin folder (In Web Content or in project PortalWebAssets).
- In Skin files (like portal-skin.css) change ADF Skinning of components only. Is the best way to maintain the hierarchy of adf skins.
About the solution full ADF:
- Read this document about full ADF Skin and Templates: http://www.oracle.com/technetwork/middleware/webcenter/portal/learnmore/pagetemplates-1438595.pdf
More info:
- In adf-config.xml you can provide rewrite rules to search your static-files when you are using Web Server (OHS) to server static-files.
I hope this help you.
Regards.

Bug: Data filter and "Mac OS X" look and feel

I am running Mac OS X 10.5.5 and SQLDeveloper 1.5.1 (MAIN-5440). I have the "Look and Feel" set to "Mac OS X." When I attempt to use the "Filter" box in the Data tab of a table, the autocomplete of past values continually selects the whole filter after each keypress, making it impossible to type normally. I have to type the filter into TextEdit, then paste it into SQLDeveloper.
This does not happen in the "Oracle" Look and Feel.

I'm relatively new to OTN, and don't see any place to view/track this bug, or file new ones. I searched around & couldn't find anything - is there such a place? This bug makes using SQLDeveloper on a Mac a real pain the butt. I tried switching over to Oracle look/feel, but then I get weird errors while using keyboard shortcuts (which deserves to be a bug of its own).
On a related note, in case anybody's listening, I've recently upgraded from SQLDeveloper 1.2.x to 1.5.x, and the font used by version 1.5.x Mac OS look & feel is really small & hard to read (and very un-Mac-like). The old font (1.2.x) was much easier to read, and I'd recommend switching it back, or making it configurable. (If there's a good place to officially provide this feedback, somebody plz let me know - thx!)

Instant portal Look and Feel

Guru's,
A customer is looking to brand an instant portal. Here's my question.
Can they change the CSS that is delivered with Instant Portal to Brand?
Can they use the HTML Template capability within Instant Portal
Kwesi

Search this forum for tips. There's an unsupported API (wwpob something...), or you can do a recursive query (think CONNECT BY) that crawls up the page hierarchy or you can select the page GUID from wwv_things (which I'd need to remember how to do), and then access it using /portal/pls/portal/<GUID> syntax.
I'd kinda recommend the last option. It looks to me that Instant Portal does something to that effect.
Thanks for mentioning Instant Portal. I showed it to our web content guy, and he's all excited about it for solving the "i need a departmental intranet!" quagmire.
Now all the portal CM guys need to do is extend those amazing, AJAX-y Instant Portal bits to the rest of the product! That would definitely lower the ease-of-use barrier.

Themes and CSS. Portal Look&Feel

Hello,
We've modified standard themes from portal. Are SAP Chrome SAP Streamline, SAP Tradeshow
CSS files? Please, we need to know if we can upload CSS file (made by ourserlves) to portal and add it to a user.
Thanks!

Hi,
The standard SAP themes are made up of a number of CSS files that are custom to SAP. You can modify them to create your own themes, however it is not a simple exercise of just uploading your own CSS files.
In general you should use the standard Theme Editor available to administrators in the Portal.
Hope this helps,
Simon

I wake up one morning and i turn my laptop on and its all statci looking and then as i swipe to my different screens the apple sign moves It might be a hardware or software crash?

Help

Perform SMC reset and re-verify
SMC reset
Shut down the computer.
Plug in the MagSafe power adapter to a power source, connecting it to the Mac if its not already connected.
On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time.
Release all the keys and the power button at the same time.
Press the power button to turn on the computer.
Note: The LED on the MagSafe power adapter may change states or temporarily turn off when you reset the SMC.
need more specifics
What does this mean: "as i swipe to my different screens the apple sign moves It" , specify.
report back with details.
You can make an appt. with your Apple store for full diagnostics

How to give BSP Iview look and feel of portal??

Hi All,
I've created a BSP application that I use to create an Iview for portal.
I thought that if i used htmlb tags that the look and feel of portal would be automatic to my app but its not.
I've tried assigning portal css classes to a html table but there's no effect.
I've previewed one of the standard ivews and viewed the source and found the path of the css file. But when i looked for it on the server, while the out folder was there (com.sap.portal.design.portaldesigndata) , there was no css files in this folder.
So i'm at a loss. In summary, how do i get my bsp app to have the portal look and feel????? I would prefer to use the css files so that if any changes are made to the standard, the changes will be reflected in my custom iviews too.
Any help, would be most welcome,
Liz.

Hi Liz,
on the properties tab for the BSP application try selecting the "Supports Portal Integration" checkbox.
Cheers
Graham Robbo

SAP Portal Custom Themes to change ESS/MSS UI Look and feel , possible ?

Hi,
I have a requirement where the look and feel of the UI controls of the ESS/MSS applications have to be different - Jazzy
I know XSS homepage framework is for the customisation of Areas, Sub Areas. What I am more interested is only the look and feel UI of ESS/MSS applications.
If I change the standard theme of portal using Theme Editor and create a new custom theme with different back ground colors, fonts, sizes for all the UI controls,.Will the customised Theme apply on the standard ESS / MSS screens ? Also my doubt is we are using EHP3 and I am not sure how many are Webdynpro java based or webdynpro Abap based.
Will the theme apply to both WDA and WDJ application UI controls?
Any inputs in this regard will be of great help. thanks in advance.
Regards,
Sreeram

Hello,
Check :
[Overview on changing the Portal look and feel.|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d077fa17-7fbf-2a10-d983-fb12decf63c7]
FYI :- Search for wiki on : Stylesheet for WDA without integrating in SAP Portal
Cheers,
Remi

Problem With ButtonUI in an Auxiliary Look and Feel

This is my first post to one of these forums, so I hope everything works correctly.
I have been trying to get an axiliary look and feel installed to do some minor tweaking to the default UI. In particular, I need it to work with Windows and/or Metal as the default UI. For the most part I let the installed default look and feel handle things with my code making some colors lighter, darker, etc. I also play with focus issues by adding FocusListeners to some components. I expect my code to work reasonably well no matter what the default look and feel is. It works well with Motif, Metal, and Windows, the only default look and feels I've tested with. What I'm going to post is a stripped down version of what I have been working on. This example makes gross changes to the JButton background and foreground colors in order to illustrate what I've encountered.
I have three source code files. The first, Problem.java, creates a JFrame and adds five buttons to it. One button installs MyAuxLookAndFeel as an auxiliary look and feel using MyAuxButtonUI for the look and feel of JButtons. The next button removes that look and feel. The next button does nothing except print a line to System.out. The next button installs MyAuxLookAndFeel as an auxiliary look and feel using MyModButtonUI for the look and feel of JButtons. The last button removes that look and feel.
The problem is, when I install the first auxiliary look and feel, buttons are no longer tabable. Also, they cannot be invoked by pressing the space button when they're in focus. When I remove the first auxiliary look and feel everything reverts to behaving normally. When I add the "Mod" version, button tabability is fine. The only difference is I've added the following code:
if ( c.isFocusable() ) {
   c.setFocusable(true);
}That strikes me as an odd piece of code to profoundly change the program behavior. Anyway, after adding and removing the "Mod" look and feel, the tababilty is forever fixed. That is, if I subsequently re-install the first look and feel, tababilty works just fine.
The problem with using the space bar to select a focused button is more problematic. My class is not supposed to mess with the default look and feel which may or may not use the space bar to press the button with focus. When the commented code in MyModButtonUI is uncommented, things behave correctly. Even the statement
button.getInputMap().remove( spaceKeyStroke );doesn't mess things up after the auxiliary look and feel is removed. So far I've tested this with JRE 1.4.2_06 under Windows 2000, JRE 1.4.2_10 under Windows XP, and JRE 1.5.0_06 under Windows XP and the behavior is the same.
All of this leads me to two questions.
1. Is my approach fundamentally flawed? I've extended TextUI and ScrollBarUI with no problems. This is the only problem I've encountered with ButtonUI. My real workaround for the space bar issue is better than the one I've supplied in the example, but it certainly is not guaranteed to work for any arbitrary default look and feel.
2. Assuming I have no fundamental problems with my approach, it's possible I've found a real bug. I searched the bug database and couldn't find anything like this. Of course, this is the first time I've tried seasrching the database for a bug so my I'm doing it badly. Has this already been reported as a bug? Is there any reason I shouldn't report it?
What follows is the source code for my example. It's in three files because the two ButtonUI classes must be public in order to work. Thanks for insight you can provide.
Bill
File Problem.java:
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class Problem extends JFrame {
   public boolean isAuxInstalled = false;
   public boolean isModInstalled = false;
   public LookAndFeel lookAndFeel = new MyAuxLookAndFeel();
   private static int ctr = 0;
   public static void main( String[] args ) {
      new Problem();
   public Problem() {
      this.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
      setSize(250, 150);
      setTitle("Button Test");
      JButton install = new JButton("Install");
      JButton remove = new JButton("Remove");
      JButton doNothing = new JButton("Do Nothing");
      JButton installMod = new JButton("Install Mod");
      JButton removeMod = new JButton("Remove Mod");
      this.getContentPane().setLayout(new FlowLayout());
      this.getContentPane().add(install);
      this.getContentPane().add(remove);
      this.getContentPane().add(doNothing);
      this.getContentPane().add(installMod);
      this.getContentPane().add(removeMod);
      install.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            if ( !isAuxInstalled ) {
               isAuxInstalled = true;
               UIManager.addAuxiliaryLookAndFeel( lookAndFeel );
               SwingUtilities.updateComponentTreeUI( Problem.this );
      remove.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            if ( isAuxInstalled ) {
               isAuxInstalled = false;
               UIManager.removeAuxiliaryLookAndFeel( lookAndFeel );
               SwingUtilities.updateComponentTreeUI( Problem.this );
      doNothing.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            System.out.println( "Do nothing " + (++ctr) );
      installMod.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            if ( !isModInstalled ) {
               isModInstalled = true;
               UIManager.addAuxiliaryLookAndFeel( lookAndFeel );
               SwingUtilities.updateComponentTreeUI( Problem.this );
      removeMod.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent e) {
            if ( isModInstalled ) {
               isModInstalled = false;
               UIManager.removeAuxiliaryLookAndFeel( lookAndFeel );
               SwingUtilities.updateComponentTreeUI( Problem.this );
      setVisible(true);
   class MyAuxLookAndFeel extends LookAndFeel {
      public String getName() {
         return "Button Test";
      public String getID() {
         return "Not well known";
      public String getDescription() {
         return "Button Test Look and Feel";
      public boolean isSupportedLookAndFeel() {
         return true;
      public boolean isNativeLookAndFeel() {
         return false;
      public UIDefaults getDefaults() {
         UIDefaults table = new MyDefaults();
         Object[] uiDefaults = {
            "ButtonUI", (isModInstalled ? "MyModButtonUI" : "MyAuxButtonUI"),
         table.putDefaults(uiDefaults);
         return table;
   class MyDefaults extends UIDefaults {
      protected void getUIError(String msg) {
//         System.err.println("(Not) An annoying error message!");
}File MyAuxButtonUI.java:
import javax.swing.*;
import java.awt.*;
import javax.swing.plaf.*;
import javax.swing.plaf.multi.*;
import javax.accessibility.*;
public class MyAuxButtonUI extends ButtonUI {
   private Color background;
   private Color foreground;
   private ButtonUI ui = null;
   public static ComponentUI createUI( JComponent c ) {
      return new MyAuxButtonUI();
   public void installUI(JComponent c) {
      MultiButtonUI multiButtonUI = (MultiButtonUI) UIManager.getUI(c);
      this.ui = (ButtonUI) (multiButtonUI.getUIs()[0]);
      super.installUI( c );
      background = c.getBackground();
      foreground = c.getForeground();
      c.setBackground(Color.GREEN);
      c.setForeground(Color.RED);
   public void uninstallUI(JComponent c) {
      super.uninstallUI( c );
      c.setBackground(background);
      c.setForeground(foreground);
      this.ui = null;
   public void paint(Graphics g, JComponent c) {
      this.ui.paint( g, c );
   public void update(Graphics g, JComponent c) {
      this.ui.update( g, c );
   public Dimension getPreferredSize(JComponent c) {
      if ( this.ui == null ) {
         return super.getPreferredSize( c );
      return this.ui.getPreferredSize( c );
   public Dimension getMinimumSize(JComponent c) {
      if ( this.ui == null ) {
         return super.getMinimumSize( c );
      return this.ui.getMinimumSize( c );
   public Dimension getMaximumSize(JComponent c) {
      if ( this.ui == null ) {
         return super.getMaximumSize( c );
      return this.ui.getMaximumSize( c );
   public boolean contains(JComponent c, int x, int y) {
      if ( this.ui == null ) {
         return super.contains( c, x, y );
      return this.ui.contains( c, x, y );
   public int getAccessibleChildrenCount(JComponent c) {
      if ( this.ui == null ) {
         return super.getAccessibleChildrenCount( c );
      return this.ui.getAccessibleChildrenCount( c );
   public Accessible getAccessibleChild(JComponent c, int ii) {
      if ( this.ui == null ) {
         return super.getAccessibleChild( c, ii );
      return this.ui.getAccessibleChild( c, ii );
}File MyModButtonUI.java:
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import javax.swing.plaf.*;
public class MyModButtonUI extends MyAuxButtonUI
   static KeyStroke spaceKeyStroke = KeyStroke.getKeyStroke(KeyEvent.VK_SPACE, 0 );
   public static ComponentUI createUI( JComponent c ) {
      return new MyModButtonUI();
   public void installUI(JComponent c) {
      super.installUI(c);
      c.setBackground(Color.CYAN);
      if ( c.isFocusable() ) {
         c.setFocusable(true);
//      final JButton button = (JButton) c;
//      button.getInputMap().put( spaceKeyStroke, "buttonexample.pressed" );
//      button.getActionMap().put( "buttonexample.pressed", new AbstractAction() {
//         public void actionPerformed(ActionEvent e) {
//            button.doClick();
//   public void uninstallUI(JComponent c) {
//      super.uninstallUI(c);
//      JButton button = (JButton) c;
//      button.getInputMap().remove( spaceKeyStroke );
//      button.getActionMap().remove( "buttonexample.pressed" );
}

here is the code used to change the current look and feel :
try {
               UIManager.setLookAndFeel("com.sun.java.swing.plaf.motif.MotifLookAndFeel");
         catch (InstantiationException e)
              System.out.println("Error occured "+ e.toString());
         catch (ClassNotFoundException e)
              System.out.println("Error occured "+ e.toString());
         catch (UnsupportedLookAndFeelException e)
              System.out.println("Error occured "+ e.toString());
         catch (IllegalAccessException e)
              System.out.println("Error occured in .. " + e.toString());
         Dimension dim = Toolkit.getDefaultToolkit().getScreenSize();
         Fenetre fen = new Fenetre();
         fen.setSize(dim.width, dim.height);
         fen.setResizable(false);
             fen.setLocation(0, 0);
              fen.setVisible(true);

SWT/RCP loses Look and Feel

My RCP application uses SWT widgets, and it loses its look and feel after executing through Webstart. Before, it had a nice 'clipse look when executed through Eclipse. When going through Webstart, it looks like default java (maybe worse). I tried setting the nativelib to the org.eclipse.swt_3.1.0.jar and when os is Linux I jar referenced the swtLinux*x86*.jar. The latter contains several *.so files referring to the architecture and window systems.
Thanks for your suggestions/solutions,
Ben

The snippet I posted is obviously not "real" code from our product, but it does follow the same pattern-- Swing and AWT mixed and displayed through an SWT pane. Yes, it's pretty horrible. The SWT is a recent addition-- one that has complicated a lot of things, but we really can't get rid of it. The Swing and AWT are intertwined throughout the code, thousands of classes. Many of our group of developers have been forced to learn Java/Swing/Eclipse/SWT as we work, while those of us coming in with Java experience are overwhelmed by the sheer amount of code that needs to be re-written in order to follow current Java/Eclipse paradigms. We're in the process of moving everything to pure SWT, since that's the direction the higher-ups have decided upon, but we're doing things piecemeal (again, direction from higher-ups), turning sub-parts of the product into Eclipse plugins. That means that for the time being we need to make Swing, AWT, and SWT co-exist in relative harmony.
So, everything is sort of a kludge, and the choice of technologies are dictated by people who don't have to do the actual coding. What's frustrating is that things were working fine with Java 1.5. We need to upgrade to Java 1.6 due to some other plugins that are being added to the product suite. Even when we take the code previously built against Java 1.5 and run it with Java 1.6, we see the unwanted look and feel behavior.
We would really like to just find the source of the problem. Yes, the environment is kludgey, but something changed in either Java 1.6 or the Metal PLAF to cause the change in behavior.

Portal Export and Import Steps

Hi all,
I need to export all page groups from Production portal instance and import those in brand new portal instance (target Portal)*. Source and target portal instance is as follows
Production Oracle Database Version: 10.1.0.5
Target Oracle Database Version: 10.2.0.4
Production Oracle Infrastructure Version : 10.1.2.0.2
Target Oracle Infrastructure Version: 10.1.2.0.2
Production Portal Version: 10.1.2.0.2
Target Portal Version: 10.1.2.0.2
What i have done till now is as follows
1. Install Database server 10.2.0.1
2. Upgrade Database Server to 10.2.0.4
3. Install 10.2.0.1 products from Companion CD (ultra search Schemas)
4. Create Metadata Repository using Repository Creation assistance
5. Install IAS infrastructure (10.1.2.0.2)
6. Install IAS Middle Tier (10.1.2.02.)
7. Create Transport sets in production instance
Please tell me what i am supposed to do now.
I am following below link for reference but not able to follow all
http://www.scott-tiger.dk/portalHelp2/ohw/state?navSetId=_&navId=0
Regards
Anindya

For Portal Export Import (transport), the following are the foremost links on Metalink/ My Oracle Support.
Note 306785.1 Overview of the Portal Export-Import Process
Note 263995.1 - Master Note for OracleAS Portal Export / Import Issues
Note 333867.1 Portal Export and Import Utility Supportability Scenarios
Regarding your question, please do go through all of these notes.
- Overview will tell you how to prepare your instances/environments for portal transport. you will see how to ensure they are ready, and that some patches are needed.
- Master note will tell you which patches are needed, how to get them, what are the diagnostic tools which can help you check and clean your portal repositories, and what common errors you may get and how to fix them.
- Supportability Scenario tells you what actually you can transport and what you cannot. i.e., what is supported and what is not. Do read it for your case.
I have seen several Portal Admins who keep banging their heads with problems they create in their systems because they do not read this note and try to force a case which does not follow a supportable scenario.
hope that helps!
AMN

Chromosomes and genes in portal look and feel

Similar Messages

Maybe you are looking for