Hi 

You can swap the logo bitmap, but we just use a different colour palette / scheme to make the instances distinct.

Sometimes users do not immediately recognize the instances with visual theme.

that is why we changed the logo with instance name.

We found the logo to small and users missed that signal.

Be less subtle with your colours, our UAT is bright red and so in your face failure to spot the difference results in your agile account being taken away , as IMHO  the user probably doesn’t have the mental capacity to be trusted with access.

But I am not the most PC of admins…….;-)

I like Adrian already.

Yes Anand, the recommendation is to NOT have users on any DEV instance and only access to PROD and any system you may use for user acceptance testing activities.

When we post the links we also mention the color of the GUI so users can keep them straight.

Another tact is to only post the PROD link and send the UAT link out only when necessary.  I keep a internal page for the PLM Team with all the links so at the very least we have a library of links to draw upon.

I prefer to replace the Oracle Logo with a Custom Company Logo in Production ONLY and then create a custom Color Palette  to reflect corporate company colors.  (Wasn’t too difficult to get my hands on a corporate style guide for the correct colors to use.  Google is your friend when trying to find the right color code!)

Our main company colors are Green and Yellow, so when they log in and see those colors along with the company logo – they know they’re in the right place.  I’ll use something completely different, like “Torch Red” for Test so if they log into Test by mistake and see the Oracle Logo and that everything is red – its a very obvious difference.

Production – Company Logo & Company Colors (Green/Yellow)
Test – Oracle Logo & Red Everywhere

If distinct visual themes (and a little training) are not enough for users to tell the difference from one environment to the next – I think you may have bigger fish to fry than simply getting more text into the tool bar! 🙂

Hi,
Coincidentally this week I was trying to do exactly this, but I am having hard time following the Administrator Guide instructions to replace the Oracle logo with our company logo. 

Basically I can’t find the Oracle home directory and the web.xml file they refer to (see below).

I searched the entire server and found four web.xml files. I edited them and also added the new logo file to the images folders. Of course I restarted the server.

Can someone give me guidance please?

Thanks,
Victor Turco.

To replace the default company logo with a custom logo:

1. Log in to server side.
2. Find web.xml in the Oracle home directory.
3. The bullet-items below give some samples of changing specific parameters in the web.xml file:
-These lines of code allow you to enter the filename of your custom logo file:
<context-param>
<param-name>cobranding.image</param-name>
<param-value>logo.gif</param-value>
</context-param>
Change the filename (including extension) where ―logo.gif‖ appears.

4. Restart the application server.
5. Log into Web Client to verify or evaluate your change(s).

Hi Victor,

check this out.

http://www.graywill.com/replacing-the-oracle-logo-in-agile-plm/