IBM Support

PI57169: PORTAL 8X TARGET JAX-WS CLIENT GENERATE ERROR:WSIMPORT NOT FOUND

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Portal v8.x server runtime target in JAX-WS client wizard
    generate error: Wsimport not found
    
    Using Rational Application developer (RAD) 9.5 to generate a
    JAX-WS web services client (into a portlet project) targeting
    WebSphere Portal 8.5(on WAS 8.5) ,  results in this pop-up error
    from the web services wizard:
    
    â œThe Wsimport Web service tool was not found in the server
    installation. For WebSphere Application Server classic V8.5 and
    V8.0, verify the installation directory and its content. For
    WebSphere Application Server classic V7.0, ensure that the
    appropriate feature packs are installed for JAX-WS Web Services
    support. Once installed, the tool is available in:
    C:\IBM\WebSphere\AppServer\bin\jaxws⠝
    
    
    Recreate:
    
    Recreate this error in RAD 9.5 by attempting to generate a
    JAX-WS Web Services client from any WSDL, against any WebSphere
    Portal 8.x server into any web project. It does not have to be a
    portlet project.
    Gives Error"
    
    "..
    The Wsimport Web service tool was not found in the server
    installation.
    For WebSphere Application Server (WAS) v8.5 and v8.0, verify the
    installation directory and its content.
    For WAS v7.0, ensure that the appropriate feature packs are
    installed for JAX-WS Web Services support.
    Once installed, the tool is available in: {WebSphere Portal
    Home}\AppServer\bin\jaxws
    .."
    
    Note: AppServer is the WAS 8.0 or WAS 8.5 used by Portal
    
    The key was that a  WPortal 8.x server runtime was specified.
    It seems to expect the wsimport to be in
    {WAS 8x server used by WPortal 8.x}\bin\jaxws folder
    , instead of
    {WAS 8x server used by WPortal 8.x}\bin\
    
    wsimport is always in .../AppServer/bin
    There is no .../AppServer/bin/jax-ws folder
    If the server runtime target is some WAS 8.x server there is no
    problem
    
    
    You can recreate this also by creating a web project targeting
    say the Portal80 on WAS85 stub
    in RAD (if Portal 8x stubs and WAS 8x stubs are installed as
    part of RAD server tools), and
    then generating a web service client from a wsdl into that
    project.
    
    Note:
    {RAD Install Dir}/runtimes/portal_v85_stub
    uses
    {RAD Install Dir}/runtimes/was85_stub
    ,for build or generate puposes.
    
    The error will be:
    "..
    The Wsimport Web service tool was not found in the server
    installation.
    For WebSphere Application Server (WAS) v8.5 and v8.0, verify the
    installation directory and its content.
    For WAS v7.0, ensure that the appropriate feature packs are
    installed for JAX-WS Web Services support.
    Once installed, the tool is available in: {RAD Install
    Dir}/runtimes/was85_stub\bin\jaxws
    .."
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the Portal tools                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Portal v8.x server runtime target in JAX-WS client wizard    *
    * generate error: Wsimport not found                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is included in Rational Application
    Developer version 9.5.0.3
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI57169

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-12

  • Closed date

    2017-08-11

  • Last modified date

    2017-08-11

  • 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

    RATL APP DEV WI

  • Fixed component ID

    5724J1901

Applicable component levels

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 October 2021