This documentation relates to an earlier version of Application Links.
View this page in the current documentation or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

This page describes an example of how to set up a common application links scenario — creating a two-way link between two applications that trust each other and share the same set of users. For example, you may wish to link your internal JIRA server to a private FishEye server. Setting up an application link allows you to take advantage of integration features like viewing FishEye changesets in JIRA. The instructions below also detail how to link two entities of your two linked applications, e.g. a JIRA project to a FishEye repository.

Applications Links is bundled with FishEye 2.4, Confluence 3.5, JIRA 4.3, and all later versions of those applications. In addition, Bamboo 3.1 is compatible with AppLinks. You can configure JIRA-to-Bamboo links via the JIRA administration screens. If one of the applications you are connecting to does not have Applinks, you can still set up an application link to it. See Adding an Application Link.

On this page:

Before You Begin

 

In this example, we will create a two-way Trusted Applications link between a 'local' FishEye server with Application Links ((http://fisheye.example.com/ in this example) and a 'remote' JIRA server without Application Links (http://jira.example.com/ in this example). We'll add the link from the FishEye server.

In FishEye, do the following: Log in as a system administrator and go to the administration page. Click 'Application Links' in the administration menu. The 'Configure Application Links' page will appear, showing the application links that have been set up. Click 'Add Application Link' to open the add application link wizard.

1. Specifying the Remote Application

First, we need to specify which application we are linking to. Enter the URL for the JIRA server in the 'Link to another server' dialogue, as shown in the screenshot below, and click 'Next'.

Screenshot: Entering the server URL

Gliffy Zoom Zoom

Enter an 'Application Name' and choose the 'Application Type' to be 'JIRA'. Click the 'Create' button. The application link will be created and displayed on the 'Configure Application Links' page.

Our JIRA server does not have Application Links, so we cannot automatically create a link back to our FishEye server nor set up authentication. We'll manually set these up in the next step.

Screenshot: Creating the application link

Gliffy Zoom Zoom

We are going to use Trusted Applications authentication for all incoming and outgoing requests via the application link, as both servers share the same userbase. Trusted Applications authentication is recommended when both applications fully trust each other and share the same set of users (read more about configuring Trusted Applications authentication). Other authentication configurations are described in Configuring Authentication for an Application Link.

On the 'Configure Application Links' page, click the 'Configure' link next to the application link just created. The configuration dialogue for the application link will be displayed.

First, we need to configure our JIRA server to trust our FishEye server. Navigate to the 'Outgoing Authentication' tab on the configuration dialogue and click the 'Configure' button on the 'Trusted Applications' sub-tab. Click the 'Apply' button to apply Trusted Applications authentication.

We also need to configure our FishEye server to trust our JIRA server. Navigate to the 'Incoming Authentication' tab on the configuration dialogue and click the 'Configure' button on the 'Trusted Applications' sub-tab. Click the 'Apply' button to apply Trusted Applications authentication.

Screenshot: Setting up Trusted Applications authentication (click to view larger image)

Gliffy Zoom Zoom

4. Additional JIRA Configuration

Our JIRA server does not have Application Links, so we need to perform additional Trusted Applications configuration in JIRA before our application link will work.

Follow the instructions on adding a trusted app in the JIRA documentation: Configuring Trusted Applications. You will need to enter the following information:

  • 'Base URL' — Enter the URL of your FishEye server, 'http://fisheye.example.com/'
  • 'Application Name' — Enter the name for your FishEye server, 'Example FishEye'.
  • 'Timeout' — '10000'
  • 'IP Addresses' — Leave this blank, unless you are using a proxy server (if so, see the Trusted Applications documentation for further instructions).
  • 'URL Patterns' — Enter the following URLs: /sr/jira.issueviews:searchrequest, /secure/RunPortlet, /rest, /rpc/soap

(tick) You may also want to enable issues activity in your activity stream. To do this, navigate to your Application Links and click the 'JIRA settings' link next to your application link. Tick the 'Include in 'Activity Streams' checkbox and click 'Save'.

Congratulations, you've just created an application link!

Configuring Project Links across Applications

 

Let's assume that you are managing a project or team. You would like to connect your project's Confluence space with your JIRA project, and link up your team's source repository too.

When you have connected your applications via Application Links, you can also connect the areas of those applications that contain information relating to your project or team. Using project links (also called entity links) you can associate one or more projects, spaces and repositories across the linked applications.

To connect all the information relating to the project or team that you are managing, you can link one or more of the following:

  • JIRA projects.
  • Confluence spaces.
  • FishEye repositories.
  • FishEye projects. A FishEye 'project' is the Crucible project if you have installed FishEye and Crucible, otherwise it is the paths associated via the 'FishEye Project Content' function in FishEye.
  • Crucible projects.
  • Bamboo projects.

    Icon

    Note, we do not recommend the use of project links with FishEye 2.9 and later, if you have JIRA 5.0 or later as well as the latest version of the JIRA FishEye Plugin. This is because application links now provide all of the functionality previously available with project links. However, project links are retained in FishEye and Crucible for the following reasons:

    • Setting up project links provides a way to restrict the scope of JIRA searches, which can provide performance benefits.
    • Legacy configurations can continue to use project links without any need for changes.
    • Third-party plugins may continue to rely on project links for their functionality.

In the following example, we'll create an two-way project link between a JIRA project (project key is 'MYPROJECT') and a FishEye repository (repository key is 'MYREPO'), for the application link we previously created.

First, navigate to the FishEye administration console and find the repository that you want to link from. Click the icon and select 'Application Links' from the dropdown menu. The project links screen will be displayed.

Screenshot: Project links for a FishEye repository

Click 'Add Link' and click the remote application where the target project is located. In this case, it will be the 'Example JIRA' application that we linked to previously. The add project link dialogue will be displayed.

Screenshot: Adding a project link

Enter the key ('MYPROJECT') and an alias, i.e. display name, for the project ('My Project'). Click 'Create' to create the project link.

Congratulations, you've just added a project link!

What Next?

 

You've now successfully linked your JIRA server to a FishEye server. Try out some of the integration features enabled by your new application link, including:

  • No labels