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.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21579391