IV27434: BUSINESS SPACE ERRORS WITHIN A WEBSEAL SECURED ENVIRONMENT

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The Business Space UI reports on screen the following:
    .
    Method: createActionsMenu-getNextTransitions - Message: Error:
    Unable to
    load
    
    
    .
    Another symptom is the transition options will be missing
    from the 'Action' button in the detail widget.
    .
    Finally the logs will report the following.
    .
    [8/17/12 15:49:36:044 EDT] 00000043 URLConnection 2
    IOException
    catched, response code is 404, Exception was
    java.io.FileNotFoundException:
    https://wsrr-Servername:port/ServiceRegistryFeeds/WSRR/7.5/
    lifecycl
    e/states/http:/www.ibm.com/xmlns/prod/serviceregistry/lifecycle/
    v6r3/Lif
    (http://www.ibm.com/xmlns/prod/serviceregistry/lifecycle/v6r3/Li
    f)
    ecycleDefinition%23Identified
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Service Registry and Repository Server
    Version 7.5.0 and 8.0.0
    
    
    ****************************************************************
    PROBLEM SUMMARY:
    When the WSRR Business Space user interface has been
    configured to be accessed via WebSeal, errors are displayed
    within the UI and the WSRR widgets do not render or populate
    with data correctly.
    

Problem conclusion

  • The WSRR Business Space widgets depend upon the REST and ATOM
    APIs provided by the WSRR server. Requests were made for
    Business Model and Ontology data using a fully qualified OWL URI
    that contains percent encoded forward slash characters.
    WebSeal will not allow two forward slash characters to be
    included in the final part of an HTTP request regardless of
    whether they are encoded or not. It was therefore altering the
    encoded double forward slash characters in the OWL URIs to a
    single encoded forward slash. This meant that the URIs were no
    longer correct and so the requests for the required Business
    Model and Ontology data returned no data.
    
    The required APIs have been updated to allow the OWL URIs to
    be sent in a new encoding that means they will never contain two
    consecutive forward slash characters.
    
    This fix is targeted for inclusion in fix pack 3 for WSRR v7.5
    and fix pack 2 for WSRR v8.0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV27434

  • Reported component name

    SERVICE REGISTR

  • Reported component ID

    5724N7200

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-04

  • Closed date

    2013-02-07

  • Last modified date

    2013-02-07

  • 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

    SERVICE REGISTR

  • Fixed component ID

    5724N7200

Applicable component levels

  • R750 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Service Registry and Repository

Software version:

7.5

Reference #:

IV27434

Modified date:

2013-02-07

Translate my page

Machine Translation

Content navigation