Announcing vijavaNG: Much Lighter and Faster with Commercial License and Support
Since I left VCE four months ago, I have been working intensively on a commercial version of the open source vijava API supporting all versions of vSphere APIs (5.5 is the latest). If you have used the open source API, you know the vijava is much faster than other alternatives. Since its debut, it has been used in many commercial products from companies like Cisco, EMC, HP, etc.
Still, there are rooms to improve. I am happy to introduce the significant improvements in the vijavaNG:
Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.
1. Higher performance and lighter streaming XML engine
The open source vijava uses dom4j as the XML engine and has boosted the performance for several times over the others using Apache AXIS. While most people are happy with the performance, vijavaNG makes it even faster. The secret is the new super performance streaming engine.
More than the performance gain is the memory consumption. Because the streaming API does not need to generate the intermediate DOM objects, we can reduce the memory requirement by half at least, not to mention much less stress on the JVM garbage collector.
This may not be a big deal for small deployment but critical for large deployment where you have tons of hosts and virtual machines.
2. Better Security Support
vijavaNG supports pass through of client certificates to vCenter for log in. This allows server extensions to log into vCenter without password after it’s registered. This feature is only supported in vijavaNG, not the open source version.
3. Javadoc is ready
Although VMware API Reference is great but it cannot be easily integrated in IDEs like Eclipse/Netbeans/Intellij. The vijavaNG now provides full javadoc so that developers can read the comments rigth inside the IDEs while hovering their mouses over an API method. This convenience can save quite some time and frustration during the development.
4. Consistent APIs with open source vijava
As I mentioned before, the open source vijava will continue on its path. If you have application built on top of vijava API, it will also run as it is on the vijavaNG. With the commerical vijavaNG, you will get additional features and commmerical support options.
You can now easily logging SOAP message between the API and the server. With the flexible architecture, you can hook it up with your logging framework like log4j or the Java native logging framework.
6. Higher level APIs
vijavaNG now includes the guest APIs (experimental) that I designed to provide higher level abstraction over the existing vSphere API. It makes it one line call to do something like downloanding a while directory and its subdirectories to local machine. More similar APIs will be included in the future to drive more benefits.
7. New architecture for other APIs
The vijavaNG has a new archiecture that is ready to support other VMware APIs like ESX Agent Manager APIs, etc. If you are interested in EAM APIs, please send me an email.
8. Commerical support
If you have critical applications/systems built on the API, you have the option for commercial support from the author and his company.
9. Better quality
Last, but not the least, is the higher quality backed by many unit test cases I wrote. They covers many aspects of the APIs.
A few friend in the community has tried the vijavaNG from months ago. It’s now your turn. If you are interested in buying or evaluating it, please send me an email (steve __aT__ doublecloud.org, remove the space and _) and I will send you a download link for your evaluation.