...
- The more you bring into the campus portal, the higher risk of outages there is (if the portal goes down, you can't access the other systems even if they're still up.)
- Single point of failure? Almost inevitable. But making it as small of a footprint as possible, and as easily resolved as possible.
- "proxy portlets" and "mini apps" - writing like a mini version of the portal for different apps, where the apps sit on the servers themselves, but connected through to the portal itself through a proxy connection, so even if the portal goes down, you can still access that interface from the server itself
- Data validation, transaction verification, etc.