Seems to me that it's such a major overhaul that simply documenting
the changes en-masse might be better...
On Mar 3, 2008, at 12:13 PM, Jennifer Chou wrote:
I need to create an issue for changing start-database/stop-database
from local to remote for ccc with the following info: Anything else
I should add?
* which interfaces are being changed
o asadmin start-database, asadmin stop-database
* reason for change
o ease of use: allow the user to start database from a
* impact on other functional groups
o SQE will need to update test scripts.
o Docs will need to be updated.
o CTS may need to be updated
o Dev will need to change start/stop-database from a local
to remote command. The server will need to start the
process in a smart way so there are no deadlocks.
* customer impact and risks
o Scripts that call start-database before start-domain will
not have the database started.
* migration for people who use the existing interface
o Change scripts to reverse order of start-database,
* blurb for compatibility guide
o In V2 start-database and stop-database worked with or
without the application server running. For V3 to allow
for starting and stopping the database from a remote
machine, the start-database and stop-database commands
will only work on a running application server.
Lloyd L Chambers
Sun Microsystems, Inc