Perform the following steps to provision EBS AppsTier VDB.

  1. Log in to DCT.

  2. Go to Data > Data Management > VDBs.

  3. Click the Actions button in the top-right corner and select Provision VDB from the drop down menu.

  4. Select the AppsTier dSource.

  5. Select a dSource snapshot.
    All snapshots will have staged configuration prepared by adpreclone.pl and any hook operations placed on the dSource.

  1. Click Provision. The Provision VDB wizard will open

  2. Select an Environment. This environment will host the virtual AppsTier and be used to execute hook operations specified in a few steps. This environment will also run the WebLogic Admin server (Web Administration service) for the virtual AppsTier.
    If you are provisioning a multi-node AppsTier, you will be able to specify additional environments to host the virtual AppsTier in a few steps.

  3. Select E-Business Suite R12.2 AppsTier from the Installation dropdown.

  4. Select an Environment User. This user should be the applmgr user-outlined in Requirements for Oracle EBS target databases for provisioning.

  5. Enter a Mount Path for the virtual AppsTier VDB.If you are provisioning a multi-node AppsTier, this mount path will be used across all target environments.

  6. Enter the EBS-specific parameters for the virtual AppsTier. A subset of these parameters are discussed in more detail below:

Privileged OS Account (Optional) field should contain a high privileged user when a low privileged user is being used for provisioning.

  1. The Target APPS Password is the new apps password that is required to configure and manage the virtual AppsTier.
    This password is encrypted when stored within the Delphix Continuous Data Engine and is available as an environment variable to the adcfgclone, adstrtal, and adstpall processes.

  2. The Weblogic AdminServer Password is the new WebLogic password required to configure the virtual AppsTier. A password change will be performed if this password does not match that of the source EBS instance. This password is encrypted when stored within the Delphix Continuous Data Engine and is available as an environment variable to the adcfgclone, adstrtal, and adstpall processes.

  3. Enter the SYSTEM Password is required to configure the virtual AppsTier with the new apps password. This password is not required if the Target Apps Password is the same as the source

  4. Enter the Target Application hostname.

  5. Enter the Target DB/PDB SID which is the new database SID (PDB SID in case of 19c) that is required to configure and manage the virtual AppsTie

  6. Enter the Target DB server node hostname

  7. Enter the Target DB Domain Name, this will be provided to the adcfgclone.

  8. The provisioning workflow derives Instance Home Directory automatically from Mount Path.

For multi-node AppsTier, ensure the Mount Path is shared/accessible across all target nodes.

  1. Ensure that the Target Application Hostname and Target DB Server Node values are the short hostnames, not the fully-qualified hostnames.

  2. Select Services, by default all the Root, Web Entry Point, Web Application, and Batch Processing would be checked. In case you are using a multi-node environment and want to start a few services on a secondary node then this field is going to be very useful for you.

  3. Enter the DISPLAY variable value, the default value is hostname:0.0
    For example - ukapps99.delphix.com:0.0

  4. (Optional)Enter the Custom Database Port Number on which the database listener must run.

Enter the numeric port value in this field only if you want to use DB port customisation, and this value should match with the custom database port number given during the DBTechstack provisioning. Leaving this field blank automatically uses the default port based on the port pool. The custom database port number is applicable only for Oracle 19c database.

  1. Provide Target Run Edition Port Pool, the value of this field should be 0 to 99. This should match with the port pool value given during the DBTechstack provisioning if the Custom Database Port Number input field is left blank.
    Enter the Target Patch Edition Port Pool, the value of this field should be between 0 to 99.
    Target Run Edition Port Pool and Target Patch Edition Port Pool ranges shouldn't intersect with each other.
    For example: if Run Edition Port Pool is 9 then the patch FS port pool value can be anything between 0 to 99 except 9.

If the database listener is running on a Custom Database Port Number then Target Apps server’s RUN Edition Port Pool and PATCH Edition Port Pool value cannot have the same port pool value of source Application server.

 

  1. Enter the EBS AppsTier Timeout value which is required to terminate all the long-running AppsTier processes which have exceeded the timeout value when stopping the applications as part of a refresh. This timeout will be calculated in minutes. For example, if set to 30, then we run adstpall at the start of the refresh, and if after 30 minutes the application has not stopped, then the processes will be terminated to allow the refresh to continue.

  2. Enter the EBS AppsTier Provision/Refresh Timeoutvalue which is required to terminate configure and cloning via adcfgclone process which have exceeded the timeout as part of a provision/refresh. This timeout will be calculated in hours and the default value will be 8 hours. For example, if set to 9, then the connector will detect a timeout after 9 hours instead of getting in a hung state and UI error for the same will be prompted.

  3. Select the Java Color Scheme value is an optional parameter and is used to change the JAVA color for provisioned Oracle EBS JAVA based form interface. Choose any of the following colors (Swan, Blue, Khaki, Olive, Purple, Red, Teal, Titanium) to set Java Color Scheme for EBS AppsTier java-based forms interface.

  4. (Optional)Enter the Target System Proxy Hostname value. The parameter used if adcfgclone requires it.

  5. (Optional) Enter the Target System Proxy Port value. The parameter used if adcfgclone requires it.

  6. Enable the Cleanup Before Provision option if you want to permit the Delphix Continuous Data Engine to automatically clean up stale EBS configuration during a refresh. This option is recommended, but only available if your Oracle Home is patched with Oracle Universal Installer (OUI) version 10.2 or above.

    • With this option enabled: the Delphix Continuous Data Engine will inspect the target environment's oraInventory prior to refreshing this virtual AppsTier. If any Oracle Homes are already registered within the specified Mount Path, the Delphix Continuous Data Engine will detach them from the inventory prior to running adcfgclone. These homes must be detached/unregistered prior to running post-clone configuration. If they are not detached/unregistered, adcfgclone will fail, citing conflicting oraInventory entries as an issue. The Delphix Continuous Data Engine will also remove any conflicting INST_TOP directories left in the environment. Non-conflicting INST_TOP directories will not be modified.

    • With this option disabled, Oracle Homes or INST_TOP directories that conflict with the specified Mount Path or desired INST_TOP location will be reported in errors instead of automatically cleaned up. For refresh to succeed, you must manually detach/register conflicting Oracle Homes and manually remove conflicting INST_TOP directories prior to refresh.

31. Enable the Start Services After Provision option if you want to permit the Delphix Continuous Data Engine to automatically start the services for EBS AppsTier after provisioning.

  • With this option enabled: the Delphix Continuous Data Engine will start all the services of EBS AppsTier after provisioning.

  • With this option disabled: the Delphix Continuous Data Engine will NOT start the services of EBS AppsTier after provisioning. This will allow customers to prevent EBS services from being started at the conclusion of provisioning or refreshing. That way, customers can perform post-clone processing automation using a configure-clone hook without having to stop services first.

32. If you are provisioning a multi-node AppsTier, enter additional AppsTier nodes mentioned below:

  • Select the Environment for the secondary node.

  • Enter the Environment User for each node should be the applmgr user-outlined in Requirements for Oracle EBS target databases for provisioning

  • Ensure that the Hostname value for each node is the short hostname, not the fully-qualified hostname.

  • Enter the DISPLAY variable value, the default value is hostname:0.0.

  1. The Mount Path is not configurable for each node individually. The Mount Path provided for the primary environment will be used for each additional node.

  2. Click Next.

  3. Enter a VDB Name.

  4. Select a Target Group for the VDB.
    If necessary, click the Plus icon to add a new group.

  5. (Optional)When provisioning a new VDB in the VDB Provisioning wizard, check the Auto VDB Restart box. Reference - Automatic VDB restart on target server after reboot.

  6. Select a Snapshot Policy for the VDB.If necessary, click the Plus icon to create a new policy.

    When Snapshot is running against the DBTechstack, database, or AppsTier, the Delphix Continuous Data Engine also executes pre-clone logic to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
    To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

  7. Click Next.

  8. Enter any custom hook operations that are needed to help correctly manage the virtual AppsTier.
    The Configure Clone hook will be run after the adcfgclone.pl tool has both mounted and configured the AppsTier.
    All hook operations run against the environment specified for provision. For a multi-node AppsTier, hook operations never run against additional nodes specified

  9. Click Next.

  10. Click Submit.

dbTier must be accessible during AppsTier provisioning for the following actions:

  • Faster failure visibility for invalid DB connectivity during AppsTier provision/refresh workflow.

  • Improved consistency of Java color scheme in EBS AppsTier.

  • Improved database services cleanup and hook behavior in EBS oracle database flows.

Post-clone configuration will fail if the AppsTier cannot connect to the database. Ensure the target dbTier is accessible to the AppsTier during the provisioning process. Ensure both the virtual database and database listener are running.
If your source setup is EBS ISG enabled, then during virtual AppsTier creation on the target server, perform post cloning steps as described in Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID 1311068.1).

43. When provisioning starts, you can review the progress of the job in the Datasets panel, or in the Job History panel of the Dashboard. When provisioning is complete, the AppsTier VDB will be included in the group you designated and listed in the Datasets panel. If you select the AppsTier VDB in the Datasets panel and click the Configuration tab, you can view information about the virtual files and its Data Management settings.

44. Once all three EBS virtual datasets have been provisioned successfully, your virtual EBS instance should be running and accessible.

AppsTier topology Is configurable. The AppsTier topology of the virtual EBS instance does NOT need to match the AppsTier topology of the source EBS instance. The Delphix Continuous Data Engine will automate scale up or scale down logic as required during provisioning.

 

 

Last updated
Oct 9, 2026