Network Deployment (Distributed operating systems), v8.0 > Set up the application serving environment
Work with server configuration files
This topic show how to manage application server configuration files.
Application server configuration files define the available application servers, their configurations, and their contents.A configuration repository stores configuration data.
By default, configuration repositories reside in the config subdirectory of the profile root directory. Do not store any non-default XML or XML backup files under the $PROFILE_ROOT/config directory. Limit the config directory and subdirectories to valid default WAS 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 dmgr. The deployment manager and each node have their own repositories. A node-level repository stores configuration data that is 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 your administrative configuration. We can change the default locations of configuration files, as needed.
Procedure
- Edit configuration files.
The master repository is comprised of .xml configuration files We can edit configuration files , scripting, wsadmin commands, programming, or by editing a configuration file directly.
- Save changes made to configuration files. Using the console, you can save changes as follows:
- In the navigation select System Administration > Save changes to master repository.
- 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.
Related
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 restore administrative configuration files
Server configuration files: Resources for learning
Remote files services for file transfer and file synchronization
Hardening security configurations
Use the administrative console
Get started with wsadmin scripting
Use command-line tools
Use administrative programs (JMX)