Fnt.command pimC

{{#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}}}} This page documents the enPortal integration for {{#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 }}

  • Vendor: {{#var:pim_vendor}}
  • Product: {{#var:pim_title}}
  • Supported Version(s): {{#var:pim_prodvers}}
  • Name of enPortal Integration Package: {{#var:pim_name}}
  • Required enPortal Version: 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 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 page.


Installation

Perform the following steps to install the {{#var:pim_title}} PIM:

  1. Install AppBoard/enPortal as detailed in the Installation documentation
  2. Download the file {{#var:pim_name}}.jar
  3. Start enPortal and login as a portal administrator

{{#ifeq: "5.3" | "{{#var:portal_version}}" |

  1. Under the Advanced tab, select PIMImport

|

  1. Under the Web Integrations tab, select PIM Import

}}

  1. Click the Browse... button
  2. Locate the file {{#var:pim_name}}.jar in the Open dialog
  3. Click the Start button to extract the files from the PIM .jar archive

{{#ifeq: "5.3" | "{{#var:portal_version}}" |

  1. Under the Advanced tab, select XMLImport
  2. Click the Start button to load the PIM into the system
  3. Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_{{#var:pim_name}}.txt"
  4. Under the Advanced tab, select Explore System
  5. Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel
  6. Right-click on the “Manage Proxy” channel and select Open to launch the channel
  7. In the Manage Proxy tool, click “Reset All”

|

  1. Confirm that the following messages are displayed:
    1. "Upload completed."
    2. "Loaded the following file(s): load_{{#var:pim_name}}.txt"
    3. "CRS cache cleared."

}}

Integration Details

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


Channel Types

  • Home - Channel that displays the default Home page for the logged in user, including full navigation controls (no custom configuration required)
  • Proxy - Channel that is used by the system to display FNT Command channels (no custom configuration required)


Configuration

After installing the {{#var:pim_title}} PIM, perform the following steps to configure access to the host {{#var:pim_title}} server:

{{#ifeq: "5.3" | "{{#var:portal_version}}" |

  1. Click on the Applications tab

|

  1. Under the Web Integrations tab, select Applications & Licenses

}}

  1. Right-click on the name sample in the row for {{#var:pim_title}} ({{#var:pim_name}}) and select Modify
  2. Fill in the items in the Modify Application Wizard dialog:
    1. Select the protocol used to access your {{#var:pim_title}} server (http or https)
    2. Change the host name from "changeme" to the hostname or ip address that will resolve to your {{#var:pim_title}} server
    3. Change the port to the port number of your {{#var:pim_title}} server
    4. Click "Save" to keep your changes

{{#ifeq: "5.3" | "{{#var:portal_version}}" |

  1. Click on the Integrations tab

|

  1. Under the Web Integrations tab, select Explorer

}}

  1. In the Explorer, under Packages, expand the cuculus.zonoscontrolcenter_pimA tree and click on the sample target. Confirm that the information you entered is displayed for your {{#var:pim_title}} server
  2. Under the sample target, click on the Home channel. A login prompt should be displayed.
  3. Log in using the same credentials you would use for accessing the {{#var:pim_title}} application in a browser. Confirm that the {{#var:pim_title}} Home page is displayed.


SSO Configuration

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:

SSO attributes
Name Default Value Description
username user name used to log on to the application
password password used to log on to the application
language 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, 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 G 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 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

After installing the {{#var:pim_title}} PIM and configuring access to the host {{#var:pim_title}} server, perform the following steps to create channels to display {{#var:pim_title}} content:

{{#ifeq: "5.3" | "{{#var:portal_version}}" |

  1. Click on the Applications tab
  2. Right-click on the name "sample" in the row for {{#var:pim_name}} and select a channel type
  3. In the "Channel Name" box, enter the name you want to give to the new channel
  4. For "Channel Type", select "3rd Party Pims"
  5. Select Pim, Class, and Target for your channel
  6. Click Next
  7. Click Finish
  8. Click on the Integrations tab

|

  1. Under the Web Integrations tab, select Applications & Licenses
  2. Right-click on the name sample in the row for {{#var:pim_name}} and select a channel type
  3. In the "Channel Name" box, enter the name you want to give to the new channel
  4. Click Next
  5. Click Finish
  6. Under the Web Integrations tab, select Explorer

}}

  1. In the Explorer, under Packages, expand the {{#var:pim_name}} tree and click on the sample target. Confirm that the new channel is listed along with the other sample channels

Repeat the above steps to create additional channels. Select a different Channel Type in step 2 to create a different type of channel.


Known Issues

The following known issues are associated with this PIM:

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


License Usage

In order for the AppBoard/enPortal administrator to configure the {{#var:pim_name}} PIM, the AppBoard/enPortal license.properties file must include licensing for at least one {{#var:pim_name}} server. The administrator can create one additional host ("target") in AppBoard/enPortal for each server license included in the license file.

Each AppBoard/enPortal user maintains one user session with the {{#var:pim_title}} server. The {{#var:pim_title}} application must be licensed to support the number of users that will be accessing the application through AppBoard/enPortal.


Version Support

The following matrix details the supported {{#var:pim_title}} and compatible AppBoard/enPortal versions:

Version Support
Package Name enPortal Version {{#var:pim_title}} Supported Versions
{{#var:pim_name}} {{#var:portal_minversion}}+ {{#var:pim_prodvers}}
Template-tip.png
To see the current enPortal version, run the portal version command from the [AppBoard_Home]/server/bin directory.

Upgrades

Upgrading from an older version

Older versions of {{#var:pim_title}} are not supported by this PIM, so this upgrade path is not supported. It is recommended that you validate the PIM in your {{#var:pim_title}} environment to confirm that it supports the required functionalities.


Upgrading to a newer version

Perform the following steps when the {{#var:pim_title}} server is upgraded to a newer version of {{#var:pim_title}}:

  1. Check the AppBoard/enPortal PIM online documentation to see if the new {{#var:pim_title}} version is supported by the existing {{#var:pim_name}} PIM.
  2. Test if the new {{#var:pim_title}} version is supported by the existing PIM that you have installed, perform the following steps:

{{#ifeq: "5.3" | "{{#var:portal_version}}" |

    1. Click on the Applications tab

|

    1. Under the Web Integrations tab, select Applications & Licenses

}}

    1. Right-click on the row for the old {{#var:pim_title}} server and select "Modify"
    2. Update the protocol, host, and port to reference the server where the new version of {{#var:pim_title}} is running
  2. If the new {{#var:pim_title}} version is not supported by the existing PIM that you have installed, perform the following steps to upgrade the PIM:
    1. Download the new PIM version from the PIM download site
    2. Follow the steps in the Installation section above to install and configure the new PIM version
    3. Re-create all {{#var:pim_title}} channels to reference the new PIM
    4. [Optional] Perform the steps outlined in the Uninstall section below to remove the old PIM from the system


Uninstall

Perform the following steps to uninstall the {{#var:pim_name}} PIM:


Template-warning.png
Uninstalling the {{#var:pim_name}} PIM will break all of the channels in your AppBoard/enPortal system that reference this integration.

{{#ifeq: "5.3" | "{{#var:portal_version}}" |

  1. Click on the Integrations tab

|

  1. Under the Web Integrations tab, select Explorer

}}

  1. In the Explorer, under Packages, locate the {{#var:pim_name}} integration
  2. Right click on the integration name, and select "Delete"
  3. Click "Ok" to confirm that you want to delete the integration package
Retrieved from "http://ab.edge-technologies.com/docs/index.php?title=Fnt.command_pimC&oldid=5972"