In case you are working in a migration surroundings the place you usually must rename the area identify, this information will aid you.
Altering the WebLogic area identify is feasible by modifying sure information underneath your area.
I examined this in a growth surroundings and it labored properly for me.
On this train, I modified the identify from base_domain to new_domain
- Make a full backup of your area
- Copy the outdated area identify folder to the brand new area identify
cp –rp base_domain new_domain
- Search all information containing base_domain within the newly copied folder
chandan$ grep -r * base_domain --exclude-dir={tmp,logs,information,domain_bak}
base_domain/bin/setDomainEnv.sh:DOMAIN_HOME="/Customers/chandan/weblogic/base_domain"
base_domain/bin/setDomainEnv.sh:LONG_DOMAIN_HOME="/Customers/chandan/weblogic/base_domain"
base_domain/bin/startManagedWebLogic.sh:DOMAIN_NAME="base_domain"
base_domain/bin/startManagedWebLogic.sh:DOMAIN_HOME="/Customers/chandan/weblogic/base_domain"
base_domain/bin/startWebLogic.sh:DOMAIN_HOME="/Customers/chandan/weblogic/base_domain"
base_domain/bin/stopManagedWebLogic.sh:DOMAIN_HOME="/Customers/chandan/weblogic/base_domain"
base_domain/bin/stopWebLogic.sh:DOMAIN_HOME="/Customers/chandan/weblogic/base_domain"
base_domain/config/config.xml: <identify>base_domain</identify>
base_domain/config/config.xml: <identify>base_domain</identify>
base_domain/config/config.xml: <identify>base_domain</identify>
base_domain/init-info/startscript.xml:<worth>/Customers/chandan/weblogic/base_domain</worth>
base_domain/init-info/startscript.xml:<worth>/Customers/chandan/weblogic/base_domain</worth>
base_domain/init-info/startscript.xml: <worth>/Customers/chandan/weblogic/base_domain</worth>
base_domain/init-info/startscript.xml:<worth>base_domain</worth>
base_domain/init-info/startscript.xml:<worth>/Customers/chandan/weblogic/base_domain</worth>
base_domain/init-info/startscript.xml:<worth>/Customers/chandan/weblogic/base_domain</worth>
base_domain/init-info/startscript.xml:<worth>/Customers/chandan/weblogic/base_domain</worth>
base_domain/init-info/startscript.xml:<worth>/Customers/chandan/weblogic/base_domain</worth>
base_domain/init-info/tokenValue.properties:@DOMAIN_HOME=/Customers/chandan/weblogic/base_domain
base_domain/init-info/tokenValue.properties:@DOMAIN_NAME=base_domain
base_domain/init-info/tokenValue.properties:@USERDOMAIN_HOME=/Customers/chandan/weblogic/base_domain
base_domain/startWebLogic.sh:DOMAIN_HOME="/Customers/chandan/weblogic/base_domain"
chandans-imac:weblogic chandan$
- Change base_domain to new_domain in all information above. You should utilize sed to make modifications, or you are able to do it manually one after the other. The selection is yours.
grep -r base_domain * --exclude-dir={tmp,logs,information,domain_bak} | xargs sed –I ‘s/base_domain/new_domain/g’
- Make sure that not one of the information have base_domain
bash-3.2$ grep -r base_domain * --exclude-dir={tmp,logs,information,domain_bak}
- Go to the AdminServer folder and delete it cache, information, tmp folder
bash-3.2$ pwd /Customers/chandan/weblogic/new_domain/servers/AdminServer bash-3.2$ rm -rf cache/ information/ tmp/
- Go to your new area and begin Weblogic
chandans-imac:bin chandan$ pwd /Customers/chandan/weblogic/new_domain/bin chandans-imac:bin chandan$ bash-3.2$ ./startWebLogic.sh <Jan 8, 2013 11:32:53 PM SGT> <Discover> <WebLogicServer> <BEA-000329> <Began WebLogic Admin Server "AdminServer" for area "new_domain" working in Manufacturing Mode> <Jan 8, 2013 11:32:53 PM SGT> <Discover> <WebLogicServer> <BEA-000365> <Server state modified to RUNNING> <Jan 8, 2013 11:32:53 PM SGT> <Discover> <WebLogicServer> <BEA-000360> <Server began in RUNNING mode>
That is all! I additionally began WebLogic’s managed server with no issues.
Learn extra about Oracle Weblogic administration right here.