This documentation relates to an earlier version of FishEye.
View

Unknown macro: {spacejump}

or visit the current documentation home.

This page describes the initial configuration of FishEye, including the steps contained in the FishEye setup wizard.

Initial Configuration

FishEye runs its own HTTP web server, and additionally listens on a socket for administration/shutdown commands. These default to :8060 and 127.0.0.1:8059 respectively. You can change both these addresses before starting FishEye by editing config.xml.

On this page:

Running FishEye for the First Time

To run FishEye for the first time:

  • Windows の場合

    C:\> cd FISHEYE_HOME\bin
    C:\FISHEYE_HOME\bin> run.bat
    
  • On UNIX-based systems:

    $ cd /FISHEYE_HOME/bin
    $ ./run.sh
    

Once started, FishEye will run its own HTTP web server, on port 8060 by default.

You can access FishEye immediately by going to http://HOSTNAME:8060/ in a browser.

If you want to run FishEye as a Windows service, please refer to Run FishEye as a Windows Service.

Setting the Administration Password

The first time you run FishEye, when you access the FishEye web server you will be asked for:

  • An administrator password. This password controls access to the FishEye Administration pages.
  • A license key. You can get a trial license from the Atlassian website.

If you need to reset the administrator password, delete the admin-hash attribute in the <config> element. You will be prompted to enter an administrator password next time you start FishEye. See How to reset the Admin password in Fisheye or Crucible.

Integrating FishEye with JIRA

アプリケーションを JIRA に接続し、JIRA で情報を共有しながらユーザーの管理もできます。JIRA がインストールされている場合は、アプリケーションのインストール時、設定ウィザードに JIRA との連携設定ボタンが自動的に表示されます。これは、ほとんどのオプションを標準条件とした状態で JIRA との連携を設定するためのものです。

また、JIRA への接続設定はアプリケーションの管理画面からでも行えます。その場合、接続は個々に設定する必要があります。連携プロセスは 2 箇所で行います。

  • JIRA - アプリケーション間のP2P リンク:情報共有と連携機能を円滑にします。このリンクはアプリケーションリンクから設定します。
  • アプリケーション - JIRA 間のクライアントサーバーリンク:ユーザーとグループの管理を JIRA サーバーに割り当てます。

要件: JIRA 4.3 以降が必要です。

For detailed instructions and troubleshooting, see Configuring JIRA Integration in the Setup Wizard.

Accessing the Administration Pages

Once you have set up an administrator password, you can access the administration pages at http://HOSTNAME:8060/admin/.

One of your first steps will be to add a repository.

You will also want to read about the command-line options for controlling FishEye.

You can disable FishEye's Administration pages by setting admin-hash="" in the <config> element of config.xml before starting FishEye.

What's Next?

Want a hands-on tour of the best FishEye features? See FishEye 101.

12 Comments

  1. user-3f4ab

    this page only mentions the "run" batch file / shell scripts. what about the "start" and "stop" scripts? what are they for?

  2. user-3f4ab

    Also you ought to refer to configuring fisheye as a windows service (http://confluence.atlassian.com/pages/viewpage.action?pageId=91554194), since that is the normal desired behavior on a Windows system. Using the "run" script is ok to try running fisheye, but it's not a normal method on Windows.

    I did this previously for 2.0.6 (using the wrapper package), and upon upgrading I forgot about it, and was confused how to upgrade. I had to google "fisheye windows service" and after a bunch of puzzling, finally realized that I just needed to copy the "wrapper" directory, stop the old service, and run the new service (through the Fisheye-Uninstall-NTService.bat and Fisheye-Install-NTService.bat scripts in the wrapper/bin directory).

  3. Jeffrey Silverman

    This comment applies to running bin/run.sh on Solaris 10.

    The "bin/run.sh" and the sub-scripts that it calls are not, strictly speaking, portable. The "/bin/sh" on the first line of fisheyectl.sh, for example, depends on "sh" actually being "bash". This is true on Linux systems but not, for example, on Solaris. I was getting an error:

    /opt/fisheye/bin/fisheyectl.sh: syntax error at line 49: `FISHEYE_OPTS=$' unexpected
    

    I changed the first line of fisheyectl.sh to

    #!/usr/bin/bash

    And this issue was resolved.

    1. Toby Thain

      Quite correct, I fixed the same issue on Solaris 10 last week.

      Unfortunately bash is not /usr/bin/bash on a typical Linux system, so {{ #!/bin/bash }} might be the most portable path; that's valid on my Solaris 10 release.

      Speaking of Solaris, a bundled SMF manifest would be nice. I've hacked one up for my purposes.

      1. Jeffrey Silverman

        Sweet. Please post or link to your SMF manifest. thanks!

        1. Toby Thain

          I didn't have much luck with the code markup above, so to be on the safe side, here's a link:

          http://telegraphics.com.au/~toby/fisheye.xml.txt

          1. Anonymous

            thanks for this, Toby

  4. burhan

    I'm not sure what is wrong, but here is my setup:

    1. Windows Server 2008
    2. Java 1.6.0
    3. Fisheye version 2.4.3 (extracted to D:\fecru-2.4.3)

    When I type run.bat from bin, I get the following:

    2010-12-09 04:26:08,973 ERROR main fisheye.console com.cenqua.crucible.model.managers.PermissionManager-getDefaultPermissionScheme - No default permission scheme exists
    2010-12-09 04:26:08,988 ERROR main org.springframework.web.context.ContextLoader org.springframework.web.context.ContextLoader-initWebApplicationContext - Context initialization failed
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'linkerService': Autowiring of fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.cenqua.fisheye.syntax.LinkerFactory com.cenqua.fisheye.syntax.DefaultLinkerService.linkerFactory; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'linkerFactory' defined in URL file:/D:/fecru-2.4.3/fisheye.jar!/com/cenqua/fisheye/syntax/LinkerFactory.class: Unsatisfied dependency expressed through constructor argument with index 1 of type com.cenqua.crucible.model.managers.ProjectManager: : Error creating bean with name 'projectManager' defined in URL file:/D:/fecru-2.4.3/fisheye.jar!/com/cenqua/crucible/model/managers/impl/DefaultProjectManager.class: Invocation of init method failed; nested exception is org.hibernate.PropertyValueException: not-null property references a null or transient value: com.cenqua.crucible.model.Project.permissionScheme; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'projectManager' defined in URL file:/D:/fecru-2.4.3/fisheye.jar!/com/cenqua/crucible/model/managers/impl/DefaultProjectManager.class: Invocation of init method failed; nested exception is org.hibernate.PropertyValueException: not-null property references a null or transient value: com.cenqua.crucible.model.Project.permissionScheme

    Followed by a very large trace. Any ideas?

    1. Same Prob under SLES 11 and JDK 1.6 with Fisheye 2.4.3

      1. Anonymous

        Got the same issue...

        1. Andrew

          Hi,

          Please raise a support request at http://support.atlassian.com. One of our support staff will assist you.

          Kind Regards,
          Andrew

  5. Ivan Demkovitch

    I'm running JIRA and Confluence and had no issues. Confluence runs behind IIS and JIRA runs behind Apache server with SSL. All on Windows server machines.

    I've got Fisheye setup. First of all - it seems to be huge PITA to run it as a service. Instructions here is a joke and everyone have issues it seems: Run FishEye as a Windows service

    Next, if I want to integrate it with my JIRA - I need to expose FishEye on SSL and proxy out through Apache. Instruction here shows how to do SSL: FishEye SSL Configuration, but I need to run behind Apache server (and reuse Apache SSL) : Integrating with Other Web Servers However it doesn't show how I run and make proxy through SSL on Apache.

    And before all that - I'm having various issues / errors linking to and from JIRA. After about 10hr wasted - I don't feel like I want to try harder. My point is that install need to be little easier than that. I don't think my setup is unique or unusual. I think 90% of installs will run behind Apache or other server.

    I'm not even mentioning Crucible. It supposed to work there as well, and it seems to be with FishEye but how it integrates? Where is data?  It just becomes huge frustration. Please make it easier to setup..

    Why can't we have detailed HOW TO on integrating JIRA and FishEye to show what ports used to communicate, how to setup, etc, etc.