By shalini_m on Aug 09, 2007
In-line upgrade is performed when "asadmin start-domain" is invoked on a particular domain. asadmin is found in install_root/bin directory. The domain on which start-domain command is invoked, is evaluated if it corresponds to the latest binaries or it matches that of an old installation. For ex: Let us consider domain1 is started, it is checked if it is a v2 domain or v1 domain or an earlier 8.x domain. If it is not a v2 domain, upgrade tool is automatically invoked. The domain is upgraded maintaining all the old configuration. It becomes ready-to-use with v2 binaries. After an upgrade, this upgraded domain can be started for further deployment and other processing.
Let me explain this with an example.
Example : SJSAS8 is installed in /opt/sjsas. The domains root is /opt/sjsas8/domains with a single domain, domain1. When GlassFish is also installed in /opt/sjsas, the binaries are upgraded in /opt/sjsas directory. The domain still exists in /opt/sjsas/domains without any configuration upgrade. To do this upgrade, execute
/opt/sjsas/bin/asadmin start-domain --domaindir /opt/sjsas/domains domain1
Actual Process :
The asadmin command recognizes an old domain in the specified domain dir and performs upgrade by invoking upgrade tool with all the inputs needed. This is an in-line upgrade viz., the domains root will remain the same before and after the upgrade for both source and target.
Upgrade tool becomes the internal process that is forked. If an upgrade is not needed, the domain is started up, as usual.
Why this new type of upgrade?
Lot of reasons...
- Simple way of doing an upgrade
- asadmin start-domain command is known to all
- Ease of use without knowing the internal process
- No need to provide any inputs like source, target or credentials
- Only inputs provided are domain name and domain directory, where it exists