Show TOC

Object documentationSystem Locate this document in the navigation structure

 

A description of a back-end application used by iViews to connect to the application and retrieve its data during runtime.

Caution Caution

Any iView based on a system defined in your system landscape requires that you assign end user permission to that system for the relevant user, group, or role. Without end user permission to the system, the iView does not permit data retrieval from the respective back-end application at runtime. For more information, see Permission Levels.

End of the caution.

Structure

A system is based on either a portalapp.xml file contained in a PAR file, or on a template generated from the portalapp.xml file. It is represented as a set of attributes necessary for establishing a connection to an external application. It is created by setting values to its global properties.

Each type of system has its own template with its own set of properties. There is no set number of properties; nor are all properties common to all systems.

The exceptions are:

All other properties are subject to:

  • How the template is implemented

  • The operations of the Portal Runtime (PRT) and the Portal Content Directory (PCD).

    • The PRT adds properties when importing the system template from the application repository.

    • The PCD adds properties when creating the context.

Integration

  • Once created and properly edited in the System Landscape Editor, a system becomes part of the portal system landscape. For more information, see Creating Systems and Editing Systems.

  • Access to a system is through a system alias, a name by which portal components can reference a specific system. For more information, see System Aliases.

  • In the portal, you can store all systems in one folder or place them anywhere within the Portal Catalog.

  • System aliases are not displayed in the Portal Catalog; you can view them in the Alias Editor and in the System Landscape Overview iView.