Configuration documents

 

WAS stores configuration data for servers in a directory tree of XML files.

At the top of the hierarchy is the cells directory, which contains a subdirectory for each cell. The subdirectories under each cell contain the entire set of documents for every node and server throughout the cell.

Each cell subdirectory has the following files and subdirectories...

cell.xml	Configuration data for the cell
security.xml virtualhosts.xml resources.xml variables.xml	Configuration data that applies across every node in the cell
clusters subdirectory	Holds a subdirectory for each cluster defined in the cell. Each cluster subdirectory holds a cluster.xml file, which provides configuration data specifically for that cluster.
nodes subdirectory	Holds a subdirectory for each node in the cell.
server subdirectory	Holds a subdirectory for each server in the cell. Each server subdirectory holds a server.xml file, which provides configuration data specific to that server.
applications subdirectory	Holds a subdirectory for each application deployed in the cell. Each deployed application subdirectory holds a deployment.xml, .war and .jar files, and a META-INF subdirectory.

An example file structure is as follows...

cells
  cell1
     cell.xml resources.xml virtualhosts.xml variables.xml security.xml
     nodes
        nodeX
           node.xml variables.xml resources.xml serverindex.xml
           serverA
              server.xml variables.xml
           nodeAgent
              server.xml variables.xml
        nodeY
           node.xml variables.xml resources.xml serverindex.xml
     applications
        sampleApp1
           deployment.xml
           META-INF
              application.xml ibm-application-ext.xml ibm-application-bnd.xml
        sampleApp2
           deployment.xml
           META-INF
              application.xml ibm-application-ext.xml ibm-application-bnd.xml

 

---

Configuration Files

Configuration files that edit manually have an X in the Manual editing required column in the table below.

Configuration file	Purpose	Manual editing required
config/cells/cell/admin-authz.xml	Role for administrative operation authorization.	Yes
config/cells/cell/nodes/node/app.policy	Security permissions for application code.	Yes
config/cells/cell/cell.xml	Identify a cell.
config/cells/cell/clusters/cluster_name/cluster.xml	Identify a cluster and its members and weights.
config/cells/cell/applications/appname/deployment.xml	Application deployment settings.
config/cells/cell/filter.policy	Security permissions to be filtered out of other policy files.	Yes
config/cells/cell/integral-jms-authorizations.xml	Security configuration data for integrated messaging.	Yes
config/cells/cell/nodes/node/library.policy	Security permissions for shared libraries.	Yes
config/cells/cell/multibroker.xml	Data replication message broker.
config/cells/cell/namestore.xml	Persistent name binding data.	Yes
config/cells/cell/naming-authz.xml	Roles for a naming operation authorization.	Yes
config/cells/cell/nodes/node/node.xml	Identify a node.
config/cells/cell/pmirm.xml	PMI request metrics.	Yes
config/cells/cell/resources.xml config/cells/cell/nodes/node/resources.xml config/cells/cell/nodes/node/servers/server/resources.xml	Environment resources, including JDBC, JMS, JavaMail, URL, JCA resource providers and factories.
config/cells/cell/security.xml	Security, including all user ID and password data.
config/cells/cell/nodes/node/servers/server/server.xml	Identify a server and its components.
config/cells/cell/nodes/node/serverindex.xml	Communication ports used on a specific node.
config/cells/cell/nodes/node/spi.policy	Security permissions for service provider libraries such as resource providers.	Yes
config/cells/cell/variables.xml config/cells/cell/nodes/node/ config/cells/cell/nodes/node/servers/server/	Variables used to parameterize configuration settings.
config/cells/cell/virtualhosts.xml	Virtual host and MIME types.