Dear All,

Presently we are using BaaN IV c4 only one location.


I am interested to know following details:

I have installed BaaN IV licences on my central server with 20 concurrent licenses. and we are accessing through thin client software from other city.
in this situation the data is stored in the central server.

I have branches in Mumbai,Chennai,Delhi,Kolkata,Pune.
my central server is in pune.

In case of Pune central server goes down , rest all the place will not be access the system. but i want other city user should work independently on their site and finally transfer to central server.

Can any guide me how to set multi architecture options in Windows 2003environment.

Thanks in advance.

b98

What I understand , u need offline working with Baan . This is not possible with webtop / worktop and even latest version .

If u have a database and application mirror at another location/city which too have good internet backbone , then users can work on other servers with some changes in in their bwc and then work on server in other city . Maintianing db and application mirrors across geographies is difficult.

Another option could be to increase redundancy in Pune itself , say procure leased line from two ISPs , implement failover clustering at Pune so that it may not get down . This too is costly and complex but very practical and feasible .Many mission critical application use combination of failover clustering and mirroring for extreme cases .

Another option could be to analyze all possible activities ur users at branches do and then get a third party application to run at the time Baan is down and then have interface using Baan exchange at the time Baan server is available . This requires lot of planning and effort from IT Team .

One of the multi-site options that Baan offers is Exchange and Audit Tables. Your remote sites can run Baan localy, and Audit captures the changes to the database and then is exported and copied to the other sites. There you import based on indicators in Exchange to update, instert, or delete the same rows of the table. This is more of a batch process and your data will only be as current as the night before (or whenever you schedule the update).

One of the multi-site options that Baan offers is Exchange and Audit Tables. Your remote sites can run Baan localy, and Audit captures the changes to the database and then is exported and copied to the other sites.

True . But that will require the separate hardware , OS ,DB and finally Baan to be purchased and installed at all other 4 cities(Mumbai,Chennai,Delhi,Kolkata ) .

In case of Pune central server goes down , rest all the place will not be access the system. but i want other city user should work independently on their site and finally transfer to central server.
b98

Hitesh, the point you are trying to make is what? The original requirement was stated that they wanted each site to be independant and transfer to the central server. That is what this part of multi-site with Exchange does.

Dear William,


Can you please advise me how to set multi site setup.
If you have any sample diagram with details , please send it to me

Thanks in advance.

b98

From the original posts , there is only 1 baan installation at Pune City and other cities do not have Baan locally . If one has Baan at all locations then only multi-site exchange will help . In this case , baan is not installed at all in other 4 cities (only baan clients bw are available probably).

I have installed BaaN IV licences on my central server with 20 concurrent licenses. and we are accessing through thin client software from other city.

Basically you have a consolidated server installation with BW clients on all dependencies. It is a cheap solution that serves well your 20 concurrent users. To get a higher service level you need to go for the option of data replication (as mentioned or others) or have your system clustered to provide redundancy (having a replicated backup on another location) - any of these solutions will increase your setup price way up.

Your best option is to improve the reliability of the link that the central server location provides to the others by ensuring that its downtime is reduced: having a second ISP service provider as backup and improve your systems UPS may just ensure that at a fraction of the cost of the other solutions.