Skip to main content

How to Change Admin Server Name in a WebLogic Server (WLS) Domain

How to Change Admin Server Name in a WebLogic Server (WLS) Domain

Renaming the Admin Server in a WebLogic Server (WLS) domain involves using a WLST (WebLogic Scripting Tool) script in offline mode. Below is a detailed guide for performing this task.

Pre-requisites:

  • Domain Shutdown: Before starting the renaming process, ensure the entire WebLogic domain is completely shut down to avoid any conflicts or inconsistencies.
  • Backup: Take a full backup of the WebLogic domain directory to safeguard against any unintended changes.

Steps to Rename Admin Server

Step 1: Rename the Admin Server Using a WLST Script

  • Open a terminal or shell on the WebLogic server.
  • Start the WLST utility in offline mode. You can start it using the following command:

$WL_HOME/common/bin/wlst.sh

Replace $WL_HOME with the actual WebLogic installation directory.

Use the following sample WLST script to rename the Admin Server:


readDomain('path/to/domainDir')  # Replace with your domain directory
cd('/Servers')                   # Navigate to the Servers section
cd('AdminServer')                # Go to the AdminServer configuration
cmo.setName('NewAdminServerName')  # Set the new name
updateDomain()                   # Save changes to the domain
exit()                           # Exit WLST
  • readDomain('path/to/domainDir'): Reads the domain configuration from the specified domain directory.
  • cmo.setName('NewAdminServerName'): Updates the Admin Server name to the new one. Replace 'NewAdminServerName' with your desired name.
  • updateDomain(): Saves the updated configuration.

Step 2: Update Domain Files and Folders

After successfully renaming the Admin Server, update the domain files and folder structure as follows:

Adjust Domain Scripts:

  • Open the $DOMAIN_HOME/bin directory.
  • Update all scripts (e.g., startWebLogic.sh, setDomainEnv.sh, and other custom scripts) that reference the old Admin Server name (AdminServer) to use the new name (NewAdminServerName).

Update Security Folder:

Move or rename the security folder associated with the Admin Server:

mv $DOMAIN_HOME/servers/AdminServer/security 
$DOMAIN_HOME/servers/NewAdminServerName/security
This allows the renamed server to reuse the boot.properties file without needing to re-enter credentials.

Update Server Directory Structure:

Rename the Admin Server’s directory in the $DOMAIN_HOME/servers path:

mv $DOMAIN_HOME/servers/AdminServer 
$DOMAIN_HOME/servers/NewAdminServerName

Optional Cleanup: Remove temporary subdirectories (tmp and cache) 
in the renamed server directory:
rm -rf $DOMAIN_HOME/servers/NewAdminServerName/tmp
rm -rf $DOMAIN_HOME/servers/NewAdminServerName/cache

Post-Renaming Checks

  1. Start the WebLogic domain and ensure that the renamed Admin Server starts successfully:

    $DOMAIN_HOME/bin/startWebLogic.sh
  2. Log in to the WebLogic Administration Console to verify that the Admin Server is functioning correctly with its new name.
  3. Test connectivity to the Admin Server and ensure all managed servers in the domain recognize the renamed Admin Server.



Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share 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

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

How to make flash work on IE or Edge with IE Compatibility

How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...
Post a Comment
Read more