Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Administer applications using wsadmin.sh

Delete business-level applications using wsadmin.sh

We can use wsadmin.sh to remove business-level applications from the environment. Deleting a business-level application removes the application from the product configuration repository and it deletes the application binaries from the file system of all nodes where the application files are installed.

This topic assumes that a business-level applications exists in the configuration, and to delete the application.

There are two ways to complete this task. This topic uses the commands in the BLAManagement command group for the AdminTask object to remove business-level applications from the configuration. Alternatively, you can use the scripts in the AdminBLA script library to configure, administer, and remove business-level applications

Procedure

1. Start wsadmin.sh.

2. Verify that the business-level application is ready to be deleted.

   Before deleting a business-level application, use the deleteCompUnit command to remove each configuration unit that is associated with the business-level application. Also, verify that no other business-level applications reference the business-level application to delete.

   Use the following example to delete a composition unit, compositionUnit1, from a business-level application, myBLA:

   AdminTask.deleteCompUnit('-blaID myBLA –cuID compositionUnit1')
   

   Repeat this step for each composition unit that is associated with the business-level application of interest.

3. Delete the business-level application.

   Use the deleteBLA command to remove a business-level application from the configuration:

   AdminTask.deleteBLA('-blaID myBLA')
   

   If the system successfully deletes the business-level application, the command returns the configuration ID of the deleted business-level application; for example:

   WebSphere:blaname=myBLA
   

4. Save the configuration changes.

   Save the configuration changes:

   AdminConfig.save()
   

5. Synchronize the node.

   Use the syncActiveNodes script in the AdminNodeManagement script library to propagate the changes to each active node; for example:

   AdminNodeManagement.syncActiveNodes()
   

Example

Example: Create an SCA business-level application with scripting describes how to create the HelloWorldAsync business-level application. You can delete this application using wsadmin in the Jython scripting language.

1. Start wsadmin.sh.
2. Stop the HelloWorldAsync business-level application.

   AdminTask.stopBLA('-blaID WebSphere:appName=HelloWorldAsync')
   

3. Delete the helloworldws composition unit associated with the HelloWorldAsync.

   AdminTask.deleteCompUnit('-blaID HelloWorldAsync -cuID helloworldws')
   

4. Delete the HelloWorldAsync application.

   AdminTask.deleteBLA('-blaID HelloWorldAsync')
   

5. Optionally, delete the helloworld-ws-asynch.jar asset from the asset repository.

   AdminTask.deleteAsset('-assetID helloworld-ws-asynch.jar')
   

6. Save the configuration changes.

   AdminConfig.save()
   

7. Exit the wsadmin command shell.

   exit
   

Automate business-level application configuration
Set up business-level applications using wsadmin.sh
Install enterprise applications using wsadmin.sh
Create business-level applications
Example: Create an SCA business-level application with scripting

Related

BLAManagement command group using wsadmin.sh
Business-level application configuration scripts

+

Search Tips   |   Advanced Search