WebLogic - WLST Server start question

If I have an Admin Server and nodemanager on ServerA and a nodemanager on ServerB with a full WLS install can I connect to the nodemanager on ServerB from ServerA and stop and start managed servers via WLST? Is that possible or do I need to be on the remote box to do it?

Hi,
You can connect to the nodemanager on ServerB from ServerA and stop and start managed servers via WLST / Admin-Console however in both the cases the node-manager has to up and running and make sure you have done Enrolled ServerB's node-manger to ServerA's node-manger.
To get step-by-step instructions you can have a look at the following link:
http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes
Hope above information helped you.
Regards,
Ravish Mody

Similar Messages

Weblogic SIP Server start problem

I installed the evaluation version of the Welogic SIP server 2.2.0. When I start the server, I get the following error message:
"...failed to bind socket to host 192.168.1.1 and port 5060..."
"...failed to start the sip service, shutting down..."
When I try to open the the server admin concole at http://localhost:7001, I get the 404 message.
I uninstalled and reinstalled the server, but the same problem exists.
Any help from anyone is greatly appreciated.
Thank you very much.

Double-check the weblogic.policy file in your WLS 5.1 installation directory. My codeBase and
FilePermission for my WinNT installation looks like this:
grant codeBase "file:C:/wls/-" {
permission java.io.FilePermission "C:${/}wls${/}-", "read,write,delete,execute";
Niall wrote:
Hello,
When I try to start the Weblogic Commerce server 3.2,
I get the error message:
The WebLogic Server did not start up properly.
Exception raised: java.security.AccessControlException: access denied (java.util.PropertyPermission
weblogic.management.password read)
java.security.AccessControlException: access denied (java.util.PropertyPermission
weblogic.management.password read)
I have changed the property weblogic.password.system in the weblogic.properties file
to the system password for Weblogic.
Any ideas?--
Ture Hoefner
BEA Systems, Inc.
2590 Pearl St.
Suite 110
Boulder, CO 80302
www.bea.com
[att1.html]

Weblogic commerce server start problem

Hello,
When I try to start the Weblogic Commerce server 3.2,
I get the error message:
The WebLogic Server did not start up properly.
Exception raised: java.security.AccessControlException: access denied (java.util.PropertyPermission
weblogic.management.password read)
java.security.AccessControlException: access denied (java.util.PropertyPermission
weblogic.management.password read)
I have changed the property weblogic.password.system in the weblogic.properties file
to the system password for Weblogic.
Any ideas?

Double-check the weblogic.policy file in your WLS 5.1 installation directory. My codeBase and
FilePermission for my WinNT installation looks like this:
grant codeBase "file:C:/wls/-" {
permission java.io.FilePermission "C:${/}wls${/}-", "read,write,delete,execute";
Niall wrote:
Hello,
When I try to start the Weblogic Commerce server 3.2,
I get the error message:
The WebLogic Server did not start up properly.
Exception raised: java.security.AccessControlException: access denied (java.util.PropertyPermission
weblogic.management.password read)
java.security.AccessControlException: access denied (java.util.PropertyPermission
weblogic.management.password read)
I have changed the property weblogic.password.system in the weblogic.properties file
to the system password for Weblogic.
Any ideas?--
Ture Hoefner
BEA Systems, Inc.
2590 Pearl St.
Suite 110
Boulder, CO 80302
www.bea.com
[att1.html]

Weblogic Administration Server start with WLST

Hi Team,
I am looking for some WLST script to start the WLS Admin server and then check the status of the Adminserver as well.
When i tried thee command startServer( Adminserver, myserver, domainname, Domaindir )
its not working the way i want it to.....So if you tell me some way to check if its not running and start it with WLST...
I can do the same thing using Shell scripting but not WLST..
Also is there any way in jython language to execute the script from a file.
i use exec startmyfile.sh but it does not recognize it.
help appreciated!!

You can see an overview presentation of WLST here:
http://www.slideshare.net/jambay/weblogic-server-weblogic-scripting-tool-overview-presentation/
There is an Oracle By Example (OBE) tutorial for WLST here:
http://www.oracle.com/technology/obe/fusion_middleware/wls103/SystemMgmt/Command_Line/Command_Line.html
I think both of these resources would be valuable for you.

Weblogic WLST for starting weblogic server

I have created a domain with a single server running Admin Server, SOA and BAM server in the same port.
I would like to start this Server from node manager.
I have started ii with the command nmStart(...), within WLST, I can connect to the ADmin server using connect() command.
But I cannot access the url.
If I start the AdminServer by using startWeblogic.sh then the URL works.
Has anybody tried it?

Hi,
Try this...
[Starting Admin and Managed Servers using Node Manager and WLST | http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html ]
Regards,
Neeraj Sehgal

Weblogic App Server Memory Settings

Hi,
How memory management is happening weblogic app server and where I need to set the those things in weblogic server.
Thanks,

You set memory argumnets for Weblogic in server start scripts - startWeblogic.sh & startManagedWeblogic.sh. You have MEM_ARGS arguments where you set your JVM minimum and maximun heap settings.
Weblogic JVM by default has parallel garbage collection algorithm.
- - Weblogic Consultant

Help: Install "WebLogic Express Server" license

I am having problem to install my "WebLogic Express Server" license.
As I understand, the "WebLogic Server" and "WebLogic Express Server" use the same
installation file, the only difference is the license. So I downloaded the "WebLogic
Server 6.0 Service Pack 2" from BEA's web site. After the installation, I found
a "license.bea" file under WebLogic home directory. I replaced this file with
my license file for "WebLogic Express Server". Unfortunately, I can not start
the default server anymore.
Neither the "UpdateLicense" command works: it seems to me that it only merges/replaces
the existing license with the new one. So although I "updated" the "WebLogic Server"
license to "WebLogic Express Server" license using this command, it seems that
I am still using the "WebLogic Server", because I can still see the EJB component
page in the admin console.
Did I miss something? What is the best way to check whether "WebLogic Express
Server" has been sucessfully installed? Your help is highly appreciated!

Hi,
Find the Link with the screenshots of the whole installtion and domain creation process for Weblogic in all the ways
Installing Weblogic in GUI mode - weblogicexpert
Installing Weblogic 10.3.6 in console Mode in windows machine - weblogicexpert
Creating Domain In GUI mode - weblogicexpert
Creating Domain in Console Mode - weblogicexpert
Starting Weblogic Admin Server
Starting/Stoping Weblogic Admin Server - weblogicexpert
Starting Weblogic Managed Server
Starting/Stoping Weblogic Managed Server - weblogicexpert
Configuring Node manger
Configuring NODE MANAGER And Starting Managed Server from Console - weblogicexpert
Deployment process
Deployments - weblogicexpert
Security concepts
Security Concepts and Hands on - weblogicexpert
Installing Weblogic 12.1.2
Weblogic 12c - weblogicexpert
All other basic information are available in the blog
Hope it helps

Install weblogic standalone server in my laptop. Need guidelines or any blogs.

Hi,
Am planning to install weblogic stand alone server in my laptop.
Kindly help me if there is any blog to provide step by step intallation tutorial.
regards,
Prasad K T,

Hi,
Find the Link with the screenshots of the whole installtion and domain creation process for Weblogic in all the ways
Installing Weblogic in GUI mode - weblogicexpert
Installing Weblogic 10.3.6 in console Mode in windows machine - weblogicexpert
Creating Domain In GUI mode - weblogicexpert
Creating Domain in Console Mode - weblogicexpert
Starting Weblogic Admin Server
Starting/Stoping Weblogic Admin Server - weblogicexpert
Starting Weblogic Managed Server
Starting/Stoping Weblogic Managed Server - weblogicexpert
Configuring Node manger
Configuring NODE MANAGER And Starting Managed Server from Console - weblogicexpert
Deployment process
Deployments - weblogicexpert
Security concepts
Security Concepts and Hands on - weblogicexpert
Installing Weblogic 12.1.2
Weblogic 12c - weblogicexpert
All other basic information are available in the blog
Hope it helps

Problem with WLST in weblogic application server 10.3 on solaris 10 x86

Hi Friends, I installed Sun Solaris 10 on my desktop x86. I am able to install oracle weblogic application server 10.3.
I created one domain and I am trying to start AdminServer on that using WLST command.
Before that , I started the admin server from command as normal start ( nohup ./startWebLogic.sh &) and the server started perfectly alright. After that I was trying to open admin console in firefox browser. It was opening perfectly alright.
Now I stopped the server and checked no processes which are related to weblogic were running , and then initialized the WLST environment using the script "wlst.sh" , which is at (in my system) /usr/bea/wlserver_10.3/common/bin/wlst.sh. Now the environment had been set and the WLST offline prompt came up.
Now I used the below WLST scirpt command
startServer('AdminServer','mydomain','t3://localhost:7001','weblogic','weblogic1');
and the server started perfectly alright, now what I did was , I started admin console at FireFox browser , it prompted me to enter user name and password , I gave them , and once the login is done, then in my shell window , I am seeing error as
**wls:/offline> WLST-WLS-1263965848154: <Jan 19, 2010 11:39:24 PM CST> <Error> <HTTP> <BEA-101017> <[ServletContext@28481438[app:consoleapp module:console path:/console spec-version:2.5]] Root cause of ServletException.**
**WLST-WLS-1263965848154: java.lang.OutOfMemoryError: PermGen space**
**WLST-WLS-1263965848154: at java.lang.ClassLoader.defineClass1(Native Method)**
**WLST-WLS-1263965848154: at java.lang.ClassLoader.defineClass(ClassLoader.java:616)**
**WLST-WLS-1263965848154: at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)**
**WLST-WLS-1263965848154: at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:344)**
**WLST-WLS-1263965848154: at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:301)**
**WLST-WLS-1263965848154: Truncated. see log file for complete stacktrace**
**WLST-WLS-1263965848154: >**
**WLST-WLS-1263965848154: <Jan 19, 2010 11:39:24 PM CST> <Error> <JMX> <BEA-149500> <An exception occurred while registering the MBean com.bea:Name=mydomain,Type=SNMPAgentRuntime.**
**WLST-WLS-1263965848154: java.lang.OutOfMemoryError: PermGen space**
**WLST-WLS-1263965848154: at java.lang.ClassLoader.defineClass1(Native Method)**
**WLST-WLS-1263965848154: at java.lang.ClassLoader.defineClass(ClassLoader.java:616)**
**WLST-WLS-1263965848154: at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)**
**WLST-WLS-1263965848154: at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)**
**WLST-WLS-1263965848154: at java.net.URLClassLoader.access$000(URLClassLoader.java:56)**
**WLST-WLS-1263965848154: Truncated. see log file for complete stacktrace**
**WLST-WLS-1263965848154: >**
**WLST-WLS-1263965848154: Exception in thread "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space**
So I thought I have less memory consuming for this weblogic admin server and opened up ,
_/usr/bea/wlserver_10.3/common/bin/commEnv.sh_
and changed the memory arguments as
Sun)
JAVA_VM=-server
MEM_ARGS="-Xms1024m -Xmx1024m -XX:MaxPermSize=1024m" <---- previously these were 32m and 200m and MaxPermSize
and also in /usr/bea/wlserver10.3/common/bin/bin/setDomainEnv.sh_
and in this file also I changed the memory arguments as
*if [ "${JAVA_VENDOR}" = "Sun" ] ; then*
*WLS_MEM_ARGS_64BIT="-Xms256m -Xmx512m"*
*export WLS_MEM_ARGS_64BIT*
*WLS_MEM_ARGS_32BIT="-Xms1024m -Xmx1024m"*
*export WLS_MEM_ARGS_32BIT*
and restarted the server using the WLST command and again tried to open the admin console on a browser, same error is showing.
(1) Environment : Sun Solaris x86
(2) JDK : sun jdk 1.6._17
Please help me what I am doing wrong here and please let me know the solution.
I was trying to install jrockit 1.6 on this since my OS is sun solaris X86 , there is no compatible jrockit version is not there.
Thanks a lot
Peter

Hi Peter,
As you have mentioned in your Post that
MEM_ARGS="-Xms1024m -Xmx1024m -XX:MaxPermSize=1024m" <---- previously these were 32m and 200m and MaxPermSize
The Setting you have provided is wrong ...that is the reason you are gettingjava.lang.OutOfMemoryError: PermGen space. There is a RRation between PermSize and the maximum Heap Size...
Just a Bit Explaination:
Formula:
(OS Level)Process Size = Java Heap (+) Native Space (+) (2-3% OS related Memory)
PermSize : It's a Netive Memory Area Outside of the Heap, Where ClassLoading kind of things happens. In an operating System like Windows Default Process Size is 2GB (2048MB) default (It doesnt matter How much RAM do u have 2GB or 4GB or more)...until we dont change it by setting OS level parameter to increase the process size..Usually in OS like Solaris/Linux we get 4GB process size as well.
Now Lets take the default Process Size=2GB (Windows), Now As you have set the -Xmx512M, we can assume that rest of the memory 1536 Mb is available for Native codes.
(ProcessSize - HeapSize) = Native (+) (2-3% OS related Memory)
2048 MB - 512 MB = 1536 MB
THUMB RULES:
<h3><font color=red>
MaxPermSize = (MaxHeapSize/3) ----Very Special Cases
MaxPermSize = (MaxHeapSize/4) ----Recommended
</font></h3>
In your Case -Xmx (Max Heap Size) and -XX:MaxPermSize both were same ....That is the reason you are getting unexpected results. These should be in proper ration.
What should be the exact setting of these parameters depends on the Environment /Applications etc...
But Just try -Xmx1024m -Xms1024m -XX:MaxPermSize256m
Another recommendation for fine tuning always keep (Xmx MaxHeapSize & Xms InitialHeapSize same).
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Jan 20, 2010 5:33 PM

How To Set Server Start Parameters With WLST?

I have WLST scripts that create my WebLogic 10.0 domain(s), managed servers, resources, etc. I'd like to add code to set the server start parameters but I can't seem to find the properties related to server start like root directory, java home, arguments, classpath, etc.
The relevant piece of the script here that I have so far is:
def createManagedServer(d,noManagedServers,managed_server_port):
dhome = DOMAINHOME + "/" + d
readDomain(DOMAINHOME + "/" + d)
x = 0
while x < noManagedServers:
ms = d + "Man" + str(x+1)
create(ms,'Server')
cd("Servers/" + ms)
lp = managed_server_port + (x * 10)
set('ListenPort',lp)
set('AutoRestart','true')
set('AutoKillIfFailed','true')
set('AutoRestart','true')
set('IgnoreSessionsDuringShutdown','true')
set('GracefulShutdownTimeout',30)
cd('/')
x = x + 1
updateDomain()
closeDomain()

From WLST you can find these parameters in
wls:/DOMAIN_NAME/serverConfig/Servers/SERVER_NAME/ServerStart/SERVER_NAME
Of course, from your scripts you can set these parameters once you have created the managed server and getting its MBean.
I hope this helps

Cannot start WebLogic Managed Server

Hi,
I have an weblogic domain on a physical machine with two servers (AdminServer and osb_server1 [Managed Server]). (Weblogic 10.3.6)
I started nodeManager and enrolled the domain using nmEnroll command through WLST.
I can start "AdminServer" thourgh nmStart('AdminServer') command. AdminServer starts successfully.
However, when I want to start managed server (osb_server1):
1. Through WebLogic administrator console it says:
(Warning) The user is not authorized to perform lifecycle operations on server osb_server1.
(Warning) All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
2. Using startManagedWebLogic.cmd script after entering username/password, it returns authentication denied.
Oct 22, 2012 10:31:21 AM EEST> <Critical> <Security> <BEA-090403> <Authentication for user weblogic denied>
<Oct 22, 2012 10:31:21 AM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
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:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
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
>
3. Using nmStart command on nodeManager, it is complaining about boot.properties file.
I can login AdminServer with same account without problems.
Best Regards,
Edited by: ToRRaDo on Oct 22, 2012 5:25 PM

Copied boot.properties from AdminServer to osb_server1 and the error below occured. (I also with plain text passwords in boot.properties file but error did not change)
<Oct 23, 2012 8:03:59 AM EEST> <Error> <Configuration Management> <BEA-150021> <The admin server failed to authenticate the identity of the user weblogic starting the managed server. The reason for the error is .>
<Oct 23, 2012 8:03:59 AM EEST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:7001/.>
<Oct 23, 2012 8:03:59 AM EEST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Oct 23, 2012 8:03:59 AM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Oct 23, 2012 8:03:59 AM EEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Oct 23, 2012 8:04:00 AM EEST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\my_domain\servers\osb_server1\logs\osb_server1.log is opened. All server side log events will be written to this file.>
<Oct 23, 2012 8:04:19 AM EEST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Oct 23, 2012 8:04:19 AM EEST> <Critical> <Security> <BEA-090402> <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.>
<Oct 23, 2012 8:04:20 AM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password fromthe 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.
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:873)
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:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
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>
<Oct 23, 2012 8:04:20 AM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
Edited by: ToRRaDo on Oct 23, 2012 8:13 AM
Edited by: ToRRaDo on Oct 23, 2012 8:14 AM

Not able to start weblogic portal server

I installed WebLogic Portal 10.3 server on linux. After creating a domain when I start weblogic I get following exception:
<Jan 12, 2012 12:46:57 PM IST> <Error> <Security> <BEA-000000> <[Security:090759]A SQLException occurred while retrieving password information
java.sql.SQLSyntaxErrorException: Schema 'WEBLOGIC' does not exist
at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.client.am.Connection.prepareStatement(Unknown Source)
at >weblogic.security.providers.authentication.DBMSSQLReadOnlyDatabaseConnectionImpl.getPreparedStatement(DBMSSQLReadOnlyDatabaseConnectionImpl.java:37)
at weblogic.security.providers.authentication.shared.DBMSSQLRuntimeQueryImpl.passwordStringQuery(DBMSSQLRuntimeQueryImpl.java:82)
Truncated. see log file for complete stacktrace
Caused By: org.apache.derby.client.am.SqlException: Schema 'WEBLOGIC' does not exist
at org.apache.derby.client.am.Statement.completeSqlca(Unknown Source)
at org.apache.derby.client.net.NetStatementReply.parsePrepareError(Unknown Source)
at org.apache.derby.client.net.NetStatementReply.parsePRPSQLSTTreply(Unknown Source)
at org.apache.derby.client.net.NetStatementReply.readPrepareDescribeOutput(Unknown Source)
at org.apache.derby.client.net.StatementReply.readPrepareDescribeOutput(Unknown Source)
Truncated. see log file for complete stacktrace>
<Jan 12, 2012 12:46:57 PM IST> <Critical> <Security> <BEA-090402> <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.>
<Jan 12, 2012 12:46:57 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: 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.
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:959)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
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.LoginException: java.sql.SQLSyntaxErrorException: Schema 'WEBLOGIC' does not exist
at weblogic.security.providers.authentication.shared.DBMSAtnLoginModuleImpl.authenticateDBMS(DBMSAtnLoginModuleImpl.java:696)
at weblogic.security.providers.authentication.shared.DBMSAtnLoginModuleImpl.login(DBMSAtnLoginModuleImpl.java:271)
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)
Truncated. see log file for complete stacktrace>I know it means WEBLOGIC schema does not exist. But don't know how can I create it?
The steps I followed:
1. Run ./config.sh from wlserver_10.3/common/bin to create new domain.
2. Run ./craete_db.sh from newly created domain folder.
3. Run ./startWeblogic.sh
Edited by: 907606 on Jan 12, 2012 1:58 AM

Ravi Jegga wrote:
Hi
Its been a while I have not worked on Weblogic Portal. BUT after creating the Portal Domain using config wizard, why did you again run create_db scripts. As far as I know, this is NOT required. Is your intention to change the portal db schema to some other database like to Oracle etc. Then why don't you do that at the time of domain creation itself. Give those DB details. create_db is if you ever want to use any other db to have your portal schemas. After doing this, you also should run one more .sql file in one of the folders under your domain root folder structure (something like yourdomain/security/SQLAuthenticator.sql).
Now, the main point is, what ever database you use, when you run Config Wizard and choose Portal Domain facet and click next, next, at one of the screens, it shows all the Portal DataSources details (have default db or modify to use oracle etc). BUT the main thing is in next screen, when you test all these DataSources, there should be button in the bottom like Run Scripts. Make sure to hit this button. Because this will create and run full portal schema scripts. You cannot miss this. Complete the domain creation and start the domain and try again.
Thanks
Ravi JeggaHow can I run that extra .sql file? The steps I follow in creating domain is as follows:
Steps:
1. Select Create new weblogic domain.
2. Select Choose Weblogic Platform componenets.
3. Select Basic WebLogic Server Domain - 10.3.4.0 [wlserver_10.3] and WebLogic Portal - 10.3.4.0.
4. Enter domain name.
5. Enter username/password.
6. Select development mode.
7. Select JRockit SDK 1.6.0_22 @ /usr/local/Oracle/jrockit_160_22_D1.1.1-3
8. Got following on screen:
Edit the configuration of JDBC data sources. A data source contains a pool of database connections. Applications look up a data source in the JNDI tree, request a connection, use it, and
return it to the connection pool.
| Name |
_|__________________________|
1| cgDataSource |
2| portalDataSourceAlwaysXA |
3| portalDataSource |
4| p13nDataSource |
5| cgDataSource-nonXA |
6| portalDataSourceNeverXA |
Use above value or select another option:
1 - Modify
2 - Discard Changes
Enter option number to select OR [Exit][Previous][Next]>Done nothing and go to next screen.
9. Following appears:
If your connections tested OK, you may now run database scripts. For each JDBC data source, you will select the desired database loading options and database version.
1|p13nDataSource
2|portalDataSource
3|portalDataSourceAlwaysXA
4|portalDataSourceNeverXA
5|cgDataSource
6|cgDataSource-nonXA
->7|Skip JDBC Configuration
Enter index number to select OR [Exit][Previous][Next]> Here selected every datasource one by one and loaded their database.
10. Select Administration Server.
11. Following screen:
Each WebLogic Server domain must have one Administration Server. The Administration Server is used to perform administrative tasks.
| Name | Value |
_|__________________|_____________________|
1| *Name: | AdminServer |
2| *Listen address: | All Local Addresses |
3| Listen port: | 7001 |
4| SSL listen port: | N/A |
5| SSL enabled: | false |
Use above value or select another option:
1 - Modify "Name"
2 - Modify "Listen address"
3 - Modify "Listen port"
4 - Modify "SSL enabled" Kept all things default and gone to next screen.
12. Go to domain directory and run ./startWebLogic.sh.
13. Got following exception:
<Jan 13, 2012 10:03:00 AM IST> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: ><openjpa-1.1.1-SNAPSHOT-r422266:965591 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class >"kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:965591 fatal internal error> org.apache.openjpa.util.InternalException: There >was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
Truncated. see log file for complete stacktrace
Caused By: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:965591 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static >getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
Truncated. see log file for complete stacktrace
Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:965591 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class >"kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)
at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)
at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)
at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:99)
at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)
Truncated. see log file for complete stacktrace
Caused By: java.lang.RuntimeException: There were errors initializing your configuration: <openjpa-1.1.1-SNAPSHOT-r422266:965591 fatal store error> org.apache.openjpa.util.StoreException: The connection was refused >because the database weblogic_eval was not found.
at org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:235)
at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:684)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:288)
at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)
at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)
at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)
at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)
at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)
at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)
at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)
at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)
at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: java.sql.SQLNonTransientConnectionException: The connection was refused because the database weblogic_eval was not found.
at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at com.solarmetric.jdbc.PoolingDataSource.newConnection(PoolingDataSource.java:272)
at com.solarmetric.jdbc.ConnectionPoolImpl.makeConnection(ConnectionPoolImpl.java:413)
at com.solarmetric.jdbc.ConnectionPoolImpl.getConnection(ConnectionPoolImpl.java:290)
at com.solarmetric.jdbc.PoolingDataSource.getConnection(PoolingDataSource.java:199)
at org.apache.openjpa.lib.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:113)
at org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:93)
at org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:227)
... 37 more
Caused by: org.apache.derby.client.am.DisconnectException: The connection was refused because the database weblogic_eval was not found.
at org.apache.derby.client.net.NetConnectionReply.parseRDBNFNRM(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(Unknown Source)
at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(Unknown Source)
at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(Unknown Source)
at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source)
at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
at org.apache.derby.client.net.NetConnection40.<init>(Unknown Source)
at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(Unknown Source)
... 45 more
at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:302)
at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)
at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)
at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)
at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)
Truncated. see log file for complete stacktrace
<Jan 13, 2012 10:03:00 AM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 13, 2012 10:03:00 AM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)>14. Due to above I have to run create_db.sh and then I started getting the exception described in question above.

Need to write start up scrits for weblogic admin server on Linux

Hi,
I am new to weblogic i have Installed wls1035 on Linux Created Managed servers,but i want write start up and stop scripts for weblogic admin server please let me know how to write.
My weblogic server is Running on Linux..please help me its very urgent for me.....

Put something like this into a startAll.py file (excluding the ---):
startNodeManager(verbose='false',NodeManagerHome=localWlsHome + '/common/nodemanager',ListenPort=5556,ListenAddress=localhost)
nmConnect('weblogic','password','localhost','5556','domain_name')
nmStart('AdminServer','/path-to-domain-dir')
nmStart('my_server_1','/path-to-domain-dir')
nmStart('my_server_2','/path-to-domain-dir')
nmDisconnect()
exit()
source /path-to-domain-dir/bin/setDomainEnv.sh
$JAVA_HOME/bin/java weblogic.WLST startAll.py
Similar for stop (stopAll.py):
nmConnect('weblogic','password','localhost','5556','domain_name')
nmKill('my_server_1')
nmKill('my_server_2')
nmKill('AdminServer')
stopNodeManager()
exit()
source /path-to-domain-dir/bin/setDomainEnv.sh
$JAVA_HOME/bin/java weblogic.WLST stopAll.py
You might have issues with the Nodemanager having an autogenerated username and password. That can be fixed like this:
In the AdminServer console, click on Lock & Edit
In the AdminServer console, go to <domain> -> Security -> General -> Advanced and update the Node Manager username and password to use the same values as the WebLogic server.
In the AdminServer console, apply the changes.
Start WLST: $WL_HOME/common/bin/wlst.sh
Connect to the AdminServer: connect('weblogic','password','t3://<adminserver-hostname>:<adminserver-port>')
Enroll: nmEnroll('/path-to-domain-dir')
Exit WLST: CTRL^D
You might also look into customizing the nodemanager's property file:
Edit $WL_HOME/common/nodemanager/nodemanager.properties
StopScriptEnabled=true
CrashRecoveryEnabled=true
StartScriptEnabled=true
For further reading, please take a look at: http://docs.oracle.com/cd/E15051_01/wls/docs103/config_scripting/reference.html
Edited by: 925121 on Apr 3, 2012 2:16 AM

Start/Stop Weblogic Admin Server

Hello,
I have installed Forms 11g in my home Pc, so is it possible to Start/Stop Weblogic Admin Server and the Dos window that appears, not to ask me about username and password?
I mean like a bat file (script), to enter the username and password in a text file
if yes, also the same in WLS_FORMS?
Thank you.

Starting an Administration Server with a Startup Script
An Administration Server is a WebLogic Server instance that maintains configuration data for a domain. In a development environment, it is usually sufficient to start an Administration Server and deploy your applications directly onto the Administration Server. In a production environment, you create Managed Servers to run applications. For more information about Administration Servers and Managed Servers, see "Understanding WebLogic Server Domains" in Understanding Domain Configuration for Oracle WebLogic Server.
You can start an Administration Server with a default startup script or create your own. To start an Administration Server with the WebLogic Server-included startup script:
If you have not already done so, use the Configuration Wizard or WebLogic Scripting Tool (WLST) to create a domain.
See Creating Domains Using the Configuration Wizard or "Creating Domains Using WLST Offline" in Oracle WebLogic Scripting Tool.
Open a shell (command prompt) on the computer on which you created the domain.
Change to the directory in which you located the domain.
By default, this directory is MW_HOME\user_projects\domains\DOMAIN_NAME, where DOMAIN_NAME is the root directory of the domain. (The name of this directory is the name of the domain.)
Run one of the following scripts:
bin/startWebLogic.cmd (Windows)
bin\startWebLogic.sh (UNIX and Windows. On Windows, this script supports the MKS and Cygnus BASH UNIX shell emulators.)
Note:
If you use a Configuration Wizard template that is provided by WebLogic Server, your domain directory includes a start script named startWebLogic. If you use a domain template from another source, the wizard might not create a start script, or it might create a script with a different name. The template designer determines whether the wizard creates a start script and the name of the script.
The startWebLogic script does the following:
Sets environment variables by invoking DOMAIN_NAME\bin\setDomainEnv.cmd (setDomainEnv.sh on UNIX), where DOMAIN_NAME is the directory in which you located the domain; for example, WL_HOME\user_projects\domains\DOMAIN_NAME, and where WL_HOME is the location in which you installed WebLogic Server.
Invokes the java weblogic.Server command, which starts a JVM that is configured to run a WebLogic Server instance.
When the server successfully completes its startup process, it writes the following message to standard out (which, by default, is the command window):
<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Starting an Administration Server from the Windows Start Menu
When you create an Administration Server on a Windows computer, the Configuration Wizard creates a shortcut on the Start Menu for starting the server (User Projects > DOMAIN_NAME > Start Admin Server for WebLogic Server Domain).
The command that the Configuration Wizard adds to the Start menu opens a command window and calls the startup script that is described in Starting an Administration Server with a Startup Script. When the server has successfully completed its startup process, it writes the following message to standard out (which, by default, is the command window):
<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Mark this helpful/correct to help others too

Weblogic 11g on Windows - very slow admin server start

Hello,
It takes upwards of 15 minutes to fully start the admin server on my Windows box. I have read that it's a bug in the Java security random number/crypto api.
There are various work arounds for the Linux environments, but no mention of Windows. I realize that I'm in a small minority of admins running WLS on Windows, but does anybody have experience in setting the Java security stuff so the servers do not take soooooo darn long to startup?
JDM

Hi ,
I think it would be better to post this question in the Weblogic - General forum for WLS specific troubleshooting tip : WebLogic Server - General
Having said that get the thread dump for WLS server start up using kill -3 <pid> command or using jstack -l <pid> .
Post the question and the thread dumps to the above mentioned forum .
In my case the start up time is less than a minute .
Thanks
Srinath

WebLogic - WLST Server start question

Similar Messages

Maybe you are looking for