How do I migrate approval rules from one environment to another?

Title and music.

In this video I’ll explain how to migrate approval rules from one environment to another.

First, there are a few requirements:

The source and target environments must be at the same patch level and release version.

The BPM Admin Role is required to access Oracle SOA composer.

There are five steps to migrating approval rules to another environment:

Login to SOA Composer
SOA Composer Export
Examine Downloaded .JAR file
Modify Exported .JAR file
And Import to SOA Composer

First, I’ll login into my source environment and in this example, the URL starts with: etsk-test .

In the source environment, open Transaction Design Studio (TDS) to display the rule (e.g. the Promote rule).

I also have the approval rule open called Neel_Rule; which I’ll migrate over to another environment.

Show the approval rule that is to be migrated to another environment (e.g. the Promote rule called “Neel_Rule”).

My target environment starts with: etsk; which does not have the Neel_Rule in the PromotionsRuleSet.

Show the target environment which does not have the Promote rule called Neel_Rule in the PromotionRuleSet.

To export approval rules, I need to go to the SOA Composer.

On the Approval Rules page, I’ll copy the root URL from the browser tab.

1. On the Approval Rules: Promote: PromotionsRuleSet page, copy the root URL in the browser address field (in this example it is https://etsk-test.fa.us6.oraclecloud.com/ ).

I’ll then open a new browser tab and paste in the URL adding soa/composer to the end of it.

Open a new browser tab and paste the URL in the address field and add /soa/composer at the end (i.e. etsk-test.fa.us6.oraclecloud.com/soa/composer).
Press the Enter key.

Which then takes me to the SOA Composer page of my source environment.

On the right side, I’ll choose to export my SOA changes.

On the Oracle SOA Composer page in the upper-right corner, click Export/Import and select Export SOA Changes.

A dialog box appears allowing me to click Export to create an archive containing all SOA changes on this system.

In the Export SOA Changes window, click Export.

After a few moments the export completes. Then I can download the archive to my local machine.

In the Export SOA Changes window, click Download.

Once downloaded, I’ll use the proper application to open it.

I’ll navigate to the folder where it is downloaded.

At the bottom-left of the screen, click the arrow of the downloaded file and select Show in folder.

I’ll right-click on the file.

Locate the .JAR file and choose Open with WinRAR. Right-click on the .JAR file and select Open with WinRAR.

The application opens and shows me the META-INF folder and other .JAR files that are different HCM tasks that we’ve configured for approval rules.

If I wanted to migrate all these tasks, I could; however, for this example I only want to migrate the Promotions rule. So, I’ll delete all the rest.

Delete all the .JAR files except for the file that you want to migrate (e.g. default_HcmEmploymentPromotionsComposite_11.13.22.01.0.jar).

In the Delete window, click Yes.

I’ll open the META-INF folder and open the .TXT file. Open the .TXT file (e.g. CS_SOA_ExportList.txt).

A Notepad window appears showing all the .JAR files that we saw in the previous folder.

I’ll keep the HcmEmploymentPromotionsComposite.JAR file and delete the others. In the Notepad window, delete all the .JAR files except for the file you want to migrate (e.g. default/HcmEmploymentPromotionsComposite!11.13.22.01.0:default_HcmEmploymentPromotionsComposite_11.13.22.01.0.jar).

I’ll close the Notepad window. Click the X to close the Notepad window.

When prompted, I’ll click Save. At the Notepad message, click Save.

The system asks if I want to update the file in the archive, and I’ll click Yes. At the View message, click Yes.

I’ll navigate back to the previous folder to ensure that it only contains the .JAR file that I want migrated. Click the arrow to return to the previous folder.

Then I’ll close the WinRAR window. Click X to close the window.

In the target environment I’ll copy the root URL. In the target environment copy the root URL (e.g. https://etsk.fa.us6.oraclecloud.com/).

I’ll open a new browser tab and paste it in adding soa/composer to the end of it and press Enter. Open a new browser tab and paste the URL in the address field.

Add /soa/composer at the end of the URL. Press Enter.

This time in the SOA Composer, I’ll choose Import SOA Changes. On the Oracle SOA Composer page in the upper-right corner, click Export/Import and select Import SOA Changes.

I’ll locate the archive from my local machine containing the exported changes. In the Import SOA Changes window, click Choose File.

And select it. Locate and select the .JAR file you downloaded and click Open.

I’ll click import to upload and apply the changes. In the Import SOA Changes window, click Import.

And once the import has completed, I’ll close the window. In the Import SOA Changes window, click X to close the window.

In the target environment in the Approval Rules section on the Transaction Manager: Rules page, I’ll click the icon in the Configure Rules column. In the target environment in the Approval Rules section on the Transaction Manager: Rules page, click the icon in the Configure Rules column.

And I see that the Neel_Rule has successfully migrated to the target environment.

For more information on this topic, you can view the courses on Oracle University or reference the available guides on Oracle Help Center.

Thanks for watching.