Adelia Studio allows you to create an environment inside an existing database schema, for schema-compatible database management systems (DB2, Oracle or SQL Server). This enables you, in particular, to create a complete work environment (correction manager, buffers, etc.) within a single database (or Oracle instance).

Access to an environment created in a schema is provided by an expansion of the connection URL syntax. The URL is comprised of the name of the schema containing the environment, followed by the "/" character and the database connection information.

When a schema is specified, the environment name is comprised of the schema name followed by the database name. If no schema is specified, or in the case of the default SYSADEL schema, the environment name is the name of the database.

Special precautions

• Though the default SYSADEL schema can coexist with named schemas within a given database, this type of configuration should be avoided, particularly due to risks of confusion when running scripts designed for a conventional environment.
• Important: restoring a database replaces all environments defined in the database. To backup and/or restore a specific environment, we recommend importing / exporting schema data using the Adelia tools or the database management tools. The backup and restore options on an environment's Database management sub-menu are not enabled for the environments defined in a schema.

Constraints

To create an Adelia environment in an existing database, this database must meet the following constraints:

• The schema name must be entered in upper case characters and must not contain any spaces or special characters.
• For Oracle and SQL Server, the schema must be created in the database by the administrator. With DB2, however, schema creation is implicit.
• For Oracle, specific rights must be associated with the instance for querying certain metadata. The following queries must have been run in SYSDBA:

• The user used to create the tables must possess database administration rights.
• Adelia does not provide any tool for deleting a database schema. You must de-catalog the Adelia icons schema, then delete it manually using the tools provided by the concerned database management system.

Example: creating a version manager in an Oracle instance

This example details the configuration of an Oracle instance to create a version manager from an existing environment. The Oracle instance used is the default instance installed by Oracle (ORCL).

You must possess a user account with DBA rights for the creation of Adelia objects, along with SYSDBA rights for initial instance configuration.

The default system profile (system) is used in this example.

We shall convert a TEST environment to a version manager containing three environments. TESTEXP (production), TESTCOR (correction) et TESTDEV (development).

The different steps in creating the example are as follows:

1. Minimum Oracle instance configuration - definition of catalog rights

You must log on as SYSDBA to grant specific rights. To simplify the configuration process, we shall perform all operations directly on the server.

2. Create schemas for the environments

From this step onwards, you can work on the client workstation. Make sure that the ORCL instance has been cataloged under this name in the TNSNAMES.ORA file on the client workstation.

Note: These users do not require any specific rights. They do not need the CONNECT right either. Only the schema is required.

At this point in the example, you can also create Oracle users corresponding to the system profiles of the software engineers registered with the source TEST database.

3. Create the environment

From the Adelia Studio Administration menu, select Create environment/buffer > In an existing schema or database.

Select Oracle as the target DBMS, then enter the following connection parameters:

Wait while the wizard creates the tables. Once the environment has been created, use the Adelia import or copy tools to load the data from the TEST environment into the TESTEXP schema.

Note that you can create and import an environment into an earlier version using the migration scripts, in the same manner as with previous versions.

Optionally, to simplify the task of version manager configuration, the DBA profile used should also be registered as the software engineer in the environment. Since V12, however, this is no longer necessary. In this case the ADELIA software engineer is redefined on SYSTEM.

4. Create the correction environment

To create the correction environment, display the TESTEXP environment attributes, then select the Type tab.

Enter "TESTCOR/ORCL" as the name of the correction environment, click on Build and follow the wizard's instructions. Ensure that you specify the system profile in the database management tool's connection parameters:

5. Create the development environment

To create the development environment, display once more the TESTEXP environment attributes, then select the Type tab. Next, select Create from the environment list context-sensitive menu.

In the dialog box that is displayed, enter "TESTDEV/ORCL" as the development environment name, "Development environment" as the environment type, then click Create. Follow the wizard's instructions. Use the default connection parameters in the database management tool:

Version manager creation is complete. If you did not redefine the software engineer administrator at step 3, or if you have not yet created the Oracle users corresponding to the Adelia software engineers, then you must do so before you can connect to the environments.

With the exception of the Oracle-specific configuration operations, this step by step guide also applies to DB2 and SQL Server, under the following conditions:

• for SQL Server, you must also create the schemas and connect with a profile that has "db_owner" (or at the least "ddl_admin") rights for the database.
• for DB2, you simply need DBADM rights for the database.

↑ Top of page