Skip to main content

Reset WebLogic Administration Password in R12.2



TXK.C.Delta.7

Shut down all application tier services except the Admin Server
$ADMIN_SCRIPTS_HOME/adcmctl.sh stop apps/$APPS_PASS wait=y
$ADMIN_SCRIPTS_HOME/adstpall.sh apps/$APPS_PASS -skipNM -skipAdmin


Change the password and start the services:
perl $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl -action=updateAdminPassword
$ADMIN_SCRIPTS_HOME/adstrtal.sh



TXK.C.Delta.6 and earlier

Need to shutdown the server, I prefer shutting down the concurrent manager first and then then the rest.
$ADMIN_SCRIPTS_HOME/adcmctl.sh stop apps/$APPS_PASS wait=y
$ADMIN_SCRIPTS_HOME/adstpall.sh apps/$APPS_PASS


Backup the property files in case the change does not work and you want to revert back to the current settings. Notice you'll do this for each of the servers. You may have more than one oacore server or forms server so make sure to backup each.
mv $EBS_DOMAIN_HOME/security/DefaultAuthenticatorInit.ldift $EBS_DOMAIN_HOME/security/DefaultAuthenticatorInit.ldift.bkup

mv $EBS_DOMAIN_HOME/servers/AdminServer/data/ldap $EBS_DOMAIN_HOME/servers/AdminServer/data/ldap.bkup
mv $EBS_DOMAIN_HOME/servers/AdminServer/security/boot.properties $EBS_DOMAIN_HOME/servers/AdminServer/security/boot.properties.bkup
mv $EBS_DOMAIN_HOME/servers/AdminServer/data/nodemanager/startup.properties $EBS_DOMAIN_HOME/servers/AdminServer/data/nodemanager/startup.properties.bkup

mv $EBS_DOMAIN_HOME/servers/forms-c4ws_server1/data/ldap $EBS_DOMAIN_HOME/servers/forms-c4ws_server1/data/ldap.bkup
mv $EBS_DOMAIN_HOME/servers/forms-c4ws_server1/security/boot.properties $EBS_DOMAIN_HOME/servers/forms-c4ws_server1/security/boot.properties.bkup
mv $EBS_DOMAIN_HOME/servers/forms-c4ws_server1/data/nodemanager/startup.properties $EBS_DOMAIN_HOME/servers/forms-c4ws_server1/data/nodemanager/startup.properties.bkup

mv $EBS_DOMAIN_HOME/servers/forms_server1/data/ldap $EBS_DOMAIN_HOME/servers/forms_server1/data/ldap.bkup
mv $EBS_DOMAIN_HOME/servers/forms_server1/security/boot.properties $EBS_DOMAIN_HOME/servers/forms_server1/security/boot.properties.bkup
mv $EBS_DOMAIN_HOME/servers/forms_server1/data/nodemanager/startup.properties $EBS_DOMAIN_HOME/servers/forms_server1/data/nodemanager/startup.properties.bkup

mv $EBS_DOMAIN_HOME/servers/oafm_server1/data/ldap $EBS_DOMAIN_HOME/servers/oafm_server1/data/ldap.bkup
mv $EBS_DOMAIN_HOME/servers/oafm_server1/security/boot.properties $EBS_DOMAIN_HOME/servers/oafm_server1/security/boot.properties.bkup
mv $EBS_DOMAIN_HOME/servers/oafm_server1/data/nodemanager/startup.properties $EBS_DOMAIN_HOME/servers/oafm_server1/data/nodemanager/startup.properties.bkup

mv $EBS_DOMAIN_HOME/servers/oacore_server1/data/ldap $EBS_DOMAIN_HOME/servers/oacore_server1/data/ldap.bkup
mv $EBS_DOMAIN_HOME/servers/oacore_server1/security/boot.properties $EBS_DOMAIN_HOME/servers/oacore_server1/security/boot.properties.bkup
mv $EBS_DOMAIN_HOME/servers/oacore_server1/data/nodemanager/startup.properties $EBS_DOMAIN_HOME/servers/oacore_server1/data/nodemanager/startup.properties.bkup


Copy the following somewhere as you'll be exiting an initializing FMW Home without the environment variables.
echo $EBS_DOMAIN_HOME
/oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES
grep s_nm_jvm_startup_properties $CONTEXT_FILE
-XX:PermSize=128m -XX:MaxPermSize=384m -Xms1024m -Xmx1024m -Djava.security.policy=/oa01/oradata/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.policy -Djava.security.egd=file:/dev/./urandom -Dweblogic.ProductionModeEnabled=true -da -Dplatform.home=/oa01/oradata/fs1/FMW_Home/wlserver_10.3 -Dwls.home=/oa01/oradata/fs1/FMW_Home/wlserver_10.3/server -Dweblogic.home=/oa01/oradata/fs1/FMW_Home/wlserver_10.3/server -Dcommon.components.home=/oa01/oradata/fs1/FMW_Home/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES -Djrockit.optfile=/oa01/oradata/fs1/FMW_Home/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES/config/fmwconfig/servers/AdminServer -Doracle.domain.config.dir=/oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES/config/fmwconfig -Digf.arisidbeans.carmlloc=/oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES/config/fmwconfig/carml -Digf.arisidstack.home=/oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES/servers/AdminServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/oa01/oradata/fs1/FMW_Home/oracle_common/modules/oracle.ossoiap_11.1.1,/oa01/oradata/fs1/FMW_Home/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dportlet.oracle.home=/oa01/oradata/fs1/FMW_Home/oracle_common -Dem.oracle.home=/oa01/oradata/fs1/FMW_Home/oracle_common -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/oa01/oradata/fs1/FMW_Home/patch_wls1036/profiles/default/sysext_manifest_classpath


You now need to exit the session and re-enter without initializing the EBS variables: exit
su - applyes

## DON'T SOURCE ANYTHING!!!!!!!

From above echo saved echos change the directory to Domain home and source it:
cd /oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES/bin
source setDomainEnv.sh


Change the weblogic password using your weblogic admin username. DO NOT FORGET THE FULLSTOP AT THE END
cd /oa01/oradata/fs1/FMW_Home/user_projects/domains/EBS_domain_YES/security/
java weblogic.security.utils.AdminAccount weblogic yes123 .


Start your admin server with the properties that you got above
java [s_nm_jvm_startup_properties] -Dweblogic.system.StoreBootIdentity=true -Dweblogic.Name=AdminServer weblogic.Server

Now change the node password:
Log in to the WebLogic Administration console
Click the Lock & Edit button. Select the Security tab and click on the ‘Advanced’ link.

Edit the ‘Node Manager password’ field and set it to the new WebLogic Server password
Save and activate the changes

Go back to the console where you started the session, you should see something like this:
<Jan 11, 2016 4:43:14 PM GMT+02:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING> 
<Jan 11, 2016 4:43:14 PM GMT+02:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>  Press ctrl+c to kill the session
^C
<Jan 11, 2016 4:50:52 PM GMT+02:00> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Jan 11, 2016 4:50:52 PM GMT+02:00> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<Jan 11, 2016 4:50:52 PM GMT+02:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<Jan 11, 2016 4:50:53 PM GMT+02:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Jan 11, 2016 4:50:53 PM GMT+02:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jan 11, 2016 4:50:53 PM GMT+02:00> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 2.0.8.23:7001 was shutdown.>


Exit the session and login sourcing the run fs

Start the admin server
$ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

You are running adadminsrvctl.sh version 120.10.12020000.9

Enter the WebLogic Admin password:
Enter the APPS Schema password:
Starting WLS Admin Server...



Start up and shutdown each server






Shutdown the NodeManager
$ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

Copy the boot properties for each server to the security folder so that the ad scripts will be able to use them.
cp $EBS_DOMAIN_HOME/servers/AdminServer/data/nodemanager/boot.properties $EBS_DOMAIN_HOME/servers/AdminServer/security
cp $EBS_DOMAIN_HOME/servers/forms-c4ws_server1/data/nodemanager/boot.properties $EBS_DOMAIN_HOME/servers/forms-c4ws_server1/security
cp $EBS_DOMAIN_HOME/servers/forms_server1/data/nodemanager/boot.properties $EBS_DOMAIN_HOME/servers/forms_server1/security
cp $EBS_DOMAIN_HOME/servers/oafm_server1/data/nodemanager/boot.properties $EBS_DOMAIN_HOME/servers/oafm_server1/security
cp $EBS_DOMAIN_HOME/servers/oacore_server1/data/nodemanager/boot.properties $EBS_DOMAIN_HOME/servers/oacore_server1/security


Start the servers:
$ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start forms-c4ws_server1
$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start forms_server1
$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start oafm_server1
$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start oacore_server1


That's it. Well not exactly you still need to run fs_clone to duplicate the changes to the patch file system. As you can see the delta 7 patch really is a big upgrade. These contain many of the feature in R12.2.5 even if you don't want to upgrade to R12.2.5
adop phase=fs_clone

Reference:

Comments

Popular posts from this blog

Cancel or abort adop session

ADOP is in my opinion still pretty half baked. This is a critical tool that just isn't as intuitive as the old adpatch was. However we move with the times and get the hang of the new way of doing things. Along the way you might want to abort or cancel a patching cycling. With the two file systems and db editioning this can be a bit more to manage. I have learnt the hard way so you need to use the full cleanup after aborting a session.
adop phase=abort
adop phase=cleanup cleanup_mode=full

Creating new WLS domain ends with exit code 255

Cloning the instance I ran into this weird error. Was not sure what to do but after learning my lesson I dug through the error logs after seeing this in the adcfgclone log file.
START: Creating new WLS domain.
Running /u03/APPLYES/YES/fs2/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /u03/APPLYES/YES/fs2/EBSapps/comn/util/jdk64 -al /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/EBSdomain.jar -tdl /u03/APPLYES/YES/fs2/FMW_Home/user_projects/domains/EBS_domain_YES -tmw /u03/APPLYES/YES/fs2/FMW_Home -mpl /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/plan/moveplan.xml -ldl /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/tempinfo.txt
Script Executed in 1903 milliseconds, returning status 255
ERROR: Script failed, exit code 255

Dig a bit deeper into the log files
cd /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply
cat CLONE2016-01-10_04-37-11PM.log

Failed to initialize the application 'EBSDataSource' due to error weblogic.application.ModuleException after FNDCPASS apps change

Started testing password changes in our clone environments. Weblogic seems to love throwing you curve balls and when I changes the apps password with the below:
FNDCPASS apps/$APPS_PASS 0 Y system/system SYSTEM APPLSYS $APPS_PASS
I was not able to start the weblogic managed servers. A look in the log an I found this:

weblogic.application.ModuleException:
        at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:327)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
        at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
        at weblogic.application.internal.BaseDep…