IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#TechXchangePresenter
 View Only
  • 1.  Facing issue with HTTP Protocol

    Posted Thu November 20, 2014 09:30 AM

    Dear all,

    we are trying to hit the service through URL where we could able to do through IE browser but when we pass the same URL to pub.client.http , we are getting timeout error.

    we have even tried by passing the arguments with the args in the pub.client.http but still we are facing the issue.

    we set the connect timeout property also but still facing the same issue :frowning: kindly help us to resolve the same.

    Thanks,
    Raj


    #Flow-and-Java-services
    #webMethods
    #Integration-Server-and-ESB


  • 2.  RE: Facing issue with HTTP Protocol

    Posted Thu November 20, 2014 10:54 AM

    watt.net.timeout=?

    Does the url starts with http or https?


    #webMethods
    #Integration-Server-and-ESB
    #Flow-and-Java-services


  • 3.  RE: Facing issue with HTTP Protocol

    Posted Fri November 21, 2014 04:09 AM

    Hi Mahesh,

    Currently it is set as below
    watt.net.timeout=0

    and URL starts with https

    Even we have passed the value for connectTimeout in pub.client.http service

    Kindly suggest any solution.

    Thanks,
    Raj


    #Flow-and-Java-services
    #webMethods
    #Integration-Server-and-ESB


  • 4.  RE: Facing issue with HTTP Protocol

    Posted Fri November 21, 2014 07:11 AM

    Try specifying the number of seconds, I guess IS restart is not required.

    Also your URL is https and I assume there would be some certificates involved.


    #Integration-Server-and-ESB
    #Flow-and-Java-services
    #webMethods


  • 5.  RE: Facing issue with HTTP Protocol

    Posted Wed January 21, 2015 10:41 AM

    Hello Raj

    You need to check various network configurations and that depends on how security conscious your organisation is:

    • You can temporarily use a proxy configured in the integration server. This will use your organisation’s proxy server which is generally configured in your browser. Don’t use this for production, it will upset your network people!!!
    • Check the hostname in the url is resolvable. From the box where Integration Server is installed run the command nslookup . If that doesn’t work you need to tell your network people to add a DNS entry. Alternatively you can add the hostname to ip mapping in /etc/hosts file.
    • Check with your network people on firewall settings. If the server you are trying to connect to is external you need to talk to your network people to punch a hole in the firewall. This is standard practice in most organisations.
    • If the server you are trying to connect to is internal and you already have a proxy configured, then you need to configure proxy bypass for your hostname.

    #Integration-Server-and-ESB
    #webMethods
    #Flow-and-Java-services