Plan Your Migration Target Environment

You will need to make some planning decisions before you can configure and run a SaaS extension application on Oracle Cloud Infrastructure. It will be helpful to review the planning steps, sizing recommendations, and plan for required patching.

Review Planning Steps

The following steps describe at a high level the decisions that will be required for using Oracle WebLogic Server for OCI to configure and run a SaaS extension application.

As you work through these steps, make a spreadsheet or document to record all of the environment details in one place for your convenient reference later.

1. Identify your current environment details for each instance (production, test, developer, etc.):
   1. Your Fusion SaaS instance names.
   2. Your Traditional My Service Identity Domains.
   3. Your Oracle Java Cloud Service - SaaS Extension and Oracle Database Cloud Schema Service instances, including size. For example:

      java-prod (s4), db-prod (s50)

      java-test (s2), db-test (s20)

      java-dev1 (s1), db-dev1 (s5)

2. Identify your existing Oracle Cloud account with Oracle Identity Cloud Service instances.
   • Oracle provisioned a new Oracle Cloud Accounts to all Fusion SaaS customers, with one Oracle Identity Cloud Service instance for each Fusion SaaS instance.
   • Owners of those Fusion SaaS environments were notified via email about these new instances as well as credentials to access them
   • Each Oracle Identity Cloud Service instance provisioned with a Fusion SaaS instance is federated as a service provider to the Fusion SaaS instance as the identity provider

   Make a record with each of your account and instance names:

   • Cloud account, such as MyAccount.
   • Oracle Identity Cloud Service domain, such as ID_Domain
   • Production Oracle Identity Cloud Service instance. For example, MyAccount(ID_Domain), idcs-1a2b3c4d5e6f7a8b9c0d1e2f3a4baaaa
   • Test Oracle Identity Cloud Service instance. For example, MyAccount(ID_Domain-test), idcs-1a2b3c4d5e6f7a8b9c0d1e2f3a4bbbbb
   • Developer Oracle Identity Cloud Service instance. For example, MyAccount(ID_Domain-dev1), idcs-1a2b3c4d5e6f7a8b9c0d1e2f3a4bcccc
3. Determine the best Oracle Cloud Infrastructure Region. The following recommendations are based on minimizing network latency with your Fusion SaaS instances:
   • Chicago DC (us2): use US West (Phoenix)
   • Amsterdam (em2): use Germany Central (Frankfurt)
   • Linlithgow (em1): use UK South (London)
4. Create, or identify an existing, Oracle Cloud Infrastructure tenancy. This tenancy is used to create and manage Oracle Cloud Infrastructure services, including provisioning Oracle WebLogic Server for OCI.
5. Identify the version to use for Oracle WebLogic Server for OCI. You must use:
   • Type: Stack
   • Publisher: Oracle
   • Category: Application Development
   • Price: Paid
   • Name: Oracle WebLogic Server Enterprise Edition UCM
   • Version: 12.2.1.4.x
6. Identify sizing requirements for new Oracle WebLogic Server for OCI instances.
   Each Oracle WebLogic Server for OCI host needs the following Oracle Cloud Infrastructure services:

   • Compute: shape and number
   • Block Volume: size
   • Load Balancing: instance type

   Sizing information is provided in Review Sizing Requirements, later in this solution playbook.
7. Decide which Oracle Database to use. Your choice must support both Java Required Files (JRF) and non-JRF schemas. These databases are compatible:
   • Oracle Autonomous Transaction Processing
   • Oracle bare metal or virtual machine DB Systems supported by Oracle Cloud Infrastructure. Check the Oracle Cloud Infrastructure documentation for details.
8. Identify the number of database instances to use. Oracle recommends that your production environment have its own database cloud service instance. For non-production environments (for example test and developer environments), options include:
   • Schema isolation using a single database instance
   • A separate service instance per environment
9. Identify storage requirements for application data. Your requirements depend on your functional use case as well as your decision whether to use schema isolation or service instance isolation.
   Oracle Database Cloud Schema Service sizes used with Oracle Java Cloud Service - SaaS Extension were as follows:

   • S5: 5 GB
   • S20: 20 GB
   • S50: 50 GB
10. Identify network requirements for each environment.
    • The structure of Virtual Cloud Networks (VCNs) includes separating Oracle WebLogic Server for OCI and database service instances in different VCNs, requiring local VCN peering configuration.
    • Your Subnet design should account for load balancers, Oracle WebLogic Server for OCI, and database services.
    • Your Internet Gateway should enable VCN with direct connectivity to the Internet.
    • Using a private subnet requires having a public subnet for a bastion node for access, and the load balancer must be in a public subnet for Oracle Identity Cloud Service configuration.

Review Sizing Recommendations

The following sizing recommendations are based on the assumption that you are using appropriate sizing for your existing Oracle Java Cloud Service - SaaS Extension deployment. You may need to adjust your sizing based on your actual needs and usage.

Note that the first compute instance has both the WebLogic administrative and managed servers.

Oracle Java Cloud Service - SaaS Extension Shape	Recommendation for Oracle WebLogic Server for OCI
S1 Managed servers: 1 Java EE Server Memory: 1.5GB/Instance Storage: 5GB Data Transfer: 50GB/Month	Compute shape: 1 OCPU / 8 GB memory (for example, VM.Standard.E2.1) Compute instances: 1 Block Volume: 100GB Load Balancing: 400 Mbps
S2 Managed servers: 2 Java EE Server Memory: 3GB/Instance Storage: 10GB Data Transfer: 250GB/Month	Compute shape: 1 OCPU / 8 GB memory (for example, VM.Standard.E2.1) Compute instances: 2 Block Volume: 100GB for each instance Load Balancing: 400 Mbps
S4 Managed servers: 4 Java EE Server Memory: 6GB/Instance Storage: 25GB Data Transfer: 500GB/Month	Compute shape: 1 OCPU / 8 GB memory (for example, VM.Standard.E2.1) Compute instances: 3 Block Volume: 100GB for each instance Load Balancing: 400 Mbps

Plan Required Patching

You will need to perform required patching for Oracle WebLogic Server for OCI and Oracle Autonomous Linux. It's a good idea to plan ahead for when you can schedule patching.

Each Oracle WebLogic Server for OCI release includes patches from several products, namely, Oracle WebLogic Server, Oracle JDeveloper, Oracle Java Development Kit, Oracle Platform Security Services and Oracle Web Services Manager.

Patches in a new release of Oracle WebLogic Server for OCI are not automatically applied to existing domains that you created with Oracle WebLogic Server for OCI. You have to apply the patches manually if you wish to update your existing domain to match the latest release, or to match a specific supported release.

A Patch Set Update (PSU) is a group of related patches that is identified by a specific version number. When you create a domain with Oracle WebLogic Server for OCI, you choose a version of WebLogic Server in this format: <major_version>.<patch_level>.<build>. For example, 12.2.1.4.191121.01. Use your My Oracle Support account to locate and download the patch you wish to apply

The Oracle Cloud Infrastructure OS Management service allows you to manage updates and patches for the operating system environment on your Oracle Cloud Infrastructure instances. Update Oracle Linux VM by using OS Management for management and automation.