SCCS:SYSTEM THREE-TIER
path: SCCS:SYSTEM THREE-TIER

Category SCCS

Configuring a three tier development environment

For the purpose of illustration a typical hierarchal nomenclature used in Nucleus documentation

Account Description
1. DEVPROGDevelopment
2. QAPROGQuality Assurance
3. STAGINGProduction support

It is not mandatory that accounts be named as above.
These names are used for clarity in definition.

Typical setup styles

Typical configuration styles that may be found within Nelson/Pick style or Multi-dimensional environments:

Style Description and Notes
1. MixedWork within an account where both Data and program files exist

The default ‘project’ is the current account
External Program source ‘set’ (project) may be set
Least preferred method.

2. DataWork within data account.

Program source exists in an external account
Program source ‘set’ (project) may be set
Program source ‘set’ (project) may be attached or detached at will

3. ProgramWork within a program account with q-pointers to data

Data is kept externally

4. EmptyWork within an empty account, with q-pointers to both data and programs

Any ‘project’ may be attached within the “Empty” account
Designated Program source ‘set’ (project) may be attached/detached at will.
Unique data accounts can be setup for each user, and easily refreshed without a need to re-establish pointers, re-create files.
Most flexible style, demanding the least maintenance when updating data sets.

The “Empty” setup style is recommended, as it provides the most flexibility for developers and requires very little work to support once it is setup, as the attached data account can be merely deleted if required, and a new one restored without requiring ANY additional configuration or administration.

Notes:

  • Files to be controlled under Source Control are defined using NUPROJECT
  • A project can encompass numerous named program files, any or all of which may be placed under source code control, either locally or externally.
  • Any project (or named account) can be addressed from within a working account.
  • Data is NOT promoted from account to account.
  • Promotion is a ONE WAY STREET.

Typical examples of the four setup “styles”

Working within a program account

Working Account Program Source
DEVPROGDEVPROGPoints to data in DEVDATA or UserData{name}
QAPROGQAPROGPoints to data in QADATA
STAGINGSTAGINGPoints to data in STAGING{.DATA}

Working within an “Empty” account

most flexible, least work to support

Working Account Program Source
UserWork{.name}DEVPROGUserData{.Name} or DEVDATA
QAWORKQAPROGQADATA
STAGING.WORKSTAGINGSTAGING.DATA

Working from Mixed Account

least flexible

Working Account Program Source
DEVPROGDEVPROGPrograms and data live in DEVPROG
QADATAQADATAPrograms and data live in QADATA
STAGINGSTAGINGPrograms and data live in STAGING

Working from within a DATA Account:

Working Data Account Program Source
DEVDATADEVPROGProgramming done in DEVDATA
QADATAQAWORK or QADATAProgram in QADATA
STAGING.DATASTAGINGProgramming done in STAGING.DATA

See also