Prerequisite guidelines

Check the following sections for the guidelines on default settings.

Note

The Administrators of the KX Refinery platform will provide connection parameters and will be required to provide the results from some tests. They may also be required to look at logs when resolving certain issues. The document details when the Administrators are involved: Administrator : <task>

Maven

The following checks should be performed before compiling the demo project.

Proxy server

If a proxy server is being used, make sure this is configured in the user's Maven user settings file.

Open a command prompt window. Enter the command.

ping proxy

If it does not already exist, create a Maven user settings file. Copy the global settings file from:

C:\Program Files\apache-maven-3.6.0\conf\settings.xml

Save it here:

%USERPROFILE%.m2\settings.xml

Update the proxies section:

<proxies>
     <!-- proxy Specification for one proxy, to be used in connecting to the network.-->
    <proxy>
      <id>dubproxy</id>
      <active>true</active>
      <protocol>http</protocol>
      <username></username>
      <password></password>
      <host>dubproxy.firstderivatives.com</host>
      <port>8080</port>
      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
    </proxy>
  </proxies>

FD internal Maven repository access

Update the servers section of the user's Maven user settings file (%USERPROFILE%.m2\settings.xaml).

  <servers>
    <!-- server
     Specifies the authentication information to use when connecting to a particular server, identified by
     a unique name within the system (referred to by the 'id' attribute below).
     NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are used together.-->
    <server>
      <id>internal</id>
      <username>username</username>
      <password>password</password>
    </server>
  </servers>

Delta Control

The following checks are for Delta Control side of the KX Refinery client API.

DNS lookup

The code should just work. If it doesn't, the most common issue is an incorrect DNS resolution.

Look for an error message in log ( logs\debug.log ). Here is an example:

2018-10-1013:29:28,582 [9756] ERROR DeltaApiCore.QueryRouter.Connection.Async.AbstractDeltaAsyncConnection - connect failed: QR:[ds_qr_a]:[s626207nj2sl01.uswhwk6.savvis.net:24032]. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.33.122.83:24032

Host IP should be <Choose relevant IP>

Administrator : Check how the query routers are configured in Delta Control:

Run the nslookup command in a cmd window to see how your PC resolves the host name.

nslookup

Below is an example of the output seen, this will be different depending on the client's server location:

If the host is not resolving correctly, the Windows hosts file will need to be updated, as below:

Open file using administrator privileges.

C:\Windows\System32\drivers\etc\hosts

Add a new line to the file.

Launch another cmd window and check the update.

Issues running queries (e.g. getTicks)

Administrator : Check that .pm.exas function is defined on the QR and QP processes.

Note

This is unlikely to be an issue with Kx Stream version 4.2 or above.

Issues publishing data

Administrator : On the messaging server process (e.g. emea_tr_ms_a.1 ) check that host column of the .dm.qipc table is correct.