Enportal/5.4/web integrations: Difference between revisions
imported>Jason.nicholls No edit summary |
imported>Jason.nicholls No edit summary |
||
| Line 9: | Line 9: | ||
<br> | <br> | ||
Application management consists of two main components: | Application management consists of two main components: | ||
#registration of applications (servers) with the portal. These are also referred to as | #registration of applications (servers) with the portal. These are also referred to as ''targets''. | ||
#creation/configuration of the application specific channels defined in the PIM. | #creation/configuration of the application specific channels defined in the PIM. | ||
<br> | <br> | ||
This chapter describes the architecture of PIMs and how the portal registers application-related components within the system. It contains the following sections: | This chapter describes the architecture of PIMs and how the portal registers application-related components within the system. It contains the following sections: | ||
:* [[enportal/5.4/Application_Management/manage_application_tools| | :* [[enportal/5.4/Application_Management/manage_application_tools|Applications & Licenses]] | ||
:* [[enportal/5.4/Application_Management/registering_new_application|Registering a New Application]] | :* [[enportal/5.4/Application_Management/registering_new_application|Registering a New Application]] | ||
:* [[enportal/5.4/Application_Management/creating_channels|Creating Application-Specific Channels]] | :* [[enportal/5.4/Application_Management/creating_channels|Creating Application-Specific Channels]] | ||
:* [[enportal/5.4/Application_Management/CRS|Content Retrieval Service (CRS) ]] | :* [[enportal/5.4/Application_Management/CRS|Content Retrieval Service (CRS) ]] | ||
:* [[enportal/5.4/Application_Management/access_control_proxied_channels|Access Control for Proxied Channels]] | :* [[enportal/5.4/Application_Management/access_control_proxied_channels|Access Control for Proxied Channels]] | ||
Revision as of 09:40, 27 June 2014
One of the key features of the portal is the ability to proxy external web applications. These applications are accessed by the portal on behalf of the end-user, often with single sign-on and added security, and the
content is modified to fit within the portal context. To achieve this behavior, the portal relies on Product Integration Modules (PIMs).
These PIMs define the rules required to proxy the application as well as a set of channels that can be used to access specific elements of the proxied application. Before the application can be used within the portal, an administrator must first configure the parameters defined in the PIM specific to the installation environment.
Application management consists of two main components:
- registration of applications (servers) with the portal. These are also referred to as targets.
- creation/configuration of the application specific channels defined in the PIM.
This chapter describes the architecture of PIMs and how the portal registers application-related components within the system. It contains the following sections:
