Content and Design Implementation
•Portal capability augmentation. This integration enables products to add functionality to Portal Server. Examples include Altio, Bowstreet, rule engines to add group capability, and dynamic standard Portal Desktop and provider contents (HNC).
•Integratable portal stack. This integration includes products that replace elements of Portal Server. Examples include Access Manager and LDAP.
NOTE Portal Server cannot currently integrate another LDAP solution. Access Manager and Portal Server rely on features not found in other LDAP implementations.
The “depth” to which user interface integration occurs with Portal Server indicates how complete the integration is. Depth is a term used to describe the complementary nature of the integration, and points to such items as:
•Application availability through Portal Server itself
•Application availability in secure mode (using SRA, Netlet rules)
•Ability to use single
In general, the degree to which an application integrates in Portal Server can be viewed as follows:
•Shallow integration. This integration essentially uses the Portal Server as a launch point. The user logs in to the portal and clicks a link that starts a web application.
•Deep integration. The user accesses the user interface provided by the channels in Portal Server directly. That is, the integrated software works within the portal. No additional windows or applets appear.
Integrating Microsoft Exchange
Using the JavaMail™ API is one of the primary options for integrating Microsoft Exchange messaging server with Portal Server. The JavaMail API provides a platform independent and protocol independent framework to build Java
