This article describes the steps involved in setting up Prolaborate. It also describes the specific environment settings that are required in the database, web server and other supporting software.
The following are the minimum requirements. The deployment will depend on usage and other environmental factors.
|CPU||2.4 GHz x 4|
|Disk Space||20 GB|
If you think the number of concurrent users will be more than 100, recommended memory and CPU is 16.0 GB and ‘2.4GHz x 8’ respectively.
|CPU||2.4 GHz x 4|
|Disk Space||10 GB|
We don't support Firebird database as of now.
The following details of Prolaborate database should be readily available before the installation:
It is recommended to install the .NET Framework after installing IIS. If you install IIS after installing .Net Framework, you will probably need to register ASP.Net for use with IIS Ports and protocols. Please refer Appendix for more details.
Enable required Features in Windows
The following ports should be open:
It is recommended that you disable FIPS. If FIPS is not disabled, password encryption cannot happen in Prolaborate and so you will not be able to login to Prolaborate.
Kindly refer to the appendix for details on how to disable FIPS.
A minimum screen resolution of 1280x720 is required for the best use of Prolaborate.
It is recommended to not have Enterprise Architect installed on the server where Pro Cloud Server is going to be installed.
The Pro Cloud Server installer is a standard Microsoft Installer; double click on it to start the installation and follow the onscreen steps.
Kindly follow these steps to configure the Pro Cloud Server:
To enable HTTPS, comment the first occurrence of SERVER_PORT by adding '#' at start of the line and then update the second occurrence of SERVER_PORT from 805 to 443 and REQUIRE_SSL=1.
If you want both HTTP and HTTPS to be enabled, leave the first set of values as it is.
Use the following OpenSSL command to generated .pem file
openssl pkcs12 -in key.pfx -out key.pem -nodes
Check this link to learn how to enable SSL security.
Please note that Prolaborate database needs to be created before you proceed with the installation. Database server details like server name, database name, username, and password will be asked during the installation and you need to have them ready for the installation to continue. To know how to set up the database, please refer Appendix (Section 6.5 or 6.6)
To start the installer, administrator privileges are required. Run the “Setup.exe” as administrator. The installer will check the status important components and show you the status. Click on “Next”
In the next dialogue box that appears, click on 'Next' to proceed.
A full SQL Server setup or an Express edition setup will suffice.
Valid SQL server details (Database Host name, Username, Password and Database name) should be provided in order to proceed with the installation. To know how to set this up, please refer Appendix
Choose the installation mode to proceed further:
Now, provide the SQL server details.
Port Number: Ensure that the Port is available and opened in the firewall settings.
IP Address/ Host name : Machine IP or Machine name should be given
Port: Ensure that the Port is available and opened in the firewall settings.
Please note down the login credentials shown in the installer. These are Super Admin credentials, with which you can login to Prolaborate.
Click on 'Install' to install Prolaborate.
Once the Installation is complete, the following screen will appear:
Select 'Finish' to complete the installation.
If you have installed Prolaborate in a server which has Enterprise Architect 13 or up, you need to create Data Cache before going ahead. To do it, open Enterprise Architect and connect to the repository you are going to add in Prolaborate. Click on Options in the Configure tab. In the popup that opens up, under Data Cache, check the two check boxes and click on Create.
If you have installed Prolaborate in a server which does not have Enterprise Architect or has EA with version less than 13, just restart the Prolaborate services once after adding a repository to create Data cache.
In order to get started with Prolaborate, please follow the below guides.
Install License - You will need to have the right licenses installed, for your users to have complete access to the application.
Add Repositories - A repository is the first thing you see once you login to your account. Prolaborate users can only manage repositories which they have access to; New Repositories can be created by the Prolaborate administrator only.
Configure Sections - You will need to define which packages from the EA are to be accessed through Prolaborate.
Set up Access Permissions -An admin can use this feature to give controlled access to users or groups in Prolaborate, the web platform for Enterprise Architecture.
Set up Guest Access - The guest sign-up feature allows anybody to quickly sign up and gain a read-only access to the application.
Configure SMTP - Emails for Activations, Notifications, Reviews, etc. are sent out from Prolaborate through the SMTP server. Thus, in order to receive emails without any issues, SMTP should be properly configured.
Setup Active Directory - The Active Directory feature enables the users, configured in your Active Directory, to login to Prolaborate with the same credentials.
Add Users- Users are the participants working together in a particular repository. Users can view and configure the repository as per their individual access rights provided by the Prolaborate administrator.
Step 1. Press Windows Key+R to open the Run dialog.
Step 2. Type “gpedit.msc” into the Run dialog box (without the quotes) and press Enter.
Step 3. Navigate to 'Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options' in the Local Computer Policy.
Step 4. Locate the 'System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing' settings in the right panel and double-click on it.
Step 5. Set the setting to 'Disabled', click on 'OK' and restart your computer.
The following report gives details of the compatibility based on our extensive tests.
|Case #||EA Worker Available||EA Availability||EA Version||EA Version 13.5||EA Version 13.1||EA Version 12||EA Version 11|
|1||Yes||Yes||13.5||Compatible||Compatible||Not Compatible||Not Compatible|
|5||No||Yes||13.5||Compatible||Compatible||Not Compatible||Not Compatible|
|6||No||Yes||13.1||Not Compatible||Not Compatible||Not Compatible||Not Compatible|
|7||No||Yes||12||Not Compatible||Not Compatible||Not Compatible||Not Compatible|
|8||No||Yes||11||Compatible||Compatible||Not Compatible||Not Compatible|
|9||Yes||No||Not Applicable||Not Applicable||Compatible||Compatible||Compatible|
Make sure the firewall is enabled by confirming that "Firewall state" is set to 'On' and not to 'Off'.
Step 1: Open the Server Manager from the task bar.
Step 2: In the right-hand side of the top navigation bar, click on 'Tools' and select Windows Firewall with Advanced Security.
Step 3: Select either of the Inbound Rules under Windows Firewall with Advanced Security on the left side of the management console.
Step 4: From the right side of the Inbound Rules tab click on 'New Rule'. The new rule wizard launches.
Step 5: Select 'PORT' and click 'Next'.
Step 6: Select 'TCP' and click 'Next'.
Step 7: Select 'Specific local ports' and enter the Port number which needs to be opened and click on 'Next'.
Step 8: Select 'Allow the connection' and click 'Next'.
Step 9: Make sure all Domains, Private and Public are checked and click 'Next'.
Step 10: Specify the Name and Description for the port and click 'Finish'.
‘SQL server authentication’ must be enabled and an admin account must be created. The following settings must be accomplished
Step 1. Create a new Database called Prolaborate
Step 2. Create a new user by using the ‘New Login’ option under Security -> Login section
Step 3. Uncheck ‘Enforce password policy’
Step 4. Set the default database to ‘Prolaborate’
Step 5. Configure ‘Server Roles’, grant access to all admin privileges.
Step 6. ‘User Mapping’, maps the Prolaborate database to the new user.
Please follow the below steps:
Step 1. Open MySQL Workbench and create a new connection
Step 2. Open the new connection
Step 3. Create new schema
Step 4. Review SQL Script
Step 5. Apply SQL Sript
The port on which the server will listen for HTTP connections; each connection must be unique and not used by any other services on the machine. You must check that no firewalls are blocking this port on the client or server. You can use the standard HTTP port (80) or HTTPS port (443).
Note: When changing this, check firewall settings and other services using that port. Additionally, when the service is running on Wine you should not use privileged ports - those below 1024. Under Wine, most applications are only able to listen on ports above 1024.
Should be set to 1 to enable HTTPS on this port; HTTPS should be enabled for all connections that are being exposed on public networks. HTTPS requires a private key file (server.pem), to be included in the same directory as the configuration file, before it will run.
Note: This unique file must be user-created. See Creating a Self-Signed Certificate using OpenSSL.
|DEFAULT_MODEL||Allows a single model to be exposed on a port, making it possible to use a different port for each model. Model names are discussed further in the Connecting Enterprise Architect to a Cloud Server topic.|
Can be set to 1 to request HTTP authorization using the user security defined in the Enterprise Architect model being connected to. Passwords must be explicitly and individually assigned in that model using the Maintain Users procedure; the default administrator password and any passwords imported from Windows Active Directory do not work. Note that if you are not using SSL to connect, the usernames and passwords will be sent in plain text. If the model does not have security enabled, the Cloud user is not prompted for a password.
This option is mutually exclusive with GLOBAL_AUTHENTICATION.
Can be set to the name of an Enterprise Architect model with security enabled that will provide the list of users for all models accessed by the connection. This is helpful if you want to provide multiple models but only manage one list of users. Passwords must be explicitly and individually assigned in the reference model using the Maintain Users procedure; the default administrator password and any passwords imported from Windows Active Directory do not work.
This option is mutually exclusive with MODEL_AUTHENTICATION.
Enabled by default. It allows models to be queried using the 'Open Services for Lifecycle Collaboration' standard. This is discussed further in the OSLC Requirements Management topic.
Set to 0 to disable.
|Database Managers||This panel lists the defined repositories. Each row contains two columns of information - the database connection string of the repository and the number of active and available connections.|
|Refresh||Click on this button to reload the contents of the 'Database Managers' list.|
|Add||Click on this button to display the dialog on which you define a new database.|
|Remove||Click on this button to permanently delete the selected database from the Cloud Server.|
|Configure||Click on this button to display the dialog on which you change the settings for the currently selected database.|
|Server Options||Click on this button to display the dialog on which you change the Cloud Server global options.|
The Server Address format is:
The server URI can be ‘localhost’, an IP address, a DNS name or a machine name; for example, MyWebServer. If you are working on the web server, 'localhost' will be sufficient.
|Password||Enter the password you defined in Management Client Connection Settings, in the Cloud Server Configuration topic. By default this password is blank; you can reset it to a new value, as described in the Help topic Global Server Options.|
|OK||Click on this button to log in to the Management Client.|
Setup Microsoft .NET 4.5 Framework. Download the latest Microsoft .NET Framework 4.5 from Microsoft
Step 1. Under Control Panel-> Programs -> Programs and Features -> Turn Windows features on or off.
Step 2. Click next on Installation Type and Server selection steps
Step 3. In Server Roles step, select Web Server. Click on Add Feature on the popup.
Step 4. In Features step, select ASP.NET 4.5
Step 5. In Role Services step, select Application Development and all the options under it. Click on Add Features if prompted.
Step 1. To start the server, type “inetmgr” in the Run Window and click on “Ok”.
Step 2. In the 'Internet Information Service Manager', select the Local host and click on 'start'.
Step 3. Expand the server and under 'sites', you will find the option 'Default Web Site'. Select this and click 'Start'.
Step 4. After starting the site, select 'Browse'. It should open the default website on the browser.
Step 5. Ensure that the Internet Information Services landing page is displayed in the default web browser.