Work with server configuration files
Application server configuration files define the available application servers, their configurations, and their contents.
By default, configuration repositories reside in...
Do NOT store any non-default XML or XML backup files under profile_root/config.
Limit the config directory and subdirectories to valid default WebSphere Application Server configuration files. A variety of symptoms and exceptions are possible if non-default files are stored in this directory.
A cell-level repository stores configuration data for the entire cell and is managed by a file repository service that runs in the deployment manager. The deployment manager and each node have their own repositories. A node-level repository stores configuration data needed by processes on that node and is accessed by the node agent and application servers on that node.
When you change a WAS configuration by creating an application server, installing an application, changing a variable definition or the like, and then save the changes, the cell-level repository is updated. The file synchronization service distributes the changes to the appropriate nodes.
You should periodically save changes to the administrative configuration. We can change the default locations of configuration files, as needed.
- Edit configuration files.
The master repository is comprised of .xml configuration files
We can edit configuration files using the administrative console, scripting, wsadmin commands, programming, or by editing a configuration file directly.
- Save changes made to configuration files. Using the console, we can save changes as follows:
- Save changes made to configuration files. Using the console, we can save changes...
System Administration | Save changes to master repository | Save
- Put a check mark in the Synchronize changes with Nodes check box.
- Click Save.
- Handle temporary configuration files resulting from a session timing out.
- Change the location of temporary configuration files.
- Change the location of backed-up configuration files.
- Change the location of temporary workspace files.
- Back up and restore configurations.
- Configuration documents
- Configuration document descriptions
- Object names: What the name string cannot contain
- Handle temporary configuration files resulting from session timeout
- Change the location of temporary configuration files Change the location of backed-up configuration files
- Change the location of the wstemp temporary workspace directory
- Back up and restoring administrative configuration files
- (iseries) Backup and recover administrative configurations
- (zos) Back up the WAS for z/OS system
- Server configuration files: Resources for learning
- Configuration problem settings
Remote files services for file transfer and file synchronization
Related tasksHardening security configurations
Use the administrative console Get started with wsadmin scripting Use command-line tools Use administrative programs (JMX)