Working with the Application Integrator

The Application Integrator toolset provides an infrastructure for integrating remote Web applications into the portal. It allows you to create portal components that serve as templates for iViews representing the remote applications.

The Application Integrator provides portal components, focused on the following SAP applications, among others:

• SAP Transactions (SAP backend transactions)

• Business Server Pages (BSP)

• BEx Web Applications (SAP BW 3.x format and SAP NetWeaver 7.0 format)

• Web Dynpro for Java and ABAP

• SAP Business Objects reports

• Workplace 2.x MiniApps

• HTTP-based Web applications (generic portal component)

If you want to integrate one of these application types, refer to the administration documentation. If the application type you need is not in the list, you can implement your own integrator component.

The Application Integrator includes the following portal applications:

• com.sap.portal.appintegrator

• com.sap.portal.appintegrator.sap

Implementation Considerations

An Application Integrator iView creates HTML content that loads a remote application. This is done in three steps:

The loading procedure requires that content included into the portal with the Application Integrator can be accessed from a client computer. The Application Integrator infrastructure creates HTML commands to load the remote application. After the application has been loaded, the iView stops interaction with the portal.

To create an iView from an existing Application Integrator portal component, you can:

• Copy the com.sap.portal.appintegrator.sap.Generic component from the Portal Applications GPAL repository.
• Create an iView from template, for example, the SAP BSP iView template.
• Create an iView from a remote source, using the SAP Portal Component iView.

Your iView is displayed in the Portal Catalog. The properties settings of the iView depend on the application from which the iView is created.