Integrations/sevone/sevone.nms pimE - Revision history

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

2014-07-25T07:14:55Z

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

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

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

2014-06-24T17:06:54Z

← Older revision		Revision as of 17:06, 24 June 2014
Line 1:		Line 1:
	{{DISPLAYTITLE:SevOne ~~Network Management System (NMS)~~ pimE}}		{{DISPLAYTITLE:SevOne pimE}}
	[[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.2.4 - 5.2.6		* <b>Supported Version(s)</b>: 5.2.4 - 5.2.6
	* <b>Name of enPortal Integration Package</b>: sevone.nms_pimE		* <b>Name of enPortal Integration Package</b>: sevone.nms_pimE

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

2014-02-06T19:53:47Z

← Older revision		Revision as of 19:53, 6 February 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:SevOne Network Management System (NMS) pimE}}
			[[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>Nick.chang: /* Version Support */

2014-02-06T19:43:37Z

Version Support

← Older revision		Revision as of 19:43, 6 February 2014
Line 160:		Line 160:
	\| sevone.nms_pimE		\| sevone.nms_pimE
	\| 4.6.1+		\| 4.6.1+
	\| 5.2.4.0		\| 5.2.4 - 5.2.6
	\|}		\|}

	{{Tip\|To see the current enPortal version, run the <tt>portal version</tt> command from the <tt>[AppBoard_Home]/server/bin</tt> directory.}}		{{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 ==		== SevOne NMS Upgrades ==

imported>Nick.chang at 19:43, 6 February 2014

2014-02-06T19:43:15Z

← Older revision		Revision as of 19:43, 6 February 2014
Line 3:		Line 3:
	* <b>Vendor</b>: SevOne		* <b>Vendor</b>: SevOne
	* <b>Product</b>: Network Management System (NMS)		* <b>Product</b>: Network Management System (NMS)
	* <b>Supported Version(s)</b>: 5.2.4.0		* <b>Supported Version(s)</b>: 5.2.4 - 5.2.6
	* <b>Name of enPortal Integration Package</b>: sevone.nms_pimE		* <b>Name of enPortal Integration Package</b>: sevone.nms_pimE
	* <b>Required enPortal Version</b>: 4.6.1 and above		* <b>Required enPortal Version</b>: 4.6.1 and above

imported>Teri.roberts at 21:45, 15 August 2013

2013-08-15T21:45:21Z

← Older revision		Revision as of 21:45, 15 August 2013
Line 68:		Line 68:
	<tt>params[<param name>]=<param value></tt> <br/>		<tt>params[<param name>]=<param value></tt> <br/>
	i.e. <tt>params[mapId]=110</tt>		i.e. <tt>params[mapId]=110</tt>


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


	=== License Usage ===		=== License Usage ===

imported>Nick.chang: /* Known Issues */

2013-08-15T21:44:26Z

Known Issues

← Older revision		Revision as of 21:44, 15 August 2013
Line 107:		Line 107:
	The following known issues are associated with this PIM:		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~~		* It is recommended to run this application in HTTP mode. In HTTPS mode, it appears that the server certificate requires an additional validation which causes slowness when it is proxied in enPortal.

	~~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.		* To create an additional direct View/Page channel, please use View channel class as template and add an additional parameters based on force login guideline.

	~~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)		Here is the description of Force Login mechanism (extracted from https://sevdemov5.sevone.com/manual/guiparams.html)
Line 139:		Line 137:
	http://[IP_OF_APPLIANCE]/forcelogin.php?username=jsmith&password=sm!tty&domino=alerts&params[groupingType]=2		http://[IP_OF_APPLIANCE]/forcelogin.php?username=jsmith&password=sm!tty&domino=alerts&params[groupingType]=2
	</pre>		</pre>


	=== License Usage ===		=== License Usage ===

imported>Nick.chang: /* Channel Types */

2013-08-15T21:38:03Z

Channel Types

← Older revision		Revision as of 21:38, 15 August 2013
Line 55:		Line 55:
	=== Channel Types ===		=== Channel Types ===

	* Home - Channel that displays the default Home page for the logged in user, including full navigation controls (no custom configuration required)		* Home - Channel that displays the default Home page for the logged in user, including full navigation controls (no custom configuration required). This home channel is using Force Login mechanism with "domino" parameter set to "dashboard"

	* Proxy - Channel that is used by the system to display SevOne NMS channels (no custom configuration required)		* Proxy - Channel that is used by the system to display SevOne NMS channels (no custom configuration required)
Line 65:		Line 65:
	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		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

			The parameter for each domino view type is in such a format <br/>
			<tt>params[<param name>]=<param value></tt> <br/>
			i.e. <tt>params[mapId]=110</tt>

	=== Configuration ===		=== Configuration ===

imported>Mike.berman at 21:29, 15 August 2013

2013-08-15T21:29:08Z

← Older revision		Revision as of 21:29, 15 August 2013
Line 47:		Line 47:
	# In the Manage Proxy tool, click “Reset All”		# In the Manage Proxy tool, click “Reset All”
	# Refresh the browser		# Refresh the browser


	== Integration Details ==		== Integration Details ==
Line 63:		Line 64:

	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		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 ===		=== Configuration ===
Line 79:		Line 81:
	# 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 SevOne NMS application in a browser. Confirm that the SevOne NMS Home page is 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 ===		=== Create Channels ===
Line 95:		Line 98:

	Repeat the above steps to create additional channels. Select a different Channel Type in step 2 to create a different type of channel.		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 ===		=== Known Issues ===
Line 132:		Line 136:
	http://[IP_OF_APPLIANCE]/forcelogin.php?username=jsmith&password=sm!tty&domino=alerts&params[groupingType]=2		http://[IP_OF_APPLIANCE]/forcelogin.php?username=jsmith&password=sm!tty&domino=alerts&params[groupingType]=2
	</pre>		</pre>


	=== License Usage ===		=== License Usage ===
Line 157:		Line 162:

	{{Tip\|To see the current enPortal version, run the <tt>portal version</tt> command from the <tt>[AppBoard_Home]/server/bin</tt> directory.}}		{{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 ==		== SevOne NMS Upgrades ==

imported>Mike.berman at 21:28, 15 August 2013

2013-08-15T21:28:15Z

← Older revision		Revision as of 21:28, 15 August 2013
Line 69:		Line 69:

	# Click on the <b>Applications</b> tab		# Click on the <b>Applications</b> tab
	# Right-click on the name "sample" in the row for sevone.~~nms_pimD~~ and select "Modify"		# Right-click on the name "sample" in the row for sevone.nms_pimE and select "Modify"
	# Fill in the items in the <b>Modify Application Wizard</b> dialog:		# Fill in the items in the <b>Modify Application Wizard</b> dialog:
	## Select the protocol used to access your SevOne NMS server (http or https)		## Select the protocol used to access your SevOne NMS server (http or https)
Line 76:		Line 76:
	## Click "Save" to keep your changes		## Click "Save" to keep your changes
	# Click on the <b>Integrations</b> tab		# Click on the <b>Integrations</b> tab
	# In the Explorer, under Packages, expand the sevone.~~nms_pimD~~ tree and click on the <b>Sample</b> target. Confirm that the information you entered is displayed for your SevOne NMS server		# In the Explorer, under Packages, expand the sevone.nms_pimE tree and click on the <b>Sample</b> target. Confirm that the information you entered is displayed for your SevOne NMS server
	# 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 SevOne NMS application in a browser. Confirm that the SevOne NMS Home page is 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.
Line 91:		Line 91:
	# Click <b>Finish</b>		# Click <b>Finish</b>
	# Click on the Integrations tab		# Click on the Integrations tab
	# In the Explorer, under Packages, expand the sevone.~~nms_pimD~~ tree and click on the Sample target. Confirm that the new channel is listed along with the other sample channels.		# In the Explorer, under Packages, expand the sevone.nms_pimE tree and click on the Sample target. Confirm that the new channel is listed along with the other sample channels.