HOME | AFI/J DOCUMENTATION
AFI/J
Installation Guide...

   Application Fix Interface (c) 2003-2006 Octatec
   

The Application Fix Interface for Java (AFI/J) implements a simple Java API and Fix Engine providing FIX  protocol conectivity to other Fix Engines.

Note: You need JAVA to be installed on your system for the UNIX or Windows installation procedure to work!

At the end of this document, there is a quick guide to
Testing the Installation.

In both the Windows and Unix versions, there is an installation program that makes installing easy.

In the Windows version the Installation program is a self-extracting exe, just double click the downloaded EXE and installation will be started.

In the UNIX version, you should follow these simple commands…

mkdir install # name this directory anything you want
# ... download the $AFI_tar_gz file
# ... into your newly created directory
cd install
gunzip $AFI_tar_gz
tar xvf $AFI_tar
INSTALL
In the above list of commands $AFI_tar_gz represents the file name of the tar’d compressed AFI installation archive – it will have different names depending on whether it is a demo or a full version. $AFI_tar represents the name of the file after it has been uncompressed. INSTALL is a very simple installation script that allows you to install the application anywhere on your system, (you do not need to be root, unless you choose to install into a privileged directory)

The UNIX INSTALLATION should work on ANY flavour of UNIX, and indeed any Operating  system that supports a posix compliant shell.

Configuration

Configuration of the system is performed automatically during installation.

There is one very important file, fixgw.properties . This file is created during installation, it contains the location of JARs used by the system and the location of the java command. Every AFI/J application must have a fixgw.properties in its startup directory. Normally, you will never have to change this file, but if you nstalled a new JDK/JRE to a different location, changing the java= entry in this file would change the JDK/JRE to your preferred choice. During UNIX installation, JAVA_HOME must be set to a valid location of a java JDK/JRE such that $JAVA_HOME/bin/java exists. During Windows installation the registry is searched for a JavaHome entry; keys that are considered in the search are …
 

SOFTWARE\JavaSoft\Java Development Kit\1.2
SOFTWARE\JavaSoft\Java Runtime Environment\1.2
SOFTWARE\JavaSoft\Java Development Kit\1.3
SOFTWARE\JavaSoft\Java Runtime Environment\1.3
SOFTWARE\JavaSoft\Java Development Kit\1.4
SOFTWARE\JavaSoft\Java Runtime Environment\1.4
So you must have either the 1.2, 1.3 or 1.4 release of the Java SDK or JRE in order to install this application.

fixgw.properties

A typical fixgw.properties file looks like this under Windows...

Home=C:\\Program Files\\Octatec\\AFI_J\\1.00
Gateway=javaproc
Java=C:\\MyJavaJDK\\bin\\java.exe
AFIsrv=C:\\Program Files\\Octatec\\AFI_J\\1.00\\afi.jar
AFIcli=C:\\Program Files\\Octatec\\AFI_J\\1.00\\JFixGW.jar

You should not change this file, if you want to use an alternative JDK, you can change the Java= entrty, but don't change anything else.
 

Testing the installation

Whether you installed on WINDOWS or UNIX, you should have a directory structure as follows…

<installation dir>/Octatec/AFI_J/1.00/samples

  • afisrv
    • Run
    • Make
  • afitest
    • Run
    • Make


Go to the afisrv directory and type Run, this starts the test server program, then go to the afitest directory and type Run, this starts the test client program. These are 2 simple text-based menu-driven programs  that allows fix messages to be sent between them.

At the afisrv menu, issue an o and then a t
At the afitest menu, issue a 0
Return to afisrv and issue h (you should see a heartbeat message in the afitest program)

You can find more details about afisrv and afitest in the main documentation.

The Make commands in the directories compile the 2 test applications, the source code is also located in these directories.

NOTE for Windows Users...
In the WINDOWS installation, Run and Make are actually called Run.cmd and Make.cmd. If you have Windows 98 or 95, you will have to rename these to Run.bat and Make.bat and make minor changes within the file replacing %VARIABLE% substitutions with the actual value (This is because the .bat command processor runs out of Variable Space when building the classpath)
 


Home | FixGateway | AFI/J | SimpleGrid | SBpayroll | SXAzip | InstallScript | DiskUsage/DiskClean | Virtual Desktop Manager | ComBridge | Demos | Purchase