wstemp stands for “workspace temporary directory” and is a directory located at ${WAS_INSTALL_ROOT}/profiles/your_profile/wstemp. When you make a change to the Master Configuration, files are temporarily stored in the wstemp directory. A large number of changes to the Master Configuration can cause the wstemp directory to use up too much disk space. If the wstemp directory is using up too much disk space, you'll want to first stop the WebSphere server, so that no new files get written to the wstemp directory.

Then, create a backup of each profile, so that you can restore the profile if the removal of files from the wstemp directory causes some unexpected problem. On a Linux system, this can be done using the tar command.

tar -cf /path/to/example.tar ${WAS_INSTALL_ROOT}/profiles/your_profile

Be aware that the wstemp directory will contain one or more prefs.xml files, one for each user that has signed into the Integrated Solutions Console (ISC). If a user has modified their console preferences, the removal of prefs.xml will return the users console preferences back to default. You may want to retain the prefs.xml files so that you can restore each users console preferences. Or, users can reset their console preferences.

cd ${WAS_INSTALL_ROOT}/profiles/your_profile
rm -rf wstemp/*

And then you can start the WebSphere server. Starting with an empty wstemp directory, a clean start of the dmgr will add these directories to the wstemp directory.

appmgmt
com.ibm.ws.wlm.clusterMgr
events

When you sign into the dmgr admin console, a directory with a random string of numbers will be created in wstemp, something like this. Their will be a unique string of numbers for each users that sign into the Integrated Solutions Console (ISC).

16383792982

If there is a directory that starts with a dash, use this command.

rm -rf ./-16383792982