IBM Support

ClearQuest Web server in a load-balanced deployment should not be used as an OSLC provider

Troubleshooting


Problem

Problems can occur when attempting to use IBM Rational ClearQuest Web server as an OSLC provider in a load-balanced deployment .

Symptom

The following error can occur when attempting to use ClearQuest Web server as an OSLC provider in a load-balanced deployment:

403 token_not_authorized

Cause

The ClearQuest Web server is not designed to function as an OSLC provider in a load-balanced environment.

Resolving The Problem

When configuring ClearQuest Web server as an OSLC provider, use a ClearQuest discovery URL that is not configured for load balancing. The discovery URL can reference an application server that is included in a load balanced configuration. However, the URL must allow requests to bypass load balancing and be directed to a specific application server.

For example, consider a load-balanced ClearQuest Web server named lbserver that is used to distribute requests to application servers appserver1 and appserver2. Instead of using the discovery URL https://lbserver/cqweb/oslc/repo/repoName/discovery, you must specify a discovery URL that references one of the application servers. For example:

https://appserver1:9443/cqweb/oslc/repo/repoName/discovery

where 9443 is the WebSphere Application Server secure port, usually 12443 or 9443.

[{"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Web Server (7.1)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1.2;7.1.2.1;7.1.2.2;7.1.2.3;7.1.2.4;7.1.2.5;8.0;8.0.0.1","Edition":""}]

Document Information

Modified date:
16 June 2018

UID

swg21579391