About Atlassian Jira Plugin

Atlassian Jira Plugin provides protection and proactively monitors the Atlassian Jira environment’s, configuration data, services, and application data files.

Supported Versions and Platforms

• Atlassian Jira Server supported versions: all 7.x released versions starting with v7.0 up to and including v7.11
  • deployed on any of the following operating systems (where compatible):
    
    • Windows Server 2008 R2
    • Windows Server 2012
    • Windows Server 2012 R2
    • Windows Server 2016

• using one of the following Databases either local or remote (where compatible)
  • PostgreSQL 9.3, 9.4, 9.5, 9.6 – with PostgreSQL Plugin if the database is local
  • MySQL 5.6, 5.7 – with MySQL Plugin if the database is local
  • Oracle 12c – with OracleDatabase Plugin if the database is local
  • SQL Server 2012, 2014 – with SQLServer Plugin if the database is local
  • H2 (embedded - evaluation only)

Note: The Atlassian Jira Plug-in supports more instances of Atlassian Jira of any supported version, using any supported database, installed on the same server.

Install/Uninstall the Atlassian Jira Plugin Via the Neverfail Advanced Management Client

The Atlassian Jira Plugin can be installed either via the Neverfail CE deployment process or by using Application -> Plugins in the Neverfail Advanced Management Client using the procedure below. Neverfail recommends that for initial deployments of Atlassian Jira Plugin, installation should be performed using Engine Management Service.

To manually install the Atlassian Jira Plugin, follow the steps below:

1. Unzip the Atlassian Jira Plugin to the desired location.
2. Launch the Neverfail Advanced Management Client.
3. Navigate to Application -> Plugins .
4. Click on the Install 
5. Click the Browse button and navigate to the location of the <plug-in name>.dll 
6. Click OK to complete the installation.
7. Repeat this process for each individual plug-in.

To remove/uninstall the Atlassian Jira Plugin, follow the steps below:

1. Launch the Neverfail Advanced Management Client.
2. Navigate to Application -> Plugins .
3. Select the desired plug-in to be removed/uninstalled.
4. Click on the Uninstall button in the 'Plugins' pane.
5. When the plug-in is uninstalled, the files are not removed. This is by design for future functionality and therefore the following workaround is provided:
   • Copy the contents of the r2\plugins\<sponsor>\<version> folder to a different location (e.g. C:\temp).
   • Delete the contents of the r2\plugins\<sponsor>\<version> 
   • To reinstall the plug-in, when prompted for the location of the plug-in files, navigate to the new folder location (e.g. C:\temp).

Note: As an alternative, reinstallation can be accomplished by using the downloaded files from the original download location after removing the plug-in.

Important: Removing Jira instances from protection can be done via Applications Edit Plug-ins dialog, enumerating Jira services names. Their configuration data, services, and application data files will be excluded from protection.

Monitoring

For Atlassian Jira Plugin, monitoring consists of the following:

• Service Availability Monitoring
• Application Monitoring
• Application Health Monitoring 

Service Availability Monitoring

Neverfail Engine monitors services specified by the plug-ins to ensure application availability. In the event that a specified service stops or fails, Neverfail Engine can take up to three pre-configured actions to remedy the issue.

Application Monitoring

Tasks - The following 'Tasks' are installed by Atlassian Jira Plugin:

• Periodic
  • Protected Services Discovery
  • File Filter Discovery
  • Registry Filter Discovery

To configure/modify Periodic 'Tasks', follow the steps below:

1. Using the Neverfail Advanced Management Client, click on Application -> Tasks .
2. Select the desired 'Task'.
3. Click on the Edit button at the top of the 'Tasks' pane.
4. Configure/modify the 'Interval' field.

Note: 'Interval' is the only field available for configuration/modification and is measured in seconds.

5. Click OK to save the changes.

Note: This dialog is also used to Enable/Disable the selected 'Task'.

Application and Performance Monitoring 

Rules – The following 'Rules' are installed by Atlassian Jira Plugin:

• Application availability
  • Atlassian Jira Health check: verifies website availability for every protected Jira instance. The rule is triggered when one of the websites cannot be reached.
• Login check
  • Jira Login: checks the Jira login for the configured URL, username and password. The rule is triggered when the login fails.

• This rule is configure by default with http://localhost:8080 URL and needs user’s configuration.
• There are as many visible Jira Login rules as Jira instances detected on the server (limited number)1.
• If two or more instances of Jira have the same login credentials, the same rule can be used for those instances, enumerating the URLs of the instances separated by semicolon. 

Note: 1 The number of Jira Login rules is limited to 10.

Atlassian Jira Plugin

When the plug-in is installed, all protected services will be set to manual unless otherwise stated.

This is the list of all services protected by this plug-in for each Jira instance:

• JIRASoftware<timestamp>

Note : The following databases are protected by their own plugin:

• SQL Server 2012, 2014 – SQLServer Plugin
• MySQL 5.6, 5.7 – MySQL Plugin
• Oracle 12c – OracleDatabase Plugin
• PostgreSQL 9.3, 9.4, 9.5, 9.6 – PostgreSQL Plugin

Applies To

Atlassian Jira Plugin