Fnt.command pimC - Revision history

imported>Teri.roberts at 19:22, 18 April 2014

2014-04-18T19:22:13Z

imported>Teri.roberts at 19:20, 18 April 2014

2014-04-18T19:20:13Z

← Older revision		Revision as of 19:20, 18 April 2014
Line 8:		Line 8:
	{{DISPLAYTITLE:{{#var:pim_title}} {{#var:pim_version}}}}		{{DISPLAYTITLE:{{#var:pim_title}} {{#var:pim_version}}}}
	[[Category:Integrations]]		[[Category:Integrations]]
	This page documents the enPortal integration for ~~{{#var:pim_vendor}}~~ {{#var:pim_title}}.		This page documents the enPortal integration for {{#var:pim_title}}.

	{{#ifeq: "5.3" \| "{{#var:portal_version}}" \|		{{#ifeq: "5.3" \| "{{#var:portal_version}}" \|
Line 93:		Line 93:
	\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. In the case where the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with a network sniffing tool between a browser and the application. Example VFXYMCHWZLHXCS, ZZCNJRPPEBSPDO		\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. In the case where the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with a network sniffing tool between a browser and the application. Example VFXYMCHWZLHXCS, ZZCNJRPPEBSPDO
	\|}		\|}


	=== Create Channels ===		=== Create Channels ===
Line 104:		Line 103:
	The following known issues are associated with this PIM:		The following known issues are associated with this PIM:

	*~~There are currently not any known issues associated with this PIM~~		*Because FNT Command manages state in flash server, multiple FNT Command channels cannot be added in the same view.

imported>Teri.roberts at 19:17, 18 April 2014

2014-04-18T19:17:32Z

@@ Line 2: / Line 2: @@
 {{#vardefine:pim_name|fnt.command_pimC}}
 {{#vardefine:pim_vendor|FNT}}
-{{#vardefine:pim_title|Command}}
+{{#vardefine:pim_title|FNT Command}}
 {{#vardefine:pim_prodvers|9.5}}
 {{#vardefine:portal_minversion|4.6.1}}
 {{#ifeq: "{{{version}}}" | "5.4" |{{#vardefine:portal_version|5.4}}|{{#vardefine:portal_version|5.3}}}}
-{{DISPLAYTITLE:{{#var:pim_vendor}} {{#var:pim_title}} {{#var:pim_version}}}}
+{{DISPLAYTITLE:{{#var:pim_title}} {{#var:pim_version}}}}
 [[Category:Integrations]]
 This page documents the enPortal integration for {{#var:pim_vendor}} {{#var:pim_title}}.
@@ Line 56: / Line 56: @@
 {{PIM_CONFIGURATION|{{#var:pim_name}}|{{#var:pim_title}}|{{#var:portal_version}}}}

imported>Teri.roberts at 19:14, 18 April 2014

2014-04-18T19:14:28Z

← Older revision		Revision as of 19:14, 18 April 2014
Line 2:		Line 2:
	{{#vardefine:pim_name\|fnt.command_pimC}}		{{#vardefine:pim_name\|fnt.command_pimC}}
	{{#vardefine:pim_vendor\|FNT}}		{{#vardefine:pim_vendor\|FNT}}
	{{#vardefine:pim_title\|~~FNT~~ Command}}		{{#vardefine:pim_title\|Command}}
	{{#vardefine:pim_prodvers\|9.5}}		{{#vardefine:pim_prodvers\|9.5}}
	{{#vardefine:portal_minversion\|4.6.1}}		{{#vardefine:portal_minversion\|4.6.1}}

imported>Teri.roberts at 19:12, 18 April 2014

2014-04-18T19:12:47Z

← Older revision		Revision as of 19:12, 18 April 2014
Line 1:		Line 1:
			{{#vardefine:pim_version\|pimC}}
			{{#vardefine:pim_name\|fnt.command_pimC}}
			{{#vardefine:pim_vendor\|FNT}}
			{{#vardefine:pim_title\|FNT Command}}
			{{#vardefine:pim_prodvers\|9.5}}
			{{#vardefine:portal_minversion\|4.6.1}}
			{{#ifeq: "{{{version}}}" \| "5.4" \|{{#vardefine:portal_version\|5.4}}\|{{#vardefine:portal_version\|5.3}}}}
			{{DISPLAYTITLE:{{#var:pim_vendor}} {{#var:pim_title}} {{#var:pim_version}}}}
			[[Category:Integrations]]
			This page documents the enPortal integration for {{#var:pim_vendor}} {{#var:pim_title}}.

			{{#ifeq: "5.3" \| "{{#var:portal_version}}" \|
			If you are using portal version 5.4 or above please click [[Special:Call/:{{#var:pim_name}},version=5.4\|here]] for the integration documentation applicable to it \|
			If you are using portal version 5.3 or earlier please click [[Special:Call/:{{#var:pim_name}},version=5.3\|here]] for the integration documentation applicable to it }}

			* <b>Vendor</b>: {{#var:pim_vendor}}
			* <b>Product</b>: {{#var:pim_title}}
			* <b>Supported Version(s)</b>: {{#var:pim_prodvers}}
			* <b>Name of enPortal Integration Package</b>: {{#var:pim_name}}
			* <b>Required enPortal Version</b>: 4.6.1 and above


			The following section documents supported platforms, installation, and configuration of the {{#var:pim_title}} Product Integration Module on enPortal versions 4.6.1 and above.

			== Support Matrix ==
			The following Operating System, Database, and Web Browser platforms are supported:


			=== Operating System ===
			Please see the list of supported Operating Systems on the [[System_Requirements\|System Requirements]] page.


			=== Database ===
			A special database is not required to implement this integration module. The AppBoard/enPortal database is used to store all configurations related to this integration module.


			=== Web Browser ===
			Please see the list of supported Web Browsers on the [[System_Requirements\|System Requirements]] page.


			== Installation ==

			{{PIM_INSTALL\|{{#var:pim_name}}\|{{#var:pim_title}}\|{{#var:portal_version}}}}

			== Integration Details ==
			The following sections provide special details for configuring the integration module after installation.


			=== Channel Types ===

			{{PIM_CHANNEL_TYPES\|FNT Command}}
			<!--- add additional channel types below-->


			=== Configuration ===

			{{PIM_CONFIGURATION\|{{#var:pim_name}}\|{{#var:pim_title}}\|{{#var:portal_version}}}}


			=== Create Channels ===

			{{PIM_CREATE_CHANNELS\|{{#var:pim_name}}\|{{#var:pim_title}}\|{{#var:portal_version}}}}


			=== Known Issues ===

			The following known issues are associated with this PIM:

			*There are currently not any known issues associated with this PIM


			=== License Usage ===

			{{PIM_LICENSE_USAGE\|{{#var:pim_name}}\|{{#var:pim_title}}}}


			=== Version Support ===

			{{PIM_VERSION_SUPPORT\|{{#var:pim_name}}\|{{#var:pim_title}}\|{{#var:portal_minversion}}\|{{#var:pim_prodvers}}}}

			== Upgrades ==

			=== Upgrading from an older version ===

			{{PIM_UPGRADE_OLD\|{{#var:pim_name}}\|{{#var:pim_title}}}}


			=== Upgrading to a newer version ===

			{{PIM_UPGRADE_NEW\|{{#var:pim_name}}\|{{#var:pim_title}}\|{{#var:portal_version}}}}


			== Uninstall ==

			{{PIM_UPGRADE_UNINSTALL\|{{#var:pim_name}}\|{{#var:pim_title}}\|{{#var:portal_version}}}}







	This page documents the enPortal integration for FNT Command.		This page documents the enPortal integration for FNT Command.

imported>Teri.roberts at 21:30, 17 October 2013

2013-10-17T21:30:05Z

← Older revision		Revision as of 21:30, 17 October 2013
Line 75:		Line 75:
	# Under the <b>Sample</b> target, click on the <b>Home</b> channel. A login prompt should be displayed.		# Under the <b>Sample</b> target, click on the <b>Home</b> channel. A login prompt should be displayed.
	# Log in using the same credentials you would use for accessing the FNT Command application in a browser. Confirm that the FNT Command Home page is displayed.		# Log in using the same credentials you would use for accessing the FNT Command application in a browser. Confirm that the FNT Command Home page is displayed.


	==== SSO Configuration ====		==== SSO Configuration ====
Line 111:		Line 112:
	\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. In the case where the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with a network sniffing tool between a browser and the application. Example VFXYMCHWZLHXCS, ZZCNJRPPEBSPDO		\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. In the case where the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with a network sniffing tool between a browser and the application. Example VFXYMCHWZLHXCS, ZZCNJRPPEBSPDO
	\|}		\|}


	=== Create Channels ===		=== Create Channels ===
Line 134:		Line 136:

	*Because FNT Command manages state in flash server, multiple FNT Command channels cannot be added in the same view.		*Because FNT Command manages state in flash server, multiple FNT Command channels cannot be added in the same view.



	=== License Usage ===		=== License Usage ===
Line 182:		Line 186:
	### Re-create all FNT Command channels to reference the new PIM		### Re-create all FNT Command channels to reference the new PIM
	### [Optional] Perform the steps outlined in the Uninstall section below to remove the old PIM from the system		### [Optional] Perform the steps outlined in the Uninstall section below to remove the old PIM from the system


	== Uninstall ==		== Uninstall ==

imported>Teri.roberts: /* SSO Configuration */

2013-10-17T21:28:00Z

SSO Configuration

← Older revision		Revision as of 21:28, 17 October 2013
Line 78:		Line 78:
	==== SSO Configuration ====		==== SSO Configuration ====

	After completing the above configuration steps, regardless whether the SSO is assigned to a Role, Domain, or User, please ~~keeping~~ the following SSO attributes in mind:		After completing the above configuration steps, regardless whether the SSO is assigned to a Role, Domain, or User, please keep the following SSO attributes in mind:

	{\| class="wikitable" border="1" style="background-color:#eeeeee;"		{\| class="wikitable" border="1" style="background-color:#eeeeee;"
Line 97:		Line 97:
	\| language		\| language
	\|		\|
	\| the language ~~to use~~ to display the application in. This should be left blank to use the default language set for the user in the application. To override, enter a valid application supported language, example: en_US, de_DE		\| the language used to display the application. This should be left blank to use the default language set for the user in the application. To override, enter a valid application supported language, example: en_US, de_DE
	\|-		\|-
	\| mandant_id		\| mandant_id
	\|		\|
	\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. ~~And in~~ the case ~~that~~ the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example: 1001, 1002		\| mandant_id, group_accesstype, and group_access should be set together to determine what the user's view should be. Leave these values blank to have the application prompt the user for one. In the case where the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with a network sniffing tool between a browser and the application. Example: 1001, 1002
	\|-		\|-
	\| group_accesstype		\| group_accesstype
	\| G		\| G
	\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. ~~And in~~ the case ~~that~~ the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example G, U		\| mandant_id, group_accesstype, and group_access should be set together to determine what the user's view should be. Leave these values blank to have the application prompt the user for one. In the case where the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with a network sniffing tool between a browser and the application. Example G, U
	\|-		\|-
	\| group_access		\| group_access
	\|		\|
	\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. ~~And in~~ the case ~~that~~ the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example VFXYMCHWZLHXCS, ZZCNJRPPEBSPDO		\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. In the case where the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with a network sniffing tool between a browser and the application. Example VFXYMCHWZLHXCS, ZZCNJRPPEBSPDO
	\|}		\|}

imported>Jonathan.Ho: /* SSO Configuration */

2013-10-17T21:16:22Z

SSO Configuration

← Older revision		Revision as of 21:16, 17 October 2013
Line 78:		Line 78:
	==== SSO Configuration ====		==== SSO Configuration ====

	After completing the above configuration steps, regardless whether the SSO assigned to a Role, Domain, or User, please keeping the following SSO attributes in mind:		After completing the above configuration steps, regardless whether the SSO is assigned to a Role, Domain, or User, please keeping the following SSO attributes in mind:

	{\| class="wikitable" border="1" style="background-color:#eeeeee;"		{\| class="wikitable" border="1" style="background-color:#eeeeee;"

imported>Jonathan.Ho: /* SSO Configuration */

2013-10-17T20:40:53Z

SSO Configuration

← Older revision		Revision as of 20:40, 17 October 2013
Line 104:		Line 104:
	\|-		\|-
	\| group_accesstype		\| group_accesstype
	\|		\| G
	\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. And in the case that the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example G, U		\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. And in the case that the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example G, U
	\|-		\|-

imported>Jonathan.Ho: /* SSO Configuration */

2013-10-17T14:21:17Z

SSO Configuration

← Older revision		Revision as of 14:21, 17 October 2013
Line 101:		Line 101:
	\| mandant_id		\| mandant_id
	\|		\|
	\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application ~~prompting~~ user for one. And in the case that the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example: 1001, 1002		\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. And in the case that the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example: 1001, 1002
	\|-		\|-
	\| group_accesstype		\| group_accesstype
	\|		\|
	\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application ~~prompting~~ user for one. And in the case that the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example G, U		\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. And in the case that the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example G, U
	\|-		\|-
	\| group_access		\| group_access
	\|		\|
	\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application ~~prompting~~ user for one. And in the case that the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example VFXYMCHWZLHXCS, ZZCNJRPPEBSPDO		\| mandant_id, group_accesstype, and group_access should be set together to determine what user's view should be. Leave these values blank to have the application prompt the user for one. And in the case that the user has only access to one view, there will be no prompt. Setting these values will load the entered view without any prompt. The possible values can be observed with network sniffing tool between a browser and the application. Example VFXYMCHWZLHXCS, ZZCNJRPPEBSPDO
	\|}		\|}