Network Deployment (Distributed operating systems), v8.0 > Reference > Sets


Configuration document descriptions

Most configuration documents have XML content. The table describes the documents and states whether you can edit them using an administrative tool or must edit them directly.

If possible, edit a configuration document using the administrative console because it validates changes made to configurations. We can also use one of the other administrative tools (wsadmin or Java APIs) to modify configuration documents. Using the admin console or wsadmin scripting to update configurations is less error prone and likely quicker and easier than other methods.

However, you cannot edit some files using the administrative tools. Configuration files that edit manually have an X in the Manual editing required column in the table below.


Document descriptions

(The paths in the Locations column are split on multiple lines for publishing purposes.)

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 WAS ND.

 
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.

Use wsadmin scripting
Use the administrative console
Use administrative programs (JMX)

+

Search Tips   |   Advanced Search