Getting Started

[ Prerequisites ] [ Downloading Galaxy ] [ Running the Standalone Galaxy Application ] [ Configuring the WAR ] [ Logging into Galaxy ]

This page describes how to get started with Galaxy. For information on what's new in this release, see Galaxy 1.5.3 Release Notes.

Prerequisites

Ensure that you have met all the prerequisites in this section before you download Galaxy.

Java

Galaxy requires you to have Java 5 or later installed. For validation of WSDLs to work correctly (part of the WS-I BasicProfile), you must have Java 6 (version 1.6.0_10 or later) installed, or endorse Xerces by adding the following libraries to your $JAVA_HOME/jre/lib/endorsed directory:

• Xerces
• xml-apis
• Xalan

If you use Java 5 and do not endorse these JARs, you will get an error message warning you that schema validation does not work correctly. This is because of a bug in Java 5.

Environment Settings

You must have at least 128MB of heap memory available to your JVM. If you are running MacOS X, you might need even more. If you will be running Galaxy as a standalone application, you can add the -Xmx128m switch to the java command when you run Galaxy. If you will run Galaxy in a servlet container, see your container's documentation.

Additionally, Linux and UNIX users might need to increase the maximum number of open file handles in the system to 2048 or higher. Otherwise, JAR indexing could fail under load (such as when uploading Mule via Mule NetBoot). For instructions, see http://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files.

Downloading Galaxy

To download Galaxy Community Edition, go to the download page. To download Galaxy Enterprise Edition, go to the customer portal download page (customer login required) and click the link for the JAR or WAR, depending on whether you want to run Galaxy as a standalone application or embedded within a servlet container. Save the file to the directory where you want to run Galaxy (for example, you might create the folder C:\Galaxy).

To run Galaxy as a standalone application, see the next section. To run the Galaxy WAR in a servlet container, configure it using the Galaxy Configuration Utility (available with Galaxy Enterprise only), and then deploy it to your servlet container as described in your container's documentation.

If you want to work directly with the Galaxy source code, see Source Repository.

Running the Standalone Galaxy Application

After you have downloaded the standalone Galaxy JAR, type one of the following strings in a command window:

This will start Galaxy on http://localhost:8080.

To specify a different port, use the httpPort argument. For example:

java -Xmx128m -jar galaxy-web-standalone-1.5.1.jar --port 9090

Always leave the command window open while Galaxy is running.

To stop Galaxy, enter Ctrl-C in the command window before you close it. If you do not stop Galaxy properly before you close the command window, the process will still run in the background. If you then try to run Galaxy again, it will create a new instance that will conflict with the running instance, and Galaxy will not start. If you accidentally close the command window without stopping Galaxy first, you must shut down the Java process manually.

When you see the message INFO: Started SelectChannelConnector@0.0.0.0:8080, you are ready to log in to Galaxy.

Configuring the WAR

If you are a Mule ESB Enterprise customer and you want to run the service registry in a servlet container, you can use the configuration utility (available with Mule ESB Enterprise only) to configure the deployment options. For details, see Configuration Utility.

Logging into Galaxy

To log into Galaxy, point your web browser to http://localhost:8080 (your URL may be slightly different if you've embedded Galaxy in your servlet container or you've used a non-default port). The initial user name and password are admin.