PI58026: OSLC LINKS FAILS WHEN FRIEND CONFIGURATION USES PORT 443

Rational ClearQuest Fix Pack 11 (8.0.1.11) for 8.0.1
Rational ClearQuest Fix Pack 1 (9.0.0.1) for 9.0
Rational ClearQuest Fix Pack 12 (8.0.1.12) for 8.0.1
Rational ClearQuest Fix Pack 2 (9.0.0.2) for 9.0
Rational ClearQuest Fix Pack 13 (8.0.1.13) for 8.0.1
Rational ClearQuest Fix Pack 3 (9.0.0.3) for 9.0
Rational ClearQuest Fix Pack 14 (8.0.1.14) for 8.0.1
Rational ClearQuest Fix Pack 4 (9.0.0.4) for 9.0
Rational ClearQuest Fix Pack 15 (8.0.1.15) for 8.0.1
Rational ClearQuest Fix Pack 5 (9.0.0.5) for 9.0
Rational ClearQuest Fix Pack 16 (8.0.1.16) for 8.0.1
Rational ClearQuest Fix Pack 6 (9.0.0.6) for 9.0
Rational ClearQuest Fix Pack 17 (8.0.1.17) for 8.0.1
Rational ClearQuest Fix Pack 18 (8.0.1.18) for 8.0.1
Rational ClearQuest Fix Pack 19 (8.0.1.19) for 8.0.1
Rational ClearQuest Fix Pack 20 (8.0.1.20) for 8.0.1
Rational ClearQuest Fix Pack 21 (8.0.1.21) for 8.0.1
Rational ClearQuest Fix Pack 22 (8.0.1.22) for 8.0.1
Rational ClearQuest Fix Pack 23 (8.0.1.23) for 8.0.1
Rational ClearQuest Fix Pack 24 (8.0.1.24) for 8.0.1
Rational ClearQuest Fix Pack 25 (8.0.1.25) for 8.0.1

APAR status

• Closed as program error.

Error description

• Root cause:
  We set Root Service URI to
  https://servername:443/ccm/rootservices in CQ configuration. The
  uri in the error message is
  https://servername/ccm/...../services.xml. You can find that
  ":443" is missed and I guess that is because 443 is the SSL
  default port. But in CQ side, we store
  https://servername:443/ccm/rootservices in the friendsconfig
  file. When adding link from CQ, CQ find that
  https://servername:443/ccm and https://servername/ccm do not
  match and then throw exception.
  
  
  Workaround:
  You can manually fix this problem.  Please modify
  <profile>\TeamEAR.ear\cqweb.war\WEB-INF\classes\friendsconfig.rd
  f as below, and then restart the profile. You don't need to
  re-config the Friends relationship, but you should update this
  file once the Friends relationship is recreated.
  
  Original value:    <jfs:oauthDomain
  xmlns:jfs="http://jazz.net/xmlns/prod/jazz/jfs/1.0/">https://win
  -c35aq7eh0oc:443/ccm</jfs:oauthDomain>
  Updated value: <jfs:oauthDomain
  xmlns:jfs="http://jazz.net/xmlns/prod/jazz/jfs/1.0/">https://win
  -c35aq7eh0oc/ccm</jfs:oauthDomain>
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ClearQuest Web                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * OSLC links cannot be created from within ClearQuest Web if   *
  * the CLM server friendship is configured to use port 443.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A fix is available in ClearQuest 8.0.1.11 and 9.0.0.1.
  OSLC links can now be created from within ClearQuest Web if the
  CLM server friendship is configured to use port 443.
  

Temporary fix

Comments

APAR Information

• 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

  CLEARQUEST WIN

• Fixed component ID

  5724G3600

Applicable component levels

• R801 PSY

     UP