Weblogic domain Start, Set Default User Name and Password, and Problems encountered

Weblogic's domain instance is starting and needs to set default passwords, etc. If the default password is not set at startup, an exception will...

Weblogic's domain instance is starting and needs to set default passwords, etc. If the default password is not set at startup, an exception will occur.

Let's write about domain instance startup, password settings (you can start again without entering a password), service deployment and data source configuration:

Step 1:
In the console, enter the installation directory of the domain instance, and in the Linux console, execute:
sh startWeblogic.sh

At startup, you need to enter your username and password manually.

After the startup is complete, execute the command:
Netstat-ntlp View Port.

Step 2: Set up startup without re-entering username and password


User name and password set when creating domain, such as weblogic/12345678 when I created domain
Then the boot.properties are as follows:

username=weblogic password=password

The problems encountered during startup are as follows:

weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted. at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:960) at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054) at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:888) at weblogic.security.SecurityService.start(SecurityService.java:141) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) Truncated. see log file for complete stacktrace Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User bhybt_dev javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User bhybt_dev denied at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261) at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110) at java.security.AccessController.doPrivileged(Native Method) at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Truncated. see log file for complete stacktrace > <Dec 15, 2018 10:40:53 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED> <Dec 15, 2018 10:40:53 AM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down> <Dec 15, 2018 10:40:53 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Analysis at that time:
1) The password is wrong and has been reinstalled several times. The password must be okay and eliminated.
2) After installation, before starting, you need to build a password file under xxxServer, plaintext username, password, no problem.

Finally, with a try mentality, the user name uses the default weblogic, it's OK!!!!

In the next article, we will write a shell script to start and stop weblogic services.

7 October 2019, 22:43 | Views: 2110

Add new comment

For adding a comment, please log in
or create account

0 comments