Technical data

Understanding Network Channels
Creating and Configuring WebLogic Server Domains 11-5
guaranteed level of throughput, by assigning the highest weighting to an
outbound channel that utilizes a fast NIC.
Note: Network channel weights apply only to internal connections made for remote
references, such as a remote EJB reference or a resource located via JNDI.
Channel weights are not used for connections initiated directly via a URL.
If you use a Network Channel with a server instance on a multi-homed machine, you
must enter a valid Listen Address either in
ServerMBean or in the channel. If the
channel and
ServerMBean Listen Address are blank or specify the localhost address
(IP address 0.0.0.0 or 127.*.*.*), the server will bind the Network Channel listen port
and SSL listen ports to all available IP addresses on the multi-homed machine. See
“The Default Network Channel” on page 11-7 for information on setting the Listen
Address in
ServerMBean.
WebLogic Server and the Channel Selection Process
This section describes how WebLogic selects among multiple channel to use under
various circumstances.
Prioritizing Outgoing Connections
If a Managed Server has several channels that support outgoing connections, it must
choose which channel to use when connecting to another server instance. WebLogic
Server first selects channels based on the protocol required for the connection. If
multiple channels have the same protocol support, you can prioritize those channels by
assigning a different weight to each.
A channel weight is a simple numerical value that can be applied to the
NetworkChannelMBean. Channel weights are considered only when multiple
channels with the same service level could be used to initiate an outgoing connection.
(If a channel with a higher service level is currently active, it is used regardless of
channel weights). Higher-valued weights are selected over lower-weighted channels to
choose a channel for outgoing connections.
In a multihomed system, channel weights allow you to prioritize equivalent channels
based on the known capacity of available network cards.