The 5 most recent pages less than 1000.0 days old in space WebRadar 3 Documentation with label popular.
Updated: 22 weeks 6 days ago
Configuring WebRadar
Page edited by Morgan Smith
WebRadar can be configured in the following ways:
View Online | View Changes Online Morgan Smith 2011-11-04T00:10:07ZAuthorization Failed Error
Page edited by Gavin Douglas - "Migrated to Confluence 4.0"
Upon loading the WebRadar portlet, if you are displayed with the message Error 403: AuthorizationFailed, please perform the following steps:
- On the machine running WebSphere, open the SystemOut.log file located in wp_profile/logs/YOUR_SERVER (where YOUR_SERVER is the name of the WebSphere server running WebRadar).
- Scroll to the bottom of this file and search for a log statement similar to the following:
SECJ0129E: Authorization failed for user <some_user>:<some_realm> while invoking <POST/GET> on <host>:<URL>, Authorization failed, Not granted any of the required roles: ephox_webRadar.user - If this error is found, one cause may be that when the WebRadar application was installed the Map Users and Groups step was not performed. Verify this by performing the following steps:
- If you are running WebSphere Application Server 6.1, expand the Applications link and click Enterprise Applications.
If you are running WebSphere Application Server 7.0, expand the Applications link, expand the Application Types link and click WebSphere enterprise applications.
- Select the checkbox next to EphoxWebRadar and press the Stop button.
- Click EphoxWebRadar from the list of Enterprise Applications.
- Click the Security role to user/group mapping link.
- If you are running WebSphere Application Server 6.1, verify that the users and/or groups that should be allowed access to WebRadar are listed in the Mapped users/Mapped groups fields.
If you are running WebSphere Application Server 7.0, verify that the users and/or groups that should be allowed access to WebRadar are listed in the Mapped users/Mapped groups fields.
- If the users and/or groups are not listed, follow the steps outlined in Map Users and Groups to resolve the issue.
- Ensure you start the application again when done, by checking the checkbox for EphoxWebRadar from the list of applications and clicking the Start button.
- If you are running WebSphere Application Server 6.1, expand the Applications link and click Enterprise Applications.
- If adjusting the WebRadar application security role to user/group mappings did not resolve the issue or you are seeing the Error 403: AuthorizationFailed message for a different reason, please lodge a support request with Ephox. Information on lodging support requests can be found in Requesting Support.
Troubleshooting WebRadar
Page edited by Mark Hibberd
Startup Order Configuration Error Upon loading the WebRadar portlet, if you are displayed with the message Oops, an error occurred, please perform the following steps:- On the machine running WebSphere, open the SystemOut.log file located in wp_profile/logs/YOUR_SERVER (where YOUR_SERVER is the name of the WebSphere server running WebRadar).
- Scroll to the bottom of this file and search for an instance of the following error:
Internal Server Error (500)
Unexpected error
Unexpected error : Application is not started - If this error is found, one cause may be that when the WebRadar application was installed the startup order was not set to 999. Verify your startup order by following the steps outlined in Configure Startup Behavior.
- If adjusting the WebRadar application startup behavior did not resolve the issue or you are seeing the Oops, an error occurred message for a different reason, please lodge a support request with Ephox. Information on lodging support requests can be found in Requesting Support.
- On the machine running WebSphere, open the SystemOut.log file located in wp_profile/logs/YOUR_SERVER (where YOUR_SERVER is the name of the WebSphere server running WebRadar).
- Scroll to the bottom of this file and search for a log statement similar to the following:
SECJ0129E: Authorization failed for user <some_user>:<some_realm> while invoking <POST/GET> on <host>:<URL>, Authorization failed, Not granted any of the required roles: ephox_webRadar.user - If this error is found, one cause may be that when the WebRadar application was installed the Map Users and Groups step was not performed. Verify this by performing the following steps:
- If you are running WebSphere Application Server 6.1, expand the Applications link and click Enterprise Applications.
If you are running WebSphere Application Server 7.0, expand the Applications link, expand the Application Types link and click WebSphere enterprise applications.
- Select the checkbox next to EphoxWebRadar and press the Stop button.
- Click EphoxWebRadar from the list of Enterprise Applications.
- Click the Security role to user/group mapping link.
- If you are running WebSphere Application Server 6.1, verify that the users and/or groups that should be allowed access to WebRadar are listed in the Mapped users/Mapped groups fields.
If you are running WebSphere Application Server 7.0, verify that the users and/or groups that should be allowed access to WebRadar are listed in the Mapped users/Mapped groups fields.
- If the users and/or groups are not listed, follow the steps outlined in Map Users and Groups to resolve the issue.
- Ensure you start the application again when done, by checking the checkbox for EphoxWebRadar from the list of applications and clicking the Start button.
- If you are running WebSphere Application Server 6.1, expand the Applications link and click Enterprise Applications.
- If adjusting the WebRadar application security role to user/group mappings did not resolve the issue or you are seeing the Error 403: AuthorizationFailed message for a different reason, please lodge a support request with Ephox. Information on lodging support requests can be found in Requesting Support.


