Enportal/5.4/web integrations - Revision history

imported>Jason.nicholls at 13:04, 27 June 2014

2014-06-27T13:04:05Z

← Older revision		Revision as of 13:04, 27 June 2014
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.
	# '''[[enportal/5.4/web_integrations/explorer\|Explorer]]''': Used to manage and/or create new PIMs. Also ~~browser~~ sample PIM content.		# '''[[enportal/5.4/web_integrations/explorer\|Explorer]]''': Used to manage and/or create new PIMs. Also browse sample PIM content.
	# '''[[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.

imported>Jason.nicholls at 13:03, 27 June 2014

2014-06-27T13:03:52Z

← Older revision		Revision as of 13:03, 27 June 2014
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.
	# '''[[enportal/5.4/web_integrations/explorer\|Explorer]]''': Used to ~~actually~~ manage and/or create new PIMs.		# '''[[enportal/5.4/web_integrations/explorer\|Explorer]]''': Used to manage and/or create new PIMs. Also browser sample PIM content.
	# '''[[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.

imported>Jason.nicholls at 12:01, 27 June 2014

2014-06-27T12:01:43Z

@@ 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.
-# '''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.

imported>Jason.nicholls at 11:43, 27 June 2014

2014-06-27T11:43:26Z

← Older revision		Revision as of 11:43, 27 June 2014
Line 12:		Line 12:
	# '''[[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.		# '''Explorer''': Used to actually manage and/or create new PIMs.
	# '''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:		Application management consists of two main components:

imported>Jason.nicholls at 11:41, 27 June 2014

2014-06-27T11:41:29Z

← Older revision		Revision as of 11:41, 27 June 2014
Line 10:		Line 10:
	The ''Web Integrations'' administration menu provides the following functions:		The ''Web Integrations'' administration menu provides the following functions:

	# '''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.		# '''Explorer''': Used to actually manage and/or create new PIMs.
	# '''PIM Import''': Used to load or upgrade PIMs onto the system.		# '''PIM Import''': Used to load or upgrade PIMs onto the system.

imported>Jason.nicholls: moved enportal/5.4/Application Management to enportal/5.4/web integrations

2014-06-27T11:34:00Z

moved enportal/5.4/Application Management to enportal/5.4/web integrations

← Older revision	Revision as of 11:34, 27 June 2014
(No difference)

imported>Jason.nicholls at 11:31, 27 June 2014

2014-06-27T11:31:51Z

← Older revision		Revision as of 11:31, 27 June 2014
Line 1:		Line 1:
	[[Category:enPortal 5.4]]		[[Category:enPortal 5.4]]
	{{DISPLAYTITLE:~~Application Management~~}}		{{DISPLAYTITLE:Web Integrations}}

			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
	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).		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.		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.
	~~<br>~~
	~~<br>~~		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:

			# '''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.
			# '''PIM Import''': Used to load or upgrade PIMs onto the system.

	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 ''targets''.		#registration of applications (servers) with the portal. These are also referred to as ''targets''.

imported>Jason.nicholls at 09:40, 27 June 2014

2014-06-27T09:40:41Z

← Older revision		Revision as of 09:40, 27 June 2014
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 ~~_targets_ sometimes~~.		#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\|~~Managing 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]]

imported>Jason.nicholls at 09:39, 27 June 2014

2014-06-27T09:39:43Z

← Older revision		Revision as of 09:39, 27 June 2014
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		#registration of applications (servers) with the portal. These are also referred to as _targets_ sometimes.
	#creation/configuration of the application specific channels defined in the PIM.		#creation/configuration of the application specific channels defined in the PIM.
	<br>		<br>

imported>Jason.nicholls: 1 revision

2013-12-19T15:17:45Z

1 revision

← Older revision	Revision as of 15:17, 19 December 2013
(No difference)