Indexing log messages are stored in the application server log (\App_Data\Logs\AppServer.log by default).
A new indexing run usually starts after the indexing interval period specified by the Common | Indexing | Interval configuration parameter has elapsed.
If a table being indexed contains more objects to be indexed than the maximum specified by the Common | Indexing | BatchSize configuration parameter, then the indexing process for the table will stop.
A message is written to the application server log:
INFO (Indexing ) : Index for Person partially updated, will continue at next run
If at least one table has not been fully indexed, then indexing will restart after three seconds. A message is written to the application server log:
INFO (Indexing ) : Index is incomplete (28.06%); indexing will continue in 3000 ms
If a signal to reuse (<recycling>) the application pool has already been received, the log message will read, for example:
INFO (Indexing ) : Index is incomplete (28.06%); indexing will continue when the application re-starts
As long as there is at least one incomplete table, then only the incomplete tables will be indexed during an indexing run.
NOTE: The Web Installer uses default values for most configuration settings. You can use these values normally. It is recommended you check the settings with the help of the Manager Web Configuration Editor.
You configure the Manager web application configuration with the Manager Web Configuration Editor. The Manager Web Configuration Editor is part of the web application and can be found in the install directory in the subdirectory WebConfigEditor.
To run configuration
-
Start the file WebConfigEditor.exe and log in to the One Identity Manager database.
The Manager Web Configuration Editor automatically opens the web.config file of the web application.
-
Modify the configuration settings.
- Save the changes.
Detailed information about this topic
In the General pane of the Manager Web Configuration Editor, configure the appearance of the Manager web application.
Table 41: Meaning of general configuration settings
|
Language |
Language. The language influences how dates and numbers displayed amongst other things. |
|
Session timeout |
User's idle time in minutes after which the user is automatically logged out. This value depends on the timeout mode and directly effects memory requirements and therefore the application's performance.
NOTE: This value should be set as long as required and as short as possible because orphaned sessions use memory and negatively effect the application's performance. |
|
Timeout mode |
Methods for determining timeouts. Permitted values are:
-
TimeOut: A session is ended when the period of time defined under the session timeout has elapsed with no user activity.
-
HeartBeat: A session is ended when the period of time defined under the session timeout has elapsed with no user activity. The user's open browser window prompts automatically. The timeout begins when the browser window is closed. |
|
Visualization |
Visualization of the application. |
|
Dynamic design select |
Not in use. |
|
Enable portal mode |
Permits the application in a frame to be linked to another application. |
In the Database connection pane of the Manager Web Configuration Editor, specify all database parameters for the Manager web application.
Table 42: Meaning of database connection configuration settings
|
Database |
Database connection. You can select between a SQL Server database connection and an application server. |
|
Application |
Application which specifies the contents of the web application. Usually, you select Manager. |
|
Display name |
Name used as application name, as in the title bar of the browser, for example. |
|
Authentication |
Methods for authenticating the user when logging in to the application. |
|
Single sign-on |
Specifies whether single sign-on is used. Set this option if you user single sign-on. The application does not display a login page to the user but tries to identity the user automatically. |
