there will be 3 types of environments in weblogic
1)developmnent
2)uat
3)production level
out of these 3 production will be the critical level

there will be 3 types of environments in weblogic
1)sit
2)uat
3)production level
out of these 3 production will be the critical level

heart beat is a signal,this signals are sent by objects.

think that there are 5 servers.(the servers with in the 
cluster to communicate each other they use multicast ip)
if u add one objet to any  oneof these server that object 
will send a heart beat signal to multicast ip from there 
remainig servers will receive that signals and update thire 
jndi tree.from this only each server will known the helth 
of each object.if the object is stop sending heart beats 
the servers treat that that object is failed

www.abc.com

www--servername
abc--domain name
.com--top level domain
if u give like www.abc.com ,the dns will chech for ip 
adress for abc domain in .com top level domain ,after 
geting that ip address the dns send a request to that 
particular ip and get responce.

Middleware services of Weblogic Application Server are 
totally 16+ But i could remember only few of them 

1. Transactions
2.Connection Pooling(JDBC Connection Pooling)
3.Security(Realms)

using connection pool we can retrive the value in the 
database.

Connection pool staus changes to suspended.

it tries to poll the connection. It depends on the 

configuration  of connection pool .I will log an error if 

application tires to use the connection pool

in app server u will diffine that connect to which data 
base according to that connection will be establised and u 
can get data from data base.if the data base is not working 
then u will get a error page(related to database).
if u want to give 100% availability for clint then u can 
use failover concept and place the data in to different 
databases and give instructions for u r application that if 
one data base is fail to serve the data after partucular 
time the request will rediirect to another database where 
data is present.

HTTP tunneling provides a way to simulate a stateful socket 
connection between WebLogic Server and a Java client when 
your only option is to use the HTTP protocol. It is 
generally used to tunnel through an HTTP port in a security 
firewall. HTTP is a stateless protocol, but WebLogic Server 
provides tunneling functionality to make the connection 
appear to be a regular T3Connection. However, you can 
expect some performance loss in comparison to a normal 
socket connection.

Configuring the HTTP Tunneling Connection
Under the HTTP protocol, a client may only make a request, 
and then accept a reply from a server. The server may not 
voluntarily communicate with the client, and the protocol 
is stateless, meaning that a continuous two-way connection 
is not possible. 

WebLogic HTTP tunneling simulates a T3Connection via the 
HTTP protocol, overcoming these limitations. There are two 
attributes that you can configure in the Administration 
Console to tune a tunneled connection for performance. It 
is advised that you leave them at their default settings 
unless you experience connection problems. These properties 
are used by the server to determine whether the client 
connection is still valid, or whether the client is still 
alive. 

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. 

You can say so many diff b/w welogic and websphere

In websphere u can add standalone server as a maneged 
server in Domain

Where as in weblogic u can't add WLS server as member to 
the another domain.

In websphere u can add webserver as a unmanaged node where 
as u cannnt do that in weblogic.

i am also looking the right answer of this v. imp. question...

Weblogic has self Concole 7001,
where as Jboss is dependent on Tomcat i.e,8080.

Hi,

If Weblogic Server is up, then the application working on 
this server will also be up. But the only effect due to 
database server to be down is "All the results in 
application which retrieve some information from database 
will not be visible and some error message will be 
displyed".

All the functionalities except those dependent on DB will 
work as usual but whenthe proxy server is down ,no requests 
will be routed to the Weblogic Server .

All the functionalities except those dependent on DB will 
work as usual but whenthe proxy server is down the requests 
will directly hit the app server and get the responce.
why because proxy means behalfof(instedof),proxy server 
means insted of going request to main server first it will 
hit the proxy server(webserver) and then hit the app server
so if proxy is down request can hit app server but it is 
not sequre.

All the database connections are logged during server 
startup in the server logs.

you can get the connection details by executing netstat -a 
| grep <ipaddress of DB Server

in admin console you can go to the JDBC->connection pool-> test
it will test the pool and display the result, if the
application is connected to the db it will show a test
successful message else error

1.In admin console you can go to the JDBC->connection pool-> 
You will find status as running if DB is up i.e connected.

And to be more confident
       JDBC->connection pool-> test

- Test connection successfully ( test connection attributes
in the advance configuration of the connection pool should
be checked and there should be a dummy table -- "dual" is by
default)
- If "Test connection" attributes are not checked then a
warning will appear.

2. If a DB connection is not available , you can find
related message in the server logs also.