The examples below illustrate the Oracle 12.2 usage on the server with CentOS 7.


Overview

This article is intended to help customers who use ICE Trade Capture connection and provides the instructions for pure installation of ICE Trade Capture solution

Please note, if you have multiple connections (not only ICE Trade Capture) on the same FIXEdge instance, contact SupportFIXAntenna@epam.com to get full instructions.

Installation of the ICE Trade Capture solution

This section shows how to set up an ICE Trade Capture solution. It is assumed that:

Preparation

  1. Make sure you have sufficient administration permissions for further uninstall/install procedures;
  2. Download new ICE Trade Capture solution package for the corresponding OS version from the Client Space;
  3. Make sure the Oracle server is installed and available in the local network;
  4. Make sure you have a valid license (engine.license).
    If your license has expired or was lost, contact sales@btobits.com to obtain the new one;

Installation Process

  1. Unpack new version of ICE Trade Capture solution to the separate folder, e.g.: /opt/fixedge/;

  2. Create an Oracle schema for ICE trades storage:
    1. Connect to Oracle server using the privileges allowing the new schema creation

    2. Create a user, schema, and tablespace. To do it, execute the script 0_ECNMSO_script_schema.sql

    3. Create the ECN_TRADE TYPE: execute the script 1_ECNMSO_script_types_ECN_TRADE_TYPE.sql


    4. Create the tables: execute the script 2_ECNMSO_script_tables.sql 

    5. Specify the package MESSAGE_PACKAGE with stored procedures: compile the script 3_ECNMSO_script_packages_MESSAGE_PACKAGE.pks

    6. Compile the package MESSAGE_PACKAGE body: compile the script 4_ECNMSO_script_packages_MESSAGE_PACKAGE.pkb

  3. Add ODBC data source for the database on the server with installed FIXEdge

    The examples below illustrate the Oracle 12.2 usage on the server with CentOS 7.

    All actions must be performed on the server where the FIXEdge is installed.


    1. Install the appropriate Oracle client (see Instant Client Application)

    2. Set the environment variables listed below for the user used to run FIXEdge: 

      ORACLE_HOME=/usr/lib/oracle/12.2/client64
      
      TNS_ADMIN=/etc/oracle/
      
      LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/lib/oracle/12.2/client64/lib"
      
      PATH=$ORACLE_HOME/bin:$PATH
    3. Create the files listed below for the user used to run FIXEdge

      OracleConnectionName =
      (DESCRIPTION=
      (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521))
      (CONNECT_DATA=(SID=OracleServiceID))
      )
      [OracleODBCConnectionName]
      Description = test connect to ORACLE DB
      Driver = /usr/lib/oracle/12.2/client64/lib/libsqora.so.12.1
      ServerName = OracleServiceName
      DSN = OracleODBC-12c
      [OracleODBC-12c]
      Description = Oracle ODBC driver for Oracle 12c
      Driver = /usr/lib/oracle/12.2/client64/lib/libsqora.so.12.1
      # Driver Logging = 7 
      # "Driver Logging" is an optional parameter
  4. Adjust FIXEdge configuration
  5. In case several ICE Handler components should be used to connect to multiple ICE Trade Capture feeds:
    1. Create copies of the ICE Handler from the new package (libICEHandler-MD-x64.so in Linux package), give them names according to your specifics, and put them to the /bin folder;
    2. Adjust configuration according to p.4 above;
  6. Copy your FIXEdge license into the license file path;
  7. Install FIXICC Agent instance (means register the services in the system):
    1. For Linux: run installDaemon.sh as sudo from fixicc-agent\bin directory
  8. Start the new FIXICC-agent instance;
  9. Connect FIX Integrated Control Center (FIXICC) to fixicc-agent and start FIXEdge.

In order to ensure that the upgraded ICE Trade Capture solution was successfully setup, please check the FixEdge.log file:

  • Find the following record with the target FIXEdge version:

    2016-09-20 10:46:19,459 UTC   INFO    [CC_Layer]  5552  FIXEdge Version X.Y.Z (rxyz) started
  • Make sure there are no [ERROR] records in the log file.