If the Admin Password of an EBS WebLogic Domain is lost or forgotten :
1. Shut down all running services. Since the AdminServer password is not known, the
servers cannot be stopped from the console and so must be killed as follows.
--1. Connect to the Oracle E-Business Suite instance and source the application tier
environment file.
--2. Identify the PIDs of Node Manager, AdminServer, and all running Managed
Servers:
$ ps -ef | grep "NodeManager"
$ ps -ef | grep "weblogic.Name=AdminServer"
$ ps -ef | grep "weblogic.Name=forms-c4ws_server"
$ ps -ef | grep "weblogic.Name=forms_server"
$ ps -ef | grep "weblogic.Name=oafm_server"
$ ps -ef | grep "weblogic.Name=oacore_server"
3. Kill all these processes, starting with Node Manager and followed by the
Managed Servers.
2. Back up these folders, and then delete them:
<EBS_DOMAIN_HOME>/security/ DefaultAuthenticatorInit.ldift
<EBS_DOMAIN_HOME>/servers/<server_name>/data/ldap
<EBS_DOMAIN_HOME>/servers/<server_name>/security/boot.properties
<EBS_DOMAIN_HOME>/servers/<server_name>/data/nodemanager/boot.
properties
Where:
• <EBS_DOMAIN_HOME> is the absolute path of the EBS WebLogic domain
• <server_name> is the name of the server directory under
<EBS_DOMAIN_HOME>.
If the password is not reset correctly, the backed up files and folders can be
restored.
Note: For certain servers, the boot.properties file may be present in
only one location of the two specified above. In such a case, back it
up and then delete it.
--3. Set up a new environment to change the WLS AdminServer password.
1. Start a new session and connect to the Oracle E-Business Suite instance.
2. Do not source the application tier environment file.
3. Run the following command to source the WebLogic Server domain
environment:
$ cd <EBS_DOMAIN_HOME>/bin
$ source setDomainEnv.sh
4. Run the following commands:
$ cd <EBS_DOMAIN_HOME>/security
$ java weblogic.security.utils.AdminAccount <wls_adminuser>
<wls_admin_new_password> .
Where:
• <wls_adminuser> is the same as the value of context variable
s_wls_admin_user
• <wls_admin_new_password> is the new WLS AdminServer password you
wish to set.
Note: Do not omit the trailing period ('.') in the above
command: it is needed to specify the current domain directory.
--4. Start AdminServer from the command line. You will be prompted for the WebLogic
Server username and password, so that the AdminServer boot.properties file
can be generated.
1. Go to the EBS Domain Home:
$ cd <EBS_DOMAIN_HOME>
2. Start AdminServer:
$ java <s_nm_jvm_startup_properties> -Dweblogic.system.
StoreBootIdentity=true -Dweblogic.Name=AdminServer weblogic.
Server
• <s_nm_jvm_startup_properties> is the same as the value of context variable
ss_nm_jvm_startup_properties
Example:
MAke sure to remove trailing space and line separators.
$ java -d64 -Xms1024m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Djava.security.policy=/u01/oracle/PROD/fs2/FMW_Home/wlserver_10.3/server/lib/weblogic.policy -Xverify:none -da -Dplatform.home=/u01/oracle/PROD/fs2/FMW_Home/wlserver_10.3 -Dwls.home=/u01/oracle/PROD/fs2/FMW_Home/wlserver_10.3/server -Dweblogic.home=/u01/oracle/PROD/fs2/FMW_Home/wlserver_10.3/server -Dcommon.components.home=/u01/oracle/PROD/fs2/FMW_Home/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain_PROD -Doracle.server.config.dir=/u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain_PROD/config/fmwconfig/servers/AdminServer -Doracle.domain.config.dir=/u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain_PROD/config/fmwconfig -Digf.arisidbeans.carmlloc=/u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain_PROD/config/fmwconfig/carml -Digf.arisidstack.home=/u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain_PROD/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain_PROD/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain_PROD/servers/AdminServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/u01/oracle/PROD/fs2/FMW_Home/oracle_common/modules/oracle.ossoiap_11.1.1,/u01/oracle/PROD/fs2/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=/u01/oracle/PROD/fs2/FMW_Home/oracle_common -Dem.oracle.home=/u01/oracle/PROD/fs2/FMW_Home/oracle_common -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/u01/oracle/PROD/fs2/FMW_Home/patch_wls1036/profiles/default/sysext_manifest_classpath -Dweblogic.system.StoreBootIdentity=true -Dweblogic.Name=AdminServer weblogic.Server
The above command prompts for the WebLogic Server username and password:
Enter username to boot WebLogic server:
Enter password to boot WebLogic server:
Provide the same credentials as you provided in Step 3.
--5. Change Node Manager password
1. Log in to the WebLogic Administration console.
2. Click the 'Lock & Edit' button.
3. In the left panel, click on the EBS Domain link.
4. Select the 'Security' tab.
5. Click on the 'Advanced' link.
6. Edit the 'Node Manager password' field and set it to the new WebLogic Server
password. The password should be same as set in Step 3.
7. Edit the 'Confirm Node Manager Password' field and set it to the new
WebLogic Server password. The password should be same as set in Step 3.
8. Save and activate the changes.
--6. The first time, AdminServer has to be stopped from the Admin console. Follow
these steps:
1. Log in to the WebLogic Administration console.
2. Shut down AdminServer.
--7. Set up your environment to start AdminServer again. AdminServer should now be
started using the normal AD script, which will also start Node Manager using the
new password.
1. Launch a new session and connect to the Oracle E-Business Suite instance.
2. Source the application tier environment file.
3. Start AdminServer with the following command:
$ $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh
--8. Start the Managed Servers. For the first time, all Managed Servers should be started
from the WebLogic Server Admin console. This step will create boot.properties
files for the respective Managed Servers. Follow these steps:
1. Log in to the WebLogic Server Administration Console
2. Start all Managed Servers, one at a time
--9. Shut down all the Managed Servers. This is so the new credentials will be picked up
at the next startup. Follow these steps:
1. Log in to the WebLogic AdminServer console.
2. Shut down all Managed Servers.
3. Shut down AdminServer.
--10. Shut down Node Manager using the normal AD script.
$ $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop
--11. Copy the boot.properties file for each Managed Server.
WebLogic Server native scripts use the boot.properties file. The above steps
have created the boot.properties file under
<EBS_DOMAIN_HOME>/servers/<Managed Server
name>/data/nodemanager, which is used by Node Manager. For each Managed
Server, copy the newly-generated boot.properties file from
<EBS_DOMAIN_HOME>/servers/<Managed Servername>/data/nodemanager to <EBS_DOMAIN_HOME>/servers/<ManagedServer name>/security.
The EBS WebLogic Server domain password has now been changed, and all servers
can now be started using the normal AD scripts.
To start AdminServer:
$ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
To start the Managed Servers:
$ $ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start <managed_server_name>
--12. The above steps have changed the Oracle WebLogic AdminServer password on the
run file system. You now need to perform an fs_clone operation, to change the
WebLogic EBS Domain password on the patch file system:
1. Launch a new session and connect to the Oracle E-Business Suite instance.
2. Source the application tier environment file.
3. Run the command:
3-42 Oracle E-Business Suite Setup Guide
$ adop phase=fs_clone
No comments:
Post a Comment