Please enable JS

Deployment Options

At Prolaborate, we understand that installing a web-server product into your IT infrastructure can be difficult.

So we offer as many options as possible, to try and fit-in with how you’d like to do things. And if you don’t see the configuration you need in the examples below, please give us a call: we’re sure can make Prolaborate fit for you.

Some Deployment options

All these options need the five components below:

Component Description Prerequisites
Prolaborate Web server This is the engine which drives Prolaborate, and gets installed using a simple Windows installer Microsoft IIS Version (7.5 and above). Enterprise Architect Corporate Edition, V11 or above
Prolaborate Database The database which Prolaborate uses to store your configuration, your discussions etc. Microsoft SQLServer – Express or full
Your EA model repository This is where your EA content lives. The Prolaborate Web Server accesses this, and you can use the same repository for your day-to-day EA modellers Can run on SQL Server, Oracle, or any of the EA-supported relational databases
Email server Required to send notification emails to Prolaborate users, and invitations to new users SMTP Configuration. (Access to SMTP Port and SMTP mail server)
Active Directory server Optional. If you want to re-use login credentials and group memberships, Prolaborate fully integrates with AD Active Directory Access for Live Sync

Summary of options

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
1 Server 1    
2 Server 1 Server 2    
3 Server 1 Server 2 Server 3    

Options in detail:

Option 1

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.

Option 2

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.

Option 3

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.

Option 4

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.

Confidentiality and Security

With Option (4), the EA Repository database stays on your servers, to maintain confidentiality.

The only data saved on our servers are:

  • Comments and discussions. These are linked only to the ‘GUID’ keys in your repository,
  • Setup information. So none of your information ever sits on our servers.
  • Users and groups, unless you are using Active Directory integration, in which case we just know the names of AD groups
  • When a user does a direct update of EA data, Prolaborate does not keep arecord of the update: only EA remembers what happened

We will still need to do some integrations into your network:

  • To your EA database, via an ODBC connection. This usually requires firewall changes, and might not be acceptable to your network security team.
  • To your email server. This also may require firewall changes
  • If you decide to integration Prolaborate with your Active Directory, also access to your AD server.

Option 5

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:

  • To your Active Directory server, to allow for seamless login and management of groups
  • Your EA users access the shared EA Repository via ODBC or the EA Cloud interface.

We have described the most common deployment options here, but please if you don’t see the option you need, give us a call.