Deployment

The deployment of Derivatives system is divided between the client to be deployed on remote computers and the services to be deployed on the server, the database and other optional components.

Client deployment

The client can be deployed via .msi file or clickonce. Client comes preconfigured for each customer.

• Before deployment, a DNS name or IP address needs to be provided for the server that runs the Derivatives services and the OMS services respectively, although usually the same server
• To run the client, user needs to be authorized and authenticated

Server deployment

Server components are deployed by .msi file supplied preconfigured for each client from Kóði.

The following components are set up

• Service
• Backoffice
• Reports
• Batch

SQL setup

• MSSQL database required
• Database name should be KodiakDerivatives
• An db users should be created with full privilege (Owner)
• DB owner needs to have read privilege on the Kodiak OMS database
• SQL script will be provided by Kóði 

Mifid2 reporting

Kodiak Derivatives can report daily activities to FME authorities via Libra's DropZone. 

Mifid2 reporting consists of 3 sql modules,

• [KodiakDerivatives].[dbo].[ReportTransactions]
  a view that gathers the appropriate data
  This needs to be updated with correct LEI code for the customer
• [KodiakDerivatives].[dbo].[SubmitReportedTransactions]
  a stored procedure that selects the data from the view for today and inserts into the Libra reporting table.
  This needs to be adjusted for the naming scheme for Libra in the customers database. 
• [KodiakDerivatives].[dbo].[Scheduled Task]
  an sql server agent scheduled task that calls the stored procedure.
  This should run at the end of the day when all operations for the day has stopped.