The main skill of enterprise sales teams sometimes seems to bein making sure no-one who can ask pointed questions is in the rooms where decisions are made.
Browsing through the PDF, they make references to Webcenter Portal and Webcenter Content, but not Webcenter Sites.
Source: I implemented and supported the largest (in terms of assets and users) (allegedly, according to Oracle) installation of Fatwire as of a year ago. I work on a Portal/Content project now.
I got to Fatwire in your comment, and I laughed my ass off. Maybe I know of people who used it for a CMS, and boy does that continue to be a nightmare.
Let's say this. Someone evaluated all off the shelf CMS options for a large educational org, and somehow the org settled on the only CMS where sales engineers and businessmen have the gall to tell them "well, it is really more of a caching system than a CMS" many months into this project. My oh my did the turd get stinkier and stinker after I heard those tales.
Thanks for clarifying. It all makes sense now.
Oh yeah, and this org, after more than a million wasted, this uses Fatwire. Or whatever they call themselves now.
I've see plenty of Oracle disasters, but I think if you're going to rank horrible Oracle products, you should add Application Express to WebCenter and FatWire.
In the end, they dumped it after spending about US$ 10 million (licenses, fees, our time) and wrote a new CMS.
I've long suspected that Oracle made and sold solutions that fit this description.
Which relied on cloning IBM's SQL implementation back in the day. Odd to see them now arguing APIs should be proprietary...
> still fills a niche no one else can really compete with.
Not really true. DB2 will do everything Oracle DB does, and more (12c is only now adding the multitenant capabilities that DB2 has had for a long time). IBM don't do as good a job of marketing it, though.