| Oracle® Identity Manager Administrative and User Console Guide Release 9.0 B25936-01 |
|
 Previous |
 Next |
| Oracle® Identity Manager Administrative and User Console Guide Release 9.0 B25936-01 |
|
Previous |
Next |
This section describes how to use the main features of the Oracle Identity Manager Administrative and User Console. It includes the following sections:
Many fields within Oracle Identity Manager pages come with lookup capabilities. These capabilities are very useful when you need to locate a record (a particular user account) or assign a particular entity to a record (for example, adding users to requests). Some fields come equipped with pre-defined menu choices, others provide full search capabilities (also referred to as a query function).
This section covers the following topics related to searching:
When searching for a particular record, there may be one or more fields in which you can supply information before clicking Search. Enter as much information as is available to you about the record you are trying to locate. For example, if you are only able to remember a user's first name, enter that and leave the other fields blank. Oracle Identity Manager will then display all user records that have the same first name as the one you entered. If you leave all fields blank prior to conducting a search, Oracle Identity Manager will display all records of that type. If you wish to restart a search, click Clear. Some screens also provide a Cancel button that you can click to cancel a search.
In additional to using the various fields to limit the records retrieved by your search, you can also use wildcard characters with the values you enter in a particular search field. This will cause Oracle Identity Manager to further filter your search.
The asterisk (*) wildcard character is used to represent unspecified portions of field values in a search. You can use the asterisk at the beginning, middle, or end of the value you are entering within a given field. For example, if you enter b* in the User ID field and execute a search, Oracle Identity Manager will display all users whose User ID begins with the letter B (for example, bsmith, bobj, barbarak, and so on). If the asterisk is placed in the middle of a search value, as in j*n, Oracle Identity Manager will display all records that begin with j and end with n (for example, john, joan, johann, and so on). If you place the asterisk at the beginning of the search value, as in *A, you will retrieve all records that end in A (for example, laura, maria, and so on).
Depending on the type of search you are performing, the manner in which the search is constructed and executed will differ. In addition, the results you retrieve will vary based on the context in which you are executing the search. A brief explanation of these differences is provided here.
|
Note: Searches in Oracle Identity Manager are case insensitive. For example, you can enter "RAJA" or "raja" to search for a user named Raja. |
If you are performing a user record search while creating or tracking a request, Oracle Identity Manager will only show users for whom you are the manager or administrator. In addition, the search parameters you enter will be combined to retrieve results. For example, if you enter John in the First Name field and NYoffice in the Organization field, Oracle Identity Manager will display all users with a first name of John, who work in the NY office and who are managed by you.
If you are performing a request record search (for example, while tracking requests), you must select which data element of the request you wish to search on. For example, you can search for requests by entering the request ID or a target user's ID, but not both.
The following sections describe how you can configure the Administrative and User Console to meet your data display requirements:
The Administrative and User Console will display text entries as truncated followed with three dots (…) at the end to indicate that the field length is insufficient for the entire entry. Here are two example when this occurs:
The web page, User Detail >> Resource Profile >> Resource Provisioning Detail displays some names in the Task Name field as partial entries.
During direct provisioning or request provisioning through the use of the Provisioning wizard (Provision Resource to User page), the Child table is displayed when you click Add to add child objects. The text entries in the Child table are partially displayed.
This display of entry is normal behavior. You can customized the field to show the entire entry name by modifying the global.property.tableColumnSize in xlWebAdmin.properties file and changing the default of 25 characters to a larger string value. The xlWebAdmin.properties file is located inside the xlWebApp.war file, which is located in the XellerateFull.ear file. You can find the xlWebAdmin.properties file in the
<XL_HOME>/xellerate/webapp/precompiled/jsp-temp/WEB-INF/classes directory.
During the resource provisioning process, the Administrative and User Console will display any associated Process Form with a child table that has 10 visible columns or fewer, by default.
To display a child table with more than 10 columns, change the value of the global.property.NumberOfChildTableColumns property in the xlWebAdmin.properties file, which is set to 10 by default. Set this value to the number of columns you want displayed.
Here are some Administrative and User Console page examples, which will display the child table with 10 columns at a time:
The User Detail >> Resource Profile: Click the Edit and View links for the Resource and Process Form.
The User Direct Provisioning Wizard >>Step 3 through Step 6.
The Organization Detail >> Resource Profile: Click the Edit and View links for the Resource and Process Form.
The Organization Direct Provisioning Wizard >>Step 3 through Step 6.
In the Resource Detail >> Organizations Associated with this Resource, click the Edit and View links for the Resource and Process Form.
