Install Behave Pro Server
Behave Pro Server is available as both a virtual appliance for deploying on your own hardware in a supported hypervisor, and also as an Amazon AMI for use when deploying to the AWS Cloud.
Minimum hardware requirements
- 1.2 GHz dual core CPU
- 2GB of RAM
- 20GB of free hard disk space
- OVA compatible - VMware/ESXi and VirtualBox
Download Virtual Appliance OVA (750mb)
- JIRA version 6.3 or higher
- JIRA secured using HTTPS
If you are using a read only LDAP or AD (Active Directory) system for user management, please see Installing with LDAP.
Depending on the deployment method you chose above, import the appliance into a compatible hypervisor or deploy an EC2 instance using a region specific AMI ID, then boot machine image.
The virtual machine uses DCHP for automatic network address assigning by default, depending on your network environment this may need to be configured.
You can access the virtual machine using SSH on port 22, with the credentials below:
- User: appliance
- Pass: appliance
Behave Pro can send email notifications to users associated with the issue that is being modified, for this to happen an SMTP server is required.
$ sudo nano /usr/share/behavepro/conf/application.conf
# Email notification Configuration smtp.host="" smtp.port=587 smtp.tls=true smtp.user="" smtp.password=""
Uncomment all the SMTP properties and replace the values with your email servers settings. If you prefer not to use the email notifications, ensure the properties have empty values (as above) and make a note to disable the functionality once installed. See end of guide.
$ sudo service behavepro restart
After making configuration changes Behave Pro will need to be restarted with the command above.
Behave Pro is required to use SSL by JIRA to create a secure bridge between the two, to support this requirement the virtual appliance ships with nginx preconfigured as a reverse proxy.
The configuration for the reverse proxy is available at
/etc/nginx/sites-enabled/behave.pro.conf and expects a valid SSL certificate at
/etc/ssl/behavepro.crt and its private key at
Both of the required files are created when either you generate a self-signed certificate or purchase one from a CA vendor. We recommend against using self-signed certificates in production environments as browsers will complain.
You may also need to update the
server_name property within
/etc/nginx/sites-available/behave.pro.conf to match the hostname that points to the virtual machine.
$ sudo service nginx restart
Nginx configuration changes require the service to be restarted.
Atlassian ConnectAtlassian Connect is required to provide a secure bridge between Behave Pro and JIRA so they are able to communicate. To install Connect for JIRA Server, download the following plugins and upload them to your JIRA add-ons manager.
Different versions of JIRA are required to use different versions of the Atlassian Connect plugins, select your version from the tabs below.
Connecting to JIRA
Once the Connect plugins are installed, installing Behave Pro is as straight forward as saving and uploading the descriptor file, this allows JIRA to install Behave Pro.
Save your descriptor file at
https://<server address>/atlassian/connect/atlassian-jira.json, then inside JIRA go to the add-ons manager (UPM) and select "Manage Add-ons", click on the "Upload add-on" button and upload the descriptor file.
Behave Pro Server License
To use Behave Pro, a license is required. A license or trial license can be requested from the Behave Pro website.
If you didn't use a valid SMTP in the previous steps you will need to ensure you disable email notifications from the Behave Pro configuration page to prevent send failures.
The configuration page can be accessed from the sidebar of the add-ons manager in JIRA or at