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.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
  • 1.  Connector not working with wM HTTPS port

    Posted 09/29/16 07:59 PM

    Hi All,

    As part of security we’ve implemented HTTPS port in webMethods 8.2. We in the progress of testing the WS connector from the HTTPS Port. We getting below exception when the HTTPS port acts as a Primary port,

    Status - 900
    Status Message- Error occurred while preparing SOAP request.

    Fault Error -
    [ISC.0081.9164] Exception occurred during generation of WSDL for service Reports1: WSDLException: faultCode=OTHER_ERROR: Unable to resolve imported document at ‘http://SJD-ISSQA-001.paypalcorp.com:5443/ws/InterfaceExtn.FoundationIP.WebServices:Reports1?WSDL’.: java.net.SocketException: Unexpected end of file from server

    Thanks,
    Karthik


    #API-Management
    #soa
    #webMethods


  • 2.  RE: Connector not working with wM HTTPS port

    Posted 09/29/16 10:09 PM

    You have mentioned connector, WS consumer always points to external endpoint. Why does the consumer throws error with a new port? Does your provider also exists in the same IS?


    #soa
    #API-Management
    #webMethods


  • 3.  RE: Connector not working with wM HTTPS port

    Posted 09/30/16 02:20 AM

    Hi Srikanth,

    We acting as a consumer here. We getting the same error mentioned. Not sure what went wrong.

    Thanks,
    Karthik


    #soa
    #API-Management
    #webMethods


  • 4.  RE: Connector not working with wM HTTPS port

    Posted 09/30/16 04:15 AM

    It looks issue with WSDL. Did you check in Soap ?

    Thanks,


    #webMethods
    #soa
    #API-Management


  • 5.  RE: Connector not working with wM HTTPS port

    Posted 09/30/16 05:07 AM

    Have you tried testing this on SOAP UI tool? What are your IS fix levels?


    #soa
    #API-Management
    #webMethods


  • 6.  RE: Connector not working with wM HTTPS port

    Posted 10/13/16 08:25 AM

    Hi,

    when changing protocol (and port), you will have to change the URL-prefix as well.

    The error message indicates a protocoll mismatch (using http on an https-port in this case).

    Regards,
    Holger


    #webMethods
    #soa
    #API-Management


  • 7.  RE: Connector not working with wM HTTPS port

    Posted 10/13/16 04:02 PM

    Thanks everyone for the replies,

    From SAG;

    I note that we are on IS_8.2_SP2_Core_Fix2. The issue we have reported seems to be fixed in IS_8.2_SP2_Core_Fix3
    Please refer to PIE-23221 in the below url
    https://empower.softwareag.com/sl24sec/fixsis_extern/FIXSIS2/ALL/PIE/822/IS_8.2_SP2_Core_Fix21_Readme.txt?prdfamily=Integration
    Please install this fix in your development/test environment and see if this addresses the issue

    PIE-23221 (IS_8.2_SP2_Core_Fix3):
    When using Deployer to configure an MWS connection and
    Integration Server has an HTTPS primary port, a
    com.wm.lang.ns.NSException is thrown.

    When configuring an MWS connection from Deployer when
    Integration Server is configured to use an HTTPS primary port,
    the following exception is logged to the server log:
    com.wm.lang.ns.NSException: [ISC.0081.9164] Exception occurred
    during generation of WSDL for service
    DeployerPluginRPCEncoded: WSDLException:
    faultCode=OTHER_ERROR: Unable to resolve imported document at
    ': Unexpected end of file from server. This issue
    occurs because Integration Server is unable to process all the
    imported XML schema files within the WSDL.

    This issue is resolved by updating Integration Server logic
    and the Web Services Stack API.

    Thanks,
    Karthik


    #webMethods
    #API-Management
    #soa