01283 500255 enquiries@sfl.co.uk

Connecting – BT and SWIFT

In real CREST, an organisation requires a Secure Network Gateway provided by either:

  • SWIFT Alliance Gateway
  • BT Radianz Settlenet Gateway

To aid connectivity to the CREST Simulator, we support both networks methods of file tranfer.  This document outlines a brief overview of the file transfer process.

Note: SWIFT or BT should be contacted for a more detailed description of the processing.

SWIFT File Transfer

Directory Structure

Swift uses the following directory structure without any triggers.

Transmit to CREST (or Sim) Directories:

  • /OPER/inp         << Data directory
  • /OPER/inp_bak << Once transferred, the data file from INP is moved to here

Receive from CREST (or Sim) Directories:

  • /OPER/out >> Data directory
  • /OPER/out_bak >> Date directory archive

File Names

File sending to CREST/Sim;

  • A “I”HHMMSS.JUL file is sent through the INP directory.
  • Once a “I” file is transferred it creates a “T”HHMMSS.JUL file in the INP directory to signal a successful send.

Response Files from CREST/Sim;

  • Files coming back from CREST are “O”HHMMSS.JUL.

Julian Day

The JUL extensions represent the Julian Day.

X Mode File Testing Options

The SWIFT gateway has a X mode testing options which allows for reflex testing.   I.e. you can a file with :79:/HMDE/X, and it will generate a return file based on the details of this file.

File Headers and Footer Tags

It is possible to configure the Swift Gateway to use file headers and trailers.   

  • :SENDERREFERENCE: tags to the start of a file.
  • :EndOfText: tags to the end of file.

The show tags are the minimum requirement and many other tags can be used.  However, the Simulator does not process the tags.

 

BT Radianz Syntegra File Transfer

Directory Structure

Syntegra uses the following directory structure;

Transmit to CREST (or Sim) Directories;

  • /OPER/transmit/pending   << Data directory – Should be placed first and only once transfer is succesfull does it then create the following DO file
  • /OPER/transmit/do            << Trigger files for corresponding data file in transmit/PENDING
  • /OPER/transmit/done        << Once transferred, the trigger file from DO is moved to here
  • /OPER/transmit/success   << Once transferred, the data file from PENDING is moved to here
  • /OPER/transmit/status      << Once transferred, a status file is created which is used by some systems to flag the result of the transfer to crest
  • /OPER/transmit/fail           << Files that cannot be sent to CREST are places here. NOTE: The CREST Simulator does NOT use this.

Receive from CREST (or sim) Directories;

  • /OPER/receive/done          >> Trigger files for corresponding data file in receive/SUCCESS
  • /OPER/receive/success     >> Date directory (file of same name as trigger in DONE
  • /OPER/receive/status         >> status directory. A status file is created which is used by some systems to flag the result of the transfer from crest.

File Names

  • Inbound: “I” + File Sequence
  • outbound : “O: File sequence and continue sequence id as extension

Status Files

Syntegra uses status files that are created when a file is either SENT or RECEIVED from CREST. The files contains either 0000 to show success or 0000 and a path to the created file.

An extended method provides more information about the file.

File Headers and Footers

Syntegra does not added or remove anything from the files being sent or received from CREST