Configuring Network Resources 4-7
■
Other types of network traffic, for example replication data, need to occur over a separate network connection.
■
Certain types of network traffic need to be monitored.
4.2.4.1 Channel Selection
All internal traffic is handled via a network channel. If you have not created a custom network channel to handle administrative or clustered traffic, WebLogic Server
automatically selects a default channel based on the protocol required for the connection. For more information on default channels, see
Section 4.2.3.1, The Default Network Channel
.
4.2.4.2 Internal Channels Within a Cluster
Within a cluster, internal channels can be created to handle to the following types of server-to-server connections:
■
Multicast traffic
■
Replication traffic
■
Administration traffic For more information on configuring channels within a cluster, see
Section 4.3.2, Configuring Network Channels For a Cluster
.
4.3 Configuring a Channel
You can configure a network channel using Servers Protocols Channels page in the Administration Console or using the NetworkAccessPointMBean.
To configure a channel for clustered Managed Servers see, Section 4.3.2, Configuring
Network Channels For a Cluster .
For a summary of key facts about network channels, and guidelines related to their configuration, see
Section 4.3.1, Guidelines for Configuring Channels .
4.3.1 Guidelines for Configuring Channels
Follow these guidelines when configuring a channel.
4.3.1.1 Channels and Server Instances
■
Each channel you configure for a particular server instance must have a unique combination of listen address, listen port, and protocol.
■
A channel can be assigned to a single server instance.
■
You can assign multiple channels to a server instance.
■
If you assign non-SSL and SSL channels to the same server instance, make sure that they do not use the same combination of address and port number.
4.3.1.2 Dynamic Channel Configuration
■
In WebLogic Server, you can configure a network channel without restarting the server. Additionally, you can start and stop dynamically configured channels
while the server is running. However, when you shutdown a channel while the server is running, the server does not attempt to gracefully terminate any work in
progress.
