Steps:
Step1). open a Command Prompt and then run “setDomainEnv.sh” or “setDomainEnv.cmd”.
Step2). Just for Safety Take a Backup of (C:\oracle_middleware\user_projects\domains\7001_Domain\security\*DefaultAuthenticatorInit.ldift*) file …because in the Next Command which we are going to run is going to Create a New File “DefaultAuthenticatorInit.ldift”.
Step3). In the Command Window Move inside your Domain’s Security Directory…And then Run the Following Command:
Example: C:\oracle_middleware\user_projects\domains\7001_Domain\security>java weblogic.security.utils.AdminAccount newAdmin newPassword .
Syntax: java weblogic.security.utils.AdminAccount <NewAdminUserName> <NewAdminPassword>
NOTE:- There is a . (DOT) at the end of the Above command which represents the Current Directory. Here you can see that after this command Executes A new “DefaultAuthenticatorInit.ldift” file will be created in the Current Directory.
Step 4). In the Same command prompt Move inside the admin Server folder inside your domain. And then Just remname the “data” folder to something else ….like “data_OLD” this is a way of taking safe backup….
Example: C:\oracle_middleware\user_projects\domains\7001_Domain\servers\AdminServer> rename data data_OLD
Step 5). Now Similarly rename the boot.properties as well to an other File….
Example: C:\oracle_middleware\user_projects\domains\7001_Domain\servers\AdminServer\security> rename boot.properties boot.properties_OLD
Step 6). Make sure that “boot.properties” file exists….If yes then Now start The Admin Server….
While starting it will ask for the UserName and Password to be entered as ..we havenot created any “boot.properties” file at present. But it is always recommended that u create the “boot.properties” file on your own …to prevent WebLogic Prompting you for Admin Username & Passwords while starting the Server.
————> At the End Login to Admin Console with the New Useraname and Password—–> Check the Users in Security realms …you will not find any user with name “weblogic” There….
This is most important Step: Because Sometimes we face this kind of issue if you have provided a Wrong format in your “boot.properties” file there should be NO Special Charachers (UTF or Invisible sharacters) Or NO Space in your “boot.properties” file …except below two Lines:
1 username=MyAdminUserName
2 password=MyAdminPassword
Step 7). To import other User Data back Please do the following:
Login to Admin Console
Security Realms—> myrealm(Your realm Name)—> Migration(Tab)—> Import (Tab)
Now provide the folder Name where u have all the above files:
DefaultAuthenticator.dat
DefaultCredentialMapper.dat
exportIndex.dat
XACMLAuthorizer.dat
XACMLRoleMapper.dat
Enjoy….
Step1). open a Command Prompt and then run “setDomainEnv.sh” or “setDomainEnv.cmd”.
Step2). Just for Safety Take a Backup of (C:\oracle_middleware\user_projects\domains\7001_Domain\security\*DefaultAuthenticatorInit.ldift*) file …because in the Next Command which we are going to run is going to Create a New File “DefaultAuthenticatorInit.ldift”.
Step3). In the Command Window Move inside your Domain’s Security Directory…And then Run the Following Command:
Example: C:\oracle_middleware\user_projects\domains\7001_Domain\security>java weblogic.security.utils.AdminAccount newAdmin newPassword .
Syntax: java weblogic.security.utils.AdminAccount <NewAdminUserName> <NewAdminPassword>
NOTE:- There is a . (DOT) at the end of the Above command which represents the Current Directory. Here you can see that after this command Executes A new “DefaultAuthenticatorInit.ldift” file will be created in the Current Directory.
Step 4). In the Same command prompt Move inside the admin Server folder inside your domain. And then Just remname the “data” folder to something else ….like “data_OLD” this is a way of taking safe backup….
Example: C:\oracle_middleware\user_projects\domains\7001_Domain\servers\AdminServer> rename data data_OLD
Step 5). Now Similarly rename the boot.properties as well to an other File….
Example: C:\oracle_middleware\user_projects\domains\7001_Domain\servers\AdminServer\security> rename boot.properties boot.properties_OLD
Step 6). Make sure that “boot.properties” file exists….If yes then Now start The Admin Server….
While starting it will ask for the UserName and Password to be entered as ..we havenot created any “boot.properties” file at present. But it is always recommended that u create the “boot.properties” file on your own …to prevent WebLogic Prompting you for Admin Username & Passwords while starting the Server.
————> At the End Login to Admin Console with the New Useraname and Password—–> Check the Users in Security realms …you will not find any user with name “weblogic” There….
This is most important Step: Because Sometimes we face this kind of issue if you have provided a Wrong format in your “boot.properties” file there should be NO Special Charachers (UTF or Invisible sharacters) Or NO Space in your “boot.properties” file …except below two Lines:
1 username=MyAdminUserName
2 password=MyAdminPassword
Step 7). To import other User Data back Please do the following:
Login to Admin Console
Security Realms—> myrealm(Your realm Name)—> Migration(Tab)—> Import (Tab)
Now provide the folder Name where u have all the above files:
DefaultAuthenticator.dat
DefaultCredentialMapper.dat
exportIndex.dat
XACMLAuthorizer.dat
XACMLRoleMapper.dat
Enjoy….
No comments:
Post a Comment