../E24215-14.epub /> ../E24215-14.mobi />
This chapter answers frequently asked questions regarding Application Dependency and Performance.
This chapter includes the following sections:
In general, you should not erase the darchive directory while the ADP manager is running. If you erase the darchive directory after shutting down the ADP manager, the darchive directory will be re-populated when the ADP manager next restarts.
If the size of the darchive directory is of concern, determine which subdirectories are occupying the most space. If there are large directories that do not contain Java class files (for example ., .., or wlserver10.3), modify the Acsera.properties file to exclude them. Search for Model.StaticAnalysis.ExcludeClassPaths and add the path to the list, separated by comma.
The darchive directory is located under $ACSERA_HOME:
There is a drop-down menu in the last step in the deployment process that, by default, is set to deploy. Change it to disable to remove the agent startup arguments from the application servers, and to remove to erase the agent files from the application servers.
Note:On some platforms, for example Windows, you need to restart the application servers before the Remove command can be run. Otherwise the Remove command may run into File Still In Use errors.
To undeploy the agent, follow these steps:
From the Targets menu, select Middleware, then select Middleware Features (drop-down list). Select Application Dependency and Performance.
Click the Configuration tab.