WebSphere Application Server - webshere session information need

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > December 2005 > webshere session information need





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author webshere session information need

2005-12-24, 7:50 am

Hi Experts,

I would like to know the websphere session infomation? Hows its work?
I tried to read websphere redbooks but i am not able to understand in details?

What is the persistent sessions?
What is the memory-to-memory sessions?

In above seesions, which is the works for database servers and which is the works for websphere application server?

Also, I am confused about the following redbook text :-
In persistence sessions, One drawback to the database solution, just as with application data, is that it provides a single point of failure (SPOF) so it should be implemented in conjunction with hardware clustering products such as HACMP or solutions suc
h as database replication. Another drawback is the performance hit, caused by database disk I/O operations and network communications.

can anybodys please throw lights on this.
Thanks
vaze
Paul Ilechko

2005-12-24, 5:57 pm

vazeamit@hotmail.com wrote:
> Hi Experts,
>
> I would like to know the websphere session infomation? Hows its work?
> I tried to read websphere redbooks but i am not able to understand
> in details?
>
> What is the persistent sessions? What is the memory-to-memory
> sessions?
>
> In above seesions, which is the works for database servers and which
> is the works for websphere application server?
>
> Also, I am confused about the following redbook text :- In
> persistence sessions, One drawback to the database solution, just as
> with application data, is that it provides a single point of failure
> (SPOF) so it should be implemented in conjunction with hardware
> clustering products such as HACMP or solutions such as database
> replication. Another drawback is the performance hit, caused by
> database disk I/O operations and network communications.
>
> can anybodys please throw lights on this. Thanks vaze


What makes you think that someone here can summarize this in a few
sentences more effectively than people who have written books on the
subject?
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com