Using the Policy Manager Browser Client
The browser client version of the Policy Manager allows you to manage the using a standard web browser.
The browser client version of the Policy Manager allows you to manage the
API Gatewayusing a standard web browser.
The user interface and functionality of the browser client version is very similar to the standard desktop client
Browser client access can be disabled by clearing the
Enable web-based administrationcheck box in the Listen Port Properties (Endpoints tab) for the SSL endpoint. If you experience problems starting the browser client, access the Java Control Panel for your operating system, clear the temporary Java files, and then try starting the browser client again.
Note that 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 on running the browser client, see Start the Policy Manager.
Browser Client Differences
Browser client difference
[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
API Gatewaylogs and audit records, which continue to be available through the Gateway Audit Events and 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.