The Custom Build process of the Schemation DEM is a process called:
schemation_build
This process interfaces to the DEM through the Oracle database in which the DEM is located. It can only operate when a set of four parameters are correctly defined.
There are four Schemation specific parameters which affect the operation of Schemation during a Custom build. If building from a Windows platform, make sure the parameters are appropriately defined for the shell running the schemation build process. If from UNIX, again, make sure they are suitably defined and exported before running the schemation build process. If any of these mandatory parameters are undefined an error of the following type will be displayed:
ERROR SCH-00001: The mandatory environment parameter SCH_HOME is not set.
This parameter defines the location on the file system where the DEM will find all the source files and data required to build an environment. When invoked, the schemation build process examines this directory and will expect to find two directories at this level. The build code and the build data directory. These are discussed later.
This parameter defines the Oracle username, password and connect string that the 'schemation build' process uses to connect to the database containing the DEM. The database connection is used for two purposes:
* To gain access to the DEM configuration and logging tables;
* To gain access to the environment being built to load data.
The DEM does not require direct access to the environment being built using this account. The account is built using the capabilities and privileges of the DEM. The account used for the pupose of performing the database build must be registered as a controller of the environment that is to be built. (See next parameter.)
The format of this parameter's value is:
{username}/{password}@{tns string}
where
{username} is the username of an Oracle account which is also a registered DEM user and is also a controller of the environment to be built.
{password} is the Oracle account password for {username}
{tns string} is the TNS alias defined that can be used to connect to the DEM database.
This is the Schemation Project Environment (PENV) identifier. In DEM terminology, an environment is uniquely identified by its Project-id and its Environment-id. This permits several projects to have environments with the same name. A project should be thought of in business terms where a company may be working on different projects for different clients.
Within a project you may define several environments for special reasons (e.g. Customer Acceptance Test, Reference Model, Internal Test, Regression Tests or even an isolated environment that each developer has on the project for their own testing and coding activities.) Each of these environments will be given an identifier within the Project. It is the combination of the Proiect-id and the (project specific) Environment-id that uniquely identifies the environment to be built. The SCH PENV should be set to this value.
The SCH PEN parameter value is case sensitive.
This parameter governs the number of data load pipelines that the schemation_build process may invoke, concurrently, to load data into an environment as part of the environment build activity. The default value is set at four.
Setting this parameter will override the default setting of four.
In addition to the Schemation specific parameters outlined above there are three other parameters used by the schemation build process.
This is the standard ORACLE HOME parameter which is required to use standard Oracle Server utilities and tools. It must be valid for an Oracle Client Installation which is compatible with the Oracle Database that runs the DEM.
This may be required if the connection to the Oracle database server is not to be specified through SQL *Net. If the SCH DBCON contains a TNS name, then there is no need for this parameter to be set.
The standard PATH parameter must include the location of the Schemation code base. It is recommended that the Schemation code be installed at usr/local/bin' for UNIX. If this is not the chosen location for the code then the actual location of the executables must be listed in the PATH environment variable.