The web console was created to solve a number of issues imposed by the Java console.
It also slots right into the paradigm of web and rest api communication.
That said the early console was… bad… like really bad.
But over the years it has gotten better and it keeps getting better.
So my suggestion for people who are new to commvault is to use the webconsole as it is intended to replace the java gui, the Java GUI has to drag along the all the cruft from the inception of the product, making it so that some things don’t even make any logical sense as presented in the Java GUI, also many new features simply do not get back ported to the java GUI.
At one point, the Webconsole was a poor substitute for the Java GUI, but I would strongly suggest that you foster the habit of using the web console.
There will always be the graybeards that stick to the old ways, and while there are definite benefits to doing but there are also downsides, the graybeards are often not aware of the new functionality being added, and while they may be exceptionally good at using the Java GUI in its current form the new things are passing them by.
Technology has a life-cycle that looks very much like a human life.
Infancy → growth → maturity → old age → death
The Java Console is somewhere between maturity and old age.
The Web Console is somewhere between growth and maturity.
In the next few years the Java console will simply get old and then die.
The Web Console during that same time tired will reach maturity.
Think about all those Pascal programmers you know. Don’t know any? Exactly.
