Administration Console Online Help
|
 |
 |
|
|
Server --> Configuration --> General
Tasks Related Topics Attributes
Overview
The Server
Tasks
Configuring the Listen Address
Starting Managed Servers from the Administration Console
Shutting Down Instances of WebLogic Server
Adding and Removing Servers in an Existing Domain
"Creating Execute Queues" in WebLogic Server Performance and Tuning
Related Topics
Using WebLogic Server Clusters
Administration Port Configuration and Startup
Configuring WebLogic Server Web Components
Attributes
|
An alphanumeric name for this server instance. This field will not accept spaces. Each server instance in your WebLogic environment must have a unique name, regardless of the domain or cluster in which it resides, or whether it is an Administration Server or a Managed Server. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain. The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only. The server name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server. After you have created a server, you cannot change its name. Instead, clone the server and provide a new name for the clone. For more information, refer to Cloning a Server. |
||
|
The WebLogic Server host computer (machine) on which this server is meant to run. If you want to use a Node Manager to start this server, you must assign the server to a machine and you must configure the machine for the Node Manager. Node Manager uses this information to communicate with the server on its host machine. |
||
|
The cluster to which this server belongs. If set, the server will listen for cluster multicast events. |
||
|
The address from which this server listens for requests. Servers can be reached through the following URL: By default, a server's listen address attribute is undefined, which enables you to reach the server through an IP address of the computer that hosts the server, a DNS name that resolves to the host, or the |
||
|
Determines whether the server can be reached through the default plain-text (non-SSL) listen port. If you disable this listen port, you must enable the default SSL listen port. You can define additional listen ports for this server by configuring network channels. |
||
|
The default plain-text (non-SSL) listen port for this server. For more information, refer to Configuring the Listen Ports. |
||
|
Determines whether the server can be reached through the default SSL listen port. If you disable this listen port, you must enable the default plain-text (non-SSL) listen port. You can define additional listen ports for this server by configuring network channels. |
||
|
The default SSL listen port for this server. For more information, refer to Configuring the Listen Ports. |
||
|
When set to true for a server instance, this attribute specifies that certs from clients of web applications hosted on the server instance are provided in the special ( This setting is useful if user authentication is performed on the proxy server—setting The header can be used by any client with direct access to WebLogic Server. WebLogic Server takes the certificate information from that header, trusting that is came from a secure source (the plug-in) and uses that information to authenticate the user. If you set |
||
|
The Java Compiler for all applications that need to compile Java code. |
Advanced Attributes
Set this attribute to true if the server instance will receive requests from a proxy plug-in or HttpClusterServlet.
When WeblogicPluginEnabled is true, a call to getRemoteAddr will return the address of the browser client from the proprietary WL-Proxy-Client-IP header, instead of the web server.
If the server instance is a member of a cluster that will receive proxied requests, set WeblogicPluginEnabled for the cluster, on the Cluster -->Configuration-->General tab.
WeblogicPluginEnabled can be configured in ClusterMBean or ServerMBean. If specified in both ClusterMBean and ServerMBean, the value in ClusterMBean value takes precedence.
The state in which this server should be started.
In the RUNNING state, a server offers its services to clients and can operate as a full member of a cluster. In the STANDBY state, a server can accept administration commands and participate in cluster communication, but is not accessible for requests that come from external clients. (If you select STANDBY, you must also enable the domain-wide administration port under this domain's Configuration > General tab.)
The options to prepend to the Java compiler classpath for when we need to compile Java code.
The options to append to the Java compiler classpath for when we need to compile Java code.
The extra options passed to rmic during server-side generation.
If extra rmic options
are specified at the EJB component level—on EJBComponentMBean—that value overrides this server-level value. See Configuring Compiler Options.
The extra options passed to ejbc during server-side generation.
Note: If extra ejbc options
are specified at the EJB component level—on EJBComponentMBean—that value overrides this server-level value. See Configuring Compiler Options.
The external DNS name for the current server, which will be sent with HTTP session cookies and also with the dynamic server lists to HTTP proxies.
Do not specify an IP address for this attribute—the value must be an actual domain name.
This attribute is required for configurations in which a firewall is performing Network Address Translation, unless clients are accessing WebLogic Server using t3 and the default channel. For instance, define the external DNS name for configurations in which a firewall is performing Network Address Translation, and clients are accessing WebLogic Server using HTTP via a proxy plug-in.
Indicates whether the administrative channel is enabled for the domain.
You enable the administrative channel on the Domain > Configuration > General tab.
For more information, refer to "Administration Port Configuration and Startup."
Overrides the domain-wide administration port and specifies a different listen port on which this server listens for administrative requests. Valid only if the administrative channel is enabled for the domain.
By default, if you enable the domain's administrative channel, all servers in the domain use the same listen port to listen for administrative requests.
|
Set this attribute to true if the server instance will receive requests from a proxy plug-in or When If the server instance is a member of a cluster that will receive proxied requests, set
|
||
|
The state in which this server should be started. In the |
||
|
The options to prepend to the Java compiler classpath for when we need to compile Java code. |
||
|
The options to append to the Java compiler classpath for when we need to compile Java code. |
||
|
The extra options passed to If extra rmic options |
||
|
The extra options passed to Note: If extra ejbc options |
||
|
The external DNS name for the current server, which will be sent with HTTP session cookies and also with the dynamic server lists to HTTP proxies. Do not specify an IP address for this attribute—the value must be an actual domain name. This attribute is required for configurations in which a firewall is performing Network Address Translation, unless clients are accessing WebLogic Server using t3 and the default channel. For instance, define the external DNS name for configurations in which a firewall is performing Network Address Translation, and clients are accessing WebLogic Server using HTTP via a proxy plug-in. |
||
|
Indicates whether the administrative channel is enabled for the domain. You enable the administrative channel on the Domain > Configuration > General tab. For more information, refer to "Administration Port Configuration and Startup." |
||
|
Overrides the domain-wide administration port and specifies a different listen port on which this server listens for administrative requests. Valid only if the administrative channel is enabled for the domain. By default, if you enable the domain's administrative channel, all servers in the domain use the same listen port to listen for administrative requests. |
