Independent Software Vendors

Listed below are some types of independent software vendor (ISV) integrations.

• Application user interface. This integration uses the provider API and SRA for secure access. (SRA is not an integration type on its own.) Examples include FatWire, Interwoven, SAP, Tarantella, Documentum, Vignette, PeopleSoft, Siebel, Citrix, and YellowBrix.

• Security products. This integration uses the Access Manager Login API to enable portal access by using a custom authentication scheme. Examples include RSA Security.

• Content Management. This integration provides data access into Portal Server, enabling searches on the data. Examples include FatWire, Interwoven, and Vignette.

• Content Syndication. This integration provides managing and customizing information that appears on websites. Examples include YellowBrix and Pinnacor.

• Collaboration software. This integration enables Sun Java^TM System InstantMessaging product to move a collaboration session from one forum to a another. Examples include WebEx, BeNotified, and Lotus.

• Monitoring. This integration focuses on billing, performance measurement, and diagnostics, for which you rely on log files (or Portal Server’s Logging API) and traffic snooping. Examples include Mercury Interactive, Hyperion, and Informatica.

• 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.

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

• Application availability in secure mode (using SRA, Netlet rules)

• Ability to use single sign-on

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.