Launching Third Party Applications - Extreme Networks EPICenter Guide Manual

Configuring Devices for Use With EPICenter
Add any new entries to the end of the file only, do not add them in between existing entries.
●
Make sure each entry is unique
●
Make sure each MIB file name matches the MIB definition name.
●
You must restart the EPICenter server to have these changes take effect.

Launching Third Party Applications

EPICenter can launch an external application for a 3rd party device under the following conditions:
The EPICenter client and server and the 3rd party application client and server are installed on the
●
same system
The EPICenter client and the 3rd party client are installed on the same system
●
The EPICenter client is installed on one system, and a remote (web-based) 3rd party client and
●
server is installed on a different system.
The 3rd party application must be added to the
directory. The format of the entry in the XML file is as follows (using the Summit WM as an
Types
example):
<?xml version="1.0" encoding="UTF-8"?>
<tools>
<tool oid="Summit WM" description="Summit WM launch tool" name="Launch Summit WM">
<contents>
https://$deviceIP:5825
</contents>
<variable/>
<role roleid="3 2 1"/>
<context type="device"/>
</tool>
</tools>
The contents of the Tool.xml has some similarities to the form of a Telnet macro—in particular, in the
use of the
roleid
Once this integration has been accomplished, the user can launch the 3rd party application from the
External App menu accessed from the device right-click pop-up menu.
204
and to control which users can launch the application.
context
file found in the
Tool.xml extreme.war/ATL/Device
EPICenter Concepts and Solutions Guide