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 IDCS

Oracle Java Cloud Service with IDCS

Note:

It is not possible to use the same IDCS application that is used in Oracle Java Cloud Service for Oracle WebLogic Server for OCI, because Oracle WebLogic Server for OCI uses an IDCS app gateway. In the same way, you cannot use the same load balancer that is used in Oracle Java Cloud Service for Oracle WebLogic Server for OCI because the load balancer in Oracle Java Cloud Service is managed by Oracle while the resources in Oracle WebLogic Server for OCI are managed by the user.
The following diagram illustrates a Oracle Java Cloud Service instance using IDCS 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-2 Oracle Java Cloud Service with IDCS


Oracle Java Cloud Service with IDCS

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

Table 2-5 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

9999

IDCS app gateway 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

IDCS app gateway for accessing the Managed Server

Stateful Ingress

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

5556

Used for accessing node manager

Table 2-6 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-7 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