Setting background applications using wsadmin scripting

You can enable or disable a background application using scripting and the wsadmin tool.

About this task

Background applications specify whether the application must initialize fully before the server starts. The default setting is false and this indicates that server startup will not complete until the application starts. If you set the value to true, the application starts on a background thread and server startup continues without waiting for the application to start. The application may not ready for use when the application server starts.

Procedure

  1. Start the wsadmin scripting tool.
  2. Locate the application deployment object for the application. For example:
    • Using Jacl:
      set applicationDeployment [$AdminConfig getid /Deployment:adminconsole/ApplicationDeployment:/]
    • Using Jython:
      applicationDeployment = AdminConfig.getid('/Deployment:adminconsole/ApplicationDeployment:/')
    Table 1. getid command elements. Run the getid command to get an application object.
    set is a Jacl command
    applicationDeployment is a variable name
    $ is a Jacl operator for substituting a variable name with its value
    AdminConfig is an object that represents the WebSphere® Application Server configuration
    getid is an AdminConfig command
    Deployment is a type
    ApplicationDeployment is a type
    adminconsole is the name of the application
  3. Enable the background application. For example:
    • Using Jacl:
      $AdminConfig modify $applicationDeployment "{backgroundApplication true}"
    • Using Jython:
      AdminConfig.modify(applicationDeployment, ['backgroundApplication', 'true'])
    Table 2. modify command elements. Run the modify command to set the backgroundApplication value.
    $ is a Jacl operator for substituting a variable name with its value
    AdminConfig is an object that represents the WebSphere Application Server configuration
    modify is an AdminConfig command
    applicationDeployment is a variable name that was set in step 1
    backgroundApplication is an attribute
    true is the value of the backgroundApplication attribute
  4. Save the configuration changes.
    Use the following command example to save your configuration changes:
    AdminConfig.save()
  5. Synchronize the node.
    Use the syncActiveNode or syncNode scripts in the AdminNodeManagement script library to propagate the configuration changes to node or nodes.
    • Use the syncActiveNodes script to propagate the changes to each node in the cell, as the following example demonstrates:
      AdminNodeManagement.syncActiveNodes()
    • Use the syncNode script to propagate the changes to a specific node, as the following example demonstrates:
      AdminNodeManagement.syncNode("myNode")



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 5:30:17 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=txml_background
File name: txml_background.html