Introduction:

In the dynamic world of enterprise software, the ability to customize and migrate these customizations seamlessly is crucial. This blog post delves into the world of Oracle Fusion Redwood pages, focusing on how you can efficiently migrate your customizations from one environment to another, such as from a TEST instance to a Production environment or between non-production instances.

Oracle Fusion Redwood represents the next generation of enterprise application aesthetics, offering a user experience that is both intuitive and adaptable to the varying needs of businesses. In this guide, we’ll explore the nuances of migrating customizations within this innovative platform, using the “Connections” page – an employee directory-like feature – as our example.

Why Customize Oracle Fusion Redwood Pages?

Customizations in Oracle Fusion Redwood serve several purposes. They can enhance user experience, streamline workflows, and ensure that the application aligns perfectly with your organization’s specific processes and needs. Whether it’s tweaking the layout, modifying fields, or adding new functionalities, these customizations make Oracle Fusion not just a software solution, but a tailored extension of your business operations.

The Significance of Migration

Migrating customizations is a critical task when moving from a development or testing environment to a production environment. This process ensures that all the tailored features and functionalities are seamlessly transferred without disrupting the existing workflow. It’s a process that demands precision and understanding of the Oracle Fusion architecture to ensure a smooth transition.

Steps to migrate changes done for Connections from TEST Instance to Production Instance:

• Login to Test pod
• Navigate to Fusion: Me -> Connections > Setting and Actions > “Edit Page in Visual Builder”
• Click on the Back arrow or on the Workspace1 to navigate to Menu option

• Environment: Click on Environments -> Create Environment

• Enter Environment Name and Click on Create:

• Once the Environment is created. Click on Add Instance

• In Add Server Instances, select Instance Type as Oracle Cloud Applications and Authentication Method as Application Credentials

• Enter the PROD URL, Username and Password and save the Environment
• Builds: Click on the Builds option available on the left side of the menu

• Click on Create Job
• Enter the Name as PROD-Package
• Check the option Copy from Existing -> Select Application – Extension – Package
• Click on Create

• You will see the below option. Uncheck automatically Perform build on SCM Commit check box. Rest all should not be changed. Click on save

• Click on Jobs Overview and Click on Create Job again
• Enter the Name as PROD-Deploy. Select the checkbox Copy from Existing and Select Application-Extension-Deploy
• Click on Create.

• The Job will be created.
• In the steps section, please change the target instance and give the corresponding username and password of the User:

• Click on Save.
• Click on Job Overview -> Pipelines tab
• Click on Create Pipeline
• Give the name as PROD Pipeline Migration
• Uncheck Auto start when pipeline jobs are built externally

• The pipeline will be created.
• Drag and Drop the Package and Deploy into the pipe line and connect the dots by arrow as show in the below image.

• Click on save.
• Click on Build button to deploy the changes to the destination instance

• Click on Build. The changes will be deployed on the Destination instance.

Key Considerations

When migrating customizations, it’s essential to consider factors such as compatibility between environments, the impact on existing data, and ensuring that all dependencies are correctly mapped and transferred. A successful migration is not just about moving data from point A to B; it’s about ensuring that the customizations function as intended in their new environment.

Conclusion

Migrating customizations in Oracle Fusion Redwood requires a careful approach, but with the right guidance, it can be a smooth and efficient process. By following structured steps and keeping in mind the key considerations mentioned, you can ensure that your customizations enhance your Oracle Fusion experience, irrespective of the environment.

We hope this guide provides you with valuable insights and assists you in successfully migrating your Oracle Fusion Redwood customizations. For more detailed steps, refer to the subsequent sections of this blog.