...
| Gliffy | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
User Accounts
MettleCI needs the following dedicated accounts described in the sections below to enable installation activities as well as support on-going operation.
| Info |
|---|
Note: The names given below are simply proposals for reference purposes and can be changed to meet your organisational requirements. If |
...
you administer your accounts via a centralised repository (e.g. Active Directory) then any accounts specified in the following list with the same name can, of course, be the same account with privileges as necessary to cover multiple roles across multiple environments and components. |
| Info |
|---|
Note: The account used to install MettleCI is not required to be shared with the Developers. Developers log in to MettleCI using their existing DataStage user accounts. |
MettleCI Host
Two Windows user accounts are required for the purpose of installing and administering MettleCI-related components on this host. They must...
ideally be named mciconfig1 and mciconfig2
have administrator privileges sufficient to
run Windows tools "...as administrator"
install software for use by other users on the host; and
create, remove, start and stop Windows services.
Note: The second account acts to complement the first account in case the owner of the first account becomes unavailable, for whatever reason, or we collectively choose to perform work in parallel.
A Windows user account is required to act as a service account for executing MettleCI services. It ...
would ideally be named mciservice
must have only sufficient privileges to run the services installed by the mciconfig* accounts
...