What you really need is an admin-client-only install of GlassFish, which is
not there. Ideally, for *remote* asadmin commands (e.g. the one that you
cite) there are few things from asenv that it needs, it is more importantly
the class files that are needed by asadmin to function properly.
The other thing you'll need to do it to segregate the libraries needed by
asadmin (which contains jars like appserv-rt.jar and appserv-admin.jar).
This is probably not difficult, but since these jars are large, I am not
sure if you are saving anything while going through the pain.
What are your basic reservations against having an SJSAS/GF installation
just for asadmin's sake? Size?
Thanks,
Kedar
Alex Sherwin wrote:
> I'm working on making deployment of some proprietary applications as
> easy as possible.
>
> The last major thing I would like to overcome if possible is the
> requirement to have a local copy of SJSAS/glassfish installed to use
> asadmin. I looked at how asadmin.bat or .sh is invoked, and it seems
> feasible to be able to pull that out and satisfy the dependencies for
> the classpath by grabbing the appropriate libs, but it does invoke
> asenv.bat or .sh; which is generated per-system with some absolute paths.
>
> The only thing it would be used for it invoking commands in a remote
> fashion, such as "asadmin --host xx --port xx create-jdbc-resource ..." etc.
>
> I've poked around on Google a bit and haven't come up with anything
> regarding a standalone asadmin CLI.
>
> Is this feasible, or just a waste of my time to persue it?
>
> --
> Alexander Sherwin