The Administration Program displays information about the status, update times and inactivity options for repository model servers. It also allows the editing of some properties.
Purpose
If a model server with the same version as the administration program is selected in the Standalone Servers tab, information about the model server appears in the right-hand information area, or some of the properties are offered for editing. You can switch between these two views.
Prerequisites
Model server administration login is required for most information and editing properties.
Structure
The information area consists of the following expandable sections and further elements for model servers, depending on the view.
* This information and properties require a login as a model server administrator.
Information View
This view displays properties of the selected model server.
-
Status
The following information is displayed as the status for the server: name, computer name, IP address, user and status of single sign-on and logins.
-
Update*
The Innovator security concept consists of manual and automatic repository updates. The settings for the time interval and automatic update times are displayed here.
-
Inactivity*
The settings for automatic logout if a user is inactive are displayed.
This function allows model elements that are locked for exclusive editing by inactive users to be released, for example.
-
Log File*
Displays the log file of the respective model server and allows the saving of the file.
Properties View*
This view allows the editing of some model server properties.
-
Update
You can enter a positive integer between 1 and 1440 (24 hours) into the Interval (min) field as the time interval for the automatic data update. If you do not want a regular update, leave the field empty or enter a zero.
You can enter the times for the automatic data update in the format HHMM (hours and minutes) in the Times field. You can specify several different times by separating the entries using commas (e.g., 0900, 1200, 1500, 1800). If you do not want an update at defined times, leave the field empty or enter a zero.
Once an update has been carried out, all changes to the repository are successively stored in a telegram file; this file and the stored repository enable a repository that has crashed to be restored.
Note
Make sure that the repositories are not updated at the same time in order not to overload the system as this can lead to drastically increased response times.
-
single sign-on
Single sign-on simplifies logging-in to the repository's model by using the user's system login. This means that it is not necessary to reenter the password.
If the single sign-on check box is activated, the central user management rules of the main license server are applied for this repository. You then need a model server rule for the further management of the repository.
Note consequences?!
-
Inactivity
Define the time criterion for the recognition of inactive users in order to release model elements locked for exclusive editing, for example.
You can set a period in minutes during which the user must not have caused any model server activity for the user to be regarded as inactive. The time frame must be at least 10 minutes. 0 or empty deactivate this mechanism.
Use the Automatically log out inactive users check box to activate the automatic logout of inactive users. You can log out inactive users at any time using the Log Off Inactive Users context command.
-
Logins
You can prevent users logging-in so that you can carry out administrative tasks. You can inform them about the reason for login prevention. You can then permit the users to log-in again.
-
Apply Button
Modified properties only take effect when confirmed with the Apply button.
-
Discard Button
Modified properties are reset.
Processes Supported
Changing the Properties of Model Servers and Repositories
Model Server and Repository
Related Topics
