The Policy Server is managed through a user interface that is generated dynamically based on the administrative privileges of the user.
Important! When working on the task pane on the right, always save your changes before opening or closing the menu pane on the left or navigating to another task.
Do not use the Refresh or Back buttons of the browser while using the Administrative UI. Using these buttons resubmits the form, repeats the action that was initiated by clicking a button in the form, and creates an invalid state.
The Policy Server is managed through a graphical user interface. The interface is generated dynamically based on the administrative privileges of the user. This chapter discusses how to log in to the Administrative UI and the common procedures that you use while configuring and managing Policy Server objects.
The Administrative UI contains two panes:
The menu of tasks on the left can be open or closed. If the menu is closed, you can open it by clicking the right-facing arrow. Likewise, if the menu is open, you can close it by clicking the left-facing arrow.
Important! When working on the task pane on the right, always save your changes before opening or closing the menu pane on the left or navigating to another task.
Do not use the Refresh or Back buttons of the browser while using the Administrative UI. Using these buttons resubmits the form, repeats the action that was initiated by clicking a button in the form, and creates an invalid state.
Follow these steps:
https://host.domain:8443/iam/siteminder/adminui
http://host.domain:8080/iam/siteminder/adminui
http://host.domain:port/iam/siteminder/adminui
https://host.domain:port/iam/siteminder/adminui
Specifies the name of the Administrative UI host system.
Specifies the fully qualified domain name of the Administrative UI host system.
Specifies the port on which the application server listens for requests.
The system displays the relevant tabs for your administrator privileges. The contents of this window differ based on the privileges of the administrator account you use to log in to the Administrative UI.
The Administrative UI lets you view, modify, and delete Policy Server objects. Although the details of each task differ by object, the general methods are similar. For example, the procedure for deleting an agent is similar to the procedure for deleting a response.
The easiest way to create a Policy Server object is to copy an existing object and modify its properties. You can use the properties of the existing object as a template, only changing the information that is different for the new object. The copy option is not available for all objects.
Note: Your administrative privileges determine the objects you can access.
Follow these steps:
Example: Click Infrastructure, Agent.
Example: Agent
The object is created.
You can view the properties of a Policy Server object.
Note: Your administrative privileges determine the objects you can access.
Follow these steps:
Example: Select Policies, Domain.
Example: Domain
The View screen appears with information about the object you selected.
The Administrative UI lets you modify the properties of existing Policy Server objects.
Note: Your administrative privileges determine the objects you can access.
Follow these steps:
Example: Click Policies, Domain.
Example: Realms
The object is modified.
You can delete a Policy Server object that is no longer needed.
Note: Your administrative privileges determine the objects you can access.
Follow these steps:
Example: Click Infrastructure, Authentication.
Example: Authentication Schemes
The Policy Server object is deleted.
Every Administrative UI task stays in the task-persistence database indefinitely or until removed by a CA SiteMinder® administrator. You can remove tasks from the database and free up disk space by scheduling cleanup tasks. Cleanup tasks allow you to manage the size of the task-persistence database and improve runtime performance.
Every task exists in the task-persistence database in one of the following states:
A task in the audit state has been initiated in the Administrative UI, but not submitted. For example, View tasks are initiated in the Administrative UI, but are never submitted.
Submitted tasks are tasks that have been submitted for processing in the Administrative UI, but that are not yet complete.
Completed tasks are submitted tasks that completed processing. Completed tasks include tasks that completed processing successfully and tasks that failed to complete processing successfully, but are nonetheless complete.
Cleanup tasks can remove tasks in the audit state and completed state from the task-persistence database. Cleanup tasks cannot remove submitted tasks that are still pending.
You can schedule, modify, and delete cleanup tasks through the following two options:
Use this option to schedule new cleanup tasks or modify existing ones.
Use this option to delete scheduled cleanup tasks.
Copyright © 2015 CA Technologies.
All rights reserved.
|
|