Cohesive FT Elastic Server On Demand

1. Overview

1. Select a package type from a dropdown list above.
2. Fill out the form. You will need to define package name, version, description as well as various other parameters - these will vary based on which package type you select.
3. If necessary, upload your file(s).
4. Launch the package build process.

2. Archives

Our current system accepts tarballs (uncompressed, gzip- and bzip2-compressed) and zip archives. Archive can not contain absolute paths (i.e, those which start with "/"). For example, when using tar, do NOT use -P or --absolute-names flags.

3. TCP Ports

Before you create your package, please note that the following TCP ports are used by some preconfigured services and will not be available for use within your application:

• 22/tcp - SSH
• 2999/tcp - Elastic Server Manager (web-based management console)
• 4433/tcp - SSL gateway to Elastic Server Manager
• 9090/tcp - Web Services for Elastic Server Manager

4. Package Types

4.1. Java Application or Library (JAR)

Upload JAR files, store them in a directory of your choice and optionally provide a main class to run. This package does not include any application containers.

4.2. Java Web Application (WAR)

Select a Java web application container and upload your WAR file.

4.3. Ruby on Rails Application Archive

Upload your archived RAILS_ROOT directory.

4.4. Mule Endpoint

Upload JAR files and XML endpoint definition.

4.5. Filesystem Tree Archive

This is a generic package type, it represents an archived filesystem subtree or can be used to upload regular files. You upload an archive of your software with its directory structure organized exactly like it will appear on the filesystem. For example, your achive might include foo/, foo/bar/, foo/bar/file1.txt, baz/, baz/file2.txt. The resulting package will include all your files and directories relative to a toplevel directory which you will define on the form (default directory is /usr/local).