Webservice client program returning HTTP status code 8

I have autogenerated Webservice client program using how to article in Micro focus documentation link Programming > COBOL Programming > Interface Mapping Toolkit (IMTK) > How toGenerate Clients > To generate a RESTful COBOL console client from JSON

It is working fine for HTTP based webservices. However, same approach does not work for HTTPS based webservice. Its throwing HTTP status code 8 (Communication error) 

Error: HTTP Status Code 00008
Error: Communications component error

Our Micro focus environment does not have HTTPS listener available which could be the reason for above error.

I went through the Micro focus documentation and found below article which could explain the missing Communications component error message

www.microfocus.com/.../GUID-0C6B4853-13B1-4759-8041-80D9509D6058.html

Did anyone faced similar issue? What was done to fix it? 

Parents
  • Verified Answer

    Is your web service running under Enterprise Server or is it a 3rd party service running under some other web server?

    If you are using https then you will need to configure the client program for SSL as explained in the documentation link that you provided so that the web server can authenticate the user.

  • Hi Chris, 

    Its a 3rd party service running under some other web server.

  • Hi Chris, 

    I am the microfocus admin working on the issue

    Do we need to configure the client program for SSL in enterprise server or the 3rd party web server?

    Client - Enterprise server

    Host - 3rd party web server

  • I am not quite sure I understand your environment. The original post is in regards to generating a client console program that will call a web service which turns out to be a 3rd party web service. This does not involve Enterprise Server at all as Enterprise Server is used to host a web service itself.

    Are you running a web service under Enterprise Server that needs to call a 3rd party web service or is the client a standalone program? If it is not running under Enterprise Server then you do not need to configure Enterprise Server.

    Both the client and server sides need to be configured to use SSL. The original documentation deals with securing the generated client side. The 3rd party web service should already be configured to use SSL as you have no control over this. You will need to configure the client to use the same certificates that the server is expecting.

Reply
  • I am not quite sure I understand your environment. The original post is in regards to generating a client console program that will call a web service which turns out to be a 3rd party web service. This does not involve Enterprise Server at all as Enterprise Server is used to host a web service itself.

    Are you running a web service under Enterprise Server that needs to call a 3rd party web service or is the client a standalone program? If it is not running under Enterprise Server then you do not need to configure Enterprise Server.

    Both the client and server sides need to be configured to use SSL. The original documentation deals with securing the generated client side. The 3rd party web service should already be configured to use SSL as you have no control over this. You will need to configure the client to use the same certificates that the server is expecting.

Children