MettleCI Platform Components
The following high-level MettleCI architecture shows the key software components to be installed, and their communications between hosts.
| Gliffy | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Some points to note:
MettleCI works with all Information Server deployment topologies, including High Availability, Grid, and Cluster environments, For clarity, this diagram shows each tier residing on its own, dedicated host.
Application Lifecycle Management components can be co-hosted with the other tools on the MettleCI Host or located on another host (on-premise, cloud or SaaS).
...
User Accounts
MettleCI needs the following dedicated accounts to enable installation activities as well as support on-going operation.
Note: The names given below are simply proposals for reference purposes and can be changed to meet your organisational requirements. If a customer administers its 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.
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
DataStage Development Engine Tier
An operating system user account and corresponding DataStage application account for in-bulk tasks (e.g. CI, CD) performed by MettleCI
Ideally named
...
mciagent
...
Accessible via SSH from both the MettleCI Host and the MettleCI consultant's computer.
Capable of accessing your DataStage Engine Tier's filesystem such that DataStage can read files and directories generated or modified by this account.
In particular this account will make changes to the contents of your DataStage Projects directory.
Primary group must be
...
dstage
...
(or equivalent as configured for your DataStage platform)
On *nix hosts, this account must be able to source the
$DSHOME/.dsenvfile.The DataStage application account must be assigned the Information Server
...
Suite Administrator
...
and
...
DataStage Administrator
...
roles.
An operating system user account and corresponding DataStage application account for use by MettleCI end-user functions (e.g. MettleCI Workbench)
Ideally named
...
mciworkb
...
Accessible via SSH from both the MettleCI Host and the MettleCI consultant's computer.
Primary group must be
...
dstage
...
(or equivalent as configured for your DataStage platform)
rootmust be able to run commands under this user (viasudo) from within a SysVinit service.On *nix hosts, this account must be able to source the
$DSHOME/.dsenvfile.The DataStage application account must be assigned the Information Server 'Suite Administrator' and 'DataStage Administrator' roles.
Password Expiry
All MettleCI-related service accounts (both application and operating system) should have passwords that don't expire. A change to a service account password will require updates to MettleCI configuration to re-enable the MettleCI functions that rely on that service account. Unplanned service account password changes are highly likely to cause unnecessary delays.
...