5 Configuring the Source Environment and the Target Environment

Before you can use SCM to transfer content from the source environment to the target environment, you must first configure both the source and target environments.

Note: In order to work with Agile e6, the user EDB-SCM must be activated. For security reasons, the user EDB-SCM is not activated in a new Agile e6 application. The EDB-SCM user must be activated by the Administrator by either setting a password or by configuring the LDAP login for the EDB-SCM user. For more information about how to activate a user, see the Administrator Guide for Agile e6, "Setting and Changing Initial Passwords in a New Agile e6.2.0.0 Application."

5.1 Configuring the Source Environment

Configure the source application where you define the customization code.

Note: A valid vault must exist before you begin this procedure.

1. Define which vault is used by SCM to store created files.

   Configure the LogView Constant EDB_SCM_CHG_DOC_AREA to a valid vault name.

   For more information about how to create a valid vault, refer to the Administrator Guide for Agile e6.

   Choose Manager > Macro > LogiView > Declarations > Constants.

   The Constants tab is displayed.

   Search for the EDB_SCM_CHG_DOC_AREA constant. Change the value from "TEST" to the valid vault name you have defined, for example, "SCMFiles".

2. Register the directory to store SCM files as allowed directories for server-side checkout/checkin.

   For more information see Administrator Guide for Agile e6, section/chapter "File Server Administration."

   In the context of SCM, normally the application dump directory is used ( %ep_root%\<app_name>\dmp,)

   You must define the directory where the loader files are stored as an allowed directory.

   Choose System > Other Parameters.

   The Configuration form is displayed.

   Create a new parameter and enter a name in the Rubric/Parameter field, for example, EDB-FMS-ALLOWED-PATHS.

   On the Configuration Parameter tab, add a new directory, for example, EDB-FMS-UNIX-DMP-DIR. In the Configuration dialog, enter the appropriate path for your installation.

   Select the row you just added in the Configuration dialog and choose Take Entry in the context menu to assign the parameter to the rubric.

3. Update the number variant for SCM.

   Choose Manager > Tools > Number Server.

   Search for SCM, and then create a new number variant by editing all occurrences of the name of SCM-DEV to SCM-SRC. Save it.

5.2 Configuring the Target Environment

Configuring the target environment is very similar to configuring the source environment.

For more information about how to create a valid vault, refer to Oracle Agile Engineering Data Management Administration Guide for Agile e6.2.1.0.

1. Define which vault is used by SCM to store files from the source environment.

   Configure the LogView Constant EDB_SCM_CHG_DOC_AREA to a valid vault name.

   For more information about how to create a valid vault, refer to the Oracle Agile Engineering Data Management Administration Guide for Agile e6.2.1.0.

   Choose Manager > Macro > LogiView > Declarations > Constants.

   The Constants tab is displayed.

   Search for the EDB_SCM_CHG_DOC_AREA constant. Change the value from "TEST" to the valid vault name you have defined, for example, "SCMTargetFiles".

2. You must define the directory where the loader files are stored as an allowed directory.

   Choose System > Other Parameters.

   The Configuration form is displayed.

   Create a new parameter and enter a name in the Rubric/Parameter field, for example, EDB-FMS-ALLOWED-PATHS.

   On the Configuration Parameter tab, add a new directory, for example, EDB-FMS-UNIX-DMP-DIR. In the Configuration dialog, enter the appropriate path for your installation.

   Select the row you just added in the Configuration dialog and select Take Entry in the context menu to assign the parameter to the rubric.

3. Update the number variant for SCM.

   Choose Manager > Tools > Number Server.

   Search for "SCM-EXP-ID", and then update the number variant by editing all occurrences of the name of SCM-DEV to SCM-TRG. Save it.

Note: For the Target environment, you must use a different prefix value for number server "SCM-EXP-ID" than you defined for the Source environment.

5.3 Configuring Modification Types for SCM

In the source system, you define the types of customization objects than can be assigned to a bundle.

Agile e6 SCM is delivered with a preconfigured list of customization object types (Agile e6 Masks).

You can review the list of customization object types:

Choose Manager > SCM > Configuration list

5.3.1 Define and Add Customization Modification Objects

The customization objects recognized by SCM are defined in the SCM Configuration.

You can define your own customization type objects and then add those objects to the Configuration list.

1. Open the Configuration list:

   Choose Manager > Tools > SCM > Configuration List.

2. In the SCM Configuration list, you define the mask names.

   Refresh the tab to see the names supplied with the standard delivery.

   The masks are grouped by the rubrics and define the data models associated with each rubric.