An administrator manages independent model servers and repositories in the Administration Program.
Prerequisites
Innovator repositories are managed by a model server administrator.
Prerequisites for repository administration:
- A License Server must be started
- A Model Server must be started
- The Administration Program must be started
- You must be logged-in as repository administrator
In the following sections we'll assume that these requirements are met.
Repository Administrator Tasks
The repository administrator's tasks include
-
Starting and stopping model servers
-
Creating, recovering and saving repositories
-
Setting times for automatic recovery of a repository
-
Manually saving a repository
-
Locking the model server so that you can carry out administrative tasks with models
-
Renaming and deleting repositories
-
Setting single sign-on for user login to all a repository's models.
-
Creating, renaming and deleting repository models
-
Exporting complete models to a new repository
-
Copying and pasting a model in a repository using the clipboard
-
Setting options regarding inactive users
-
Setting-up automatic closure of inactive model servers
Repositories
All directories and files of an Innovator repository are located in a directory that has the same name as the repository itself. This structure facilitates administrative tasks such as backup operations or the creation of copies.
The central data management in the Innovator online repository makes all modeling results immediately available to all project members. This ensures that the necessary data is always up-to-date and also, that model results once obtained can be re-used at any time.
A consolidation of the work results of different project team members is not necessary1 as all team members use the same dataset and thus modifications carried out by individual users are visible to all other users right away.
A repository's models are provided via a model server.
Models
Repositories may contain any number of models. We recommend careful consideration into how models and repositories are organized to speed up performance.
Note
Only using one model per repository reduces concurring access to the model server and can considerably improve performance. Saving and versioning the respective model is targeted and therefore easier. Downtime when administrative tasks need to be carried out for the repository only affect one model. This is why this process is recommended.
On the other hand, every model server process in the main memory has a minimum size of more than 100 MB thanks to the basic model database structure. This may mean that it is necessary to split onto various different systems due to the high volume. Repository backup points on one system have to be phased so that the system is not overloaded.
Structure directories and systematic directory and repository names make model administration easy to use.
You can create new models using model templates as a basis or use existing models as a template.
A model template allows you to define defaults for modeling results for special application fields or special process models. By defining such a model template, you specify adaptations and extensions.
Related Topics
This chapter contains the topics:
