Enhancements to Inline Upgrade

Problem Statement

The asadmin command currently passes-in only the essential arguments (ie. source server, target server, admin user and password file) while doing an inline upgrade. It does not handle certificate migration. There are a host of other arguments that the upgrade tool takes in that need to be addressed. The other arguments that need to be addressed are - nsspwdfile, targetnsspwdfile, jkspwdfile, capwdfile and clinstancefiles. Technically, there are three possible options for taking in the additional arguments - (a) Make the process interactive and prompt the user for these options during the upgrade process (b) Allow the user to upload the arguments through a state file (c) Add more arguments to the asadmin command. The approach we plan to take is to prompt the user for these options.

Comments

Discussed this with Kedar on 12/12/06. Kedar's comments: We could assume that the user has not changed the master password and proceed. In case the JKS password has changed, we could ask him to change it back to the default before the upgrade process.

To do

Need to decide if we will support certificate migration through inline upgrade. If we do, we will need to prompt the user to check if he would like to migrate certificates and in case he does, he needs to prompted for the JKS password. If we choose not to support certificate migation, we will need to print a warning message stating that certificates are not migrated through inline upgrade and the asupgrade script needs to be invoked if certificates are to be migrated.

Kedar's Update

I have updated the dashboard. Please let me know what I am missing (again).

Back

Option to turn off inline upgrade for better performance

Problem Statement

Since StartDomainCommand.java currently checks if the specified domain needs to be upgraded each time the start-domain command is invoked, this could have an impact on the performance. We have introduced a new system property in StartDomainCommand to turn off the inline upgrade feature (and hence this check). The feature can be disabled by setting the 'com.sun.aas.EnableAutoUpgrade' property to 'n'. This check has, however, existed for a while (from 9.0?). Profiling has shown that about 8.8% of the total start up time is spent on doing the StartDomainCommand.checkAndExecuteUpgrade.

Comments

Discussed this with Kedar on 12/12/06. Kedar's comments: Would like a publicly exposed interface to allow users to turn-on/off the option rather than having them change the value of the system property in the asadmin script.

To do

Kedar to check with Jane if it would be possible to introduce a new argument to the start domain command to enable users to turn-on and turn-off auto upgrade

Kedar's Update

I am still not convinced that this cannot be done differently. Actually, start-domain command ALWAYS needs the config context to be created. We can easily reuse that config context. So, this means that we will need to implement the checkAndExecuteUpgrade method differently. Can you please create a bug and assign it to Jane for the time being? The synopsis of the bug should say something like: parse the domain.xml during start-domain.xml exactly once.

Back