Use the wsadmin tool and scripting to update installed applications on an application server.
Both the update command and the updateinteractive command support a set of options. You can also obtain a list of supported options for an Enterprise Archive (EAR) file using the options command, for example:
$AdminApp options
print AdminApp.options()
You can set or update a configuration value using options
in batch mode. To identify which configuration object is to be set
or updated, the values of read only fields are used to find the corresponding
configuration object. All the values of read only fields have to match
with an existing configuration object, otherwise the command fails.
Perform the following steps to update an application:
The steps in this task return a success message if the system successfully updates the application. When updating large applications, the command might return a success message before the system extracts each binary file. You cannot start the application until the system extracts all binary files. If you installed a large application, use the isAppReady and getDeployStatus commands for the AdminApp object to verify that the system extracted the binary files before starting the application.
AdminApp.isAppReady('myapp1')
AdminApp.getDeployStatus('app1')
Running the getDeployStatus command where app1 is DefaultApplication results in status information about DefaultApplication resembling the following:
ADMA5071I: Distribution status check started for application DefaultApplication. WebSphere:cell=myCell01,node=myNode01,distribution=unknown,expansion=unknown ADMA5011I: The cleanup of the temp directory for application DefaultApplication is complete. ADMA5072I: Distribution status check completed for application DefaultApplication. WebSphere:cell=myCell01,node=myNode01,distribution=unknown,expansion=unknown
In this information ...Related reference
| IBM Redbooks, demos, education, and more(Index) |