Page tree
Skip to end of metadata
Go to start of metadata

Overview 

This document contains description of REST Initiator Transport Adaptor for FixEdge and common steps required to configure and use it. 

FIXEdge REST initiator adaptor is a module in FIXEdge which sends FIX message from Business Layer to destination system as an http(s) REST POST request. 

Features 

Outgoing message representations 

An outgoing HTTP message body can be formed in several modes:

  • Raw FIX message with SOH as a delimiter
  • JSON representation of FIX messages tags and values
  • content of 213 tag  of FIX message

Example of raw FIX message (pipe symbol stands for SOH symbol): 

8=FIX.4.2|9=153|35=D|49=BLP|56=SCHB|34=1|50=30737|97=Y|52=20000809-20:20:50|11=90001008|1=10030003|21=2|55=TESTA|54=1|38=4000|40=2|59=0|44=30|47=I|60=20000809-18:20:32|10=061| 


Example of JSON message (contains repeating groups)

{"35":"E","50":"30737","116":"OMS1","52":"20150101-01:01:01.080","66":"List1","394":"3","68":"2","73":[{"11":"0003","67":"1","100":"DSMD","55":"MSFT","54":"1","38":"100"},{"11":"0004","67":"2","100":"DSMD","55":"IBM","54":"2","38":"200"}]}




BeginString(8), BodyLength(9), SenderCompID(49), TargetCompID(56) and CheckSum(10) tags are not inserted in output JSON file. 

In case of the third option (receiving 35=n message) the value of 213 tag will be extracted and sent. See the example below (the value of 213 tag is marked orange):

Input (from BL)

Output (sent to destination system)

8=FIX.4.4| 9=259| 35=n| 49=0| 56=0| 34=1| 52=20200317-10:23:55.068| 212=201| 213=8=FIX.4.4| 9=168| 35=E| 49=0|

56=RESTAdapter| 34=1| 50=30737| 66=List1| 116=OMS1| 52=20191101-11:11:01.080| 394=3| 68=2|

73=2| 11=0003| 67=1| 100=DSMD| 55=11| 54=1| 38=100| 11=0004| 67=2| 100=DSMD| 55=12| 54=2| 38=200| 10=235| | 10=219|

8=FIX.4.4| 9=168| 35=E| 49=0| 56=RESTAdapter| 34=1| 50=30737| 66=List1| 116=OMS1| 52=20191101-11:11:01.080| 394=3| 68=2| 73=2| 11=0003| 67=1| 100=DSMD| 55=11| 54=1| 38=100| 11=0004| 67=2| 100=DSMD| 55=12| 54=2| 38=200| 10=235|

To define message convertion type use TransportLayer.RestOutTA.ConversionMethod parameter, for details see. 

Using proxy server 

Proxy server can be used if direct connection from FIXEdge server to destination system is forbidden. For such cases the Transport Adapter has to be configured to connect a proxy server. A host, port, user and password for proxy connection should be configured in FIXEdge.properties file, for details see. 

Using security and non-secure connections 

The Transport Adapter supports secure (https) and non-secure (http) connections, for details see. 

Message validation 

Message validation is configured by using TransportLayer.RestOutTA.ValidateFIXMessage

Example1: validation is off: 

TransportLayer.RestOutTA.ValidateFIXMessage = No 

Example2:  message is not sent, OnUndelieveredEvent on BL is generated: 

TransportLayer.RestOutTA.ValidateFIXMessage = ValidateAndReject 

Example of log record:

2020-02-12 12:18:11,971 UTC   WARN    [RestInitiatorClient2]  140246545049344  FIX validation error: Incorrect integer value in tag 67: 'check'[Group tag=73, Entry #=0] in message New Order - List (E) with sequence number 3.2020-02-12 12:18:11,971 UTC   ERROR   [RestInitiatorClient2]  140246545049344  Error in sendToClient: Incorrect integer value in tag 67: 'check'[Group tag=73, Entry #=0] in message New Order - List (E) with sequence number 3.




For details see. 

Error handling 

Error information about http error codes is saved to log, see logging section

User can handle errors with Business Layer Engine in case of  error responces from destination system (for example receiving 400 or 500 error codes).   

An OnUndeliveredMessageEvent is generated and undelievered message is transfered to FIXEdge Business Layer for further processing. In the example below rejected message from RestInitiatorClient will be sent to FIX session : 

<OnUndeliveredMessageEvent> 
    <Source> 
        <Client Name="RestInitiatorClient"/> 
     </Source> 
   <Action> 
        <Send><FixSession SenderCompID="FE" TargetCompID="SC"/></Send> 
    </Action> 
</OnUndeliveredMessageEvent> 




Logging 

The Transport Adapter logs information on connection, transmitting messages, errors. Information can be stored in FixEdge.log file or in a separate file

LogFile name can be changed by user. This file is intended to store errors and events related to sending messages. Other events and errors related to transport adapter working are stored in FIXEdge.log file  

If Log Device is not configured everything will be logged to FIXEdge.log 

Log categories

 One log category is pre-defined for REST interface events. It is hardcoded with the "RestOutTA" name and cannot be changed by user. Other log categories will be used to save events related to initialization of the Adapter, parsing configuration parameters, sending/receiving messages .    

Logging levels

Different log levels can be turned on independently:

  • Note 
  • Trace
  • Debug 
  • Warn
  • Error
  • Fatal

Configuring logging to FixEdge.log file 


Configuration example: 

... 
TransportLayer.RestOutTA1.LogCategory = RestInitiatorClient1 
Log.RestOutTA.Device = File 
Log.RestOutTA.DebugIsOn = true 
Log.RestOutTA.TraceIsOn = true 
Log.RestOutTA.NoteIsOn = true 
Log.RestInitiatorClient1.Device = File 
Log.RestInitiatorClient1.DebugIsOn = true 
Log.RestInitiatorClient1.TraceIsOn = true 
Log.RestInitiatorClient1.NoteIsOn = true
... 


Log example (for /FIXEdge1/log/FixEdge.log)

2019-10-29 13:34:04,676 UTC   INFO    [RestOutTA]  10012  Log Category is registered to FileLogger 
    Category name: RestOutTA 
    File name: '../FIXEdge1/log/FixEdge.log' 
    File record format: %date{ISO8601} %timezone   %level%tablevel   [%logger]  %thread  %message 
    Create unique file name: off 
    Recreate file on restart: off 
    Flush on each record: on 
    Time zone: UTC 
    Log rotate is on: 
        size limit is 104857600 
        File Limit: 10 
        Rotate directory: ../FIXEdge1/log 
    Note: Filename is shared with other categories 
2019-10-29 13:34:04,677 UTC   DEBUG   [RestInitiatorClient1]  10012  Setting up HTTP session with jsonplaceholder.typicode.com:80 endpoint 
2019-10-29 13:34:04,677 UTC   DEBUG   [RestInitiatorClient1]  10012  Timeout for client 'RestInitiatorClient1' = 60. 
2019-10-29 13:34:04,677 UTC   INFO    [CC_Layer]  10012  Client RestInitiatorClient1 has logged in 
2019-10-29 13:34:04,677 UTC   INFO    [RestInitiatorClient1]  10012  REST Initiator TA v.0.0.0.1 started. 
2019-10-29 13:34:04,677 UTC   INFO    [TransportLayer]  10012  Module 'TransportLayer' version 0.1.1.5 was loaded. 
2019-10-29 13:34:04,677 UTC   INFO    [CC_Layer]  10012  Admin REST API is disabled 
2019-10-29 13:34:04,677 UTC   INFO    [CC_Layer]  10012  Control Centre XML Sockets Monitor is started 
2019-10-29 13:34:04,677 UTC   INFO    [CC_Layer]  10012  Control Centre Layer is initialized 
2019-10-29 13:34:04,677 UTC   INFO    [CC_Layer]  10012  FixEdge pid file '../FIXEdge1/log/FixEdge.pid'. 
2019-10-29 13:34:04,678 UTC   INFO    [XmlSockImpl]  12532  Log Category is registered to FileLogger 



Configuring logging to a separate file  

Different log levels can be turned on independently- Note, Trace, Debug.

Configuration example: 

... 
TransportLayer.RestOutTA1.LogCategory = RestInitiatorClient1 
Log.RestOutTA.Device = File  
Log.RestOutTA.DebugIsOn = true 
Log.RestOutTA.TraceIsOn = true 
Log.RestOutTA.NoteIsOn = true 
Log.RestOutTA.File.Name = FIXEdge1/log/RestOutTA.log 
Log.RestInitiatorClient1.Device = File 
Log.RestInitiatorClient1.DebugIsOn = true 
Log.RestInitiatorClient1.TraceIsOn = true 
Log.RestInitiatorClient1.NoteIsOn = true 
Log.RestInitiatorClient1.File.Name = FIXEdge1/log/RestOutTA.log 
... 



Log example (for /FIXEdge1/log/RestOutTA.log)

2019-10-29 13:40:07,830 UTC   INFO    [RestInitiatorClient1]  18488  Log Category is registered to FileLogger 
    Category name: RestInitiatorClient1 
    File name: '../FIXEdge1/log/RestOutTA.log' 
    File record format: %date{ISO8601} %timezone   %level%tablevel   [%logger]  %thread  %message 
    Create unique file name: off 
    Recreate file on restart: off 
    Flush on each record: on 
    Time zone: UTC 
    Log rotate is on: 
        size limit is 104857600 
        File Limit: 10 
        Rotate directory: ../FIXEdge1/log 
2019-10-29 13:40:07,830 UTC   DEBUG   [RestInitiatorClient1]  18488  Setting up HTTP session with jsonplaceholder.typicode.com:80 endpoint 
2019-10-29 13:40:07,830 UTC   DEBUG   [RestInitiatorClient1]  18488  Timeout for client 'RestInitiatorClient1' = 60. 
2019-10-29 13:40:07,831 UTC   INFO    [RestInitiatorClient1]  18488  REST Initiator TA v.0.0.0.1 started. 



 Configuring several instances of TA 

To define several connections (in case messages are routed to different destination systems) several instances of the Transport Adapter must be configured.  Parameter TransportLayer.<AdapterName> must be unique, for details see

Monitoring Rest Initiator Transport Adapter with FIXICC

REST Initiator Transport Adapter is displayed in FIXICC in the tree in the "servers" list at the left. In the example below RestOutTA1 is an adapter name and ResInitiatorClient1 is ClientID. Messages statistics is shown at the right -

  • total number of sent messages
  • total number of received messages
  • total number of rejected messages 

On the picture below the configuration with two Rest Initiator adapters is shown (RestOutTA1 and RestOutTA2).

restout_fixicc3.png


Configuration  

Configuration parameters 

Property 

Description 

Required 

Values/Examples 

TransportLayer.TransportAdapters = TransportLayer.<AdapterName>  

Transport Adapter Name. It should be different for different instances of adapters. Names for several instances are separated by comma 

Yes 

TransportLayer.RestOutTA 

TransportLayer.RestOutTA1, TransportLayer.RestOutTA2 

TransportLayer.RestOutTA.Description = <Description> 

Description of adapter 

Yes 

 REST Initiator Client 

TransportLayer.RestOutTA.DllName =  <TA_lib_name>

path to TA library 

Yes 

 ./libREST_Initiator_TA-gcc44-MD-x64.so

TransportLayer.RestOutTA.Type = DLL 

TA library type 

Yes 

 Obsolete

TransportLayer.RestOutTA.ClientID = <ClientID>

ClientID is the name to be referred on BL 

Yes 

 RestInitiatorClient 

TransportLayer.RestOutTA.LogCategory = <LogCategory>

Transport adaptor log category. 

Yes 

 RestInitiatorClient 

TransportLayer.RestOutTA.Protocol = <protocol_type> 

Security type of connection. Allows user to setup secure or non-secure http connection.  

Yes 

HTTP - non-secure connections 

HTTPS - secure connections 

TransportLayer.RestOutTA.ServerHost = <destination_ip_address> 

Destination for sending messages 

Yes 


TransportLayer.RestOutTA.ServerPort = <destination_port> 

Port for destination host 

Yes 


TransportLayer.RestOutTA.ProxyHost = <proxy_host_address> 

Proxy host 

No 


TransportLayer.RestOutTA.ProxyPort = <proxy_port> 

Proxy port 

Conditional (if proxy host is defined) 


TransportLayer.RestOutTA.ProxyLogin = 

Proxy user name 

No 


TransportLayer.RestOutTA.ProxyPassword = 

Proxy user password 

Conditional (if proxy login is defined) 


TransportLayer.RestOutTA.URI = <URI>

URI for http request 

Yes 

https://10.10.10.10/messages 

TransportLayer.RestOutTA.SendingTimeout = 

Time for waiting for response. After this time the adapter tries next time  to start connection

The maximum value of this time may be limited by Operating System 

No 

Default value = 0 - no timeout 

TransportLayer.RestOutTA.SendingMaxAttempts = 

Number of connection attempts 

No 

Default value = 2 

TransportLayer.RestOutTA.ConversionMethod = 

Conversion method is the way the outgoing message is converted

Yes 


Raw - raw FIX message (FIX message is sent to destination system as is)

WrapInXmlMessage - the value of 213 tag is sent to destination system

  NumericTagValueMapping - message is converted to JSON format and sent to destination system

TransportLayer.RestOutTA.ValidateFIXMessage =  

Enables/disables validation of FIX message (is not applied for raw conversion method) 


  

No 

No (default) -  validation is disabled 

ValidateAndReject - validation enabled, do not transmit message that didnt pass validation. The message is pushed back to BL.  

ValidateAndWarn - validation enabled, transmit message that didnt pass validation  but save error message to log file  

Log.RestOutTA.Device = 

Target device for logging the received and sent messages: 

File – writes log to a separate file 

Console – sends a log to console window 

No 

If parameter is not defined there will be no logging. Recommended value "File" 

File Console 

Log.RestOutTA.DebugIsOn =  

logging level 

No 

Values:true orfalse

Default value = false 

Log.RestOutTA.TraceIsOn =  

logging level 

No 

Values:true orfalse

Default value = false 

Log.RestOutTA.NoteIsOn =  

logging level 

No 

Values:true orfalse

Default value = false 

Log.RestOutTA.WarnIsOn =  

logging level 

No 

Values:true orfalse

Default value = false 

Log.RestOutTA.ErrorIsOn =  

logging level 

No 

Values:true orfalse

Default value = false 

Log.RestOutTA.FatalIsOn = 

logging level 

No 

Values:true orfalse

Default value = false 

Log.RestOutTA.File.Name = 

Path to logfile.

No 

 FIXEdge1/log/RESTITA.log 


TransportLayer.RestTA.Protocol=<protocol_type> 

Security type of connection. Allows user to setup secure or non-secure http connection.  

Yes 

HTTP - non-secure connections 

HTTPS - secure connections 


TransportLayer.RestTA.HTTPS.PrivateKey=<path_to_key> 

path to private key file 

Conditional (if HTTPS protocol type  is chosen) 


TransportLayer.RestTA.HTTPS.Certificate=<path_to_cert_key> 

path to certificate key file 

Conditional (if HTTPS protocol type  is chosen) 


TransportLayer.RestTA.HTTPS.PrivateKeyPassword=<password> 

password for private key file 

Conditional (if Private Key is password-encrypted) 


TransportLayer.RestTA.authHeader=<auth_header> 

HTTP header name for authentication. 

When <auth_header>  is specified, then all outcoming requests will contain the HTTP header with AuthValue. 


No 


TransportLayer.RestTA.authValue=<auth_value> 

Authentication value in HTTP header 

No 




Configuration example 

TransportLayer.TransportAdapters = TransportLayer.RestOutTA1
TransportLayer.RestOutTA1.Description = RESTInitiatorClient1 
TransportLayer.RestOutTA1.DllName = bin/REST_Initiator_TA-vc10-MD-x64.dll 
TransportLayer.RestOutTA1.Type = DLL 
TransportLayer.RestOutTA1.ClientID = RestInitiatorClient1 
TransportLayer.RestOutTA1.LogCategory = RestInitiatorClient1 
TransportLayer.RestOutTA1.Protocol = HTTP 
TransportLayer.RestOutTA1.ServerHost = jsonplaceholder.typicode.com 
TransportLayer.RestOutTA1.ServerPort = 80 
#TransportLayer.RestOutTA1.ProxyHost = 
#TransportLayer.RestOutTA1.ProxyPort = 
#TransportLayer.RestOutTA1.ProxyLogin = 
#TransportLayer.RestOutTA1.ProxyPassword = 
TransportLayer.RestOutTA1.URI = /posts 
TransportLayer.RestOutTA1.SendingTimeout = 60 
TransportLayer.RestOutTA1.SendingMaxAttempts = 2 
TransportLayer.RestOutTA1.ConversionMethod = NumericTagValueMapping 
TransportLayer.RestOutTA1.ValidateFIXMessage = ValidateAndWarn 
Log.RestOutTA.Device = File Console    
Log.RestOutTA.DebugIsOn = true 
Log.RestOutTA.TraceIsOn = true 
Log.RestOutTA.NoteIsOn = true 
Log.RestOutTA.File.Name = FIXEdge1/log/RestOutTA.log 
Log.RestInitiatorClient1.Device = File 
Log.RestInitiatorClient1.DebugIsOn = true 
Log.RestInitiatorClient1.TraceIsOn = true 
Log.RestInitiatorClient1.NoteIsOn = true 
Log.RestInitiatorClient1.File.Name = FIXEdge1/log/RestOutTA.log 



Example of configuration of security mode parameters

… 
TransportLayer.RestOutTA1.Protocol = HTTPS 
TransportLayer.RestOutTA1.HTTPS.PrivateKey = FIXEdge1/conf/TestRESTAPI.key 
TransportLayer.RestOutTA1.HTTPS.Certificate = FIXEdge1/conf/TestRESTAPI.crt 
TransportLayer.RestOutTA1.authHeader = apikey 
TransportLayer.RestOutTA1.authValue = QWERTY0123456789



Routing 

The Transport Adapter can be accessed in BL via ClientIDparameter. See example below (ClientID=RestInitiatorClient1): 

<Rule> 
          <Source> 
               <FixSession SenderCompID="FIXCLIENT1" TargetCompID="FIXEDGE"/> 
          </Source> 
               <Action> 
                    <Send Name="RestInitiatorClient1" /> 
               </Action> 
</Rule> 




Troubleshooting 

In all trouble cases first of all check error information in REST TA logfile (defined by Log.*.File.Name parameter) and FIXEdge.log.  

To check the Adapter is started correctly search for the string "REST Initiator", the example of output: 

REST Initiator TA v.0.0.0.1 started 




Host not found 

Description 

Message is not sent, adapter is initiated correctly, user gets error in REST TA log file: 

2019-10-24 06:46:21,622 UTC DEBUG [RestInitiatorClient1] 27532 sendRequest attempt 1 of 2 
2019-10-24 06:46:21,629 UTC ERROR [RestInitiatorClient1] 27532 Client 'RestInitiatorClient1' could not send POST request to the server (2) 'jsonplaceholder.typicodes.com'. Reason: Host not found: jsonplaceholder.typicodes.com. 
2019-10-24 06:46:21,629 UTC DEBUG [RestInitiatorClient1] 27532 sendRequest attempt 2 of 2 
2019-10-24 06:46:21,630 UTC ERROR [RestInitiatorClient1] 27532 Client 'RestInitiatorClient1' could not send POST request to the server (2) 'jsonplaceholder.typicodes.com'. Reason: Host not found: jsonplaceholder.typicodes.com. 
2019-10-24 06:46:21,631 UTC WARN [RestInitiatorClient1] 27532 sendToClient failed. Sending message reject. 
2019-10-24 06:46:21,639 UTC DEBUG [RestInitiatorClient1] 27532 sendToClient finished 


In FIXEdge.log

2019-10-24 06:46:21,631 UTC ERROR [RestOutTA] 27532 Error in sendToClient: Client 'RestInitiatorClient1' could not send POST request to the server (2) 'jsonplaceholder.typicodes.com'. Reason: Host not found: jsonplaceholder.typicodes.com. 


Solution 

Possible reason is wrong host. Check the host is available (ping  <ServerHost> ). If the host is available contact Support, otherwise correct TransportLayer.RestOutTA.ServerHostparameter value in adapter configuration. 

Send to Client failed 

Description 

Message is not sent, adapter is initiated correctly, user gets error in REST TA log file: 

2019-10-24 07:17:05,706 UTC DEBUG [RestInitiatorClient1] 24408 sendToClient started 
2019-10-24 07:17:05,706 UTC DEBUG [RestInitiatorClient1] 24408 sendRequest attempt 1 of 2 
2019-10-24 07:17:06,146 UTC ERROR [RestInitiatorClient1] 24408 REST server returned an error response status: 404 
2019-10-24 07:17:06,146 UTC WARN [RestInitiatorClient1] 24408 sendToClient failed. Sending message reject. 
2019-10-24 07:17:06,146 UTC DEBUG [RestInitiatorClient1] 24408 sendToClient finished


Solution 

Possible reason is wrong URI. If the URI value is correct contact Support, otherwise correct the TransportLayer.RestOutTA.URIparameter value in adapter configuration. 

Validation error 

Description 

User gets validation error, but message is sent successfully: 

2019-10-24 08:19:25,663 UTC DEBUG [RestInitiatorClient1] 31516 sendToClient started 
2019-10-24 08:19:25,663 UTC WARN [RestInitiatorClient1] 31516 FIX validation error: Field value 'FUT' does not meet ValBlock dictionary conditions in tag SecurityType (167) in message Execution Report (8) with sequence number 3. 
2019-10-24 08:19:25,663 UTC DEBUG [RestInitiatorClient1] 31516 sendRequest attempt 1 of 2 
2019-10-24 08:19:26,108 UTC TRACE [RestInitiatorClient1] 31516 Message sent successfully. 
2019-10-24 08:19:26,108 UTC DEBUG [RestInitiatorClient1] 31516 sendToClient finished 




User gets validation error, message is rejected: 

2019-10-24 08:22:27,526 UTC DEBUG [RestInitiatorClient1] 34024 sendToClient started 
2019-10-24 08:22:27,526 UTC WARN [RestInitiatorClient1] 34024 FIX validation error: Field value 'FUT' does not meet ValBlock dictionary conditions in tag SecurityType (167) in message Execution Report (8) with sequence number 2. 
2019-10-24 08:22:27,526 UTC WARN [RestInitiatorClient1] 34024 sendToClient failed. Sending message reject. 
2019-10-24 08:22:27,526 UTC DEBUG [RestInitiatorClient1] 34024 sendToClient finished 


Solution 

Validation error means that FIX message has incorect tag values of message structure. In the first case message is sent successfully because ValidateFIXMessage = ValidateAndWarn is set up. In the second case message is rejected because ValidateFIXMessage = ValidateAndReject is set up. Possible actions: 

  • correct message 
  • update dictionary 
  • turn off validation: TransportLayer.RestOutTA.ValidateFIXMessage = No). 

Wrong security options 

Description 

Message is not sent, adapter is initiated correctly, user gets error in log: 

2019-10-24 08:36:44,231 UTC DEBUG [RestInitiatorClient1] 22820 sendToClient started 
2019-10-24 08:36:44,232 UTC DEBUG [RestInitiatorClient1] 22820 sendRequest attempt 1 of 2 
2019-10-24 08:36:44,436 UTC ERROR [RestInitiatorClient1] 22820 Client 'RestInitiatorClient1' could not send POST request to the server (2) 'jsonplaceholder.typicode.com'. Reason: SSL Exception: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol. 
2019-10-24 08:36:44,436 UTC DEBUG [RestInitiatorClient1] 22820 sendRequest attempt 2 of 2 
2019-10-24 08:36:44,561 UTC ERROR [RestInitiatorClient1] 22820 Client 'RestInitiatorClient1' could not send POST request to the server (2) 'jsonplaceholder.typicode.com'. Reason: SSL Exception: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol. 
2019-10-24 08:36:44,561 UTC WARN [RestInitiatorClient1] 22820 sendToClient failed. Sending message reject. 
2019-10-24 08:36:44,561 UTC DEBUG [RestInitiatorClient1] 22820 sendToClient finished 


or: 

019-10-30 06:23:10,941 UTC DEBUG [RestInitiatorClient1] 24840 Setting up HTTP session with jsonplaceholder.typicode.com:443 endpoint 
2019-10-30 06:23:10,941 UTC DEBUG [RestInitiatorClient1] 24840 Timeout for client 'RestInitiatorClient1' = 60. 
2019-10-30 06:23:10,941 UTC INFO [RestInitiatorClient1] 24840 REST Initiator TA v.0.0.0.1 started. 
2019-10-30 06:23:25,490 UTC DEBUG [RestInitiatorClient1] 27036 sendToClient started 
2019-10-30 06:23:25,490 UTC DEBUG [RestInitiatorClient1] 27036 sendRequest attempt 1 of 2 
2019-10-30 06:23:25,660 UTC ERROR [RestInitiatorClient1] 27036 REST server returned an error response status: 400 
2019-10-30 06:23:25,660 UTC WARN [RestInitiatorClient1] 27036 sendToClient failed. Sending message reject. 
2019-10-30 06:23:25,660 UTC DEBUG [RestInitiatorClient1] 27036 sendToClient finished 


Solution 

Possible reason is security parameters are not correct - do not correspond to destination system connection properties. Try to change  TransportLayer.RestOutTA.Protocol or TransportLayer.RestOutTA.ServerPort parameters. 



  • No labels