8 Transfer Content from the Source Environment to the Target Environment

The chapter illustrates an example of transferring content from the source environment to the target environment

8.1 Creating Customization Files

1. Log in to the Agile e6 source application.

2. For this example, choose Message Data.

   Define a Bundle to contain all the modification. Choose Manager > Tools > SCM - System Customization Management > Bundles.

   The customization files are created and are checked into the file vault (name is defined by LGV constant EDB_SCM_CHG_DOC_AREA).

3. In the Bundles form, create a new bundle. Enter a bundle number and a short description. Click Set Active.

4. Click the Message Data tab and refresh. Select the row you want to modify and press Ctrl-B to lock the record. Modify the message and click Save.

5. To add the message to the current active bundle, select the row and press Ctrl-A. On the Modifications tab, you can view the modifications you can view the modifications that you made.

6. To create a new message, clear the active bundle in the SCM toolbar. Insert a new row, create the message and save it.

7. Select the new message and press Ctrl-A. Because there is no active bundle selected in the SCM toolbar, a dialog appears that prompts you to select a bundle, and click Continue.

8. To export, click the Export button. The Entity Relations for Export dialog appears. Click Continue. Click Yes.

9. The File Names dialog appears. It displays the loader file name and the path. Click Continue.

   An export report message is displayed.

8.2 Example: Transfer Content by Releasing the Bundle

1. On the Bundle form, change the status of the bundle from In Work (110) to Released (230).

   Click the change status icon (Change status of the current object).

2. The "Please choose an option" dialog appears. Released is selected. Click OK.

3. In the next dialog, you can select the validity range: a Valid From date (defaults to the current date) and a Valid Until date. Click OK. The files are checked in.

8.3 Importing Customization Files into the Target Environment

1. Prerequisite: Copy the SCM files created by the "Export" from the dump directory of the source environment to the dump directory of the target environment.

2. Log in to the target environment.

3. Choose Manager > SCM > Import. The File Names dialog appears.

4. Enter the file name you want to import in the Loader field. Click Continue. Click Yes, then click Yes again. The file is imported, and an import report is displayed.

5. Refresh the Message Data tab to view the imported customizations.

In the target environment, after import, you can check for inconsistencies by using the bundle list/form context menu function Check Import.

8.4 Identify Modifications with Post Action UserExit

An active bundle must be set to use Post Action UserExit.

1. Log in to the source environment.

2. Create a new bundle. Set the bundle to Active.

3. Determine modification you wish to include.

4. Choose Manager > Tools > SCM > Configuration.