users@glassfish.java.net

Re: cleanest upgrade path from early V3 to FCS

From: Kedar Mhaswade <Kedar.Mhaswade_at_Sun.COM>
Date: Fri, 11 Dec 2009 18:02:06 -0800

Hassan Schroeder wrote:
> On Fri, Dec 11, 2009 at 5:17 PM, Kedar Mhaswade <Kedar.Mhaswade_at_sun.com> wrote:
>
>> Now, you should simply do:
>>
>> /v3/bin/asadmin start-domain --domaindir /oldv3/domains/domain1
>
> glassfish-v3-web]$ ./bin/asadmin start-domain --domaindir
> ../glassfish-01/glassfish/domains/domain1
> CLI303 There is more than one domain in
> ../glassfish-01/glassfish/domains/domain1. You must specify one
> domain as an operand.
> Command start-domain failed.
>
> Uh, what???

Yeah, the message is less than useful.
Try: start-domain --domaindir ../glassfish-01/glassfish/domains domain1.

Sadly, we did not name the thing correctly. It should be something like:
--domains-parent-folder (but that too suffers from verbosity).

>
>> and if all goes well, the domain1 will be "upgraded" to use the new
>> v3 FCS binaries and code. Alternatively, you can use:
>> /v3/bin/asupgrade and a GUI screen will show up that will help you
>> upgrade.
>
> glassfish-v3-web]$ ./bin/asupgrade

Right. This is one of those other confusing things. The top level
bin (install-dir/bin) does not have asupgrade. It's inside the
glassfish subfolder of the installation.

> bash: ./bin/asupgrade: No such file or directory
>
> Sigh. Keep 'em coming :-)