Skip to main content

Discovery feature in Oracle EBS Cloud Manager to register Oracle E-Business Suite environments on OCI

Discovery feature in Oracle EBS Cloud Manager to register Oracle E-Business Suite environments on OCI

In this post I am sharing how we can use a discovery feature of Oracle EBS cloud Manager and check if we make a EBS environment compliant when manually migrating it to OCI.



Source environments can be environments that result from one of the following operations.

  • A manual migration from on-premises to OCI
  • A platform migration from on-premises to OCI
  • An environment initially deployed by Cloud Manager, where either EBS or Oracle Database were upgraded
  • An environment initially deployed by Cloud Manager, where any of the following configuration changes were later made:Addition of a load balancer
  • Addition or deletion of a node
  • Resizing of block volume
Pre-Req: EBS Cloud Manager is already setup




High Level Discovery Process

    1. Meet All Prerequisites
    2. Prepare For Discovery
      1. Enable SSH Connectivity -SSH connectivity must be enabled from the Oracle E-Business Suite Cloud Manager instance to all application tier and database tier nodes. To enable this connectivity, log in to the Oracle E-Business Suite Cloud Manager VM as the oracle user and copy the contents of ~/.ssh/id_rsa.pub into ~/.ssh/authorized_keys for the opc user on all nodes that are part of the environment to be discovered.
      2. Create Network Profile-As an Oracle E-Business Suite Cloud Manager administrator, use Oracle E-Business Suite Cloud Manager to create a network profile describing the network on which the candidate Oracle E-Business Suite instance is deployed.
      3. Create Stage Directory - Create a directory on the database server to use as the database node stage directory. like /u01/app/oracle/discovery
    1. Submit Discovery Request
    2. Review Discovery Compliance Report
    3. Either Confirm Compliance, or Correct Issues and Resubmit Discovery Request
    4. Register Environment

A compliance report would look like below. If the compliance is not passed we will not be able to register the environment in Cloud Manager like below.
I have done custom setup for migration to EBS cloud manager so my compliance got failed. I would need to do other way to use EBS cloud manager. I will share that in other post.

Certain Values are hidden in screenshot which cannot be displayed here.






Reference: Document 2656874.1, Standards Used by the Oracle E-Business Suite Cloud Manager for Provisioning Oracle E-Business Suite on Oracle Cloud Infrastructure




If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more