|
Home > Archive > WebSphere Application Server > March 2004 > Branch Transformation Toolkit problem
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 |
Branch Transformation Toolkit problem
|
|
| Lutfi Yelkenci 2004-02-26, 11:33 am |
| 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,
| |
| Gie Indesteege 2004-03-24, 5:34 am |
| 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,
>
>
|
|
|
|
|