We used to use sharepoint in our office. Though I have not used Oracle Portal, after using sharepoint, I would have to hope that anything is anything else would be better. We found it to be a composite of a plethora of microsoft products taped together. The sharepoint portal itself is very small, as it depends on the IIS server, SQL server, active directory, windows server 2003, and a bunch of other modules and add ons with to work with these.
Here are some critical problems we not able to resolve: - We found it difficult if not impossible to add users that were not users in the active directory. Our business model had more non-employees than we had active directory employees. It was quite a pain to maintain security accounts for this situation. - it forces you to use IIS web server. Our internet presence was Apache with name virtual hosts. This completely does not work with sharepoint, to make it work we had to expose IIS through the DMZ. Since our sharepoint was installed all on one box, that meant we had to put the entire box into the DMZ. - we found the sharepoint portal skins nearly impossible to customize. A lot of the functionality and flow logic in share point is implemented in .DLL handlers (ISAPI?). It made it impossible to customize it to the level we had wanted to. We started investigating getting the developer kit, but it is $$$$$, and to boot the code project environment needed visual studio team foundation server (and another plethora of products). So unless you are some microsoft partner and/or reseller, and have a full time team of microsoft product support personnel, you just can't work with it.
my forum-friendly comments are: In the end, sharepoint was only useful to us an internal only site, and not functional to the level we had wanted it to be.
Error: Keyboard not attached. Press F1 to continue.