What is a brief description of how the AppZero solution works from VAA creation through execution and maintenance?

There is a Creator – a graphical process that allows you to capture the application and its requirements in a VAA.  The VAA can be tweaked or adjusted as you need to accommodate your application.  The result is a VAA which is then compressed and can be copied to whatever server is desired. 

At run time, we have a small runtime layer called the AppZero Director.  It redirects requests an application makes for things like files and registry entries to the VAA instead of to the underlying OS.  That’s how we encapsulate an application.  It “believes” it’s running normally, making registry requests, calling for files …. But it is the AppZero Director that supplies these items to the VAA.

Any changes the app makes to a file or any configuration changes it makes, are also contained in the VAA.  The underlying OS (UOS) is never effected so the VAA can be moved to another environment if desired.  Or replicated if you’re trying to scale up.  We see that you get the full configuration of the app.

We also have an administration tool to manage VAAs, that is graphically based – that lets you start them and stop them, or reconfigure them if you like.  That’s what we use for on-going maintenance of VAAs.