|Your server||Prolaborate needs Windows Servers|
|Server provided by Prolaborate||Our servers run on AWS, Rackspace or your preferred Private Cloud provider|
|Option||Prolaborate Web Server||Prolaborate Database||EA Repository||Email server||Active Directory Server|
|2||Server 1||Server 2|
|3||Server 1||Server 2||Server 3|
Options in detail:
This option is the simplest to deploy, because both of the Prolaborate components are on the same server, as is the EA Repository. This is also going to be the best performing, as there are lots of calls from Prolaborate to the EA Repository, and they share a single machine.
If you already have a shared EA Repository on a server, then it may be necessary to install Prolaborate on its own server. We have tested this in several situations, and, provided there is a good network link between the Prolaborate and EA Repository servers, the performance is good.
Your local standards may even require you to put each component on a separate server. As with option (2), so long as the network connections are good, this performs well. We have already installed this option on a customer site, and it works fine.
We are happy to run an instance of the Prolaborate web server and the Prolaborate database on servers provided by us. Please ask us for a quote.
With Option (4), the EA Repository database stays on your servers, to maintain confidentiality.
The only data saved on our servers are:
We will still need to do some integrations into your network:
Option 5 takes away as much of the overhead of running Prolaborate as possible- all that’s left in your network is your AD server.
Option 5a re-uses your email server:
..and option 5b uses an email server from Prolaborate:
This reduces the integrations between the Prolaborate platform to the minimum:
We have described the most common deployment options here, but please if you don’t see the option you need, give us a call.