Managing the Weblogic password

Changing the Weblogic password

For existing EBS 12.2 customers who intend to use this WebLogic password change feature need to follow the below steps for their EBS application:

1. Disable all the virtual datasets created on Delphix Engine in the following order:

   1. appsTier vFiles

   2. VDB utilized by your EBS instance

   3. dbTechStack vFiles

2. Disable all the EBS dSource created on Delphix Engine once you have disabled all three EBS virtual datasets in the above step.

3. Upgrade Delphix Engine to 5.3.2.0 release and upload EBS 1.4.0 plugin release.

   Go to Manage>Plugins

   • Upload a plugin file to upgrade the existing plugin by clicking plus (+) symbol.

4. Refresh all host environments added on the Delphix Engine.

   Go to Manage> Environments

   • From the symbol (...) located in the upper left-hand corner, select Refresh All.

5. Change the Weblogic admin password on EBS appsTier vFile.

   • Select the appsTier vFiles hosting your virtual EBS database.

   • Go to Configurations >Custom

   • Update the Target Weblogic AdminServer Password field with the password you would like to set for EBS appsTier.

6. Enable all the EBS dSource created on Delphix Engine.

7. Enable all the virtual datasets created on Delphix Engine in the following order:

   1. appsTier vFiles

   2. VDB utilized by your EBS instance

   3. dbTechStack vFiles

8. Verify the changed WebLogic password by logging into the WebLogic console.

EBS 12.2 customers configuring appsTier on a multi-node environment will need to manually enable passwordless SSH on all target nodes only when they want to change the Weblogic password and then proceed with EBS appsTier provision. The passwordless SSH should be enabled between all nodes and for both low privileged and high privileged user.

Enabling passwordless SSH between target application nodes

To enable passwordless SSH between target application nodes complete the following

The following is an example of a two-node EBS appsTier.

Node 1: test1-ap1

Node 2: test1-ap2

1. Create Authentication SSH-Kegen Keys on Node 1.

   

2. Create .ssh Directory on Node 2.

   

3. Upload Generated Public Keys to Node 2.

   

4. Set Permissions on Node 2 and Login to verify without password.