Migrate to Your Target Environment Manually

After you have completed the migration preparation steps, you can migrate to your target environment by manually importing or re-creating all the configurations of your source. This will ensure successful deployment of the target instance.

To migrate to your target environment:

1. Create the required WLS artifacts.

   WLS artifacts can be: Java Message Service (JMS) queue, Java EE Connector Architecture (JCA) adapter configurations, data source, work managers, J2EE app deployment, JMS servers, JMS topics, and so on.

2. Implement any security configurations.

   Security configurations can be: custom Oracle Web Service Manager (OWSM) policies, Credential Store Framework (CSF) keys, certificates, users, groups, custom Oracle Platform Security Service (OPSS) roles, custom OPSS permissions, group memberships, role memberships, enterprise roles, OPSS credentials, and so on.

   For more information about:

   • OPSS commands to migrate keystores, see Managing Keystores with WLST in Securing Applications with Oracle Platform Security Services.
   • OPSS commands to migrate credentials, see Managing Credentials with WLST in Securing Applications with Oracle Platform Security Services.
   • OWSM commands to migrate custom policies, see Migrating Policies in Administering Web Services.

   Note:

   The source Oracle SOA Cloud Service internal LDAP data can be migrated into the target Oracle SOA Suite on Marketplace or Oracle SOA Cloud Service instance.
3. Test that your security configurations work.

   1. Create a simple application comprising of SOA composite, Oracle Service Bus proxy service, B2B agreement, ESS job.

   2. Ensure that the application uses at least one of the keys/certificates/credentials.

   3. Test to check if the application works.

   4. Check if you can view an imported user in LDAP.

4. Import shared artifacts in MetaData Services (MDS) schemas for SOA.
5. Deploy projects from the console for SOA/Oracle Service Bus.

   Use the prepared customization file/configuration plan. Ensure loopback abstract WSDL/Schema references and loopback HTTP invokes point to the target environment load balancer and not the DNS name.

   For inbound adapters, if the address for both deployments is the same, ensure that it doesn’t start processing production messages by externally blocking it from accessing inbound endpoints. Then, if possible, you can deactivate the SOA adapter.

6. Import artifacts for B2B.

   The inbound channels are disabled by default. If required, add URLs in the console for the cloud and deploy all artifacts.

7. Import /oracle/apps/ess/custom namespace and /oracle/as/ess/essapp/custom namespace for Oracle Enterprise Scheduler.
8. Enter the token values noted earlier for Oracle Enterprise Scheduler.
9. Rebind work assignments to the cluster or managed server for Oracle Enterprise Scheduler.

   See Managing Work Assignments and Workshifts in Administering Oracle Enterprise Scheduler.

10. Add file system artifacts captured from the source environment, such as custom XPath functions, SOA token mapping file, B2B java callouts.
11. Test the endpoints.

    Use the endpoints in the application (SOA composite, OSB proxy service, B2B agreement, ESS job) created for testing and check if it works. After testing, change it back to the original endpoints.

12. Add scripts scheduled with Oracle Enterprise Scheduler.
13. Set your tuning settings if they are available.
14. If the FTP adapter is used, move the contents of the privateKeyFile source location to the same location on the target.
15. If the MQ adapter is used, move the contents of the KeyStoreLocation and TrustStoreLocation source locations to the same locations on the target.
16. Redo all the SOA Composer customizations manually.
17. Redo any Enterprise Manager configuration steps manually.

    For details, see Reconfigure Tuning and Configuration Parameters.

18. If the target instance is going to access endpoints on-premises then you may need VPN.

    You can set up VPN through VPNaaS.

19. Apply UMS configuration manually to the target environment.
20. Deploy other supported third-party resource adapters (for example, OracleApps Adapter, SAP Adapter) that are being used in the Oracle WebLogic Server Administration Console to both the Administration Server and the Managed Servers.