IBM Support

PK88285: DEBUG SERVER FUNCTIONALITY DOESN'T WORK WHEN TARGET PLATFORM IS UNIX AND CLIENT/SERVER SEPARATED BY A FIREWALL.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Remote Debugger utilises the RMI technology and the ports should
    be free and no restrictions on both ends with respect to the
    network.  Debug Server uses 2590 and Design Studio has been
    using a random port when exporting the RMI object as RMI
    Callback used in the Design Studio.  This random port usage
    could be problematic in firewall scenarios.
    

Local fix

  • WTXCQ - WTX00029277
    PB / PB
    Fixed a problem with Remote Debug feature in Design Studio where
    it uses a random port for remote debugging which could be
    problematic in firewall scenarios.
    

Problem summary

  • Problem Description:
    Remote Debugger utilises the RMI technology and the ports should
    be free and no restrictions on both ends with respect to the
    network. Debug Server uses 2590 and Design Studio till now has
    been using a random port when exporting the RMI object as RMI
    Callback used in the Design Studio. This random port usage could
    be problematic in firewall scenarios. Using 15865 port for the
    Remote debugger at the Design Studio end to take care of this
    scenario. So, the ports 2590, 2591, 2592 and 2593 (RMI ports) on
    the server side should be open. Similarly, 15865 should be open
    for communication on the Design Studio end.  Besides ports being
    open and free for communication, network access should be
    compatible as we have encountered in our lab test case. It runs
    when the machine is on the same network as the server. But,
    laptops fail due to different network and corresponding security
    issues.
    
    Users Affected:
    Integration Flow Designer, msdimport.exe
    Platforms Affected:
    Windows ALL
    

Problem conclusion

  • Problem Conclusion:
    Fixed a problem with Remote Debug feature in Design Studio where
    it uses a random port for remote debugging which could be
    problematic in firewall scenarios.
    
    As a reference, the steps for running the Remote debugger are as
    follows:
    
    1. Install 8.2.0.x on Unix or Windows.
    2. Run script  startDeuggerServer.sh found in root_install/bin.
    3.  Windows Click Debug Map icon from tool bar of Eclipse Map
    Designer.
    4. Click Map and Remote.
    5. Go to output card and right click on any map rule and select
    Add Breakpoints.
    6. Build map for unix platform and deploy to that unix platform.
    7. Click Map | Remote and remote Debug window appears.
        A. Enter host name including the .bocaraotn.ibm.com suffix.
        B. Default port number is 2590.
        C. Enter User Name and Password that you use to sign in on
    UNIX.
        D. Click Unix for Map in Platform and enter full path and
    map compiled map name were the map is on the UNIX platform.
    
    Delivered in:
    8.2.0.5, 8.3.0.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK88285

  • Reported component name

    WEBSPHERE DESIG

  • Reported component ID

    5724M4008

  • Reported release

    820

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-06-09

  • Closed date

    2009-07-10

  • Last modified date

    2009-07-10

  • 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

    WEBSPHERE DESIG

  • Fixed component ID

    5724M4008

Applicable component levels

  • R820 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSD8","label":"IBM Transformation Extender"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
10 July 2009