Network-Addressing
Features
For
many development environments, configuring the Oracle WebLogic Server network
resources is simply a matter of identifying a managed server’s listen address
and listen port. However, in most production environments, administrators must
balance finite network resources against the demands placed on the network. The
task of keeping applications available and responsive can be complicated by
specific application requirements, security considerations, and maintenance
tasks, both planned and unplanned.
Oracle
WebLogic Server allows you to control the network traffic associated with your
applications in a variety of ways, and configure your environment to meet the
varied requirements of your applications and end users. You can:
•Designate
the Network Interface Cards (NICs) and ports used by managed servers for
different types of network traffic
•Support
multiple protocols and security requirements
•Specify
connection and message time-out periods
•Impose
message size limits
You
specify these and other connection characteristics by defining a network
channel, the primary configurable Oracle WebLogic Server resource for managing
network connections. You configure a network channel either in the
Administration Console (Servers > Protocols >
Channels) or by using NetworkAccessPointMBean.
A
channel is a way that WebLogic Server can refer to an IP address:port
combination by assigning a name to it for purposes of segregating traffic. This
can be useful to guarantee that one kind of traffic does not monopolize
specific network hardware at the expense of another kind of traffic (for
example, user traffic versus administrative traffic). If the standard Oracle
WebLogic Server administrative channel does not satisfy your requirements, you
can configure a custom channel for administrative traffic. For example, a
custom administrative channel allows you to segregate administrative traffic on
a separate Network Interface Card (NIC).