Enportal/5.4/web integrations: Difference between revisions

imported>Jason.nicholls
No edit summary
imported>Jason.nicholls
No edit summary
Line 11: Line 11:


# '''[[enportal/5.4/web_integrations/applications_and_licenses|Applications & Licenses]]''': Manage the list of registered application instances, also referred to as ''Targets''. Also view license usage.
# '''[[enportal/5.4/web_integrations/applications_and_licenses|Applications & Licenses]]''': Manage the list of registered application instances, also referred to as ''Targets''. Also view license usage.
# '''Explorer''': Used to actually manage and/or create new PIMs.
# '''[[enportal/5.4/web_integrations/explorer|Explorer]]''': Used to actually manage and/or create new PIMs.
# '''[[enportal/5.4/web_integrations/pim_import|PIM Import]]''': Used to load or upgrade PIMs onto the system.
# '''[[enportal/5.4/web_integrations/pim_import|PIM Import]]''': Used to load or upgrade PIMs onto the system.
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.
<br>
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|Applications & Licenses]]
:* [[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/CRS|Content Retrieval Service (CRS) ]]
:* [[enportal/5.4/Application_Management/access_control_proxied_channels|Access Control for Proxied Channels]]

Revision as of 12:01, 27 June 2014


One of the key features of enPortal is the ability to proxy external web applications. These applications are accessed by enPortal 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.

For enPortal to proxy external external web applications it must know what type of application (generic or PIM) and other instance specific information such as what host and port that web application is running on.

The Web Integrations administration menu provides the following functions:

  1. Applications & Licenses: Manage the list of registered application instances, also referred to as Targets. Also view license usage.
  2. Explorer: Used to actually manage and/or create new PIMs.
  3. PIM Import: Used to load or upgrade PIMs onto the system.
Retrieved from "http://ab.edge-technologies.com/docs/index.php?title=Enportal/5.4/web_integrations&oldid=5470"