Content Comparison

This topic provides an overview of CME's Canadian Trade Repository (CTR). It details supporting functions, workflows, message flows, and interfaces to allow registered users to submit and retrieve swap data in the CTR. CTR leverages existing CME repository and clearing services connectivity, functionality, and processes in order to accept, store, and report swap data.

...

1. Obtain a Legal Entity Identifier (LEI).
   
   An LEI is strictly required at the time of full registration. An LEI is required for each separate legal entity for whom data will be submitted or retrieved in the CME CTR. Users may acquire a LEI through one of the authorized LEI issuers listed in http://www.leiroc.org.  An LEI obtained previously for a legal entity to satisfy other business purposes (including trade reporting in a different global jurisdiction) may be used in the CME CTR registration if the issuer is recognized on the LEI ROC website.
   
   CME Central Counterparty (CCP) LEI's provided for reference:
   • CME ChicagoMercantileExchangeInc.(USClearingHouse) 
     
     • CME Inc. LEI: SNZ2OJLFK8MNNCLQOF39
       
     • CME Inc. UTI Namespace: 1010000023
2. Execute the agreement (User Agreement or Service Provider Agreement).
   
   User Agreement:  Entered into by a party to a derivatives transaction; the agreement enables the registered user to (1) submit, (2) analyseanalyze/filter, (3) extract, and (4) authorize their counterparty or service provider (not a party to the transaction) to view its derivative data stored in CME CTR. In order to execute the CME CTR User Agreement:
   • Download the agreement from the CME CTR website www.cmegroup.com/ctr. Complete the user agreement and click select the send button to electronically submit the agreement to the CME CTR Registration team.
   • The user agreement is received and processed by the CME CTR Registration team. Notification of receipt of the submission is provided, and a subsequent notification is sent when the registration is completed. In the registration complete email, instructions are provided to contact the CME registration team to receive the login information over the phone (for security reasons).
   • Schedule A (CME CTR registration entity details): A required form as part of CME CTR registration. Firms are required to specify at least one Verification Officer upon registration. The Verification Officer acts as the account administrator--approving any new requests, access modifications, etc. In addition to a Verification Officer, regular users are also requested. Verification Officers have a choice of admin roles or view only roles. Admin roles allow users to upload, amend, and view; whereas a View Only role allows for read only access to the CTR.
   • Schedule C: bulk registration for investment advisors or multiple entities under the same corporate structure. Schedule C is available from www.cmegroup.com/ctr.
     

...

For more information on establishing an MQ connection or leveraging an existing MQ connection with CME, please send an email to repositorysupport@cmegroup.com.

Web Services

CME CTR allows programmatic submissions, cancellations, and amendments via secure http web services. This web service submission facilitates connection to the CME CTR via the internet, removing the need for any other type of connectivity infrastructure (such as MQ). Either FiXML or CSV formatted data may be passed via this transport method. Full technical details are available below:

...

Please note:  Public key may not be required as it is dependant dependent of the connection method you use

...

If you don’t have an RFC4716 Public Key file yet installed at CME
Here are the steps, you’ll need to have the Public Key file named “USERNAME” “USERNAME,” which contains the keys in keys in the local directory on your source host in order for these steps to work:

...

The folder will have two sections: Incoming and Outgoing. Files must be dropped for upload into the incoming section, and reports can be pulled from the outgoing section. There will be a response file in the outgoing file, which is prefixed with ‘res_’ to the data file.  There is an acknowledgment for each file; if the data is successful, the response file will simply contain ‘success’‘success.'  If there are errors the response file will be larger and will contain ‘error’ and give a detailed message explaining the failure.    Duplicate submitted records are rejected with an appropriate error message and for every 1 file submitted into incoming there will be 2 files in outgoing (the original file submitted and the results file).  Files dropped in the incoming folder to upload in the TR should be asset class specific.

...

3. Enter your username and password and click select “Generate Token”Token." It should give you your authentication code for using for using web service in Token text field. You will have to use valid username and password which that is authorized by CME by CME Repository Support Group during Registration. (Make sure you have already changed the temporary password temporary password provided during registration. You can use https://ctruinr.cmegroup.com/ctrui/ to change your temporary password. It will prompt you to change the password when you login first time)

...

1. Open https://ctrws.cmegroup.com/datacapture-ws/ctr/submitCSV/CMDTY URL in IE.
2. Click on Select Lock image and click on select View Certificate. You will see following dialog box.

3. Open Certificate Path Tab and select VeriSign as shown in image below.

4. Select Details tab and click select “Copy to File” and Click select Next.


5. Select first format option of “DER encoded binary X.509 (.CER) on “Certificate Export Wizard” dialog and click Next select Next as shown in below screen shot

6. Specify file name and local path to store the certificate on your local machine (e.g C:/etrwsnr.cer)
7. Click Select Next and Finish. It will save the certificate locally on your machine in C:/etrwsnr.cer file, which we will import will import to your local java keystore.
8. Open DOS command window
9. Type following command at DOS prompt to create and import the certificate in local keystore.

...

10. It will prompt you for password for your keystore. Enter any password which that you will be passing later to your Web your Web Service client along with path to the keystore you will be creating (e.g., password “trwsnrclient”). Hit enter keyenter key. Retype same password and hit enter key again. 
11. Type “yes” for Trust this certificate? [no]. Hit enter key. You should see last line as “Certificate was added to keystore” as shown in following screen shot.