Changing the Oracle WebLogic Server Administration User Password

The option to set the Oracle WebLogic Server Administration User password to a non-default value is available during Oracle E-Business Suite installation. This section describes the procedure to use (on the run file system) if you need to change the password at a later time.

Important: If you need to change the Administration User password, you must change the Node Manager password first. If you do not do this, the WebLogic Server configuration change will not be detected and the next online patching cycle may fail.

The Oracle WebLogic Server domain EBS_domain_<SID> (dedicated to Oracle E-Business Suite) uses Node Manager to control the Administration Server and the managed servers. For this domain, the Node Manager and Oracle WebLogic Server Administration User passwords must be same or the AD control scripts will not work properly.

By default, Oracle WebLogic Server used with Oracle E-Business Suite enforces the following password validation rules:

• Minimum password length: 8
• Minimum number of non-alphabetic characters, including numeric characters or special characters such as %, *, #, or }: 1

Important: If any provider-specific attributes have been changed for either the default WebLogic Authentication provider (DefaultAuthenticator) or the default Password Validation provider (SystemPasswordValidator), the new password must adhere to the above rules.

The password-changing instructions that follow should be performed on the run file system. The password change will be automatically propagated to the patch file system during the next adop prepare phase or fs_clone operation.

For more information, see: "Changing the Administrative User Password" in Chapter 3 of Oracle Fusion Middleware Administrator's Guide 11g Release 1 (11.1.1).

1. Shut down all application tier services except the Admin Server.
   1. On the primary node, run the command:

       $ <ADMIN_SCRIPTS_HOME>/adstpall.sh -skipNM -skipAdmin

      On all secondary nodes, run the command:

       $ <ADMIN_SCRIPTS_HOME>/adstpall.sh 

   Note: The above examples are for UNIX. If you are using Windows, employ the appropriate equivalent syntax.
2. Change the Oracle WebLogic Server Administration User password by performing the following steps as applicable.
   1. Source the environment on the run file system.
   2. Run the commands appropriate for your platform:
      • On UNIX, run the command:

        $ perl $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl -action=updateAdminPassword

      • On Windows, open a DOS command window and perform the following steps on the nodes directed:
        1. Run the following command on all nodes:

           C:\>perl %FND_TOP%\patch\115\bin\txkUpdateEBSDomain.pl -action=updateAdminPassword -allnodes=no
           

           Warning: Do not specify -allnodes=no on UNIX platforms.
        2. Run the following commands on the primary node only:

           C:\><ADMIN_SCRIPTS_HOME>\adadminsrvctl.cmd stop
           C:\><ADMIN_SCRIPTS_HOME>\adnodemgrctl.cmd stop

        3. Start Node Manager by running the following commands on all nodes:

           C:\>cd %INST_TOP%\admin\install
           C:\>adsvNodeManager.cmd

        4. When prompted, enter the new password you just set.
        5. Close the DOS command window.
3. From a terminal window, start all services on all nodes using the appropriate command for your platform.
   • On UNIX, run the command:

     $ <ADMIN_SCRIPTS_HOME>/adstrtal.sh 

   • On Windows run the command:

     C:\><ADMIN_SCRIPTS_HOME>\adstrtal.cmd

4. 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 following command:

      $ adop phase=fs_clone

If the Admin Password of an EBS WebLogic Domain is lost or forgotten

As noted earlier, the EBS WebLogic domain uses Node Manager to control startup of the AdminServer and Managed Servers. For the EBS WebLogic domain, the Node Manager and WebLogic AdminServer passwords must be same. If the passwords are different, the AD control scripts will not work properly.

If the AdminServer password has been lost or forgotten, it can be reset by carrying out the following steps on the run file system. As described in the final step, an fs_clone operation should then be performed to synchronize the run and patch file systems.

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

      Where:
      • <s_nm_jvm_startup_properties> is the same as the value of context variable ss_nm_jvm_startup_properties
      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 the 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 start

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 Server name>/data/nodemanager to <EBS_DOMAIN_HOME>/servers/<Managed Server 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 following command:

       $ adop phase=fs_clone

Known Issues

For the most current list of known issues with the AutoConfig-related configuration management of Oracle E-Business Suite Release 12.2 environments, see My Oracle Support Knowledge Document, 1905593.1, Managing Configuration of Oracle HTTP Server and Web Application Services in Oracle E-Business Suite Release 12.2.