http client protocol

This topic has 13 replies, 8 voices, and was last updated 7 years, 2 months ago by Ryan Maginity.

Creator

Topic
June 18, 2015 at 11:15 pm #54726
ivan quan
Participant
Can anyone help me set up the http-client protocol on cloverleaf 6.0?

I have a little experience with http package in Tcl but I have no idea how to actually set up the protocol in the CL GUI.

Sample screen shots would be helpful.

Thanks
Creator

Topic

Viewing 12 reply threads

Author

Replies
- June 19, 2015 at 12:43 pm #82723
  James Cobane
  Participant
  Ivan,
  
  Attached is a document with screen shots of our configuration for an https thread. Configuring an http should be similar without the need for an certificates/https info.
  
  Hope this helps.
  
  Jim Cobane
  
  Henry Ford Health
- June 20, 2015 at 11:32 am #82724
  ivan quan
  Participant
  Thanks for this James.
  
  Before your reply we figured out how to code a simple HTTP POST operation in Tcl.
  
  We haven’t plugged in the Tcl script to any test threads yet because it required an extended tcltls library which our linux environment does not have.
  
  Theoretically, after we installed the extended library we should be able to plug the simple HTTP POST Tcl script into any protocol correct (pdl:tcp-ip)? Of course assuming that we use cloverleafs TPS template.
  
  What do you think? Do you have any experience with this?
  
  Thanks,
  
  Ivan
- June 20, 2015 at 12:36 pm #82725
  Jim Kosloskey
  Participant
  Why not use the provided vendor supported protocol?
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- June 20, 2015 at 1:06 pm #82726
  James Cobane
  Participant
  Ivan,
  
  I believe you would need to use the UPOC protocol if you are going to use your custom code to make/manage the connection and perform the write/post.
  
  Jim Cobane
  
  Henry Ford Health
- July 2, 2015 at 1:36 pm #82727
  ivan quan
  Participant
  James,
  
  I tried your configuration with my url and i keep getting “SSL is not licensed – ignoring SSL configuration parameters” in my process error log.
  
  ~Ivan
- July 2, 2015 at 2:37 pm #82728
  James Cobane
  Participant
  If you’re not using SSL, you should uncheck the HTTPS option. I believe HTTPS requires additional licensing from Infor (which I believe is a no cost license).
  
  Jim Cobane
  
  Henry Ford Health
- July 6, 2015 at 5:03 pm #82729
  Connie Kraska
  Participant
  Jim,
  
  What version of Cloverleaf are you using? I am comparing the screen shots to mine install of 5.7. I’ll be upgrading soon, before I have to get https working.
- July 6, 2015 at 5:43 pm #82730
  James Cobane
  Participant
  We are currently running 5.8.5 on AIX. We will be upgrading to 6.1.1 in August.
  
  Thanks,
  
  Jim Cobane
  
  Henry Ford Health
- July 8, 2015 at 6:01 pm #82731
  ivan quan
  Participant
  We are using CL 6.0
  
  I got my https to work using pure Tcl with package http and package tls…
  
  but it would be nice to know how to use the http client protocol GUI from CL.
  
  side note:
  
  Sometimes I feel like learning and using the GUIs are harder than just using Tcl. But if I’m using all Tcl then it’s a waste of all the GUI features available with CL interface engine.
  
  ~Ivan
- July 14, 2015 at 8:12 pm #82732
  Russ Ross
  Participant
  Ivan with regards to what James wrote:
  
  Code: I believe HTTPS requires additional licensing from Infor (which I believe is a no cost license).
  
  I’m not certain but also think that the SSL license might be at no cost, but I did have to request it.
  
  Cloverleaf has a license file ( $HCIROOT/vers/license.dat ) that will at least need an entry for SSL something like the cl-aom-ssl entry from my example below:
  
  Code: #————————————————————————— # Cloverleaf 6.0 license keys for 1MC-P740-6A (hcihostid = dc2fbfacde437be5) # initially created 2/26/2013 by Russ Ross #————————————————————————— FEATURE cl-pkg-cl hcilicmgrd 6.0 permanent uncounted B657D1D58D2A HOSTID=dc2fbfacde437be5 ck=173 category=prod FEATURE cl-intfc-master hcilicmgrd 6.0 permanent uncounted 5CDB4BFFCB8B HOSTID=dc2fbfacde437be5 ck=31 category=prod FEATURE cl-mm-master hcilicmgrd 6.0 permanent uncounted 79E7A1C0F5FC HOSTID=dc2fbfacde437be5 ck=10 category=prod FEATURE cl-aom-webservices hcilicmgrd 6.0 permanent uncounted 673D50FB2E8E HOSTID=dc2fbfacde437be5 ck=103 category=prod FEATURE cl-aom-site-doc hcilicmgrd 6.0 permanent uncounted 897D6EC548C4 HOSTID=dc2fbfacde437be5 ck=48 category=prod FEATURE cl-aom-gmon hcilicmgrd 6.0 permanent uncounted 48BDEE1A1065 HOSTID=dc2fbfacde437be5 ck=224 category=prod FEATURE cl-aom-ftps hcilicmgrd 6.0 permanent uncounted 24A260A23B16 HOSTID=dc2fbfacde437be5 ck=95 category=prod FEATURE cl-aom-sftp hcilicmgrd 6.0 permanent uncounted CD6C279E2090 HOSTID=dc2fbfacde437be5 ck=238 category=prod FEATURE cl-aom-ssl hcilicmgrd 6.0 permanent uncounted BE6BC1B25C3F HOSTID=dc2fbfacde437be5 ck=209 category=prod FEATURE cl-aom-odbc-mw hcilicmgrd 6.0 permanent uncounted 1E3653E8CF8B HOSTID=dc2fbfacde437be5 ck=172 category=prod FEATURE cl-aom-odbc-tcl hcilicmgrd 6.0 permanent uncounted 7E2185E421AC HOSTID=dc2fbfacde437be5 ck=221 category=prod FEATURE cl-aom-sec-advanced hcilicmgrd 6.0 permanent uncounted 37360F7DB59B HOSTID=dc2fbfacde437be5 ck=210 category=prod
  
  Once installed in your license file, it can be confirmed if it is working by running:
  
  Code: hcilictest cl-aom-ssl
  
  I’ve always found it takes some effort to know what license entries are needed for what, because they are cryptically unique in the license file, but more ambiguous when people talk about them.
  
  Russ Ross
  RussRoss318@gmail.com
- January 12, 2016 at 4:05 pm #82733
  Andres Alvarez
  Participant
  Ivan,
  
  Can you share how you got it to work using tcl?
  
  ~~ivan quan wrote:~~
  
  We are using CL 6.0
  
  I got my https to work using pure Tcl with package http and package tls…
  
  but it would be nice to know how to use the http client protocol GUI from CL.
  
  side note:
  
  Sometimes I feel like learning and using the GUIs are harder than just using Tcl. But if I’m using all Tcl then it’s a waste of all the GUI features available with CL interface engine.
  
  ~Ivan
- March 14, 2017 at 5:06 pm #82734
  Dave Scoggins
  Participant
  Ivan,
  
  I’m very interested in the TCL TLS solution too. Can you please share with us?
  
  Thanks
- September 29, 2017 at 3:21 pm #82735
  Ryan Maginity
  Participant
  I have a couple questions regarding the http-client protocol. This will be the first time we used this standard option which requires us to send ADT via a POST method. We have Cloverleaf 6.1.2.1.
  
  1. Based on the screenshots posted previously by Jim Cobane, under HTTP Options; Headers: Our Cloverleaf defaults to {Content-Type “text/xml; charset=utf-8”} {User-Agent “CIS”} which seems to be different from what Jim has in the screen shot. Is this something that needs to be changed?
  
  2. The receiving vendor says the message must be wrapped in XML. Does this protocol automatically do that? If not is there a standard way to make that happen?
  
  I’m guessing an ADT interface using POST has been done many times. Any additional details or lessons learned would be appreciated.
Author

Replies

Viewing 12 reply threads

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