This chapter provides information about the messages produced by OM Web Viewer.
This section contains the following topics:
UI Messages for Configuration Errors
OM Web Viewer includes a set of error messages that an incomplete configuration causes. Messages are displayed in the Web Viewer Login page.
Reason:
The required CAOMWV12_HOME environment variable for the CA OM Web Viewer system level configuration is not setup in the server environment.
Action:
The CAOMWV12_HOME environment variable has the path of your CA OM Web Viewer install home or the configuration parent folder. Administrators have to define the variable manually on your system platforms. For more information, see Chapter 4.
Reason:
The CA OM Web Viewer configuration folder does not exist, or is not accessible by the product. If the configuration folder does exist, it is not in the path that the environment variable CAOMWV12_HOME defined.
Action:
Check for the existence of the configuration folder, %CAOMWV12_HOME%/config. If the configuration folder does not exist, then the administrator has to run the configuration tool at the system level or copy the configuration tool folder from another computer. If the configuration folder exists, check for the CA OM Web Viewer application access rights to the folder. If necessary, ask your system administrator to grant the folder access rights for the CA OM Web Viewer application.
Reason:
The CA OM Web Viewer configuration path does not exist, or the folder is not accessible by the product instance with the path of configuration folder that the web context defined in the specific CA OM Web Viewer install.
Action:
Check for the existence of configuration folder, %CAOMWV12_HOME%/${CAOMWebViewer12_INST}/config. Where %CAOMWV12_HOME% is the Web Viewer install home path and ${CAOMWebViewer12_INST} is the context name of the specific Web Viewer install instance. If not, the administrator has to run the configuration tool for this specific Web Viewer instance at the application level. If the configuration folder exists, check for the Web Viewer application access rights to the folder. If necessary, ask your system administrator to grant the folder access rights for the Web Viewer application.
Reason:
The CA OM Web Viewer configuration file and WVProfile.properties cannot be loaded from the configuration folder.
Action:
Check the configuration file is in the configuration folder, %CAOMWV12_HOME%/config. If not, the administrator has to run the configuration tool at the system level or at the application level for a specific Web Viewer instance. If the configuration file exists, check for the Web Viewer application access rights to the file. If necessary, ask your system administrator to grant the file access rights for the Web Viewer application.
Reason:
The External Security EXIT service cannot be initiated for the first end user authentication with CA OM Web Viewer configured for External Security EXIT.
Action:
Check that the security EXIT jar file and associated files are located in the following configuration folder:
%CAOMWV12_HOME%/config/external_ExtSec_lib
If these files are not in the configuration folder, the administrator has to run the configuration tool at the system level or at the application level for a specific CA OM Web Viewer instance. If the EXIT jar file exists, check that SecurityEXITSPI.jar is in the same folder as the EXIT jar.
Reason:
The CA OM Web Viewer instance is not configured to use External Security EXIT for user authentication.
Action:
The administrator has to run the configuration tool at the system level or at the application level for a specific CA OM Web Viewer instance to enable the External Security EXIT service for user authentication process.
Reason:
CA OM Web Viewer cannot find user roles that are defined for users authenticated through the External Security EXIT.
Action:
The administrator has to log in to CA OM Web Viewer as a System Administrator to create roles with a role profile named EXIT before any EXIT calls for the user authentication.
Reason:
CA OM Web Viewer catches an exception error that is thrown from the External Security EXIT, or the date that is returned from the EXIT is invalid.
Action:
The administrator or EXIT developer has to check that their implementation of the security EXIT catches all exceptions, including RuntimeException and subclasses of RuntimeException. Also, ensure that the EXIT does not return invalid data such as null points for UserContext or RepositoryContext. If there is any code defect, the administrator has to provide a code fix and create a new EXIT jar file. Then, copy the new EXIT jar file to the system level external configuration folder:
%CAOMWV12_HOME%/config/external_ExtSec_lib
The administrator can run the configuration tool at the system level or at the application level for a specific CA OM Web Viewer instance to update the EXIT jar.
OM Web Viewer includes a set of error messages that are caused by user errors. Messages are displayed in the Web Viewer Login page.
Reason:
The CA OM Web Viewer does not allow users to have more than one login instance using the same session for security risk concerns. If a user closes the browser tab without logging out from Web Viewer and logs back in from a new tab within the same browser window, this error message is displayed in the Web Viewer login page.
Action:
The user has to create a new web session by using File/New session menu command in Internet Explorer or using New Private Browsing Window in Firefox to open the Web Viewer login page for a new login.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|