Red Hat NETSCAPE DIRECTORY SERVER 6.01 - DEPLOYMENT Guide d'installation Page 125

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 143
  • Table des matières
  • DEPANNAGE
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 124
115
Chapter 25
Migrating from Pramati Server 3.0 to Pramati Server 4.1
New Server Configuration XMLs in Version 4.1
The server-config.xml in Version 3.0 has been split up into the following sub-configuration files:
server-config.xml for configuring the service information.
individual service config XMLs for configuring individual services.
Note: All types of Server nodes always run off server-config.xml instead of the earlier separate central
configurations. To recall, in Version 3.0 the embedded JMS server had emb-jms-config.xml, the cluster
node had cluster-config.xml as the central configuration stores.
New Service Configurators and other XMLs in Version 4.1
•deploy-config.xml
•jms-config.xml
•ejb-cache.xml
resource-config.xml
•web-config.xml
management-config.xml
•dashboard.xml
history-collector.xml
•alerts-config.xml
logging-config.xml
•web-cache.xml
•web-lbconfig.xml
New configuration tags in deploy-config.xml
Handling of RARs
connector-config.xml has been removed. The contents are now in pramati-j2ee-server.xml.
Table 10: Configuration tags in deploy-config XML
New Tag Purpose
<application-hooks> for per application hooks
<classloader-for-multiple-apps enabled="false"> for using single classloader for group of applications
<application-properties versioning-enabled="true"> for versioning of applications
<out-of-process-compilation enabled="false"> for out of the process compilation
<auto-deploy> the path of the auto deploy directory
<startup-hooks> for Server hooks
Vue de la page 124
1 2 ... 120 121 122 123 124 125 126 127 128 129 130 ... 142 143

Commentaires sur ces manuels

Pas de commentaire