![[Note]](images.admon/note.gif)
Config XML data
WebSphere Application Server's configuration data is stored in XML files. Knowing the structure and the content of these files is useful when it comes to understanding how the system operates.
In a Network Deployment environment, master copies of the xml files are stored in the cell repository on the deployment manager node. The master files overwrite local files on each node in a cell.
The config files are stored in the config directory for the specific profile defined for the
WebSphere Application Server under the product installation directory. For example, the config files for a
Deployment Manager profile are stored in /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/.
Within this directory is a specific WAS subdirectory hierarchy. At the top of the hierarchy is the
cells directory, followed by the nodes, and then the servers directory.
For example, an Application Server with a Deployment Manager profile, Dmgr01,
having a subdirectory hierarchy of cell, test317Cell01, node, test317CellManager01,
and server, dmgr, can be shown as:
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/test317CellManager01/servers/dmgr/
Important config files:
server.xmlThe
server.xmlis the only required XML config file. In a cell configuration, each node directory contains a subdirectory for each server defined on the node. The subdirectory names match the server names. Aserver.xmlfile is always contained in this directory and it provides the configuration data specific to that server. It contains Host, Cell, Node, and AppServer data.test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/test317CellManager01/servers/dmgr # ls -l server.xml -rwxr-xr-x 1 root root 24135 May 21 08:45 server.xml
When there are more that one servers, the
server.xmlfile resides under the appropriate server folder.test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/exampleNode01/servers/server1 # ls -l server.xml -rw-r--r-- 1 root root 34106 Jun 1 15:58 server.xml
serverindex.xmlIn the WAS Deployment Manager profile, each node subdirectory contains a
serverindex.xmlfile. This file contains information about the network ports (e.g.SOAP_CONNECTOR_ADDRESS, etc.).test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/test317CellManager01 # ls -l serverindex.xml -rwxr-xr-x 1 root root 2933 May 21 08:45 serverindex.xml
test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/test317CellManager01 # cat serverindex.xml <?xml version="1.0" encoding="UTF-8"?> <serverindex:ServerIndex xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:serverindex="http://www.ibm.com/websphere/appserver/schemas/5.0/serverindex.xmi" xmi:id="ServerIndex_1" hostName="test317.java.boot.by" endPointRefs="NamedEndPoint_1 NamedEndPoint_2"> <serverEntries xmi:id="ServerEntry_1" serverDisplayName="dmgr" serverName="dmgr" serverType="DEPLOYMENT_MANAGER"> <deployedApplications>WebSphereWSDM.ear/deployments/WebSphereWSDM</deployedApplications> <deployedApplications>isclite.ear/deployments/isclite</deployedApplications> <deployedApplications>OTiS.ear/deployments/OTiS</deployedApplications> <specialEndpoints xmi:id="NamedEndPoint_1" endPointName="CELL_DISCOVERY_ADDRESS"> <endPoint xmi:id="EndPoint_1" host="test317.java.boot.by" port="7277"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_2" endPointName="BOOTSTRAP_ADDRESS"> <endPoint xmi:id="EndPoint_2" host="test317.java.boot.by" port="9809"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_3" endPointName="IPC_CONNECTOR_ADDRESS"> <endPoint xmi:id="EndPoint_3" host="${LOCALHOST_NAME}" port="9632"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_4" endPointName="SOAP_CONNECTOR_ADDRESS"> <endPoint xmi:id="EndPoint_4" host="test317.java.boot.by" port="8879"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_5" endPointName="ORB_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_5" host="test317.java.boot.by" port="9101"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_6" endPointName="SAS_SSL_SERVERAUTH_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_6" host="test317.java.boot.by" port="9405"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_7" endPointName="CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_7" host="test317.java.boot.by" port="9406"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_8" endPointName="CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS"> <endPoint xmi:id="EndPoint_8" host="test317.java.boot.by" port="9404"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_9" endPointName="WC_adminhost"> <endPoint xmi:id="EndPoint_9" host="*" port="9061"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_10" endPointName="WC_adminhost_secure"> <endPoint xmi:id="EndPoint_10" host="*" port="9044"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_11" endPointName="DCS_UNICAST_ADDRESS"> <endPoint xmi:id="EndPoint_11" host="*" port="9352"/> </specialEndpoints> <specialEndpoints xmi:id="NamedEndPoint_DPMGR1" endPointName="DataPowerMgr_inbound_secure"> <endPoint xmi:id="EndPoint_DPMGR1" host="*" port="5555"/> </specialEndpoints> </serverEntries> </serverindex:ServerIndex>nodegroup.xmlThis file contains information about Nodes in specific Node Group inside a specific Cell. Each Node Group has its own
nodegroup.xmlfile and is stored in the Deployment Manager's profile under its own directory.test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodegroups/DefaultNodeGroup # ls -l nodegroup.xml -rwxr-xr-x 1 root root 519 Jun 1 15:58 nodegroup.xml
test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodegroups/DefaultNodeGroup # cat nodegroup.xml <?xml version="1.0" encoding="UTF-8"?> <topology.nodegroup:NodeGroup xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:topology.nodegroup="http://www.ibm.com/websphere/appserver/schemas/6.0/topology.nodegroup.xmi" xmi:id="builtin_DefaultNodeGroup" name="DefaultNodeGroup" description="WebSphere Default Node Group."> <members xmi:id="NodeGroupMember_1073317248558" nodeName="test317CellManager01"/> <members xmi:id="NodeGroupMember_1370116581082" nodeName="exampleNode01"/> </topology.nodegroup:NodeGroup>
cluster.xmlThe
cluster.xmlfile provides configuration data specific to that cluster. Each cluster has its owncluster.xmland is stored under its own directory under a Deployment Manager's profile. The file contains information about the servers residing in that cluster within a particular cell.node-metadata.propertiesThe
node-metadata.propertiesfiles contain information about an Application Server's WAS version and the Operating System on which it runs. The file exists at node level.test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/test317CellManager01 # ls -l node-metadata.properties -rwxr-xr-x 1 root root 1400 May 21 08:46 node-metadata.properties
test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/test317CellManager01 # cat node-metadata.properties #Tue May 21 08:44:32 EDT 2013 com.ibm.websphere.sdk.architecture.1.6_64=x86_64 com.ibm.websphere.baseProductShortName=ND com.ibm.websphere.sdk.version.1.6_64=1.6 com.ibm.websphere.baseProductVersion=8.0.0.4 com.ibm.websphere.sdk.platform.1.6_64=linux com.ibm.websphere.sdk.location.1.6_64=${WAS_INSTALL_ROOT}/java com.ibm.websphere.baseRuntimeComponents=WebSphere\:specName\=WS_UDDIRuntime;WebSphere\:specName\=WS_ActivitySession;WebSphere\: specName\=WS_EJBContainer;WebSphere\:specName\=WS_JaxRpcWebService;WebSphere\:specName\=WS_PortletContainer;WebSphere\: specName\=WS_SipContainer;WebSphere\:specName\=WS_AppProfile;WebSphere\:specName\=WS_WebContainer;WebSphere\: specName\=WS_WebServiceInit;WebSphere\:specName\=WS_JSF;WebSphere\:specName\=WS_StartupService;WebSphere\: specName\=WS_JaxWsWebService;WebSphere\:specName\=WS_Compensation;WebSphere\:specName\=WS_Dynacache_servlet;WebSphere\:specName\=WS_WSBA com.ibm.websphere.deployed.features=com.ibm.ws.express_6.0.0.0,com.ibm.ws.batch_1.0.0.0,com.ibm.ws.j2ee_6.0.0.0,com.ibm.ws.uddi_6.0.0.0, com.ibm.ws.osgi.applications_1.1.0.0,com.ibm.ws.nd_6.0.0.0,com.ibm.ws.cim_7.0.0.0,com.ibm.ws.base_6.0.0.0,com.ibm.ws.wsgateway_6.0.0.0 com.ibm.websphere.nodeOperatingSystem=linux com.ibm.websphere.installed.products=ND_8.0.0.4 com.ibm.websphere.sdk.nativeLibPath.1.6_64=${WAS_INSTALL_ROOT}/lib/native/linux/x86_64/ com.ibm.websphere.sdk.bits.1.6_64=64security.xmlThe
security.xmlfile is stored under the Deployment Manager's profile and contains information about the security settings for a particular cell. The configuration data applies to each node in the cell.test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01 # ls -l security.xml -rwxr-xr-x 1 root root 46534 Jul 1 08:22 security.xml
fileRegistry.xmlThe
fileRegistry.xmlfile is stored under the Deployment Manager's profile and contains a repository of users of a particular cell.pmi-config.xmlThe
pmi-config.xmlfile contains information about the Performance Monitoring Infrastructure (PMI) settings of a particular Application Server or Node Agent in the WAS environment.test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/exampleNode01/servers/server1 # ls -l pmi-config.xml -rw-r--r-- 1 root root 8870 Jun 1 15:58 pmi-config.xml
Master copies of all
pmi-config.xmlfiles are stored under the Deployment Manager's profile.There is no
pmi-config.xmlfor a Deployment Manager server.
