Categories
- All Categories
- Oracle Analytics Learning Hub
- 25 Oracle Analytics Sharing Center
- 17 Oracle Analytics Lounge
- 234 Oracle Analytics News
- 45 Oracle Analytics Videos
- 15.9K Oracle Analytics Forums
- 6.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 87 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
ORACLE logo lost after applying skin OBIEE 12c
Hi,
I applied skin by making changes in instanceconfig.xml and analytics.ear.
The skin is working fine and my company logo is coming but the oracle logo that comes on left top corner of analytics page is not there anymore.
Please help to track down the issue
Answers
-
You mean that one?
That's the logo, if you put your company logo, you replace the old one, which is that Oracle logo. If you want Oracle and your company logo, edit your company logo to add the Oracle logo inside in the same picture.
0 -
After applying skin the company logo is appearing onright top corner where it was supposed too
But Oracle logo on left top corner went missing. Not sure what caused it and how to get back
0 -
What kind of customization did you do?
Because the default way to deploy a custom logo in OBIEE 12c is the logo that goes on the left instead of "Oracle".
And what exact version of "OBIEE 12c" is yours? (including the bundle patch you are using as it could have an impact as well).
0 -
Hi,
I did the customization by making changes in analytics.ear file and Instanceconfig.xml.
I did a fresh installation of obiee12c(Obiee version - 12.2.1.4) on OCI and haven't applied any patches yet.
I used to apply skin same way in On-Prem OBIEE application same version but never got into such issue.
0 -
First of all you better quickly patch your environment, not just because 12.2.1.4 is quite old, but also for things like log4shell vulnerabilities.
And I get that you did things in analytics.ear, but you can’t really expect anyone to tell you how to fix something if you don’t say exactly how you changed things. It’s called customization for a reason: you did something that isn’t the standard and default way of doing it, therefore only you know what you did…
0 -
I have attached the document of the changes I made . Let me know where did I go wrong
0 -
The way you deploy your custom style & skin isn't supported. Never ever touch analytics.ear, there is nothing there for you. Just the fact that at every bundle patch your customization is gone is a hint that it shouldn't be done there.
The documentation cover how to customize a style & skin with a EAR file. A template EAR file is provided, you add your custom style & skin there inside, deploy it in WebLogic and job done.
And because the template EAR was based on Skyross there is one available based on Alta in a MOS document: https://support.oracle.com/epmos/faces/DocContentDisplay?id=2262460.1
So not only your method isn't officially supported, but still it doesn't say anything about how the customization is done because your process is only about copying an existing custom style & skin into the EAR.
But you really shouldn't touch analytics.ear at all and follow the documented methods instead.
0 -
Also a last note on something you posted earlier:
I used to apply skin same way in On-Prem OBIEE application same version but never got into such issue.
The fact you are now installing OBIEE 12.2.1.4 on a compute instance in OCI doesn't change anything compared to an install on a server in the basement of your company, or on your laptop. The product doesn't behave differently between cloud and not-cloud because it has no idea it is in cloud because you are only using a VM hosted in the cloud, but inside the VM it's just the same thing.
If with the same exact version of OBIEE it was working and now it doesn't, something is different somewhere else. The "location" of the install doesn't have any impact (as long as networking and firewalls etc. are all set correctly of course).
0 -
Beaten by Gianni. Modifying the core analytics.ear is
a) NOT supported
b) not the way any customization should ever have been done
c) pointless and for me points to the fact the no single bundle patch was ever applied because as Gianni correctly states your changes would have been wiped out by the bundle patch
tl;dr - stop what you're doing and do it according to the rules or your client will pay the price of this erroneous procedure as soon as the first real problem happens and the ask for support.
0
