| Download Docs | Site Map | Glossary | |
|
|
|||
| bea.com | products | dev2dev | support | askBEA |
|
|
|
|||||||
 |
| e-docs > WebLogic Server > Administration Console Online Help > Security |
|
Administration Console Online Help
|
Server --> Configuration --> General
Tasks Related Topics Attributes
The Server
Configuring Servers for Development Environments: Main Steps
Configuring Servers for Production Environments: Main Steps
Starting Managed Servers from the Administration Console
Shutting Down Instances of WebLogic Server
Adding Managed Servers to an Existing Domain
Using WebLogic Server Clusters
Administration Port Configuration and Startup
Configuring WebLogic Server Web Components
|
An alphanumeric name for this server instance. This field will not accept spaces. Each server within a domain must have a unique name. 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: protocol://listen-address:listen-port Leave this field empty to accept the default behavior, or enter an IP address of the computer that hosts the server, a DNS name that resolves to the host, or localhost. For more information, refer to Setting the Listen Address. |
||
|
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 Setting 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 Setting the Listen Ports. |
||
|
WLS HttpRequest.getRemoteAddr() used to rely on X-Forwarded-For for its returned value. This is a security hole due to HTTP header can be easily mocked and we end up with returning wrong value. This is improved by introducing a proprietary header WL-Proxy-Client-IP from our plugins and this header will only be used if WLS is configured to use our plugins. This is duplicated both in ClusterMBean and ServerMBean so the attribute WeblogicPluginEnabled can be used cluster-wide. ClusterMBean overrides ServerMBean |
||
|
The state in which this server should be started. (If you use the Node Manager to start this server, the value in this field is ignored.) In the RUNNING state, a server offers its services to clients and can operate as a full member of a cluster. In the SHUTDOWN state, a server invokes any configured shutdown classes. 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 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. This is required for configurations in which a firewall is performing Network Address Translation. |
||
|
The Java Compiler for all applications that need to compile Java code. |
|
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. |
||
|
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. |
|
|
|
|
||
 |
|
|
 |
 |
 |
|
||
