Using Act! Premium V18 Client and Web with same DB

[druff_act]

I installed ACT! Premium V18 Client  on some computers (clients) and on a Server.  The computers are sharing the Database which is placed on the server via remote (via Internet synchronization). Works fine.  We would like to be able to user also the browser Version. To do that, we have installed Act! Web on a second Server. And we can access it via the browser.

But the Client DB (Server 1) and the Web DB (Server 2). Are two different DBs. What do we have to do to sync this both DBs? The Web users and the Client users would like to work on the same DB.

Thanks for your help!

[druff_act]

I installed ACT! Premium V18 Client  on some computers (clients) and on a Server.  The computers are sharing the Database which is placed on the server via remote (via Internet synchronization). Works fine.  We would like to be able to user also the browser Version. To do that, we have installed Act! Web on a second Server. And we can access it via the browser.

But the Client DB (Server 1) and the Web DB (Server 2). Are two different DBs. What do we have to do to sync this both DBs? The Web users and the Client users would like to work on the same DB.

Thanks for your help!

[GLComputing]

Three choices:
1. Put Act! for Web on Server 1 and access it directly - no need for a separate server
2. Have Act! for Web on Server 2 use the database on Server 1 - no need for a separate database and allows targeting of the resources.
3. Have an RDB (remote database created from Server 1) on Server 2 and use the Scheduler to regularly sync to Server 1 - this would be the least preferred option

If the clients are on the same LAN, they should directly access the database on Server 1 rather than sync.

[druff_act]

Thank you for your answer!

Which choice ist the best one? 1) or 2)?

And could you give me a link for a tutorial "how to share a database between two different server" -> Choice 2)?

Thank you.

[GLComputing]

#1 is the easiest ... Just uninstall Act! and reinstall Act! Web. Then make sure that's accessible to the users who want to access via browser.

#2 is my preferred way as it gives these two advantages:
a) The Web server can be configured to handle better web throughput while the database server configured with faster drives
b) The web server can be put in a DMZ adding a layer of protection to the database

For a small site, I might use #1
For a larger one with better (internal or external) IT support, #2

For #2, just have the Web Admin Tool add the database from the other machine

[ilange]

Hi,

we strongly recomend to use a second server, and if any possible, this server should be in a Different Firewall Zone (DMZ) 

for opening Ports, we have some KB´s 

https://kayako.crmaddon.com/index.php?/Knowledgebase/Article/View/199/0/dmz-act-firewall-rules

(German) https://kayako.crmaddon.com/index.php?/Knowledgebase/Article/View/422/0/benotigte-ports-fur-das-offn...

as you asked, how to open the database on a different server, this thread shows how this can be done (German) https://kayako.crmaddon.com/index.php?/Knowledgebase/Article/View/406/0/startdatenbank-in-act-auswah...

 You should also look at this, it explains the limitations with act for web (German) 

you can test act for web on this Site (German)

If you need Support, feel fee to contact us for help

Regards

Ingo Lange

ACC Since 1995