4 out of 5.0, Reviewed Oct 17, 2016
Worked well: Improved customer experience, stability and scale Could be improved: didn't get as much reuse as expected, also, front end technology changed and it was an overengineered solution
Consider content management based approach using Web Center Sites vs. Web Center Portal (WebLogic Portal)
Scale to large implementations and stability
They did a great job supporting through a POC, attending customer summits, etc. No gripes here
Open source Separate architecture for portal versus applications surfaced by portal Planned obsolesence
3 out of 5.0, Reviewed Jun 16, 2016
I came from a C# background and I found that WebCenter is a very powerful toolset / framework that does a lot of the work for you, and it has a very powerful IDE (JDeveloper) however it also has a very difficult learning curve and I would suggest anyone using it to get training. You pretty much have to do things the WebCenter way, too much customization or trying to think outside of the box usually ends with bad results. You really need to use the product exactly how it's designed to be used or you may encounter business. With an on-premises deployment the licensing does not make it very scalable, charging by the CPU and users.
Take care to balance your need to make deadlines with overall cost and scalability. Currently, its cost is prohibitive for us to have a redundant data center, so our solution has to be, if the main data center is down, we present "sorry we are down” pages.
Incredibly powerful, if you know exactly what you are doing you can very rapidly show any data from your organization to the correct users and have some options in how you are going to display that data, and what interactions with that data will be possible.
Difficulty in the learning curve, and from a programmers stand point JDeveloper is horrible at undoing things, which lead me to trying to create a project , learning it, and then having to delete the project and start from scratch because if you delete controls or data binding JDeveloper leaves behind some of the files, which can cause errors or bugs. Not a good product for beginners on your staff.
more collaboration with our in-house staff, and better documentation of what they created. We worked (offloaded) a lot of the initial development to Oracle's partner.
Top floor was very happy with the end results, and our total time to market with such a big portal and a lot of the built-in functionality. Cost and scalability are not the best, and our own in house expertise is still somewhat lacking, years after our roll out we still work closely with a 3rd party "Oracle partner" to get some of our improvements and troubleshooting help done. Though we have found a few really good ADF / WebCenter developers.
The product has more capabilities than you will ever need. It can do basically anything any other portal software can do and then some. Configuration of those abilities may not always be easy.
Oracle is a very large corporation and they use a ticket system for support and at times, they can be a bit slow to respond or overly eager to close your ticket before you have a resolution. Also, your bug may not get fixed on your version of WebCenter.
4 out of 5.0, Reviewed Apr 25, 2016
We struggled a bit at first as Web Center Portal was a heavy application. We have since migrated to spaces and found ways to incorporate angularization to improve performance.
Make sure you have knowlegable team members or a very strong implementation partner.
The product is quite robust.
There was not quite as much "out of the box" functionality as I had hoped.
I wish there was a more user friendly content management front end.
We would have done a bit more homework on some of the functionality to ensure we were effectively utilizing the tools. We had to do quite a bit of rework after we learned more about the possibilities.