Starting and Closing the Configuration Editor

You can start the Configuration Editor in the Innovator program group, in the model editor or in the Administration Program.

Starting the Configuration Editor

Prerequisites

As is the case with any other Innovator program, the Configuration Editor (inoconf.exe) requires a license server that must be running.

Your role needs to have the Configure privilege to be able to carry out configuration tasks. You have read only access to configuration without this privilege. Model administrator mode has all privileges.

A requirement for working with Innovator is that a license server is started on the relevant computer. If the license server cannot be accessed, all other Innovator programs will not be able to run.

Context

The Configuration Editor manages all of a model's configuration elements. In addition to the actual profile definition (in the sense of UML 2), this includes, for example, display properties such as colors and fonts, dynamic menus for individual diagram types, engineering actions, verification routines and documentation structures.

You can also manage the users, their roles and rights, as well as user logins on the license server in the configuration editor.

How to proceed

Under Windows, start the Configuration Editor in the program group.
If working with Linux, start the Configuration Editor from the shell by entering inoconf.
You can select a model in the Administration Program and call its configuration in the Configuration Editor with the Model>Model>Configure menu command.
You can jump to your model's configuration using the Model>Administrative Tasks>Configure menu command in the Innovator model editor; this jumps the selected model element's stereotype or metaclass to the Stereotype view.

Unlike the previous case where the model was already selected when starting the Innovator model editor and you were already logged-in there, you need to select the model and log-in to it by directly calling the configuration editor or in the Administration Program.

The Login dialog appears when directly calling the configuration editor; select the model in the repository tree and log into the model as a user.

The Login dialog appears in the Administration Program if you select a model in the server tree and call the Model>Model>Configure menu command.

Logging-In to the Model

Context

Your role needs to have the Configure privilege and the access right for the profile to be changed if you wish to edit the configuration. Model administrator has these rights.

How to proceed

Enter which user you want to log-in as. Activate the corresponding radio button and, if necessary, select a user from the User drop-down list.
If applicable, enter the user's password in the Password field.
Select a role from the Role drop-down list.
Confirm your login with Login.

The Configuration Editor appears.

Logging-In as Administrator

Context

You can assign rights role requires as model administrator in the Configuration Editor if your role does not have the Configure privilege and access rights to the profile to be changed.

How to proceed

Select the Configuration>Model Administration>Login Administrator... menu command or double-click on the user display to the left on the status bar.

The dialog of the same name appears.
If applicable, enter the administrator's password in the Password field.
Confirm the login with OK.

You now have administrator rights. The administrator icon is shown in the status bar on the left-hand side.

Logging-Out as Administrator

Prerequisites

You logged-in as model administrator after already logging-in as a normal user.

How to proceed

Double-click on the administrator icon on the left-hand side in the status bar.

You are logged-out as model administrator and now have the rights assigned to your role. The user icon is shown in the status bar on the left-hand side.

Closing the Configuration Editor

How to proceed

Jump to the Configuration Editor.
Select the Configuration>Exit menu command or close the configuration editor's window.

You are automatically logged-out of the model if you are not logged-in on other interfaces.