After an application no longer is needed,
you can delete
it.
About this task
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.
Procedure
- Go to the Business-level
applications page.
Click in the console navigation tree.
- If you need to retain a copy of the application,
back up
composition units of the application.
- Delete
composition units of the application.
- On
the Business-level applications page,
click the name of the business-level application that you want to
delete.
- On the business-level application
settings page, delete
each composition unit of the application. Deployed assets
and business-level applications can be composition units of a business-level
application.
Select one or more composition units and
click Delete.
newfeatFor Service Component Architecture (SCA) business-level
applications that use an OSGi implementation in an enterprise bundle
archive (EBA) composition unit, delete the SCA composition unit before
attempting to delete the EBA composition unit, otherwise the product
returns an error. An EBA composition unit that is used for the implementation
cannot be deleted until the SCA composition unit that uses the implementation.osgiapp is
deleted.
- On the Delete
composition unit from Business-level
application page, confirm the deletion and click OK.
- Repeat steps b and c until the business-level
application
that you want to delete has no more composition units.
Deleting a composition unit removes the configuration
from the profile_root/config/cells/cell_name/cus directory.
- Delete the business-level application.
- Select the application that you want to delete.
- Click Delete.
Unless the application is used by
another business-level
application, deleting a business-level application removes the configuration
from the profile_root/config/cells/cell_name/blas directory.
- On the Delete business-level application page,
confirm the deletion and click OK.
- Save changes made to the administrative configuration.
Results
On single-server products, application binaries
are deleted
after you save the changes.
Example
Example: Creating an SCA business-level application with the console describes
how to create the HelloWorldAsync business-level application. You
can delete this application using the console.
- Go
to the Business-level applications page
and, if HelloWorldAsync is running, change its status to Stopped.
- Click .
- Select HelloWorldAsync.
- Click Stop.
- Go to the business-level applications settings page
for HelloWorldAsync
and delete the helloworldws composition unit.
- Click .
- From Deployed
assets, select helloworldws.
- Click Delete.
- On the Delete composition unit from Business-level application page,
confirm the deletion and click OK.
- Click
the Save link to save the changes.
- From the business-level applications page, delete the HelloWorldAsync
application.
- Click .
- Select HelloWorldAsync.
- Click Delete.
- On the Delete business-level application page,
click OK.
- Click the Save link
to save the changes.
- Optionally, from the Assets page,
delete
the helloworld-ws-asynch.jar asset from the asset repository.
- Click .
- Select
helloworld-ws-asynch.jar.
- Click Delete.
- On the Delete asset page, click OK.
- Click the Save link to save the changes.
What to do next
If using the administrative console Delete options
does not fully delete a business-level application or its composition
units, you can delete the business-level application and its composition
units manually from a stand-alone
server. Suppose you want to delete a business-level application named ExampleBLA,
and ExampleBLA is not used by another business-level
application. Complete the following steps to manually delete the ExampleBLA configurations
from the blas and cus directories:
- Delete the profile_root/config/cells/cell_name/blas/ExampleBLA directory.
- Delete the profile_root/config/cells/cell_name/cus/ExampleBLA directory.
- Save changes made to the administrative configuration.