Hello,

I do not know whether her is the right place, but there is not any BTT
topic. So here is my problem.

I'm a developer from Turkey.

We have developed a banking application using BTT. It runs on a WAS
(Websphere Application Server)). What we need is just run our application in
more than one WAS. If we cluster WAS, using session replication, can also
replicate our BTT Context s between those WASes. If not, how can we manage
scaling, failure etc. on BTT applications.

Thank you,

[ Post a follow-up to this message ]

Hello,

I don't know whether you have already found a solution to your problem.
But there is a BTT forum available
(ibm.software.websphere.components.composer). However it is not as
active as this forum.

Regarding your question. Because BTT is based on the J2EE architecture,
BTT contexts are stored in HttpSession (for user contexts and session
contexts) or ServletContext (for channel context or root context), and
as such will be replicated to other WAS nodes in the cell or cluster, if
you use session replication. So scalability should be no problem.

Kind regards
Gie Indesteege
Trainer and consultant Abis Belgium
www.abis.be



Lutfi Yelkenci wrote:

> Hello,
>
> I do not know whether her is the right place, but there is not any BTT
> topic. So here is my problem.
>
> I'm a developer from Turkey.
>
> We have developed a banking application using BTT. It runs on a WAS
> (Websphere Application Server)). What we need is just run our application 
in
> more than one WAS. If we cluster WAS, using session replication, can also
> replicate our BTT Context s between those WASes. If not, how can we manage
> scaling, failure etc. on BTT applications.
>
> Thank you,
>
>

[ Post a follow-up to this message ]