WAS v8.5 > Script 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. 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 we 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.

1. Start the wsadmin scripting tool.
   
2. 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:/')

3. Enable the background application. For example:

   • Jacl:

     $AdminConfig modify $applicationDeployment "{backgroundApplication true}"

   • Jython:

     AdminConfig.modify(applicationDeployment, ['backgroundApplication', 'true'])

4. Save the configuration changes.

   Use the following command example to save your configuration changes:

   AdminConfig.save()

Related

Start the wsadmin scripting client using wsadmin.sh
Configure application startup
Use the wsadmin scripting AdminConfig object for scripted administration

Reference:

Commands for the AdminConfig object using wsadmin.sh

+

Search Tips   |   Advanced Search