Technical data

7 Configuring WebLogic Server Web Components
7-24 Configuring and Managing WebLogic Server
Enable Tunneling
Enables or disables HTTP tunneling. HTTP tunneling is disabled by default.
Note that the server must also support both the HTTP and T3 protocols in order
to use HTTP tunneling.
Tunneling Client Ping
When an HTTP tunnel connection is set up, the client automatically sends a
request to the server, so that the server may volunteer a response to the client.
The client may also include instructions in a request, but this behavior happens
regardless of whether the client application needs to communicate with the
server. If the server does not respond (as part of the application code) to the
client request within the number of seconds set in this attribute, it does so
anyway. The client accepts the response and automatically sends another
request immediately.
Default is 45 seconds; valid range is 20 to 900 seconds.
Tunneling Client Timeout
If the number of seconds set in this attribute have elapsed since the client last
sent a request to the server (in response to a reply), then the server regards the
client as dead, and terminates the HTTP tunnel connection. The server checks
the elapsed time at the interval specified by this attribute, when it would
otherwise respond to the client’s request.
Default is 40 seconds; valid range is 10 to 900 seconds.
Connecting to WebLogic Server from the Client
When your client requests a connection with WebLogic Server, all you need to do in
order to use HTTP tunneling is specify the HTTP protocol in the URL. For example:
Hashtable env = new Hashtable();
env.put(Context.PROVIDER_URL, "http://wlhost:80");
Context ctx = new InitialContext(env);
On the client side, a special tag is appended to the http protocol, so that WebLogic
Server knows this is a tunneling connection, instead of a regular HTTP request. Your
application code does not need to do any extra work to make this happen.