Test Environment

MEFF makes available to Members and ISVs requesting access, a simulation environment, in order to facilitate the development and testing of proprietary applications.

Members can access the simulation environment through the secondary communications line.

Members who connect to MEFF using the colocation service, entities that are in the process of becoming members and ISVs can access the simulation environment without installing additional hardware, using HF MEFFGates installed in MEFF sites.

The simulation environment will normally run the same version as in the production environment. In addition to the current production versions of HF MEFFGate, future versions that are in the pre-deployment phase may also be available in the simulation environment. This will allow members to adapt their applications to the new version.

Members and ISVs need a user code to connect to the simulation environment. This code is composed of the Member code and the operator code.

Members have a code for the production environment composed of the letter "A" followed by three digits, eg. "A123". In the simulation environment, the "A" is changed to a "T", for example "T123". In case more than one simulation environment is available, the connection parameters will be communicated as needed.

One of the fields in the FIX logon message indicates whether the platform to which a user is connected is the production platform or a test environment.

MEFF will assign a fictitious member code to entities that are in the process of becoming members and ISVs.

The initialization data loaded in the simulation environment will normally have the same contracts as in the MEFF production environment.

For any queries related to the simulation environment, please contact

Copyright® BME 2024
[ ]