WAS v8.5 > Script the application serving environment (wsadmin) > Manage deployed applications using wsadmin.sh

Update installed applications using wsadmin.sh

Use wsadmin and scripting to update installed applications on an application server. Both the update command and the updateinteractive command support a set of options. We can also obtain a list of supported options for an EAR fileusing the options command, for example:

Jacl:

Jython:

We 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.

If an application is running, changing an application setting causes the application to restart. On stand-alone servers, the application restarts after you save the change. On multiple-server products, the application restarts after you save the change and files synchronize on the node where the application is installed. To control when synchronization occurs on multiple-server products, deselect Synchronize changes with nodes on the Console preferences page.

Perform the following steps to update an application:

  1. Start the wsadmin scripting tool.
  2. Update the installed application using one of the following options.

    • The following command updates a single file in a deployed application:

      • Jacl: 

        $AdminApp update app1 file {-operation update -contents c:/apps/app1/my.xml 
 -contenturi app1.jar/my.xml}

      • Jython string: 

        AdminApp.update('app1', 'file', '[-operation update -contents c:/apps/app1/my.xml  
 -contenturi app1.jar/my.xml]')

      • Jython list: 

        AdminApp.update('app1', 'file', ['-operation', 'update', '-contents', 
 'c:/apps/app1/my.xml', '-contenturi', 'app1.jar/my.xml'])

      update file command elements. Run the update command to change an installed application file.

      Element Definition
      $ is a Jacl operator for substituting a variable name with its value
      AdminApp is an object that supports application objects management
      update is an AdminApp command
      app1 is the name of the application to update
      file is the content type value
      operation is an option of the update command
      update is the value of the operation option
      contents is an option of the update command
      /apps/app1/my.xml is the value of the contents option
      contenturi is an option of the update command
      app1.jar/my.xml is the value of the contenturi option

    • The following command adds a module to the deployed application, if the module does not exist. Otherwise, the existing module is updated.

      • Jacl: 

        $AdminApp update app1 modulefile {-operation addupdate -contents 
 c:/apps/app1/Increment.jar -contenturi Increment.jar -nodeployejb -BindJndiForEJBNonMessageBinding {{"Increment EJB module" 
 Increment Increment.jar,META-INF/ejb-jar.xml Inc}}}

      • Jython string: 

        AdminApp.update('app1', 'modulefile', '[-operation addupdate -contents 
 c:/apps/app1/Increment.jar -contenturi Increment.jar -nodeployejb -BindJndiForEJBNonMessageBinding [["Increment EJB module" 
 Increment Increment.jar,META-INF/ejb-jar.xml Inc]]]')

      • Jython list: 

        bindJndiForEJBValue = [["Increment EJB module", "Increment", "Increment.jar,META-INF/ejb-jar.xml", 
"Inc"]]  AdminApp.update('app1', 'modulefile', ['-operation', 'addupdate', '-contents', 
 'c:/apps/app1/Increment.jar', '-contenturi','Increment.jar' '-nodeployejb', `-BindJndiForEJBNonMessageBinding', 
 bindJndiForEJBValue])

      update modulefile command elements. Run the update command to change an installed module file.

      Element Definition
      $ is a Jacl operator for substituting a variable name with its value
      AdminApp is an object that supports application objects management
      update is an AdminApp command
      app1 is the name of the application to update
      modulefile is the content type value
      operation is an option of the update command
      addupdate is the value of the operation option
      contents is an option of the update command
      /apps/app1/Increment.jar is the value of the contents option
      contenturi is an option of the update command
      Increment.jar is the value of the contenturi option
      nodeployejb is an option of the update command
      BindJndiForEJBNonMessageBinding is an option of the update command
      "Increment EJB module" Increment Increment.jar,META-INF/ejb-jar.xml Inc is the value of the BindJndiForEJBNonMessageBinding option. The value of this option is defined in the application configuration. To determine the value of this option, use the following Jython or Jacl command:

      Using Jython:

        AdminApp.view('myAppName')
      Using Jacl:

        $AdminApp view myAppName
      bindJndiForEJBValue is a Jython variable containing the value of the BindJndiForEJBNonMessageBinding option

    • The following command uses a partial application to update a deployed application:

      • Jacl:

          $AdminApp update app1 partialapp {-contents c:/apps/app1/app1Partial.zip}

      • Jython string: 

        AdminApp.update('app1', 'partialapp', '[-contents 
 c:/apps/app1/app1Partial.zip]')

      • Jython list: 

        AdminApp.update('app1', 'partialapp', ['-contents', 
 'c:/apps/app1/app1Partial.zip'])

      update partialapp command elements. Run the update command to change part of an installed application.

      Element Definition
      $ is a Jacl operator for substituting a variable name with its value
      AdminApp is an object that supports application objects management
      update is an AdminApp command
      app1 is the name of the application to update
      partialapp is the content type value
      contents is an option of the update command
      /apps/app1/app1Partial.zip is the value of the contents option

    • Update the entire deployed application.

      To use the existing listener port instead of using or creating a new activation specification, determine whether the EJB JAR version is lower than 2.1. The system automatically creates and uses an activation specification when we specify the -usedefaultbindings option to deploy an application. If an activation specification exists, the system ignores the listener port, and instead uses the activation specification. To deploy an application with an EJB JAR version greater than or equal to 2.1 using the defined listener ports instead of a new activation specification, set the com.ibm.websphere.management.application.dfltbndng.mdb.preferexisting system property to true in the wsadmin.properties file in the properties directory of the profile of interest.

      • Jacl: 

        $AdminApp update app1 app {-operation update -contents c:/apps/app1/newApp1.jar 
 -usedefaultbindings -nodeployejb -BindJndiForEJBNonMessageBinding {{"Increment EJB module" Increment 
 Increment.jar,META-INF/ejb-jar.xml Inc}}}

      • Jython string: 

        AdminApp.update('app1', 'app', '[-operation update -contents 
 c:/apps/app1/newApp1.ear  -usedefaultbindings -nodeployejb -BindJndiForEJBNonMessageBinding [["Increment EJB module" Increment 
 Increment.jar,META-INF/ejb-jar.xml Inc]]]')

      • Jython list: 

        bindJndiForEJBValue = [["Increment EJB module", "Increment", "Increment.jar,META-INF/ejb-jar.xml", 
"Inc"]]  AdminApp.update('app1', 'app', ['-operation', 'update', '-contents', 
 'c:/apps/app1/NewApp1.ear', '-usedefaultbindings', '-nodeployejb', `-BindJndiForEJBNonMessageBinding', bindJndiForEJBValue])

      update app command elements. Run the update command to change an installed application.

      Element Definition
      $ is a Jacl operator for substituting a variable name with its value
      AdminApp is an object that supports application objects management
      update is an AdminApp command
      app1 is the name of the application to update
      app is the content type value
      operation is an option of the update command
      update is the value of the operation option
      contents is an option of the update command
      /apps/app1/newApp1.ear is the value of the contents option
      usedefaultbindings is an option of the update command
      nodeployejb is an option of the update command
      BindJndiForEJBNonMessageBinding is an option of the update command
      "Increment EJB module" Increment Increment.jar,META-INF/ejb-jar.xml Inc is the value of the BindJndiForEJBNonMessageBinding option. The value of this option is defined in the application configuration. To determine the value of this option, use the following Jython or Jacl command:

      Using Jython:

        AdminApp.view('myAppName')
      Using Jacl:

        $AdminApp view myAppName
      bindJndiForEJBValue is a Jython variable containing the value of the BindJndiForEJBNonMessageBinding option

  3. Save the configuration changes.

    Use the following command example to save your configuration changes:

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. We 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 the system extracted the binary files before starting the application.

The isAppReady command returns a value of true if the system is ready to start the application, or a value of false if the system is not ready to start the application.

If the system is not ready to start the application, the system might be expanding application binaries. Use the getDeployStatus command to display additional information about the binary file expansion status, as the following example displays:

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


Related


Use the wsadmin scripting AdminApp object for scripted administration


Reference:

Commands for the AdminApp object using wsadmin.sh
Options for the AdminApp object install, installInteractive, edit, editInteractive, update, and updateInteractive commands using wsadmin.sh
Example: Obtaining option information for AdminApp object commands using wsadmin.sh


+

Search Tips   |   Advanced Search