Troubleshooting
Problem
For the component portion of a routing file entry an asterisk (*) may be specified to log data for all components. When an attempt is made to restart the Web Reverse Proxy (WebSEAL), after having deployed this change in the routing file, the Web Reverse Proxy will fail to start.
Resolving The Problem
In the Web Reverse Proxy (WebSEAL) Routing file do not set a single entry containing an asterisk for all components, for example the following entry will prevent the Web Reverse Proxy from starting after the change is deployed:
*:*.9:UTF8FILE:pdweb_trace.log
Instead set multiple lines containing specific component names, for example:
mgr:*.9:UTF8FILE:pdweb_trace.log
ras:*.9:UTF8FILE:pdweb_trace.log
acl:*.9:UTF8FILE:pdweb_trace.log
idb:*.9:UTF8FILE:pdweb_trace.log
ira:*.9:UTF8FILE:pdweb_trace.log
wiv:*.9:UTF8FILE:pdweb_trace.log
wns:*.9:UTF8FILE:pdweb_trace.log
wwa:*.9:UTF8FILE:pdweb_trace.log
bas:*.9:UTF8FILE:pdweb_trace.log
bcf:*.9:UTF8FILE:pdweb_trace.log
Setting these entries in the routing file will permit the Web Reverse Proxy to start after the change is deployed.
Note that this is not an issue in ISAM versions later than stipulated here (a single entry can be used from 8.0.1.0).
Was this topic helpful?
Document Information
More support for:
Tivoli Access Manager for e-business
Software version:
8.0, 8.0.0.2, 8.0.0.4, 8.0.0.5
Operating system(s):
Appliance
Document number:
519421
Modified date:
16 June 2018
UID
swg21690413