We are delighted to announce that the Eclipse plug-in for Stingray TrafficScript has been published on GitHub, following from the original Eclipse plugin made available by Zeus Technology for ZXTM. You may need to re-install the Eclipse plugin if you have an older version of the Zeus plugin already installed.
About this extension:
Eclipse is one of the most popular IDEs (Integrated Development Environments). The slick user interface makes it faster and easier to manage and edit your current software project.
The Stingray plug-in allows you to edit your TrafficScript code in Eclipse, making it easier and faster to edit and deploy your rules:
To install the plugin you must have the following:
Eclipse installs plugins via an automatic update site, which is used to download and install the latest version of a particular plugin. To install the Stingray plugin for Eclipse:
The Stingray update site should appear in the main site list, under which the Stingray plugin should be listed. Check the box next to it.
Restart Eclipse after completing the installation when prompted. The plugin should now be installed.
Open the Stingray perspective, which sets up Eclipse to edit rules:
Eclipse keeps all its code in projects, and a Stingray Project connects to a Stingray Traffic Manager cluster and lets you edit the Rules Catalog which contains all the TrafficScript rules. To add a new project click the Add new Zeus project button at the top of the Zeus Viewer:
The Create a New Stingray Project wizard will appear:
Provide the details of the cluster you want to manage in Eclipse and hit OK. The plugin will then try and connect to the Traffic Manager you specified, and will create the project once successful. The Viewer should now show your Stingray Traffic Manager with all the rules on it.
You can now edit a TrafficScript rule and deploy it from within Eclipse. When you edit a TrafficScript rule, Eclipse provides syntax highlighting, code completion and documentation to help you create your TrafficScript code more quickly and accurately:
You can drag-and-drop rules between clusters, and when you save a rule, it is immediately deployed to the cluster. If you have a syntax error in your rule, Eclipse will detect this and prevent the rule from being deployed.
You can manage several clusters within Eclipse, and drag-and-drop rules between each:
You can use the Navigator to compare rules to determine how they differ. The ‘Compare’ view allows you to copy individual changes from one rule to another.
Copyright (c) 2014 Riverbed Technology, Inc. Stingray Plugin for Eclipse is licensed under the terms and conditions of the Eclipse Public License v1.0 set forth at https://github.com/riverbed/stingray-eclipse/blob/master/LICENSE (''License''). Stingray Plugin for Eclipse is distributed ''AS IS'' as set forth in the License. Stingray Plugin for Eclipse also includes certain third party code. All such third party code is also distributed ''AS IS'' and is licensed by the respective copyright holders under the applicable terms and conditions (including, without limitation, warranty and liability disclaimers) identified at https://github.com/riverbed/stingray-eclipse/blob/master/LICENSE.
Download this extension from here:
Message was edited by: David Toth - Added the Zeus plugin URL on the Eclipse marketplace.
Message was edited by: Paul Wallace - Updated to show new download location at GitHub - corrected URL with trailing "/"
Message was edited by: Paul Wallace - Latest update includes improvements in the way that the plugin handles Developer mode software, and additional help data to cover features introduced in Stingray 9.6
If company is using TACACS+ to allow access to the STM and the user name is 'first.last' the plugin errors:
What would it take to get the plug-in fix to allow this?
I updated Owen's post with the Zeus plugin URL on the Eclipse Marketplace:
All: This has been republished on GitHub at:
(note trailing "/")
And on the Eclipse Marketplace:
I've got some problem installing this plug-in because of inside file "site.xml" the key "url" in "feature" node is pointing to the root folder not to folder "features".
I've solved reproducing repository structure locally in my pc and modifying "site.xml" pointing key "url" to the "features" folder.
Thanks - There was a problem with the URL I posted originally - now updated to show the correct URL:
We were recently forced to turn off TLS 1.0 on our Stingrays and doing so broke our ability to login via the Eclipse plugin. The only SSL option enabled on our Stingrays is: admin!support_tls1_1.
I have yet to find a way to get connected to the Stingrays through the Eclipse plugin using TLS 1.1. Any suggestions would be greatly appreciated.
Tim, thanks for this and the other info you sent over. We'll continue to look at this and let you know if we can update in due course.
Additional note: this Eclipse plugin works best when you have a production license on your Stingray Traffic Manager, and you may have problems when you are using the Developer Edition. If you need to use the Eclipse plugin in a developer environment, then for now, the best approach is to request a 30-day evaluation license via the online form: