1. Check supported platforms
Better check thepage first; it lists the application servers, databases, operating systems, web browsers and JDKs that we have tested FishEye with, and that we recommend.
Atlassian only officially supports FishEye running on x86 hardware and 64-bit derivatives of x86 hardware.
2. (recommended) Create a dedicated FishEye user
For production installations, we recommend that you create a new dedicated Windows user that will run FishEye on your system. This user:
- Should not have admin privileges.
- Should be a non-privileged user with read, write and execute access on the FishEye install directory and instance (data) directory. These directories are described below.
- Should only have read access to your repositories.
If you have created a dedicated FishEye user, ensure you are logged in as this user to complete the remaining instructions.
3. Check your version of Java
In a command prompt, run this:
The version of Java should be 1.8.x.
The recommended way to install FishEye is to use the installer, which installs FishEye as a Windows service – see step 5 below.
4. Check that Windows can find Java
Windows uses the JAVA_HOME environment variable to find Java. To check that, in a new command prompt, run:
You should see a path to the Java install location. We recommend that this path does not contain spaces, and that JAVA_HOME should point to the JDK home path.
5. Now it's time to get FishEye
Download the FishEye installer from the Atlassian download site.
There are 32-bit and 64-bit installers for FishEye on Windows. Each installer adds FishEye as a Windows service, and starts the service, automatically. The express install creates, by default, a
Data directory and a separate install directory in
C:\Atlassian. The custom install mode allows you to choose different locations for the install and
Data directories, with the restriction that the
Data directory must not be contained in the install directory.
- The installer creates the
FISHEYE_INSTsystem environment variable. This points to the location of the instance (data) directory.
- The path to the installation location is referred to as the
<FishEye install directory>
- You need separate FishEye instance (data) directories if you want to run multiple copies of FishEye.
- If you expect to have a large number of users for this FishEye installation, and FishEye will be connected to an external database, consider installing FishEye on a different server from the one running the external database, for improved performance.
- If you have a large number of repositories, we recommend you increase the default number of files that FishEye is allowed to open. See the following knowledge base article for more info: Subversion Indexer Paused with "Too many open files" Error.
For FishEye 3.4.4 and later, you can edit JVM parameters for the Windows service by going to Start > All Programs > FishEye > Configure FishEye. Ensure that you restart the FishEye service when finished. Do not reference any environment variables in the settings (e.g. %FISHEYE_INST%). Instead, set the actual path.
6. Visit FishEye!
Give the FishEye service a minute to launch. Then, in a web browser on the same machine, go to
http://localhost:8060/ (or, from another machine, type
hostname is the name of the machine where you installed FishEye).
Enter your license, then an admin password, to finish the setup. Note that this password is for the 'built-in' FishEye admin user. You can log in as this user, if necessary, by clicking the Administration link in the page footer. See also How to reset the Administration Page password in FishEye or Crucible.
You can postpone setting up JIRA integration until later if you wish; see
7. Add repositories
Now you can tell FishEye about any existing repositories you have. Please read Starting to use FishEye for the details.
FishEye will perform an initial index of your repositories, during which it accesses, indexes and organizes a view of your repositories (including all historical items) back to the earliest commits. If you are evaluating FishEye, we suggest that you index a single project, so you can use FishEye as soon as possible. If you choose to index your entire repository, be aware that this can take a long time (possibly days) for massive or complex repositories and can be more complex to set up (especially for Subversion). The basic process is slightly different for each SCM type.
8. Add users and groups
9. Set up your mail server
Configure the FishEye email server so that users can get notifications from FishEye. See
10. Connect to an external database (recommended)
If you intend to use this FishEye installation in a production environment, it is highly recommended that you use one of the supported external databases. See
11. Stop FishEye (optional)
Control the FishEye service from the Windows administration console. Alternatively, in a command prompt, change directory to
<FishEye install directory> and run this:
12. Tuning FishEye performance
To get the best performance from your new FishEye installation, please consult Tuning FishEye performance.