user manual

Converting the weblogic.properties File to XML Files
BEA WebLogic Server 7.0 Upgrade Guide 2-7
Note: The conversion utility described above specifies the Java home location in the
weblogic.xml file. It reads this location using the
System.getProperty(java.home), which means that it will specify the
Java home location on which WebLogic Server was started for the conversion.
 It is strongly recommended that you not edit the config.xml file directly.
Access the configuration through the Administration Console, a command line
utility, or programmatically through the configuration API. For details on
configuring WebLogic Server Web Components, see Configuring WebLogic
Server Web Components in the Administration Guide.
 Security properties are stored in the fileRealm.properties file located in
domain. For information about using a security realms in WebLogic Server 7.0,
see Customizing the Default Security Configuration.
 The weblogic.common.ConfigServicesDef API, which provided methods to
get properties out of the
weblogic.properties file, has been removed from
this version.
For more procedures for converting your
weblogic.properties file, see the Console
Help documentation.
For a list of which
config.xml, web.xml, or weblogic.xml attribute handles the
function formerly performed by
weblogic.properties properties, see “The
weblogic.properties Mapping Table”.
The startup scripts, which are generated when a
weblogic.properties file is
converted, are named:
z startdomainName.cmd (for Windows users)
z startdomainName.sh (for UNIX users)
where
domainName is the name of your domain directory.
These scripts exist under the
domain directory in your WebLogic Server 7.0
distribution and start the administration server in the new domain.
See Starting and Stopping WebLogic Servers in the Administration Guide for more
information on scripts and starting servers.