Technical data

Domain Restrictions
Configuring and Managing WebLogic Server 2-7
Domain Restrictions
Many WebLogic Server installations consist of a single domain that includes all the
Managed Servers required to host applications. If you create more than one domain,
note the following restrictions:
! Each domain requires its own Administration Server for performing
management activities. When you are using the Administration Console to
perform management and monitoring tasks, you can switch back and forth
between domains, but in doing so, you are connecting to different
Administration Servers.
! All Managed Servers in a cluster must reside in the same domain; you cannot
“split” a cluster over multiple domains.
! You cannot share a configured resource or subsystem between domains. For
example, if you create a JDBC connection pool in one domain, you cannot use it
with a Managed Server or cluster in another domain. (Instead, you must create a
similar connection pool in the second domain.)
Domain Directory and config.xml
The configuration of a domain is stored in the config.xml file for the domain.
config.xml specifies the name of the domain and the configuration parameter
settings for each server instance, cluster, resource, and service in the domain. The
config.xml for a domain is stored in the domain directory, which you specify when
you create the domain.
The domain directory also contains default script files that you can use to start the
Administration Server and Managed Servers in the domain. For more information
about these scripts and other methods of starting a server instance, see “Starting and
Stopping WebLogic Server.