run cURL command from TCL script

You need to provide full path to cURL.  The script is running as a child process and does not inherit all the paths.

Is there a reason you do not use TclCurl?

I believe the problem is that exec expects a list of arguments, not a single string:

Incorrect Example: exec “ls -ltr”

Correct Example: exec ls -ltr

Eric makes a valid point about exec but no need to exec cURL when TclCurl is available.

I would have to get more involved with the specifics of what you are trying to do to offer any further help.  Perhaps a few Implementation hours from Infor?

if i had to guess, your url will change with each message. so build the url variable…

set url $urlConstant/$msgID/file  # or something similar. You are doing an http get, so the webserver will need specifics in the URL. Once you post you’ll get an http status code, not the token you are hoping for. Any sort of data back will be handled outside of handing the http post action.

now set the curl command, with all the required switches.

$curlHandle configure -url $url \
-userpwd $userid:$sample_pwd \
-file $rcvFile \
-httpget 1 \
-httpversion 1.1 \
-headervar httpHeader \
-verbose 1

catch ($curlHandle perform) curlExitCode #this will execute the command and catch the http header that is returned.  now split the header to get the http code.. .now you can have more informaiton on whta the server is replying with..

set httpStatCode [lindex [split $httpHeader(http) ” “] 1] #or something like that

this is a manual way to accomplish your task, and i’m certain you could program the whole thing, but cloverleaf does have some built in tools to make this a better process. i think it is the java ws server protocol, in the netconfig, then you should be able to watch the process log for the http server response… but you can use the commands above to at least confirm the http server response.

• This reply was modified 5 years, 3 months ago by Dustin Sayes.

I have done something like this where our system has to call a Web Service to get a token and then if a good token is gotten, send the data message with the token received.

Logic to get the token using a TclCurl call

<code>

set curlHandle [curl::init]
if { $debug } {
puts “Command ID ==>> $curlHandle”
puts “The Configs are: URL==> $URL”
puts “Https Headers ==> $httpHeaders”
}

set reply “”
catch {
curl::transfer -verbose 1 -url $URL -header 1 -httpheader $httpHeaders -post 1 -postfields $soapMsg -bodyvar reply -errorbuffer err -sslverifypeer 0
} tclerr
if { $debug } {
puts “tclerr ==> $tclerr”
puts “reply ==> $reply”
}

$curlHandle cleanup

</code>

The logic gets the token out of the reply variable and then uses it in the next TclCurl call.

<code>

set curlHandle [curl::init]

if { $debug } {
puts “Command ID ==>> $curlHandle”
puts “The Configs are: URL==> $URL”
puts “Https Headers ==> $httpHeaders”
}

set reply “”
catch {
curl::transfer -verbose 1 -url $URL -header 1 -httpheader $httpHeaders -post 1 -postfields $soapMsg -bodyvar reply -errorbuffer err -sslverifypeer 0
} tclerr
if { $debug } {
puts “tclerr ==> $tclerr”
puts “reply ==> $reply”
}

$curlHandle cleanup

</code>

Rob