Server starting: jython/WLST vs console

I'm using the startServer command in WLST to start a server with jmv arguments. Some of the arguments get overridden by what is in the "Server Start" section of the console. Emphasis on SOME...and not always.
what gets overridden on a Managed server may not get overridden on an Admin server and vice verse...
is there a document that defines which jvmArgs have precedence and when?

oh yea, this is on 92 and at server boot time which is why i'm using the jython/WLST combo.

Similar Messages

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.

JRockit JVM Freezes on server start and WLST domain configuration

Hi,
Here is our configuration:
OS:
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.3 (Tikanga)
uname -a
Linux ********* 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
rpm -qa | grep glibc
glibc-2.5-34
glibc-common-2.5-34
glibc-2.5-34
We are using WLS 10.3 with 64 bit OS and 64 bit JRockit JVM on Xeon system.
The JVM freezes for about 10m when I am trying to start the server. I also see the same behavior when I am trying to create the domain using WLST. Here is the thread dump during the freeze. The JVM eventually recovers from this and continues processing. During domain configuration, the freeze happens when it is trying to write the domain files to disk. All writes are happening to local disk.
===== FULL THREAD DUMP ===============
Mon Apr 20 18:37:41 2009
BEA JRockit(R) R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-x86_64
"Main Thread" id=1 idx=0x4 tid=30539 prio=5 alive, in native
at jrockit/io/FileNativeIO.readBytesPinned(Ljava/io/FileDescriptor;[BII)I(Native Method)
    at jrockit/io/FileNativeIO.readBytes(FileNativeIO.java:46)
    at java/io/FileInputStream.readBytes([BII)I(FileInputStream.java)
    at java/io/FileInputStream.read(FileInputStream.java:199)
    at sun/security/provider/NativePRNG$RandomIO.readFully(NativePRNG.java:185)
    at sun/security/provider/NativePRNG$RandomIO.implGenerateSeed(NativePRNG.java:202)
    ^-- Holding lock: java/lang/Object@0x8577948[biased lock]
at sun/security/provider/NativePRNG$RandomIO.access$300(NativePRNG.java:108)
at sun/security/provider/NativePRNG.engineGenerateSeed(NativePRNG.java:102)
at java/security/SecureRandom.generateSeed(SecureRandom.java:495)
at com/bea/security/utils/random/AbstractRandomData.ensureInittedAndSeeded(AbstractRandomData.java:83)
^-- Holding lock: com/bea/security/utils/random/SecureRandomData@0x95f5db0[recursive]
at com/bea/security/utils/random/AbstractRandomData.getRandomBytes(AbstractRandomData.java:97)
^-- Holding lock: com/bea/security/utils/random/SecureRandomData@0x95f5db0[biased lock]
at com/bea/security/utils/random/AbstractRandomData.getRandomBytes(AbstractRandomData.java:92)
at weblogic/security/Salt.getRandomBytes(Salt.java:18)
at weblogic/security/internal/encryption/JSafeSecretKeyEncryptor.decryptSecretKey(JSafeSecretKeyEncryptor.java:108)
at weblogic/security/internal/encryption/JSafeEncryptionServiceImpl.<init>(JSafeEncryptionServiceImpl.java:206)
at weblogic/security/internal/encryption/JSafeEncryptionServiceFactory.getEncryptionService(JSafeEncryptionServiceFactory.java:23)
at weblogic/security/internal/SerializedSystemIni.getEncryptionService(SerializedSystemIni.java:214)
at weblogic/security/internal/SerializedSystemIni.getExistingEncryptionService(SerializedSystemIni.java:240)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
    at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(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 weblogic/descriptor/DescriptorManager$SecurityServiceImpl$SecurityProxy.<init>(DescriptorManager.java:149)
    at weblogic/descriptor/DescriptorManager$SecurityServiceImpl$SecurityProxy.instance(DescriptorManager.java:137)
    at weblogic/descriptor/DescriptorManager$SecurityServiceImpl.isEncrypted(DescriptorManager.java:108)
    at weblogic/descriptor/internal/AbstractDescriptorBean._isEncrypted(AbstractDescriptorBean.java:968)
    at weblogic/management/configuration/SecurityConfigurationMBeanImpl.setCredentialEncrypted(SecurityConfigurationMBeanImpl.java:1557)
    at weblogic/management/configuration/SecurityConfigurationMBeanImpl.setCredentialEncryptedAsString(SecurityConfigurationMBeanImpl.java:781)
    at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
    at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
    at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(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 com/bea/staxb/runtime/internal/util/ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
    at com/bea/staxb/runtime/internal/RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:531)
    at com/bea/staxb/runtime/internal/MultiIntermediary.setValue(MultiIntermediary.java:80)
    at com/bea/staxb/runtime/internal/ByNameRuntimeBindingType$ElementQNameProperty.fill(ByNameRuntimeBindingType.java:348)
    at com/bea/staxb/runtime/internal/LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:139)
    at com/bea/staxb/runtime/internal/ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com/bea/staxb/runtime/internal/AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com/bea/staxb/runtime/internal/LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:164)
    at com/bea/staxb/runtime/internal/LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
    at com/bea/staxb/runtime/internal/ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com/bea/staxb/runtime/internal/AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com/bea/staxb/runtime/internal/UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:189)
    at com/bea/staxb/runtime/internal/UnmarshalResult.unmarshalDocument(UnmarshalResult.java:159)
    at com/bea/staxb/runtime/internal/UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic/descriptor/internal/MarshallerFactory$1.createDescriptor(MarshallerFactory.java:95)
    at weblogic/descriptor/BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:240)
    at weblogic/management/provider/internal/DescriptorManagerHelper.loadDescriptor(DescriptorManagerHelper.java:63)
    at weblogic/management/provider/internal/RuntimeAccessImpl$IOHelperImpl.parseXML(RuntimeAccessImpl.java:683)
    at weblogic/management/provider/internal/RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:268)
    at weblogic/management/provider/internal/RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:115)
    at weblogic/management/provider/internal/RuntimeAccessService.start(RuntimeAccessService.java:39)
    at weblogic/t3/srvr/ServerServicesManager.startService(ServerServicesManager.java:459)
    at weblogic/t3/srvr/ServerServicesManager.startInStandbyState(ServerServicesManager.java:164)
    ^-- Holding lock: java/lang/Class@0x939df30[biased lock]
at weblogic/t3/srvr/T3Srvr.initializeStandby(T3Srvr.java:711)
at weblogic/t3/srvr/T3Srvr.startup(T3Srvr.java:482)
at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:440)
at weblogic/Server.main(Server.java:67)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
<<Truncated for brevity>>
===== END OF THREAD DUMP ===============
The same process works fine on a VM with the same OS. Any ideas what might be going on?
Thanks,
Chengi

This does not look familiar to me. Download R27.6.3 and see if that works things out: http://www.oracle.com/technology/software/products/jrockit/index.html. If that does not help, I recommend you to report the issue to JRockit support (see how to below).
Best Regards,
Tuva
JRockit PM
How to report to JRockit support:
You must register and file the issue on Metalink, http://metalink.oracle.com. Note that you must have purchased support to continue.
If you have problems during the registration or filing you can call our support +1.800.223.1711* or 1-800-633-0738 directly.
In case you have not purchased support call 1.800.833.3536* for support sales.
More information on our support site: http://www.oracle.com/support/index.html.
*) US numbers - for global technical support contacts see: http://www.oracle.com/support/contact.html

I depolyed a webapp in oim server problem is oim admin console is not opend

hi
i have deployed a webapplication in oim server(jboss) the application is developed using struts. the application is deployed successfully.after server starting the oim admin console is not opend it gives following error .I am using oim 9101 with jboss server
[ServletException in:/layouts/tjspClassicLayout.jsp] java.lang.NoSuchMethodError: org.apache.struts.util.RequestUtils.message(Ljavax/servlet/jsp/PageContext;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
can any one help me.
Thanks.

First of all you remove your war or ear file.
Don't take jar from outside. Take the all jar from OIM machine, used by xlWebApp. You don't need to download any extra jar if it is simple web application based on struts.
Rebuild with your war or ear with new jar. Than just try it.
Hope this is clear case of jar confliction.

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

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

Failes to start Managed server using Nodemanager from admin console

Hi
I have created the cluster using Weblogic version 9.2 MP3 with
Machine 1 --> Admin (AS) + Managed server (MS1)
Machine 2 --> Managed server(MS2)
All the servers(AS,MS1,MS2) are SSL configured to run in production mode.
Machine is associated with each managed server and node manager is up and running.
I have made Host name verification as "None"
When i start the MS 1 from admin console it comes up in running.However MS2 is not coming in running mode.
The server logs states that "Could not connect to admin server"
Cannot decrypt the password ,username and TrustKeyStorePrivatepassphrase.
Even when i write the clear text password and username in Server_Name/data/nodemanager/boot.properties,then also it throws the same error.
Node manager is not configured to SSL.
Any Clue what i am missing????

Is your Machine #2 shown as "Reachable" in the admin console ( Machines -> Machine2 -> Monitoring )?
Does your managed server #2 have the same userid and password on its Server -> Configuration -> Server Start page ( UserName & Password fields ) as managed server #1?
Your boot.properties only needs 2 lines, like:
password=your plain text password
username=your plain text username

Error message when I try to start the SC SM Console

Hi,
i get the following error message when I try to start the SC SM Console in TN MSDN Virtual Lab
Message: Failed to connect to server 'SCSM01.contoso.com'
Microsoft.EnterpriseManagement.Common.UnknownServiceException:
The
service threw an unknown exception. See inner exception for details.
---> System.ServiceModel.FaultException`1[System.UnauthorizedAccessException]:
The creator of this fault did not specify a Reason. (Fault Detail is
equal to System.UnauthorizedAccessException:
You have exceeded the
evaluation period of this product. For information on purchasing the
retail version of this product, go to
http://go.microsoft.com/fwlink/?LinkID=151842.
at Microsoft.EnterpriseManagement.ServiceDataLayer.SessionManagerService.CheckLicence()
at Microsoft.EnterpriseManagement.ServiceDataLayer.SessionManagerService.Connect(SdkClientConnectionOptions
options)
at Microsoft.EnterpriseManagement.ServiceDataLayer.BasicDispatcherService.Connect(SdkClientConnectionOptions
connectionOptions)).
--- End of inner exception stack trace ---
at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception
ex)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings
connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings
connectionSettings, ClientDataAccessCore clientCallback)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings
connectionSettings, ClientDataAccessCore callbackDispatcherService)
at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[T,P](EnterpriseManagementConnectionSettings
connectionSettings, ClientDataAccessCore callbackDispatcherService)
at Microsoft.EnterpriseManagement.ServiceManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings
connectionSettings, EnterpriseManagementGroupInternal
internals)
at Microsoft.EnterpriseManagement.ServiceManagementGroup..ctor(ServiceManagementConnectionSettings
connectionSettings)
at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ManagementGroupSessionManager.Connect(String
server)
at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.Credentials.ManagementGroupConnection.TryConnectToManagementGroupJob(Object
sender, ConsoleJobEventArgs args)
System.ServiceModel.FaultException`1[System.UnauthorizedAccessException]:
The creator of this fault did not specify a Reason. (Fault Detail is
equal to System.UnauthorizedAccessException:
You have exceeded the
evaluation period of this product. For information on purchasing the
retail version of this product, go to
http://go.microsoft.com/fwlink/?LinkID=151842.
at Microsoft.EnterpriseManagement.ServiceDataLayer.SessionManagerService.CheckLicence()
at Microsoft.EnterpriseManagement.ServiceDataLayer.SessionManagerService.Connect(SdkClientConnectionOptions
options)
at Microsoft.EnterpriseManagement.ServiceDataLayer.BasicDispatcherService.Connect(SdkClientConnectionOptions
connectionOptions)).

System.UnauthorizedAccessException: You have exceeded the evaluation period of this product
If this is an evaluation lab, then it's time to rebuild it.
If this is a production system, then you'll need to contact product support, show proof of ownership, and get their tool that will convert the management group to a licensed version.
Generally, when building a system for production, you should do it with a full product key. there is no supported method to add the license key later except through product support's special tools.

Is there any way to get an application to load automatically on server start?

We're trying to implement a load-balancing mechanism between FMS hosts in a virtual "farm". The mechanism we're using is to have the FMSs periodically send "load" data (along with a timestamp) to an application server. That server will then use that load information and timestamp to detect when an FMS server has gone down and to make stream assignments to FMSs.
Right now, I've implemented this code via a setInterval() in live/main.asc. I've added a "return false" to Application.onAppStop() to (according to the docs, I haven't tested this yet) keep the server from shutting down an idle instance. So I've left with a "chicken and egg" issue: how do I get the interval running before the first request hits the application (and forces the load of the application)? I've tried putting the setInterval in onAppStart() and as a global. In both cases, it only gets executed after application is loaded.
So, is there any way to force an application to load (via a config file parameter or local command-line)?

Hi,
I am sorry i have not read the full details what you wrote, but if you are looking for loading of application on start of the server, there is a configuration tag in application.xml called loadonstartup and by default it is set to false. Set it to true to enable it and all the apps will be loaded on server start.
alternatively , you can make an application.xml inside the application folder and set this tag to true, to have this applied only to a particular application,
Also, the fms admin console can launch a new instance of an app without any connection being made initially.
Thank you !

Using environment variable / double quotes in "Arguments" in "Server Start"

I have an admin server, NodeManager, and 1 managed server, all on the same machine (windows). I am trying to enter something similar to this to the arguments field in the Server Start tab:
-Dmy.property=%USERPROFILE%\someDir\someJar.jar
But when the managed server is started it throws this exception:
Error opening zip file or JAR manifest missing : %USERPROFILE%\someDir\someJar.jar
It appears that the environment variable is not being translated into it's value. It is just passed on to the managed server as plain-text. I tried surrounding the path with double quotes (") but the console validates the input and does not allow this: *"Arguments may not contain '"'"*
Even editing the config.xml file manually cannot work, as the admin server fails to startup after this:
<Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing failure in config.xml: java.lang
.IllegalArgumentException: Arguments may not contain '"'.>
I also tried using %20 to no avail, it is just passed as %20.
I thought that perhaps this had something to do with the spaces in the value of %USERPROFILE% (which is "C:\documents and settings.."), but the same thing happens with other env. variables which point to other directories with no spaces.
_My question:_
Is there any supported way of :
using double quotes? what if i have to reference a folder with spaces in it's name?
reference an environment variable? What if i have to rely on it's value for distributed servers where i do not know in advance the variable's value?
Edited by: 937622 on Sep 28, 2012 1:02 AM

There is workaround : http://stackoverflow.com/questions/12629395/weblogic-using-environment-variable-double-quotes-in-arguments-in-server
Just posting here for reference. Let's see if we get a different answer from anyone else.

Weblogic Admin server - Configuration/Server Start/Arguments ignored?

Hi,
I'm trying to specify a http proxy for a WebLogic Admin Server in order for an application to access external resources. I've placed the settings into the "Server Configuration / Server Start / Arguments", and verified that they have been saved into the config/config.xml file for that domain:
<server-start>
<arguments>-Dhttp.proxyHost=[XXXX] -Dhttp.proxyPort=8080</arguments>
<password-encrypted>[XXXX]</password-encrypted>
</server-start>
However, no matter how I start the server, these settings are ignored despite that the documentation states these should be added to the java command line.
starting weblogic with Java version:
java version "1.6.0_19"
Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
As a test I created a new managed server in the same domain, specifying the same startup properties, and they were picked up during startup.
If I manually place the settings into the bin/setDomainEnv.cmd batch file for the domain they are also picked up and work.
Is there an undocumented restriction on Admin Servers that they ignore the "Server Start / Arguments" setting, or is there something else I can check as to why this is not working?
Many thanks,
- Micha.

Umm... I already pasted the relevant snippet out of the config.xml, but following is the entire file. The startup arguments, as specified in the admin console, are:
-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080
which matches what is saved in the config.xml.
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>wls_starter</name>
<domain-version>10.3.2.0</domain-version>
<security-configuration>
<name>wls_starter</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>[XXXXXXXX]</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<max-http-message-size>-1</max-http-message-size>
<ssl>
<enabled>false</enabled>
</ssl>
<log>
<file-name>logs/AdminServer.log</file-name>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>true</number-of-files-limited>
<file-count>7</file-count>
<file-min-size>500</file-min-size>
<rotate-log-on-startup>true</rotate-log-on-startup>
<logger-severity>Trace</logger-severity>
<logger-severity-properties></logger-severity-properties>
<log-file-severity>Info</log-file-severity>
<stdout-severity>Info</stdout-severity>
<domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
<memory-buffer-severity>Debug</memory-buffer-severity>
<log4j-logging-enabled>false</log4j-logging-enabled>
<redirect-stdout-to-server-log-enabled>false</redirect-stdout-to-server-log-enabled>
<domain-log-broadcaster-buffer-size>1</domain-log-broadcaster-buffer-size>
</log>
<machine>[XXXXXXXXXX]</machine>
<listen-port>8080</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<web-server>
<frontend-http-port>0</frontend-http-port>
<frontend-https-port>0</frontend-https-port>
<keep-alive-enabled>true</keep-alive-enabled>
<keep-alive-secs>30</keep-alive-secs>
<https-keep-alive-secs>60</https-keep-alive-secs>
<post-timeout-secs>30</post-timeout-secs>
<max-post-size>-1</max-post-size>
<send-server-header-enabled>false</send-server-header-enabled>
<wap-enabled>false</wap-enabled>
<accept-context-path-in-get-real-path>false</accept-context-path-in-get-real-path>
</web-server>
<listen-address></listen-address>
<java-compiler>javac</java-compiler>
<tunneling-enabled>false</tunneling-enabled>
<tunneling-client-ping-secs>45</tunneling-client-ping-secs>
<tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
<server-start>
<arguments>-Dhttp.proxyHost=[XXXXXXXX] -Dhttp.proxyPort=8080</arguments>
<password-encrypted>[XXXXXXX]</password-encrypted>
</server-start>
<server-life-cycle-timeout-val>30</server-life-cycle-timeout-val>
<startup-timeout>0</startup-timeout>
<graceful-shutdown-timeout>30</graceful-shutdown-timeout>
<ignore-sessions-during-shutdown>false</ignore-sessions-during-shutdown>
<client-cert-proxy-enabled>false</client-cert-proxy-enabled>
</server>
<embedded-ldap>
<name>wls_starter</name>
<credential-encrypted>[XXXXXXXXXX]</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.2.0</configuration-version>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>[XXXXXXXXXX]</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<machine>
<name>[XXXXXXXXXX]</name>
</machine>
<jms-server>
<name>WseeJmsServer</name>
<target>AdminServer</target>
<persistent-store>WseeFileStore</persistent-store>
</jms-server>
<jms-server>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<persistent-store>WseeFileStore</persistent-store>
</jms-server>
<self-tuning>
<work-manager>
<name>weblogic.wsee.mdb.DispatchPolicy</name>
<target>AdminServer</target>
</work-manager>
</self-tuning>
<file-store>
<name>WseeFileStore</name>
<directory>WseeFileStore</directory>
<target>AdminServer</target>
</file-store>
<jms-system-resource>
<name>WseeJmsModule</name>
<target>AdminServer</target>
<sub-deployment>
<name>BEA_JMS_MODULE_SUBDEPLOYMENT_WSEEJMSServer</name>
<target>WseeJmsServer</target>
</sub-deployment>
<descriptor-file-name>jms/wseejmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<jms-system-resource>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<sub-deployment>
<name>[XXXXXXXXXX]</name>
<target>[XXXXXXXXXX]</target>
</sub-deployment>
<descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>[XXXXXXXXXX]</name>
<target>AdminServer</target>
<descriptor-file-name>[XXXXXXXXXX]</descriptor-file-name>
</jdbc-system-resource>
<saf-agent>
<name>ReliableWseeSAFAgent</name>
<target>AdminServer</target>
<store>WseeFileStore</store>
</saf-agent>
</domain>

Managed servers are started/stopped from admin console using NodeManager

Hi,
I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
I have node manager setup on the two machines. I use admin console to start/stop managed servers.
Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
Your inputs are highly appreciated.
Thanks in advance.
BR,
Ajmal

Hi Ajmal,
For your issue there are two solution's as shown below:
Solution-1
You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
Console Path:
Servers > Configuration > Server Start
However this has to be done with all the managed serves.
Solution-2
If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
This way whenever you start any of you managed servers from console it would pick up that lib files.
In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
Hope this would help you.
Regards,
Ravish Mody

Server started in RUNNING mode not showing in Startup Log File when MS Starts

Dear all,
When we start OSB Managed Server, server status is showing Running Status in Web logic console and it is also serving the requests. but in server Start up log file, it is not showing 'Server started in RUNNING mode' after it started.
this behavior is only for 4 managed servers in cluster of 6 managed servers. other 2 managed servers are starting and showing the message correctly.
please some body show some light on it as we need to fix this issue urgently.
thanks in advance.
pr

Dear all,
When we start OSB Managed Server, server status is showing Running Status in Web logic console and it is also serving the requests. but in server Start up log file, it is not showing 'Server started in RUNNING mode' after it started.
this behavior is only for 4 managed servers in cluster of 6 managed servers. other 2 managed servers are starting and showing the message correctly.
please some body show some light on it as we need to fix this issue urgently.
thanks in advance.
pr

WEBINF/classes folder contents packed in _wls_cls_gen!.jar on server start

Hi,
I'm having an issue with respect to deploying my project application in weblogic application server 9.2.
I'm creating a war file in which I'm packaging all application contents which includes the /WEBINF/classes contents.
I deployed the war in admin console, associated it with a managed server. When I started the managed server. I could see that all /WEBINF/classes contents have got packaged in wlscls_gen!.jar automatically. Because of this, Im getting ClassNotFoundException for all java classes which were supposed to be in /WEBINF/classes directory.
Is there any workaround to knock off this dynamic jar and retaining the /WEBINF/classes folder contents even after server start.
Any help would be appreciated
Thanks

Hi,
The creation of wlscls_gen.jar file can not be avoided. This is a problem with WebLogic. The only way to avoid it is by creating JAR files on your own and then keeping them inside "WEB-INF/lib" directory.
*Topic: wlscls_gen.jar Issue*
http://middlewaremagic.com/weblogic/?p=408
There is no WAY to tell WebLogic to Not to create this Problematic JAR.
Thanks
Ravish Mody

Server start arguments ignored when starting managed server

Hi
We have configured a bunch of arguments for the managed server through the Admin Console in the Server->Start Arguments
However those arguments are not picked up when we are starting the managed server.
We are using a shell script to start the managed server using the weblogic.Admin class functionality.
If the arguments are set in the JAVA_OPTIONS of setDomainEnv.sh, then they are picked up when starting the managed server.
The nodemanager is configured with startScriptEnabled=true and startscript set to startWeblogic.sh.
This is the scenario in Weblogic 10.0.0.
Can anybody please explain why the arguments are not picked up?
We tried the same arguments in Weblogic 10.2 and the arguments are picked up even if they are not configured in setDomainEnv.sh
Is the difference in behavior because of the difference in versions?
Edited by: user1030647 on Aug 29, 2010 12:26 AM

Thanks Jay for the immediate responses.
The thing I am worried about is it seems the behavior in Weblogic 10.0.2 seems to be in consistent with the behavior in Weblogic 10.0.0.
In Weblogic 10.0.2, even if the JAVA_OPTIONS in setDomainEnv.sh do not include the paramaters that are set in "Server Start->Arguments", when starting the managed servers, they are picked up as can be seen from the managed server log files.
However, in Weblogic 10.0.0, it seems that these options are not picked up when they are configured in "Server Start->Arguments". Only when they are configured in setDomainEnv.sh are they picked up.
Do you have any info which points to this discrepancy?

Server starting: jython/WLST vs console

Similar Messages

Maybe you are looking for