The iViewServer provides the following functions:

• Provide runtime environment for both .NET and Java iViews
• Maintain cache of iViews' content
• Administrate iViews and provide their content from various sources
• Handle user’s iView personalization
• Enable development of new content
• Allow import of new content such as roles and iViews from the iView Studio

In particular, the iViewServer produces the HTML content of iViews and pages. This HTML content is then requested by the browser when it displays the pages.

The following diagram illustrates the components of the iViewServer.

The different types of content that the iViewServer administers can be summarized as follows:

• Java-based content:

• Java iViews are executed in the Java iView Runtime environment on the iViewServer
• External services: External services are content that runs on a server other than the iViewServer, for example an SAP transaction that runs on an Internet Transaction Server (ITS).

• .NET-based content: .NET-based iViews are executed on the iViewServer

The Java iView Runtime is part of the iViewServer. It runs as a servlet on a Java application server. It executes Java iViews and renders the returned content. It provides Java iViews with access to infrastructure services such as user management. It also offers personalization of Java iViews and stores personalization data and any other persistent data in the persistence layer.

In addition the Java iView Runtime provides a development platform that allows developers to build their own iViews written in Java or JSP.