配置 weblogic protocol

 

what is WLS T3 protocol?

 

Weblogic's implementationof the RMI specification uses a proprietary wire-protocol known as T3. javasoft's reference
implementation of RMI uses a proprietary protocol callrdJRMP. weblogic developed T3 because they needed a scalable,efficient protocol for building enterprise-class destributed object systems with java.

 

T3 provides a framework for WebLogic Server messages that support for enhancements. These enhancements include   abbreviations and features, such as object replacement,   that work in the context of WebLogic Server clusters and   HTTP and other product tunneling. T3 predates Java Object   Serialization and RMI, while closely tracking and   leveraging these specifications. T3 is a superset of Java   Object. Serialization or RMI; anything you can do in Java   Object Serialization and RMI can be done over T3. T3 is   mandated between WebLogic Servers and between programmatic   clients and a WebLogic Server cluster. HTTP and IIOP are   optional protocols that can be used to communicate between   other processes and WebLogic Server. It depends on what you   want to do. For example, when you want to communicate   between a browser and WebLogic Server-use HTTP, or an ORB   and WebLogic Server-IIOP.

 

 

Weblogic : Configuring Protocols

 

http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/ConsoleHelp/servers.html#1140645

Configuring the HTTP Protocol

The server instance for which you configure the HTTP protocol does not need to be running. If it is running, and if you change settings on the HTTP tab, you must restart it. Changes on the Protocols —> General tab take effect without requiring you to restart the server.

To configure the HTTP protocol:

1.  
   1. • Select Protocols —> General.
      • In the Advanced Options bar, click Show.
      • Click Enable Tunneling and provide values for Tunneling Client Ping and Tunneling Client Timeout. For information about each setting, refer to Attributes.

      Note: These settings apply to all protocols in the server's default network configuration that support tunneling.

      Also see "Setting Up WebLogic Server for HTTP Tunneling."

      • Click Apply.
2. • Start the Administration Server.

   See Starting Administration Servers.

   • In the left pane of the Administration Console, expand the Servers folder and select a server. (See Figure 330-3.)
   • Select Protocols —> HTTP.
   • Modify the default settings as desired. See Attributes.
   • Click Apply.
   • To enable tunneling of connections:
   • If the server instance is running, and if you made changes on the HTTP tab, restart the server.

Configuring the T3 Protocol

The server instance for which you configure the T3 protocol does not need to be running. If it is running, all modifications to the T3 protocol settings take effect immediately.

To configure the T3 protocol:

1. • Start the Administration Server.

   See Starting Administration Servers.

   • In the left pane of the Administration Console, expand the Servers folder and select a server. (See Figure 330-3.)
   • Select Protocols —> General.
   • In the Advanced Options bar, click Show.
   • Modify the values for Complete Message Timeout, and Maximum Message Size. See Attributes.

   Note: These settings apply to all protocols in the server's default network configuration. See "The Default Network Channel."

   • To enable tunneling of connections, click Enable Tunneling and provide values for Tunneling Client Ping and Tunneling Client Timeout. See Attributes.

   Note: These settings apply to all protocols in the server's default network configuration that support tunneling.

   • Click Apply.

Note: Messages sent via the default channel can contain DNS information about the hosts they originate on or are destined to. If a T3 connection is established across a firewall that has network address translation (NAT) enabled, it is possible that some information about the network configuration behind the firewall will be revealed. Using the firewall to prevent T3 connections through the firewall will prevent this problem.