RE: WHY WHY does Oracle OEM 12c (12.1.0.5) use the following...
- From: Peter Sharman <pete.sharman@xxxxxxxxxx>
- To: tim@xxxxxxxxxxxxxxx, Chris Taylor <christopherdtaylor1994@xxxxxxxxx>
- Date: Fri, 13 Nov 2015 09:05:44 -0800 (PST)
6) Oracle teams very rarely seem to look outside of themselves for best
practices provided by other teams.
Good Lord, Tim, I thought you should have known by now We Do Not Use <evil term
alert>Best Practices</evil term alert>! :)
Seriously, the reason behind all of this is that EM is a product that sits on a
framework. That framework includes whatever version of WLS we're up to now
(10.3.6? Can't remember exactly). In any case, we have to use the version of
Java that the said framework relies on. Going back to Chris's original point,
a new version of product x (in this case Java) is not that major a thing to
test, BUT it has to be tested in light of the stack uptake for the entire
framework and THAT is not a quick thing to do. Given that there are somewhere
over 1000 pages of the product to test, it just takes time. We're a'workin' on
it though!
Pete
Pete Sharman
Database Architect, DBaaS / DBLM
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA
Phone: +61262924095 | | Mobile: +61414443449
Email: pete.sharman@xxxxxxxxxx Twitter: @SharmanPete LinkedIn:
au.linkedin.com/in/petesharman
Website: petewhodidnottweet.com
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
"Oh no, it's not, it's much harder than that!"
Bruce Pihlamae, long term Oracle DBA
-----Original Message-----
From: Tim Hall [
mailto:tim@xxxxxxxxxxxxxxx]
Sent: Friday, November 13, 2015 10:34 AM
To: Chris Taylor <christopherdtaylor1994@xxxxxxxxx>
Cc: Oracle-L Freelists <oracle-l@xxxxxxxxxxxxx>
Subject: Re: WHY WHY does Oracle OEM 12c (12.1.0.5) use the following...
Well:
1) Many (but not all) of the major security alerts around Java6 have actually
been on the client side, when running the Java plugins in browser, so server
side Java is not so much of a problem (insert caveats here).
2) Cloud Control is not for public access, so...
3) WebLogic 11g (10.3.6) is still by far the most popular version at this time.
Oracle Fusion Apps is currently built on WebLogic 11g
10.3.6 using ADF 11.1.1.9. To my knowledge, it has not been migrated to
WebLogic 12c yet. With that in mind, it's hardly surprising other projects have
not moved forward yet.
4) The teams in Oracle each have their own deadlines and time-to-market
pressures mean they rarely use the latest products.
Testing your code base against a later release of the software takes time that
could be spent adding new features. This happens to all of us. :)
5) Cloud Control is a shrink-wrapped application. You shouldn't be using it for
your own stuff, so why do you care what it's built with, provided it passes
your external penetration testing? I treat it like a black box.
6) Oracle teams very rarely seem to look outside of themselves for best
practices provided by other teams. As proof I offer you the database
installations associated with eBusiness Suite, which don't seem to follow
simple best practices that I would consider DBA101.
Even if you are a good DBA, you have to check your real DBA hat in and pick up
a Oracle Apps DBA hat before doing any work on them, because if you do things
"correctly", the apps die. :)
This is not a defence of it, it's just an observation. I made a similar comment
about Java 6 when I first installed 12.1.0.5.
https://oracle-base.com/blog/2015/06/17/oracle-enterprise-manager-cloud-control-12c-release-5-12-1-0-5-my-first-two-installations/
I too get a little frustrated by this, but it is what I've come to expect of
nearly every large software vendor. Check out what's under the hood of
Microsoft BizTalk Server and you will see much the same issues. It's cobbled
together with loads of old bits of software, but sold as a current "enterprise"
solution... :)
Cheers
Tim...
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
