Weblogic - CONFIGURATION BASICSAt the heart of WebLogic Server is the configuration file config.xml. This file contains configuration information about the entire WebLogic Server domain. Figure 1-13 demonstrates the information recorded within config.xml. The config.xml file is made up of numerous XML elements, each describing various aspects of the WebLogic Server domain. Configuration information related to various J2EE components, such as JSPs, servlets, EJBs, JDBC connections, JMS, JTA, JNDI, and so forth, is stored in this file. You can manipulate config.xml manually by using your favorite editor and check the reflection in the behavior of the configured components when you run the server. You can also use the WebLogic Administration Console to manipulate various parameters related to the WebLogic applications or server, and later check config.xml for their updated values. Exercising this is handy and helps further understanding of the role of config.xml. Following is a sample config.xml file: Sample config.xml
<?xml version="1.0" encoding="UTF-8" ?> <!--If your domain is active,
please do not edit the config.xml file. Any changes made to that file while the domain is active will not have any effect on the domain's configuration and are likely to be lost. If your domain is inactive, you may edit this file with an XML editor. If you do so, please refer to the BEA WebLogic Server Configuration Reference documentation available from http://edocs.bea.com/wls/docs61/reference.html. In general, we recommend that changes to your configuration file be made through the Administration Console.--> <Domain Name="mydomain"> <Application Deployed="true" Name="DefaultWebApp" Path=".\applications" TwoPhase="false"> <WebAppComponent Name="DefaultWebApp" Targets="myserver" URI="DefaultWebApp" /> </Application> <Application Deployed="true" Name="certificate" Path=".\applications" TwoPhase="false"> <WebAppComponent Name="certificate" Targets="myserver" URI="certificate.war" /> </Application> <ApplicationManager Name="mydomain" /> <FileRealm Name="wl_default_file_realm" /> <JTA Name="mydomain" /> <Log FileName=".\wl-domain.log" Name="mydomain" /> <PasswordPolicy Name="wl_default_password_policy" /> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm" /> <SNMPAgent Name="mydomain" /> <Security GuestDisabled="false" Name="mydomain" PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm" RealmSetup="true" /> <SecurityConfiguration Credential= "{3DES}3WOUyKIzNNk3WJRlIpgHtfjs 57CUC3t2cXoeQqSzH1w4G4V/jhBQAn v8jQNAwV2sOwz2IXE7d5B34d05T08j 0f5SwTzS9xBH" Name="mydomain" /> <Server ListenPort="7001" Name="myserver" NativeIOEnabled="true" ServerVersion="7.0.0.0"> <COM Name="myserver" /> <ExecuteQueue Name="default" ThreadCount="15" /> <JTAMigratableTarget Cluster="" Name="myserver" UserPreferredServer="myserver" /> <KernelDebug Name="myserver" /> <Log FileName=".\myserver\myserver.log" Name="myserver" /> <SSL Enabled="true" ListenPort="7002" Name="myserver" ServerCertificateChainFileName="ca.pem" ServerCertificateFileName="democert.pem" ServerKeyFileName="demokey.pem" /> <ServerDebug Name="myserver" /> <ServerStart Name="myserver" /> <SystemDataStore Credential= "{3DES}+cGRcNRxlWhCRWY+Gd1dL3rO ZqEUWe+bfKIIIfJStns=" Name="myserver" /> <WebServer DefaultWebApp="DefaultWebApp" LogFileName=".\myserver\access.log" LoggingEnabled="true" Name="myserver" /> </Server> </Domain> |