Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 9 Next »

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, as follows:

Client deployment

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

  • 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
    Default location: C:/inetpup/Kodiak_Derivatives_Server/Reports
    IIS virtual path: http://localhost/kodiak_derivatives_reports
    Authentication: Windows Authentication and ASP.NET Impersonation
  • Batch
    Default location: C:/inetpup/Kodiak_Derivatives_Server/Batch
    Creates a default task in Task Scheduler that runs dividends calculation and bonds calculation jobs


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. 

  • No labels