IBM Support

PK84574: Exiting Report Server w/o logging out causes err: Your administr ator has not specified a Rational Report Management Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Vendor Solution.

Error description

  • 7.1: Exiting Report Server without logging out causes an error:
    Your administrator has not specified a Rational Report Managemen
    t Server
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • This is not a CQWeb problem.  It is caused the default
    behavior of how WebSphere and Jazz Server handle sessions.
    By default, both use cookie "JSESSIONID" to track sessions
    and both set the path to "/".  So, when you log into the
    Jazz Server, the browser will still try to use the session
    ID from CQWeb. The Jazz server does not know the ID and
    will set a new value.  However, when doing some actions in
    CQWeb again, the browser will use the new Id from the Jazz
    server.  CQWeb server will not recognize this Id and will
    therefore require you to log in again.
    
    The solution can be:
    
    1.  Install the CQ server and the Jazz server on different
    machines.
    2. Configure CQ Server to use a different cookie name such
    as "JSESSIONID_CQWEB" to track sessions and change the path
    to be the application context, e.g., "cqweb".  This can be
    done through the Websphere admin console, e.g.,
    http://9.42.116.218:12060/admin, see
    http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/
    com.ibm.websphere.express.iseries.doc/info/iseriesexp/ae/tpr
    s_cnfs.html for more.
    
      The basic steps are:
    
      1) Log in into http://9.42.116.218:12060/admin as "admin".
      2) Expand to "Applications -? Enterprise Applications ?
    RationalClearQuestWeb ? Session management"
      3) Check "Override session management"
      4) Follow the link "enable cookies", check cookie name and
    cookie path.
      5) Save the setting.
    
    3. Configure Jazz Server (not sure about the details.)
    
    We tried option 2 and it worked for us.
    

APAR Information

  • APAR number

    PK84574

  • Reported component name

    CLEARQUEST WIN

  • Reported component ID

    5724G3600

  • Reported release

    701

  • Status

    CLOSED ISV

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-13

  • Closed date

    2009-09-15

  • Last modified date

    2009-09-15

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 September 2009