Wednesday, April 24, 2013

weblogic change admin port number

change these files:

$DOMAIN_HOME/bin/stopWebLogic.sh
$DOMAIN_HOME/bin/stopManagedWebLogic.sh
$DOMAIN_HOME/bin/startManagedWebLogic.sh
$DOMAIN_HOME/config/backup_config1.xml
$DOMAIN_HOME/config/backup_config.xml
$DOMAIN_HOME/config/fmwconfig/servers/osbpl1as/applications/em/META-INF/emoms.properties.jmxori
$DOMAIN_HOME/config/fmwconfig/servers/osbpl1as/applications/em/META-INF/emoms.properties
$DOMAIN_HOME/config/config.xml
$DOMAIN_HOME/init-info/startscript.xml
$DOMAIN_HOME/init-info/tokenValue.properties
$DOMAIN_HOME/servers/domain_bak/config_prev/config.xml
$DOMAIN_HOME/servers/osbpl1ms1/data/nodemanager/startup.properties
$DOMAIN_HOME/servers/osbpl1ms2/data/nodemanager/startup.properties
$DOMAIN_HOME/servers/osbpl1as/data/nodemanager/osbpl1as.url
$DOMAIN_HOME/servers/osbpl1as/data/ldap/conf/replicas.prop
$DOMAIN_HOME/sysman/state/targets.xml


and also:

rm -rf $DOMAIN_HOME/servers/osbpl1as/tmp/
rm $DOMAIN_HOME/servers/osbpl1as/data/store/default/_WLS_OSBPL1AS000000.DAT
MAYBE it works by simply change a couple of shell scripts and "Listen Port:" in the console. Surely updating the "Listen Port" with the console doesn't update the start and stop scripts.

My idea is that, to be on the safe side, one had better recreate the domain.

Surely, changing managed server port is easier.



No comments: