Domains: Configuration: General
Configuration Options Advanced Configuration Options Related Tasks Related Topics
A domain is a collection of WebLogic Server instances that is managed by a single Administration Server. Use this page to configure administrative options that apply to all servers in the current domain.
Each WebLogic Server domain must have an Administration Server, which runs the Administration Console and distributes configuration changes to other servers in the domain. In a typical production environment, you add one or more Managed Servers to the domain to host business applications and use the Administration Server only to configure and monitor the Managed Servers.
Name Description Name
The name of this WebLogic Server domain.
Enable Administration Port
Specifies whether the domain-wide administration port should be enabled for this WebLogic Server domain. Because the administration port uses SSL, enabling the administration port requires that SSL must be configured for all servers in the domain.
The domain-wide administration port enables you to start a WebLogic Server instance in
STANDBYstate. It also allows you to separate administration traffic from application traffic in your domain. Because all servers in the domain must enable or disable the administration port at once, you configure the default administration port settings at the domain level.
If you enable the administration port:
The administration port accepts only connections that specify administrator credentials.
Connections that specify administrator credentials can use only the administration port.
The command that starts managed servers must specify a secure protocol and the administration port:
The common secure administration port for this WebLogic Server domain. (Requires you to enable the administration port.)
Specifies whether all servers in this domain run in production mode. Once enabled, this can only be disabled in the admin server startup command line.
Enable Cluster Constraints
Specifies that deployments targeted to a cluster succeed only if all servers in the cluster are running.
By default, cluster constraints are disabled and deployment is attempted only on the servers that are reachable at the time of deployment from the Administration Server. Any servers that have been shut down or are temporarily partitioned from the Administration Server will retrieve the deployment during server startup or shortly after the network partition is resolved.
Advanced Configuration Options
Name Description Console Enabled
Specifies whether the Administration Server automatically deploys the Administration Console in the current domain.
If the Administration Console is not deployed, you can still use the WebLogic Scripting Tool or the management APIs to configure and monitor the domain.
Console Context Path
The context path that you want to use in URLs that specify the Administration Console. (Requires you to enable the Administration Console for the current domain.)
To access the Administration Console, you use the following URL: http://listen-addess:listen-port/context-path. For example, if you set the context path to
myconsole, then you use the following URL to access the Administration Console:
To specify the listen address and listen port that you use to access the Administration Console, configure the listen address and listen port of the Administration Server.
Console Extension Directory
Returns the directory path that console extensions are loaded from.
Configuration Archive Enabled
If true, then backups of the configuration will be made during server boot.
Archive Configuration Count
The number of archival versions of config.xml saved by the Administration Server each time the domain configuration is modified.
The default protocol for communicating through the administration port or administration channels. (Requires you to enable the administration port or to create an administration channel.)
If requests through the administration port or an administration channel do not specify a protocol, WebLogic Server uses the protocol specified here.
Configuration Audit Type
Returns the criteria used for auditing configuration events (configuration changes and other operations):
Configuration events will neither be written to the server log or directed to the Security Audit Framework.
Configuration events will be written to the server log.
Configuration events will be directed to the Security Audit Framework.
Configuration events will be written to the server log and directed to the Security Audit Framework.
Compatibility MBean Server Enabled
Enables JMX clients to use the deprecated
Prior to 9.0, WebLogic Server supported a typed API layer over its JMX layer. Your JMX application classes could import type-safe interfaces for WebLogic Server MBeans, retrieve a reference to the MBeans through the
weblogic.management.MBeanHomeinterface, and invoke the MBean methods directly.
Management EJB Enabled
Enables access to the Management EJB (MEJB), which is part of the J2EE Management APIs (JSR-77).
The Management API specification provides a standardized management data model for common resources on J2EE Web application servers.
The MEJB provides access to J2EE Managed Objects (JMOs), which describe the common J2EE resources. If you set this attribute to
false, WebLogic Server does not register the MEJB in the JNDI tree, and effectively disables the J2EE Management APIs for the domain.
Platform MBean Server Enabled
Causes each WebLogic Server instance to initialize the JDK's platform MBean server and to use the platform MBean server as the Runtime MBean Server.
As of JDK 1.5, JVMs provide a platform MBean server that local processes can instantiate. There can be only one instance of the platform MBean server for each JVM. When a process instantiates this MBean server, the JVM creates several platform MBeans that provide monitoring data for the JVM itself.
If you set this attribute to
true, each WebLogic Server instance invokes the method
java.lang.management.ManagementFactory.getPlatformMBeanServer()and thus causes the initialization of the JVM's MBeans. In this case, the server's Runtime MBean Server uses the
MBeanServerreturned by this method as its
MBeanServer. This makes it possible to access the WebLogic Server MBeans and the JVM platform MBeans from a single MBean server. In addition, if you enable the Runtime MBean Server to be the platform MBean server, local processes in the JVM can directly access this MBean server through the
java.lang.management.ManagementFactory.getPlatformMBeanServer()returns. With this local access, there are no WebLogic Server security checks to make sure that only authorized users can access WebLogic Server MBeans. Any application that is running in the JVM can access any of the WebLogic Server MBeans in the Runtime MBean Server/JDK Platform MBean Server. Do not use this configuration if you cannot control or cannot trust the applications that are running within a JVM.
- Change Console preferences
- Configure the domain-wide administration port
- Archive configuration files
- Disable the Console