Configuring Tivoli Access Manager WebSEAL and WSRR

If you are using Tivoli® Access Manager WebSEAL with WSRR you must create transparent path junctions for the context roots of the components that you are using.

WSRR Studio uses basic authentication to connect to the WSRR Server, so when using Tivoli Access Manager WebSEAL it must be configured for basic authentication.

Multiple authentication types can be configured. For example, if you want forms-based authentication for the WSRR web UI and dashboard, you can configure forms-based and basic authentication with the WebSEAL configuration auth-challenge-type = forms, ba.

The following table lists the components and their context roots.
Table 1. WSRR components and context roots
Component Context roots
WSRR Web UI /ServiceRegistry
WSRR Business Space UI

/ServiceRegistryFeeds
/ServiceRegistryWidgets
/ServiceRegistryPolicyAnalyticsWidgets
/BSpaceWeb
/BSpaceWebformsProxy
/BusinessSpaceHelp
/BusinessSpace
/themes
/WSRR
/mum
/WSRRReportViewer
/ServiceRegistryBIRTReport
WSRR Studio

/ServiceRegistryFeeds
/WSRR
/WSRR6_1
/WSRR6_2
/WSRR6_3
/WSRR7_0
/WSRR7_5
/WSRR8_0
/WSRR8_5
/WSRRReportViewer
/ServiceRegistryBIRTReport
REST Interface /WSRR
Web Services Interface and the Eclipse Plugin:  
Web Services for WSRR V6.0.2:

/WSRRCoreSDO
/WSRROntologyWS
/WSRRGovernanceWSRouter
Web Services for WSRR V6.3 /WSRR6_3
Web Services for WSRR V7.0 /WSRR7_0
Web Services for WSRR V7.5 /WSRR7_5
Web Services for WSRR V8.0 and WSRR V8.5 /WSRR8_0
The table lists the default context roots. If you have multiple instances of WSRR deployed, you must identify the instance by specifying its prefix.

For example, the REST interface context becomes:

/prefixWSRR
Parent topic: Configuring and customizing