The server1 template server.xml file has been updated in
WebSphere Application Server V5.0.2.5 and later releases of WebSphere
Application Server.
Before creating a new application server and enabling the audit, check
for a missing entry for
<configRepository xmi:id="RespositoryService_1"/> in the server1
template server.xml file.
You can resolve this problem by manually adding the line:
<configRepository xmi:id="RepositoryService_1"/>
in the Base and Network Deployment server1 template server.xml file. This
file is located in two places:
-
WAS_BASE_HOME\config\templates\default\nodes\servers\server1\server.xml
-
WAS_ND_HOME\config\templates\default\nodes\servers\server1\server.xml
Following is an example of WebSphere Application Server server.xml
without the <configRepository> tag:
< services
xmi:type="adminservice:AdminService" xmi:id="AdminService_1"
enable="true" standalone="false"
preferredConnector="SOAPConnector_1">
<connectors xmi:type="adminservice:SOAPConnector"
xmi:id="SOAPConnector_1">
<properties xmi:id="Property_7" name="sslConfig"
value="fstuka/DefaultSSLSettings"/> <properties xmi:id="Property_8"
name="requestTimeout" value="600"/>
</connectors>
<connectors xmi:type="adminservice:RMIConnector"
xmi:id="RMIConnector_1"/>
</services>
Following is an example of WebSphere Application Server server.xml
with the <configRepository> tag:
<services
xmi:type="adminservice:AdminService" xmi:id="AdminService_1" enable="true"
standalone="false" preferredConnector="SOAPConnector_1">
<connectors xmi:type="adminservice:SOAPConnector"
xmi:id="SOAPConnector_1">
<properties xmi:id="Property_7" name="sslConfig"
value="fstuka/DefaultSSLSettings"/>
<properties xmi:id="Property_8" name="requestTimeout"
value="600"/>
</connectors>
<connectors xmi:type="adminservice:RMIConnector"
xmi:id="RMIConnector_1"/>
<configRepository xmi:id="RepositoryService_1"/>
</services>
|