Before You Start

Welcome to developing applications with AMPS, the Advanced Message Processing System from 60East Technologies!

These guides will help you learn how to develop applications using AMPS.

Before You Start

Before reading this guide, it is important to have a good understanding of the following topics:

• Developing Applications in Java To be successful using this guide, you will need to possess a working knowledge of the Java language. Visit http://java.oracle.com for resources on learning Java.

• AMPS Concepts This guide focuses on using the AMPS client libraries and how those libraries work with the AMPS server.

  Before working through this guide, we recommend reading the Introduction to AMPS guide.

  Detailed explanations of the AMPS server behavior are in the AMPS Server Documentation.

You will also need a system on which you can compile and run code, and a server where you can host the AMPS server.

Setting up a development Instance

You will need an installed and running AMPS server to use the product as well. You can write and compile programs that use AMPS without a running server, but you will get the most out of this guide by running the programs against a working server.

Instructions for starting an instance of AMPS are available in the Introduction to AMPS guide.

The AMPS server runs on x64 Linux. The Introduction to AMPS and AMPS FAQ contain information on how to run an AMPS server on a development system that does not run Linux.

Upgrading from a Previous Version of the AMPS Java Client

The AMPS Java client is designed to maintain binary compatibility for hotfix versions, unless otherwise specified in the release notes.

For versions that introduce or change features, as indicated by a change to the major or minor version number, 60East cannot guarantee binary compatibility. An upgrade that changes either a major or minor version number may require a recompile from source. Changes that do not affect source compatibility are not generally noted in upgrade documents when the major or minor version numbers change.

For example, an upgrade from X.Y.1.0 to X.Y.1.1 of the Java client would be a drop-in replacement unless otherwise noted, as would an upgrade from X.Y.1.1 to X.Y.2.7. However, an upgrade from X.Y.2.7 to X.Z.0.0 may require that you recompile your application from source.