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

Start the wsadmin scripting tool.

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.
Element	Description
`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 product configuration
`getid`	is an AdminConfig command
`Deployment`	is a type
`ApplicationDeployment`	is a type
`adminconsole`	is the name of the application

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.
Element	Description
`$`	is a Jacl operator for substituting a variable name with its value
`AdminConfig`	is an object that represents the product 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

Save the configuration changes.
Use the following command example to save your configuration changes:
```
AdminConfig.save()
```
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")
```