imported>Jason.nicholls: moved Sevone nms pimC to integrations/sevone/sevone.nms pimC

2014-07-25T07:14:44Z

moved Sevone nms pimC to integrations/sevone/sevone.nms pimC

← Older revision	Revision as of 07:14, 25 July 2014
(No difference)

imported>Teri.roberts at 17:05, 24 June 2014

2014-06-24T17:05:21Z

← Older revision		Revision as of 17:05, 24 June 2014
Line 1:		Line 1:
	{{DISPLAYTITLE:SevOne ~~Network Management System (NMS)~~ pimC}}		{{DISPLAYTITLE:SevOne pimC}}
	[[Category:Integrations]]		[[Category:Integrations]]
	This page documents the enPortal integration for SevOne ~~Network Management System (NMS)~~ application.		This page documents the enPortal integration for SevOne application.

	* <b>Vendor</b>: SevOne		* <b>Vendor</b>: SevOne
	* <b>Product</b>: ~~Network Management System (NMS)~~		* <b>Product</b>: SevOne
	* <b>Supported Version(s)</b>: 5.1.4.0		* <b>Supported Version(s)</b>: 5.1.4.0
	* <b>Name of enPortal Integration Package</b>: sevone.nms_pimC		* <b>Name of enPortal Integration Package</b>: sevone.nms_pimC

imported>Teri.roberts at 19:54, 6 February 2014

2014-02-06T19:54:32Z

← Older revision		Revision as of 19:54, 6 February 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:SevOne Network Management System (NMS) pimC}}
			[[Category:Integrations]]
	This page documents the enPortal integration for SevOne Network Management System (NMS) application.		This page documents the enPortal integration for SevOne Network Management System (NMS) application.

imported>Teri.roberts: /* Installation */

2013-07-29T23:12:43Z

Installation

← Older revision		Revision as of 23:12, 29 July 2013
Line 42:		Line 42:
	# Click the <b>Start</b> button to load the PIM into the system		# Click the <b>Start</b> button to load the PIM into the system
	# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_sevone.nms_pimC.txt"		# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_sevone.nms_pimC.txt"
			# Under the <b>Advanced</b> tab, select <b>Explore System</b>
	# Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel		# Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel
	# Right-click on the “Manage Proxy” channel and select <b>Open</b> to launch the channel		# Right-click on the “Manage Proxy” channel and select <b>Open</b> to launch the channel

imported>Teri.roberts: /* Installation */

2013-07-29T21:00:46Z

Installation

← Older revision		Revision as of 21:00, 29 July 2013
Line 42:		Line 42:
	# Click the <b>Start</b> button to load the PIM into the system		# Click the <b>Start</b> button to load the PIM into the system
	# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_sevone.nms_pimC.txt"		# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_sevone.nms_pimC.txt"
			# Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel
			# Right-click on the “Manage Proxy” channel and select <b>Open</b> to launch the channel
			# In the Manage Proxy tool, click “Reset All”
			# Refresh the browser

	== Integration Details ==		== Integration Details ==

imported>Mike.berman: created page

2013-06-03T09:46:44Z

created page

New page

This page documents the enPortal integration for SevOne Network Management System (NMS) application.

* Vendor: SevOne
* Product: Network Management System (NMS)
* Supported Version(s): 5.1.4.0
* Name of enPortal Integration Package: sevone.nms_pimC
* Required enPortal Version: 4.6.1 and above

The following section documents supported platforms, installation, and configuration of the SevOne NMS 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 ==

Perform the following steps to install the SevOne NMS PIM:
# Install AppBoard/enPortal as detailed in the [[Installation|Installation]] documentation
# Download the file sevone.nms_pimC.jar
# Start enPortal and login as an administrator
## User Name: administrator
## Password: administrator
## Domain: System
# Under the Advanced tab, select PIMImport
# Click the Browse... button
# Locate the SevOne NMS PIM JAR file in the Open dialog
# Click the Start button to extract the files from the PIM .jar archive
# Under the Advanced tab, select XMLImport
# Click the Start button to load the PIM into the system
# Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_sevone.nms_pimC.txt"

== 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 SevOne NMS channels (no custom configuration required)

* View - Channel that allows access to a particular View in SevOne. This Channel uses SevOne's forced Login mechanism. There are pre-built channels, About, Alerts, Map that demonstrates how to configure View Channel type to go to a particular SevOne View. The fields to customize are:
** hideNav - Hide Navigation (1: hide / 0: show)
** viewName - View Name, A particular View defined by SevOne application

By using Forced Login, a portal administrator could create any short cut to almost any view in SevOne. Please see this for more information: https://sevdemov5.sevone.com/manual/guiparams.html

=== Configuration ===

After installing the SevOne NMS PIM, perform the following steps to configure access to the host SevOne NMS server:

# Click on the Applications tab
# Right-click on the name "sample" in the row for sevone.nms_pimC and select "Modify"
# Fill in the items in the Modify Application Wizard dialog:
## Select the protocol used to access your SevOne NMS server (http or https)
## Change the host name from "changeme" to the hostname or ip address that will resolve to your SevOne NMS server
## Change the port to the port number of your SevOne NMS server
## Click "Save" to keep your changes
# Click on the Integrations tab
# In the Explorer, under Packages, expand the sevone.nms_pimC tree and click on the Sample target. Confirm that the information you entered is displayed for your SevOne NMS server
# Under the Sample target, click on the Home channel. A login prompt should be displayed.
# Log in using the same credentials you would use for accessing the SevOne NMS application in a browser. Confirm that the SevOne NMS Home page is displayed.

=== Create Channels ===

After installing the SevOne NMS PIM and configuring access to the host SevOne NMS server, perform the following steps to create channels to display SevOne NMS content:

# Click on the Applications tab
# Right-click on the name "sample" in the row for sevone.nms_pimC and select a channel type
# In the "Channel Name" box, enter the name you want to give to the new channel
# For "Channel Type", select "3rd Party Pims"
# Click Next
# Click Finish
# Click on the Integrations tab
# In the Explorer, under Packages, expand the sevone.nms_pimC 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:

* To create an additional direct View/Page channel, Edge will need to work with the customers to update "view_handlers.xml" file

Out of box, the pim has three pre-built channels, About, Alerts, and Map that demonstrates the direct access of SevOne View/Page. Additionally, SevOne is using client event (via Javascript) to access a particular page. For enPortal to implement this, it requires a "view_handlers.xml" file to supply the appropriate query parameters for each client event.

Therefore, if customers require additional View/Page access, Edge will need to work with customers to modify view_handlers.xml to add additional parameters required for the additional SevOne View/Page.

Here is the description of Force Login mechanism (extracted from https://sevdemov5.sevone.com/manual/guiparams.html)

<pre>
The Forced Login script provides the ability to authenticate and redirect a user to a given interface
within SevOne NMS without human interaction. Additional parameters may also be included that will modify the interface
or perform various actions. All SevOne appliances come with the script available for use immediately. To take advantage,
a URL must be constructed using the script and some combination of the the parameters listed below:

username Required A valid SevOne NMS username.
password Required The password of the valid SevOne NMS user.
domino Required The SevOne NMS interface to navigate the user to.
hideNav Optional Whether or not to "hide" the navigation bar at the top of the SevOne NMS interface. Default is 0.
params Optional An associative array of additional parameters to be sent to the interface.

As an example, a URL that would force the login of user jsmith with password sm!tty and navigate that user to the Alerts
interface would look like so:

http://[IP_OF_APPLIANCE]/forcelogin.php?username=jsmith&password=sm!tty&domino=alerts

Passing additional parameters to an interface makes its possible to perform actions such as running reports automatically,
getting a particular Device Quick Status report, or setting up default filters for a given interface.

As an example, a URL similar to above that would change the default grouping of Alerts to "Device Group" would look like so:

http://[IP_OF_APPLIANCE]/forcelogin.php?username=jsmith&password=sm!tty&domino=alerts&params[groupingType]=2
</pre>

=== License Usage ===

In order for the AppBoard/enPortal administrator to configure the sevone.nms_pimC PIM, the AppBoard/enPortal license.properties file must include licensing for at least one sevone.nms_pimC 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 SevOne NMS server. The SevOne NMS 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 SevOne NMS and compatible AppBoard/enPortal versions:

{| class="wikitable" border="1" style="background-color:#eeeeee;"
|+ align="bottom" style="color:#e76700;" |''Version Support''
|-
! width="150" | Package Name
! width="150" | enPortal Version
! width="150" | SevOne NMS Supported Versions
|-
| sevone.nms_pimC
| 4.6.1+
| 5.1.4.0
|}

{{Tip|To see the current enPortal version, run the <tt>portal version</tt> command from the <tt>[AppBoard_Home]/server/bin</tt> directory.}}

== SevOne NMS Upgrades ==

=== Upgrading from an older version of SevOne NMS ===

Older versions of SevOne NMS are not supported by this PIM, so this upgrade path is not supported. It is recommended that you validate the PIM in your SevOne NMS environment to confirm that it supports the required functionalities.

=== Upgrading SevOne NMS to a newer version ===

Perform the following steps when the SevOne NMS server is upgraded to a newer version of SevOne NMS:

# Check the AppBoard/enPortal PIM online documentation to see if the new SevOne NMS version is supported by the existing sevone.nms_pimC PIM.
## To test if the new SevOne NMS version is supported by the existing PIM that you have installed, perform the following steps:
### Click on the Applications tab
### Right-click on the row for the old SevOne NMS server and select "Modify"
### Update the protocol, host, and port to reference the server where the new version of SevOne NMS is running
## If the new SevOne NMS version is not supported by the existing PIM that you have installed, perform the following steps to upgrade the PIM:
### Download the new PIM version from the PIM download site
### Follow the steps in the Installation section above to install and configure the new PIM version
### Re-create all SevOne NMS channels to reference the new PIM
### [Optional] Perform the steps outlined in the Uninstall section below to remove the old PIM from the system

== Uninstall ==

{{Warning|Uninstalling the sevone.nms_pimC PIM will break all of the channels in your AppBoard/enPortal system that reference this integration.}}

Perform the following steps to uninstall the sevone.nms_pimC PIM:

# Click on the Integrations tab
# In the Explorer, under Packages, locate the sevone.nms_pimC integration
# Right click on the integration name, and select "Delete"
# Click "Ok" to confirm that you want to delete the integration package

Integrations/sevone/sevone.nms pimC - Revision history

imported>Jason.nicholls: moved Sevone nms pimC to integrations/sevone/sevone.nms pimC

imported>Teri.roberts at 17:05, 24 June 2014

imported>Teri.roberts at 19:54, 6 February 2014

imported>Teri.roberts: /* Installation */

imported>Teri.roberts: /* Installation */

imported>Mike.berman: created page