1. Migrating Oracle Java Cloud Service on OCI-C to Oracle WebLogic Server for OCI Using tar
  2. Prepare to Migrate
  3. Configure Security Rules for the Network
  4. Recommended Simplified Network Configurations
  5. Oracle Java Cloud Service with OTD

Oracle Java Cloud Service with OTD

There is no Oracle Traffic Director (OTD) option in Oracle WebLogic Server for OCI. Instead, the OCI load balancer must be used to route traffic to the WebLogic managed servers.

The following diagram illustrates an Oracle Java Cloud Service instance using OTD and the Oracle WebLogic Server for OCI instance recommended to replace it. This illustration represents the state of both instances during the migration process, prior to deleting the Oracle Java Cloud Service instance.

Figure 2-1 Oracle Java Cloud Service with OTD


Oracle Java Cloud Service with OTD

The private subnet for the OCI database and the public subnet for JCS must already exist. Additionally, you should create the following subnets:
  • Oracle WebLogic Server for OCI private subnet
  • OCI load balancer public subnet
  • Bastion host public subnet
Use the following tables to configure the security lists for the these three subnets:

Table 2-1 Oracle WebLogic Server for OCI Private Subnet

Rule Type Source CIDR and Protocol Default Destination Port Description

Stateful Ingress

Bastion public subnet, TCP

22

SSH access

Stateful Ingress

Bastion public subnet, TCP

7002

Administration server SSL port

Stateful Ingress

OCI load balancer public subnet, TCP

8001

Managed server port

Stateful Ingress

Oracle Java Cloud Service public subnet, TCP

22

SSH access, so domain and binaries can be copied over

Stateful Ingress

Oracle WebLogic Server for OCI private subnet (self), TCP

22

SSH access between the compute instances of Oracle WebLogic Server for OCI

Stateful Ingress

Oracle WebLogic Server for OCI private subnet (self), TCP

9071

Used for provisioning and scaling

Stateful Ingress

Oracle WebLogic Server for OCI private subnet (self), TCP

9073

Used for WebLogic health check

Stateful Ingress

Oracle WebLogic Server for OCI private subnet (self), TCP

5556

Used for accessing node manager

Table 2-2 OCI Load Balancer Public Subnet

Rule Type Source CIDR and Protocol Default Destination Port Description

Stateful Ingress

Internet (0.0.0.0/0), TCP

443

SSL access

Table 2-3 Bastion Public Subnet

Rule Type Source CIDR and Protocol Default Destination Port Description

Stateful Ingress

Hosts with access to bastion, TCP

22

SSH access, port forwarding
Use the following table to add access for the Oracle WebLogic Server for OCI private subnet to the OCI database public subnet:

Table 2-4 Access to OCI Database Public Subnet

Rule Type Source CIDR and Protocol Default Destination Port Description

Stateful Ingress

WLS for OCI private subnet, TCP

1521

DB access