Hi
I install igniton v8 in 2 different pc but there is no gateway Control utility.
Is this utility is omit form v8.0?
Yes, it’s command-line only now. You should have a gcu.sh or gcu.bat file.
FYI, On my install it is gwcmd.bat
1 Like
Why? What’s the reason? It’s good way to reset service and backup and restart gateway.
The gateway command line utility can do all those things, and doesn't suffer on non-Windows OSes, where previously you couldn't use the graphical GCU to restart the service, only take backups and thread dumps.
It's also not new - gwcmd existed in previous versions (Gateway Control Utility - Ignition User Manual 7.9 - Ignition Documentation) , we're just deprecating the standalone graphical tool
2 Likes
I’ve discovered / proven (through some painful testing) that the user account issuing a gwcmd command requires Full security permissions on the “Program Files\Inductive Automation\Ignition\data” folder.
If you are using the -b for backup, you also need full permissions on the “.\temp” folder and the folder where the backup file is being sent.
The default install (at least in my environment) does not grant Full security permissions to anything in or under “Program Files\Inductive Automation\Ignition”.
I’ve asked our Server Team to add a GPO for the necessary permissions but I wanted to document this for others who may run into the same problem.
Wait… so since the GCU didn’t work well on Linux and Mac, we took it away from Windows? I imagine Linux users are accustomed to working with the command line, and I’m gonna go out on a limb and suggest that Macs are probably a tiny minority of users, since I’ve never seen a factory where Macs were used to host SCADA. Why not just take it away from Linux and Mac?
1 Like
The UI was poor and the GCU was a maintenance burden. There’s nothing you can’t accomplish without it, including service start/stop/restart.
only thing is that you can’t see the status of the server without GCU, unless the ignition main page is displayed.
gwcmd -i should show the same information in terms of status that the GCU did
3 Likes
I call BS on this. In version 8, you have a launcher for the Designer and the Vision client, but didn’t create one for the Gateway Control Utility. Running the bat file requires escalating with Admin access - which some folks may not have.
I know everyone at Ignition is patting themselves on the back for removing this but it should be in there. Just throw together a little launcher like you did with the other two to run the bat file - and has the permissions set during install. Easy peasy.
1 Like
I call BS on your BS. The GCU required admin privileges for most operations as well.
6 Likes
I hate to jump into the middle of this, but Kevin is correct: the CGU did require admin privileges to operate. We don't show that in the video, because we use an admin account on the OS of our recording computer(s), just so we can utilize some of these features (not to mention the User Account Controls popup gave our recording software some grief).
I apologize for the trouble that may have caused. For what it's worth, the User Manual for 7.8 and 7.9 do state the following:
Note: The Gateway Control Utility must run on the same machine as the Ignition Gateway and requires administrative privileges
1 Like
The GCU has needed elevated privileges since Windows 7, reflected in this post from 2013:
1 Like
Ok, I was incorrect. It required Admin privileges. Super. Great. Wonderful.
That was really not the point of my first post.
I still think it’s a mistake to have command line only GCU.
Perhaps it was lost in the diatribe.
The point Kevin's early posts is that the GCU was dropped because it couldn't effectively be made to be cross platform. It was a kludge on a good day, and changes in Windows (and MacOS and Linux and {insertDistroHere} ) make such things that must interact with the OS nearly impossible to keep up. It's why the CLI commands exist.
I do, however, admire your commitment be angry and stay angry about it. It rather reminds me of Jeff Dunham's Walter character.
I'm done now raking you over the coals now, as it's not constructive, and generally not in my nature.
Back to constructive things!
I had given some thought on making a Windows-only graphical interface using AutoIt. Unfortunately, I don't have the time, and that's not going to change any time soon.
Some things, I believe, can be community driven where it makes sense to do so. Therefore, if anyone else in the community wants to tackle it in the meantime, feel free.
3 Likes
The GCU was also just very outdated and still written in Swing and dependent on a local Java install instead of the bundled one.
We didn’t have time to build a new one for 8.0, there were far more pressing issues, and there are still more pressing issues. It may come back one day. It may not. No real functionality is lost in the transition.
3 Likes