WebSphere Configuration Files

Posted By Sagar Patil

Application server configuration files define the available application servers, their configurations, and their contents.

A configuration repository stores configuration data.  Configuration repositories reside in the config subdirectory of the profile root 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 that is needed by processes on that node and is accessed by the node agent and application servers on that node.

The master repository is comprised of following .xml configuration files

Configuration file Locations Purpose Manual editing required
admin-authz.xml
config/cells/
cell_name/
Define a role for administrative operation authorization.
app.policy
config/cells/
cell_name/
nodes/node_name/
Define security permissions for application code. X
cell.xml
config/cells/
cell_name/
Identify a cell.
cluster.xml
config/cells/
cell_name/
clusters/
cluster_name/
Identify a cluster and its members and weights.This file is only available with the Network Deployment product.
deployment.xml
config/cells/
cell_name/
applications/
application_name/
Configure application deployment settings such as target servers and application-specific server configuration.
filter.policy
config/cells/
cell_name/
Specify security permissions to be filtered out of other policy files. X
integral-jms-authorizations.xml
config/cells/
cell_name/
Provide security configuration data for the integrated messaging system. X
library.policy
config/cells/
cell_name/
nodes/node_name/
Define security permissions for shared library code. X
multibroker.xml
config/cells/
cell_name/
Configure a data replication message broker.
namestore.xml
config/cells/
cell_name/
Provide persistent name binding data. X
naming-authz.xml
config/cells/
cell_name/
Define roles for a naming operation authorization. X
node.xml
config/cells/
cell_name/
nodes/node_name/
Identify a node.
pmirm.xml
config/cells/
cell_name/
Configure PMI request metrics X
resources.xml
config/cells/
cell_name/
config/cells/
cell_name/
nodes/node_name/

config/cells/
cell_name/
nodes/node_name/
servers/
server_name/

Define operating environment resources, including JDBC, JMS, JavaMail, URL, JCA resource providers and factories.
security.xml
config/cells/
cell_name/
Configure security, including all user ID and password data.
server.xml
config/cells/
cell_name/
nodes/
node_name/
servers/
server_name/
Identify a server and its components.
serverindex.xml
config/cells/
cell_name/
nodes/
node_name/
Specify communication ports used on a specific node.
spi.policy
config/cells/
cell_name/
nodes/
node_name/
Define security permissions for service provider libraries such as resource providers. X
variables.xml
config/cells/
cell_name/
config/cells/
cell_name/
nodes/
node_name/
 config/cells/
cell_name/
nodes/node_name/
servers/
server_name/
Configure variables used to parameterize any part of the configuration settings.
virtualhosts.xml
config/cells/
cell_name/
Configure a virtual host and its MIME types.

You can edit configuration files using the administrative console, scripting, wsadmin commands, programming, or by editing a configuration file directly.

Leave a Reply

You must be logged in to post a comment.

Top of Page

Top menu