Working with server configuration files

This page show how to manage appserver 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 /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.

nov2010

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 appservers on that node.

When you change a WAS configuration by creating an appserver, 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 admin configuration. You can change the default locations of configuration files, as needed.

 

• Edit configuration files.

  The master repository is comprised of

  . We can edit configuration files using the admin 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:

  1. In the navigation select System Administration > Save changes to master repository.

  2. Put a check mark in the Synchronize changes with Nodes check box.

  3. 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.

---

Subtopics Configuration documents Configuration document descriptions Object names: What the name string cannot contain Handling 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 Backing up and restoring admin configuration files Server configuration files: Links Related concepts Remote files services for file transfer and file synchronization

   

---

Last updated Nov 10, 2010 8:23:07 PM CST