Configure a Job to Export Configuration

Configure a job to generate the outbound configuration set from the source Oracle Cloud Applications instance. This job will also generate a unique configuration set ID that is required by other CSM build jobs.

1. Open your VB Studio project.
2. In the left navigator, click Builds .
3. In the Jobs tab, click + Create Job.
4. In the New Job dialog box, in Name, enter a unique name.
5. In Description, enter the job's description.
6. In Template, select the System Default OL7 for Visual Builder template.
7. Click Create.
8. (Optional) Click Configure .
9. Click the Steps tab.
10. From Add Step, select Configuration Set Migration, and then select Export Data.
11. In Source Instance, select the environment that points to the Oracle Cloud Application's source instance.
12. (Optional) In ID Parameter Name, if necessary, change the parameter name for the configuration set. By default, it's set to CONFIGURATION_SET_ID.
    When a build runs, the job generates a unique configuration set ID, assigns it to the parameter name defined in ID Parameter Name, and then passes the parameter to the downstream jobs when the CSM jobs run in a pipeline. The downstream jobs can access the parameter's value by calling it in the $<PARAMETER_NAME> or ${<PARAMETER_NAME>} format.

    If you change the parameter name, note it down. You'll need it when you configure other CSM jobs.

13. In CSM/Sandbox Name, enter a name for the configuration set.
    When you import configurations later, the target Oracle Cloud Applications instance will create an internal sandbox with this name.
14. (Optional) In Description, enter a description for the configuration set.
15. In Username and Password, enter the credentials of an IDCS user who is also an Oracle Cloud Applications user.
16. (Optional) Under Optional Modules, specify the optional modules you want to export. By default, all modules are included.
    To specify a few modules only, deselect the Include all modules check box. In the Search Optional Modules dialog box that opens, enter the credentials of an IDCS user who is also an Oracle Cloud Applications user and click Search Optional Modules. Select the check boxes of optional modules you want to include and click OK.
17. (Optional) To export configurations if the target isn't registered on the source Oracle Cloud Applications instance, select the Create migration set even if target isn't registered check box.
18. (Optional) By default, the migration will move the latest application changes. To move all application changes, select the Move all changes check box.
19. Click Save.

When you run a build of this job, open the build's log to note the configuration set ID.

Here's an example:

[2020-07-01 08:00:00] Build scheduled. Build started by pipeline CSM
[2020-07-01 08:00:00] Build task id: a1b2c123-abc1-12d3-6789-5bc4d76531f2
.
.
.
[2020-07-01 08:01:35] Status: Export Started
[2020-07-01 08:01:35] Configuration Migration Set ID is 1239873457659876
[2020-07-01 08:01:39] IN_PROGRESS...
[2020-07-01 08:30:02] SUCCESS...
[2020-07-01 08:35:10] CREATED...
.
.
.
[2020-07-01 09:30:10] 2020-07-01 08:36:02.990: The outbound migration of CRM common objects completed successfully.
[2020-07-01 09:35:10] === End CSM Export Execution ===
Executor log size 4.6 KB (4,558)
[2020-07-01 09:35:12]
[2020-07-01 09:35:12] Build completed.
[2020-07-01 09:35:12] Status: DONE Result: SUCCESSFUL Duration: 35 min

After a successful build, if you want to view details of the exported migration set or download it, open the source Oracle Cloud Applications instance's Migration page and click the Outgoing tab. You don't need to download it if you plan to use the import configuration job to import configurations.

Here's an example of the Migration page:

Description of the illustration oracleapps_exported_migrationset.png