IBM Support

IT35843: WSDL DOCUMENT FOR SOAP SERVICE USING NODE WIDE LISTENER WILL EXPOSE LISTENER PORT NUMBER IN SOAP ADDRESS FIELD

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a SOAP Service is deployed to a node owned integration
    server, and the WSDL document is requested using the ?wsdl query
    url then the <soap:address> element of the WSDL will incorrectly
    include the node-wide HTTP listener port number if the Host
    header in the HTTP request does not specify a port number.
    
    For example if a request is sent to
    http://localhost:7080/MySoapService?wsdl with the header "Host:
    myservername" then the returned WSDL will incorrectly show
    
    <soap:address
    location="http://myservername:7080/MySoapService"/>
    
    Rather than
    
    <soap:address location="http://myservername/MySoapService"/>
    
    This problem is not present if the embedded HTTP listener is
    used, or an independent integration server is used.
    

Local fix

  • Use the embedded HTTP listener
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of SOAP Services in IBM App Connect Enterprise 11
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a SOAP Service is deployed to a node owned integration
    server, and the WSDL document is requested using the ?wsdl query
    url then the <soap:address> element of the WSDL will incorrectly
    include the node-wide HTTP listener port number if the Host
    header in the HTTP request does not specify a port number.
    
    For example if a request is sent to
    http://localhost:7080/MySoapService?wsdl with the header "Host:
    myservername" then the returned WSDL will incorrectly show
    
    <soap:address
    location="http://myservername:7080/MySoapService"/>
    
    Rather than
    
    <soap:address location="http://myservername/MySoapService"/>
    
    This problem is not present if the embedded HTTP listener is
    used, or an independent integration server is used.
    

Problem conclusion

  • The SOAP address location field will correctly reflect the Host
    value specified by the client when using the node-wide listener.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.12
    v12.0      12.0.6.0
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT35843

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-02-09

  • Closed date

    2021-04-28

  • Last modified date

    2022-09-30

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 September 2022