Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Configure applications using scripting
Set background applications using wsadmin.sh
We can enable or disable a background application using scripting and wsadmin.sh.
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.sh.
- Locate the application deployment object for the application. For example:
### Jacl
set applicationDeployment [$AdminConfig getid /Deployment:adminconsole/ApplicationDeployment:/]### Jython
applicationDeployment = AdminConfig.getid('/Deployment:adminconsole/ApplicationDeployment:/')
- Enable the background application. For example:
### Jacl
$AdminConfig modify $applicationDeployment "{backgroundApplication true}"### Jython
AdminConfig.modify(applicationDeployment, ['backgroundApplication', 'true'])
- Save the configuration changes.
Save the 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:
AdminNodeManagement.syncActiveNodes()
- Use the syncNode script to propagate the changes to a specific node:
AdminNodeManagement.syncNode("myNode")
Start the wsadmin scripting client using wsadmin.sh
Configure application startup
Use the wsadmin scripting AdminConfig object for scripted administration
Related
Commands for the AdminConfig object using wsadmin.sh