Using the Policy Manager Browser Client
The browser client version of the Policy Manager lets you manage the gateway using a standard Web browser.
For Gateway versions 9.3 CR5 and newer with AdoptOpenJDK, the browser client version of the Policy Manager will no longer be available.
The browser client version of the Policy Manager lets you manage the
CA API Gatewayusing a standard Web browser.
The user interface and functionality of the browser client version is very similar to the standard desktop client.
(1) If you wish to restrict browser client access, disable it by clearing the
Enable web-based administrationcheck box in the Requirements and Compatibility for a list of the compatible browsers. Be aware that the browser client does not run under Chrome.
The Java applet in the Policy Manager browser client must be in trusted mode to run certain features.
Trusted mode is enabled if you had answered [
Yes] to the browser and Java plug-in security dialogs on first use of the browser client version of the Policy Manager.
For more information about running the browser client, see Start the Policy Manager.
Browser Client Differences
The following table summarizes the differences between the browser client and the standard desktop client.
Browser client difference
Instead of a main tool bar.
[File] > Exit
The Exit command has been removed. To exit the browser client, first click [
Save] and then either click [
Disconnect] or close the browser.
[File] > Preferences
Main Tool Bar > Preferences
Preferences do not include the following settings:
[View] > Status Bar
The Status Bar is not included in the browser client.
There is no Policy Templates category in the [
Assertion] tab, but you can still import and export template files.
Exporting a policy to a file or importing a policy from a file is supported in the browser client only if the Java applet is running in the trusted mode.
Importing a policy from a UDDI Registry is supported only when the Java applet is in trusted mode.
The browser client does not write to the local log files. To view local log information, show the Java console as follows:
The local logs in the Java console only contain information about the internal activities of the browser client. These logs may be useful in helping to diagnose applet-specific problems, such as unresponsive buttons or drag-and-drop operations that do not complete.
The local logs are unrelated to the
CA API Gatewaylogs and audit records, which continue to be available through the Dashboard - Cluster Status windows.
Operations within the Manage Solution Kits task are limited. Only the Uninstall operation is available. The Install, Upgrade, and Properties operations must be run from the desktop client.