HTTP-Client configuration setup for real-time

This topic has 4 replies, 3 voices, and was last updated 15 years ago by Bob Richardson.

Creator

Topic
April 25, 2011 at 6:04 pm #52430
Umesh Chandran
Participant
I am attempting to send an XML file (straight in and out) in its entirety via the interface using the following config and with nothing happening. Nothing is writing to the outbound thread.

We are on (AIX 5.3) and QVDXi 5.8

– http-client protocol

– url defined using a Port Number that has been enabled / allowed over
Creator

Topic

Viewing 3 reply threads

Author

Replies
- April 25, 2011 at 6:31 pm #74173
  Jim Kosloskey
  Participant
  Did you have the EO Config turned up and if so what did it show?
  
  I did one of these a couple of years age (Cloverleaf 5.4) and getting the parameter settings the server wanted was critical – however, I did see some feedback.
  
  I think in 5.8 you can give the protocol a -verbose TclCurl switch to have it echo out what it is doing (even if the EO is not up).
  
  I needed to write a TclCurl module since what the server wanted was not doable with the HTTP-Client Protocol setup in Cloverleaf 5.4.
  
  email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
- April 25, 2011 at 7:27 pm #74174
  Umesh Chandran
  Participant
  turned on the EO and below is an error (not sure what this implies ?).
  
  ***********************************************************
  
  [pd :pdtd:ERR /0:to_destin:04/25/2011 14:04:40] Tcl error:
  
  msgId = none
  
  proc = ‘httpQueryCurl’
  
  args = ‘{MSGUSE DATA}’
  
  result = ‘can’t read “HTTPS”: variable is array’
  
  errorInfo: ‘
  
  can’t read “HTTPS”: variable is array
  
  while executing
  
  “lappend configCmd -sslcert $HTTPS”
  
  (procedure “curlSubs::buildConfigure” line 76)
  
  invoked from within
  
  “curlSubs::buildConfigure”
  
  (“start” arm line 48)
  
  invoked from within
  
  “switch -exact — $mode {
  
  start {
  
  # Set name of procedure
  
  set curlSubs::myName “$::HciConnName/[lindex [info level 1] 0]”
  
  # Get and …”
  
  (procedure “httpQueryCurl” line 5)
  
  ++++++++++++++++++++++++++++++++++++++++++++++
  
  httpQueryCurl has this block of code. In my example, I am using TLSV1.
  
  lappend configCmd -sslcert $HTTPS
  
  lappend configCmd -keypasswd $HTTPS(PASSWORD)
  
  }
  
  # SSL Version
  
  switch -exact — [string toupper $HTTPS(SSL_PROTOCOL)] {
  
  SSLV2 {set type sslv2}
  
  SSLV3 {set type sslv3}
  
  TLSV1 {set type tlsv1}
  
  default {set type default}
- April 25, 2011 at 7:34 pm #74175
  Jim Kosloskey
  Participant
  I think this is new to 5.8
  
  It may be that an argument should have been passed that was not (either from the configuration you set up or required for you to provide).
  
  Re-check the documentation and make sure you have all of the options set properly.
  
  Also I recall that in mine when I attempted to use cretification (before I found out they wanted SSL but did not require a certificate) if the certificate file could not be found there was no error stating that specifically.
  
  email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
- April 26, 2011 at 1:09 pm #74176
  Bob Richardson
  Participant
  Greetings,
  
  Jim, a word of comfort for your TclCurl driver and HTTPS. We have been running a custom TclCurl driver for our HTTPS posts to a Blue Cross payer since 2008 having started on CIS5.3 and now running CIS5.7R2.
  
  I had the opportunity to test our driver under a Beta CIS5.8 and it worked fine! I did not play with the canned configurable HTTPS as I ran out of time – year end and my Xmas vacation took priority!
  
  Ok… what I am saying here is that the canned HTTPS stuff in 5.8 may be buggy as its predecessor in 5.3 happened to be. For Umesh here he may need to crank up a custom TclCurl to gain control of the operations and actually see what is going on. For myself, when testing this HTTPS stuff, I have an interactive version of the TclCurl driver that uses the debug feature (klunky to set up but works) and provides a full session log of the SSL negotiation and outcomes.
  
  Umesh: I would be willing to post our version of the TclCurl driver and its interactive counterpart (scrubbed of course with our password etc) if you want to explore that avenue for a solution.
  
  And of course don’t hesitate to contact Lawson Cloverleaf support for assistance. They have some great techs who can help with the TclCurl.
Author

Replies

Viewing 3 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.