Change the location of temporary workspace files
Overview
Configuration changes are stored in temporary workspace files until the changes are merged with the master configuration repository. This topic discusses how to change the location of the temporary workspace files.
You must first install WAS before you change the location of temporary workspace files.
Whenever a user logs into the console, or uses wsadmin scripting to make a configuration change, the changes are stored in the workspace. When a user uses the ConfigService configuration service interface of the Java APIs, the user specifies a session object that is associated with the workspace in order to store the changes. Only when the user performs a save operation under the console, wsadmin scripting, or the Java APIs are the changes propagated and merged with the master configuration repository. For each console user or each invocation of wsadmin scripting, the appserver creates a separate workspace directory to store the intermediate changes until the changes are merged with the master configuration repository. Users of the Java APIs use different session objects to decide where the workspace files reside. Both the console and wsadmin scripting generate user IDs randomly. The user IDs are different from the user IDs that you use to log into the console or wsadmin scripting. The Java APIs can either randomly generate the user ID or specify the user ID as an option when creating the session object.
You might want to change the location of temporary workspace files if you want to keep them in a separate place from the product installation. WAS determines the location of the workspace in the following order by using the first JVM property in the list that is set. If no JVM property is set, the product uses the default workspace location.
JVM Property Location Comments workspace.root value of the workspace.root JVM property, irrespective of the user ID Do not set this property as it is meant for a single user environment. workspace.user.root value of the workspace.user.root JVM property/user_id/workspace Set the system property for the deployment manager to change the respective workspace locations.
websphere.workspace.root value of the websphere.workspace.root JVM property/user_id/workspace Set the system property for the deployment manager to change the respective workspace locations.
None of the workspace properties is set. The default workspace location is value of the user.install.root JVM property/wstemp/user_id/workspace.
Procedure
- Change the workspace location for a particular JVM property by setting the -D option on the java command.
This method of changing the workspace location is only needed when you run a standalone administrative program in local mode. For example, use the following option:
-Dworkspace.user.root=the location of the new workspace directory
- Change the JVM custom property through the console by setting the JVM property as a name-value pair on the Custom properties page. For example,
Click Deployment Manager > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties.
- Click New.
Specify workspace.user.root as the name.
Specify the location of the new workspace directory as the value.
Results
You have used either the console or the -D option on the java command to change the location of temporary workspace files.
Work with server configuration files