Ensure you are fully registered with the exchange via the exchange website.
When you register on the exchange website, you are assigned a unique user ID, normally a seven-digit numeric string, which is used in FIX login messages. You will be given this ID in a later step.
Formally request the VPN Config files from your Account Manager.
The request should be coming from the same email you used in step 1. In your email you should include your public key (.pub file).
This .pub file will be used to encrypt the VPN configuration files. You will be able to decrypt the VPN config file with your generated private key. While it is an extra step, please remember that this is done for your security.
Your Account Manager will get back to you over a secure chat app with the following information:
FIX user id. This is used in FIX login messages.
FIX password. This is used in FIX login messages.
An archive file. This is password-protected and contains VPN config files.
A password file. It is encrypted with your public key.
Download an archiver that supports 7z files extraction. Usually most unzipping software should work.
Decrypt the the password file ( step 3.4) using your private key that was generated with the .pub file in step 2.
Use the decrypted password (step 5) to open the archived file (step 3.3) to obtain the VPN config files.
Create a VPN folder.
Install and configure an OpenVPN client.
Refer to your FIX endpoints and test the connection.
For redundancy purposes, there are two production end points for each FIX service type:
Order Routing - 10.197.5.94:4500 and 10.197.5.229:4500
Market Data - 10.197.5.94:4501 and 10.197.5.229:4501
Test connectivity by running the command ping 10.197.5.94 in a terminal window.
Repeat this for all of the IP addresses listed in this step.
Refer to the following values when populating specific fields in your FIX messages:
1/Account = account_<user id>
49/SenderCompID = login_<user id>
56/TargetCompID = “ME”
448/PartyID = <user_id>
553/Username = user_<user id>
554/Password = <password>