Set background applications using scripting
Overview
Perform the following steps to enable or disable a background application. 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 wsadmin
- Locate the application deployment object for the application. For example:
set applicationDeployment [$AdminConfig getid /Deployment:adminconsole/ApplicationDeployment:/] applicationDeployment = AdminConfig.getid('/Deployment:adminconsole/ApplicationDeployment:/')
where:
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 - Enable the background application. For example:
$AdminConfig modify $applicationDeployment "{backgroundApplication true}" $AdminConfig save AdminConfig.modify(applicationDeployment, ['backgroundApplication', 'true'])
where:
$ is a Jacl operator for substituting a variable name with its value AdminConfig is an object that represents the WAS 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 - In a network deployment environment only, synchronize the node.
See Also
AdminConfig object for scripted administration
Commands for the AdminConfig object