Using node manager to make adminserver run as windows service.....

using:
Oracle weblogic server 11g
Oracle forms and Reports 11g
jdk 1.7.0
jre 7
i found these articles and they helped me start my forms and reports as serices but when i try to make my adminserver a windows service, it does not get past the step for Using the "nmStart" command to start a server.
the 2 articles:
http://docs.oracle.com/cd/E15586_01/web.1111/e13715/manage_servers.htm
http://wlsjavatips.blogspot.com/2009/09/how-to-install-node-manager-as-windows.html
This is what i get when i try to start it after it successfully connects:
http://i1281.photobucket.com/albums/a516/eortiz10/output_zps25fbf82f.png
* It connects to node manager but it does not start. It does start normally if i use "weblogicstart.cmd" but i would like the adminserver to start autmatically when server is on. can u explain/help in anyway.
Do i have to start the adminserver regularly then configure through there?

Was a resolution found for this?
We are having the same issue and investigating...
Thanks!

Similar Messages

Unable to start Manager server using Node Manager

Hi,
I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
Managed server log: -
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
[root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
Nodemanager log:
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
<Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
<Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)

You can start a managed server as follows:
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START MANAGED SERVER';
start('VideotheekWebServer','Server');
nmServerStatus('VideotheekWebServer');
print 'START CLUSTER';
start('VideotheekCluster','Cluster');
nmServerStatus('VideotheekServer1');
nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.

How to start coherence server using node manager of remote web-logic server

We want to manage our coherence servers using web-logic. Our requirement is as such we want to keep single web-logic Admin Server and add all other node-manager to the same web-logic Admin Server.
Now when we create machine on node 1 (on which Admin Server is running) and add node manager of other server it is not responding and shows status as inactive.
Status: Inactive
Problem description: weblogic.nodemanager.NMException Exception encountered while communicating with this node manager
Version: (not available)
Looking at the log files it gives below info
<Sep 10, 2011 6:31:55 AM> <WARNING> <Configuration error while reading domain directory>
weblogic.nodemanager.common.ConfigException: The domain 'BlazeVMA' at 'null' was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the domain in the nodemanager.domains file.
at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:254)
<Sep 10, 2011 7:53:58 AM> <WARNING> <I/O error while reading domain directory>
java.io.FileNotFoundException: Domain directory '/data/oracle/Middleware/user_projects/domains/BlazeVMA' not found
Even after I have added the domain name in above directory. It returns with the same error.
Please let me know if anyone has faced the same issue while running coherence server on remote system using weblogic admin console on one machine and node manager on other machine.

Thank You Rene.
This issue is resolved, but now I am facing issue while starting the coherence server on the remote node using node manager.
In the weblogic > coherence_server logs I am getting
Oracle Coherence Version 3.6.0.4 Build 19111
Grid Edition: Development mode
Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
2011-09-11 07:14:40.231/1.453 Oracle Coherence GE 3.6.0.4 <Error> (thread=Main Thread, member=n/a): Error while starting cluster: java.lang.IllegalArgumentException: The specified address "/hostname" is not a local address.
at com.tangosol.net.InetAddressHelper.getLocalMTU(InetAddressHelper.java:139)
Please let me know if anyone has faced the same issue and know resolution.

Using Media Manager to 'Make Offline' it re-names media files to 'Private'

For some reason Media Manager is changing the name of media files when processing them making it impossible to reconnect them.
My director always has a complete copy of our film's media files on his 'home set-up' (FCP 5.0 on a Powerbook with 2 x 500gb firewire drives) so he can look at our cuts at home. This has caused problems in the past with firewire drives expiring or failing to mount: making the whole process pointless. Also, as the amount of footage increased, he struggled to find space for the 6-8 drives required.
My solution was to down-convert our DV resolution media files to Photo-Jpeg resolution which allowed me to fit 3TB of footage onto 2 brand new G-Tech drives. Every time I sent him a cut to view all I had to do was use media manager to make the sequence offline and convert it to exactly the same Photo-Jpeg setting I used to export the files. All he has to do is reconnect the sequence to his drives at his end.
A wonderful plan except when you came to reconnecting. I found that 95% of clips connect perfectly and then you get asked for the location of some media files called 'Trashes' 'Applications' or more commonly, 'Private'. Obviously no such files existed - I use an impeccably organised and structured filename system when capturing. Therefore it made random clips in my sequence impossible to reconnect once it had been converted to the settings used by the director.
When this only happened once or twice I thought I could easily just work out what files it was actually looking for by the clip names on the timeline and tell FCP to reconnect to the correct file by ignoring the file name but this is so time consuming and impractical when you have 20/30 clips that have been renamed on a sequence. It is also not the sort of thing my director is technically capable/willing to do.
It also seems to be happening when you convert things in the other direction. When I took a sequence from the director's project and brought it back onto my system by converting his sequence to my DV-PAL settings we got the same problems with 'Private and 'Applications' clips. And we know for sure that all of these clips were online on his computer.
Has anyone seen this before or know any steps I could take to prevent it happening.
I fear that if I can't get this method to work I will have to give him full resolution media to work with and I will be fated to spend the rest of my days replacing. smashing or swearing at firewire drives that only work when they feel like it.
Anybody got any ideas.
Cheers
Paul
Powerbook G4 Mac OS X (10.4.8)

haven't tried this but it may be worth some investigation.
try exporting an XML of your sequence and passing that to the director
on the director's FCP setup, import the xml, and in the Import XML... window uncheck the "Override with setting from XML" checkbox, and choose the approriate offline res that matches the directors media.
see if the resulting sequence will reconnect

Starting managed server using node manager

When i try to start the managed server using node manager i get the following error
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Abort - core dumped
<Sep 21, 2010 3:58:07 PM> <FINEST> <NodeManager> <Waiting for the process to die: 22708>
<Sep 21, 2010 3:58:07 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Sep 21, 2010 3:58:07 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
The managed server lok file is deleted, port is not in use. With similar node manager settings the managed server on the redundant server starts fine

Hi,
I am getting same issue. Not able to start the soa_server1. Can you pleae tell me the soulution if you able to reslove the issue.
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\Oracle\MIDDLE~1\JROCKI~1.0-6\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=soa_server1 -Djava.security.policy=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle\Middleware\user_projects\domains\domain2\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2 -Dcommon.components.home=D:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1 -Doracle.server.config.dir=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\servers\soa_server1 -Doracle.security.jps.config=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\carml -Digf.arisidstack.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=D:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Djava.protocol.handler.pkgs="oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol" -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=D:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.102:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_oepe1033\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_ocp353\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<Oct 4, 2010 6:25:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 700>
<Oct 4, 2010 6:25:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Oct 4, 2010 6:25:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

Starting Manage Server using node manager

Hi,
Hi,
I am using Weblogic server 11g and I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
plz help me out in this
Thanks in advance

An example to start managed servers on different machine is provided here: http://middlewaremagic.com/weblogic/?p=6637
"By default, WebLogic is installed and configured with the DemoIdentity.jks keystore. This certificate and key are created by utils.CertGen with the default options of containing only the host name in the common name field (cn), and not the fully-qualified DNS name. As a result, attempts to establish SSL connections may fail in some situations due to a host name verification exception. When using the demo certificates in a multi-server domain, managed server instances will fail to boot if they cannot establish an SSL connection with the Admin Server and the a BAD_CERTIFICATE error is generated. This error occurs because the host name verifier, which is enabled by default in all WebLogic domains and which is used during the SSL handshake, compares the value of the cn field in the certificate with the fully-qualified DNS name of the SSL server that accepts the SSL connection. If these names do not match, the SSL connection is dropped."

Path problem when use node manager to start Managed Server

Hi, I have met a problem:
My managed server's root directory is /usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is /usr/local/bea/cluster1/weblogic700/common/nodemanager
I have some config file located under managed server's root directory and log
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server, I found
weblogic can not find the config file if I don't move the config file from Managed
server's root directory to node manager server's default directory. and also log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to node manager's
default directory.
What shall I do if I want Managed Server's default directory to be kept?

Hi Lumin,
If the weblogic version is 8.1, there is a RootDirectory field in Remote
Start tab which should resolve your problem. Just enter the absolute
directory pathname on the machine where you are starting your managed server
and the current working directory of the managed server will be this
RootDirectory. Before 8.1, the RootDirectory was used for finding the config
file for weblogic but it was never used to change the working directory of
the managed server created by the node manager.
cheers,
gaurav.
"lumin" <[email protected]> wrote in message
news:3eb7a4ae$[email protected]..
>
Hi, I have met a problem:
My managed server's root directory is/usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is/usr/local/bea/cluster1/weblogic700/common/nodemanager
>
I have some config file located under managed server's root directory andlog
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server,I found
weblogic can not find the config file if I don't move the config file fromManaged
server's root directory to node manager server's default directory. andalso log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to nodemanager's
default directory.
What shall I do if I want Managed Server's default directory to be kept?

Passing arguments to Managed Server ServerStart when using Node Manager

Below is the procedure to pass arguments to Managed Server serverstart tab when using Node Manager to start and stop the Managed Server instance
For passing the JVM arguments we will have to use "-server" which is hotspot and then pass the arguments
for eg: "-server -Xms2048m -Xmx2048m -verbosegc"
For adding jar's to the classpath you will have to add weblogic.jar and weblogic_sp.jar from WL_HOME/server/lib directory as well along with the custom jar (In some cases we can ignore weblogic_sp.jar, just adding weblogic.jar will do).
for eg: "\home\user\debug.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic.jar;\home\user\bea\wlserver_10.3\server\lib\weblogic_sp.jar;"
- - Tarun

Hi,
To me, if you don't wanna use the NodeManager, you won't be able to start your managed servers with WLST.
I guess the only ways are :
* through the console / WLST using the NodeManager
* using the startManagedWebLogic.[cmd/sh]
Regards

TNS-12560 error when running as Windows Service

Hello,
I created a VB.NET application that connects to a Oracle database using DbProviderFactory and ODP.NET for .Net Framework 2.0. This application runs on XP, I need it to run as Windows Service, but every time it try to connect to the database throw the Oracle exception TNS-12560: TNS:protocol adapter error, the weird thing is the same application running as a Console Application it works (Same code, same connection string, same query). It was using ODP.NET 10 I updated the provider to 11 still got the same error. The service is running user Local System account, and it has the same problem running under other adm account.
Following is error in the sqlnet.log (PS: The file was under the system32 folder, probably because was running as a service):
Fatal NI connect error 12560, connecting to:
+(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=XX.XX.XX.XX)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XXX)(CID=(PROGRAM=C:\Program Files\MyApp\MyApp.exe)(HOST=MYCOMPUTER)(USER=MYUSER))))+
VERSION INFORMATION:
+ TNS for 32-bit Windows: Version 10.2.0.1.0 - Production+
+ Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 10.2.0.1.0 - Production+
Time: 28-AUG-2009 02:20:19
Tracing not turned on.
Tns error struct:
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 530
TNS-00530: Protocol adapter error
nt secondary err code: 56
nt OS err code: 0
Does anyone have any thoughts as to why I'm getting this error ??
Thanks

I don't know :^(
There could be many reasons: differences in the environment, missing permissions, virus scanners, you name it.
Is it running under the same user as on the console?
I suspect that the error code will give a hint where the problem is, but I could not find any documentation what this code means.
You could try to run an Orace Net trace - maybe you get an idea if you see where in the connection process the problem occurs.
Yours,
Laurenz Albe

Problem starting Admin Server using Node Manager

I have configured the Node Manager to run as a windows service. I want it to start the Admin Server when it is started. This is not working. The Node Manager starts without problem but does not appear to even attempt to start the Admin Server. No error message is written to the nodemanager.log. I have configured the following properties as described in the documentation:
StartScriptEnabled=true
StartScriptName=startWebLogic.cmd
Starting the Admin Server using wlst works. As does starting and stopping a Managed server using the Admin console. This leads me to conclude that the Node Manager configuration is ok.
WLS version is 9.2.
All suggestions as to what could be the issue here would be greatly appreciated.
Cheers!

Ok, I just wasted a whole day before I found the tricks.
First, you don't need to do that StartScriptEnabled stuff, unless you have important things to add there.
Ok, and now what I found:
- You must make sure you have installed the NodeManager as a service
- Next, make sure the admin server is assigned to the right machine. Since you can do the WLST trick, that should be fine. If not, tough luck, because the docs say you cannot re-assign an admin server.
- In nodemanager.properties (...\weblogic92\common\nodemanager) make sure CrashRecoveryEnabled is set to true
- In nodemanager.domains (same dir) make sure your domain is mentioned with its path
- For each of the servers to be auto-started, make sure that a startup.properties (in <your-domain-dir> \servers\<server-name> \data\nodemanager) contains Arguments=-Xnohup (for JRockit, for Sun JDK its -Xrs)
Make sure they are started through the nodemanager, et voila, they'll be restarted after a reboot.
Why this works? At reboot, the OS ask all processes to die, nicely. Those that don't, get killed forcibly. Without the -Xnohup/rs, the WebLogic servers respond to the nice request, and the nodemanager immediately tries to restart them. Unfortunately, the OS refuses to do that, and the server process is marked as failed, and won't be restarted after reboot. With the option given, the servers ignore mr nice guy, and get killed after the nodemanager has disappeared.
What can go wrong? A lot. I was playing with the nodemanager username and password, and that took some time to clean up. I probably have to redo the entire setup just to make sure I have a repeatable experience now...
Cheers,
Bert

Problem starting managed server using Node Manager/WL 7

I have just configured Node Manager for the first time to start a managed server,
following the documentation 'Managing Server Availability with Node Manager'. However
when I attempt to start the managed server from the Administration Console I always
get the following exception:
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <Starting
Server webdevDomain::apps ...>
<Jul 10, 2002 1:59:29 PM EDT> <Info> <[email protected]:5555> <BaseProcessControl:
saving process id of Weblogic Managed server 'apps', pid: 15094>
Starting WebLogic Server...
Connecting to http://198.242.140.49:17043...
<Jul 10, 2002 1:59:32 PM EDT> <Critical> <WebLogicServer> <000364> <Server failed
during initialization. Exception:weblogic.management.configuration.ConfigurationException:
Exception encountered connecting to http://198.242.140.49:17043/wl_management_internal2/Bootstrap
- with nested exception:
[java.io.StreamCorruptedException: InputStream does not contain a serialized object]
java.io.StreamCorruptedException: InputStream does not contain a serialized object
     at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:844)
     at java.io.ObjectInputStream.<init>(ObjectInputStream.java:163)
     at weblogic.management.ManagedServerAdmin.bootstrapLocalServer(ManagedServerAdmin.java:212)
     at weblogic.management.ManagedServerAdmin.initialize(ManagedServerAdmin.java:122)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:665)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
     at weblogic.Server.main(Server.java:31)
But I am able to start the managed server using the startApps.sh script with no problems.
I am running WL 7 on Solaris 2.8. All processes are running on the same host.
Any help is appreciated!
John

Re-installing WL Server 7.0.0.1 resolved this problem.
- John

Managed server CLASSPATH using Node Manager

Hi All,
I ve' created a clustered (WLS 10.3) environment with tow managed servers and Admin Server all in one machine and I use the Node Manager to start the managed Servers (by Admin Console or WLST), I want to set some jars to be loaded before WEBLOGIC_CLASSPATH actually (apache XMLbeans and SAXON jars) . I tried the setDomainEnv.cmd and placed my jars in the PRE_CLASSPATH variable but It is not working.Could u help me in this please?.
Thnx in advance

Here is the WLST online script to do what David Told, please make necessary changes to it.
connect(userName, passWord, URL)
clustHM = HashMap()
edit()
startEdit()
cd("/Servers/"+ManagedServer1+"/ServerStart/"+ManagedServer1)
print "setting attributes for mbean type ServerStart"
set("RootDirectory", domainDir)
set("Arguments","-jrockit -Xms256m -Xmx256m -Xss256k -da -Dplatform.home=/usr/local/bea10/weblogic10 -Dwls.home=/usr/local/bea10/weblogic10/server -Dweblogic.home=/usr/local/bea10/weblogic10/server -Dweblogic.management.discover=false -Dweblogic.management.server="+URL+" -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/usr/local/bea10/patch_wlw1001/profiles/default/sysext_manifest_classpath:/usr/local/bea10/patch_wls1001/profiles/default/sysext_manifest_classpath -Dweblogic.Stdout=/var/Domain_Logs/Public_Domain/serverlogs/stdout_ms1.log -Dweblogic.Stderr=/var/Domain_Logs/Public_Domain/serverlogs/stderr_ms1.log -Dlog4j.configuration=/usr/local/appstage/Publicdm/cluster_1/config/log4j/log4j.properties -Dconfig.location=classpath -Dconfig.filename=dev.config.xml -DweblogicName="+ManagedServer1+" -Djava.security.policy=/usr/local/bea10/weblogic10/server/lib/weblogic.policy")
set("SecurityPolicyFile", Security_Policy)
set("JavaHome", JAVA_HOME)
set("BeaHome", BEA_HOME)
set("ClassPath",CLASSPATH)
set("Username", userName)
set("Password", passWord)
Thanks
Togotutor
<b><a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free)</b>

Native IO Disabled when using node manager to start managed server

Hi,
I am able to start my node manager and the managed server from the Admin Console. OS is AIX, WebLogic 9.2 MP3. The managed server starts OK, but Native IO is disabled even though it is enabled in the Admin Console for that manager server:
####<Jul 28, 2009 8:25:00 AM CDT> <Info> <Socket> <pstps09.statefarm.com> <PIA2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1248787500274> <BEA-000447> <Native IO Disabled. Using Java IO.>
I set NativeVersionEnabled to False in nodemanager.properties as specified in the BEA documentation, but can get Native IO to work. The log file clearly indicates that the JDK version is 32-bit:
java.fullversion = J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20071007 (JIT enabled)
Any ideas how to fix this or is this working as designed for AIX platforms?
Thanks!
-Mary Manchukian

The following document asks to set NativeVersionEnabled to False:
http://edocs.bea.com/wls/docs61/adminguide/remotestart.html#1043956:
The Node Manager is available for use only on Windows and UNIX platforms. Native libraries are available for running the Node Manager on Windows, Solaris, HP-UX, AIX and Red Hat Linux operating systems. For UNIX operating systems other than Solaris and HP UX, you will need to use the following argument on the java command line when starting the Node Manager:
-Dweblogic.nodemanager.nativeVersionEnabled=false
If we do not set NativeVersionEnabled to False, the managed server doesn't start at all and fails with the error:
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:296)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:511)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:115)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:810)
All I want is to be able to start the managed server from the Admin Console > Remote Start tab.
Thanks,
-Mary

Starting Managed Server using Node Manager Command Line

Hi,
I've configured the Node Manager and it is connected to the Admin Server without problem. Now I wanted to start the Managed Server through the console but it is failing and my guess is the command line used syntax is not correct.
My question is, how do I change the command line that Node Manager uses to start the Managed Server? I've try using the Server Start tab configuration and it seems like not working. I've also try to update the .properties file for the Managed Server as well.
Each time I look at the Managed Server logs, it is giving me this line...
NodeManager> <Starting WebLogic server with command line: <....>
The command line shown in the logs are not what I've put in the .properties file or the Server Start tab. It is taken from somewhere and I'm not sure where. I just want to configure the command line that Node Manager uses to start a Managed Server.
Hopefully, I'm clear with my problem and someone might be able to assist. Thanks.

Great stuff!!
It actually solved my problem. Thanks.
Am just wondering why it didn't work using option 1)? If anyone somehow knows the reason, if not at least it did work for me now.

Node manager not starting servers as a OS service.

Node manager is starting upon simulating OS crash but it is not bringing up the managed servers running on that machine.
The following is the nodemanager.properties file -
[orawl@qa-wl2 nodemanager]$ more nodemanager.properties
#Mon Apr 11 14:55:43 EDT 2011
#Mon Apr 11 11:57:43 EDT 2011
DomainsFile=/home/orawl/oracle/middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
DomainsDirRemoteSharingEnabled=false
javaHome=/usr/lib/jdk1.6.0_24
AuthenticationEnabled=true
NodeManagerHome=/home/orawl/oracle/middleware/wlserver_10.3/common/nodemanager
JavaHome=/usr/lib/jdk1.6.0_24/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=true
LogCount=1
DomainRegistrationEnabled=false
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
StartScriptEnabled=true
LogFile=/home/orawl/oracle/middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
#NodeManager SSL Properties
KeyStores=CustomIdentityAndCustomTrust
CustomIdentityKeyStoreType=JKS
CustomIdentityAlias=xxxxxxxxxxxx
CustomIdentityKeyStoreFileName=/home/orawl/oracle/middleware/keystores/xxxxxxxxxxxx.jks
CustomIdentityKeyStorePassPhrase={3DES}XXXXXXXXXXXXXXXXXXXXXXX
CustomIdentityPrivateKeyPassPhrase={3DES}XXXXXXXXXXXXXXXXXXXXXXX
CustomTrustKeyStoreType=JKS
CustomTrustKeyStoreFileName=/home/orawl/oracle/middleware/keystores/trustcacerts.jks
CustomTrustKeyPassPhrase=xxxxxxxxxxx
Please advice.

Hi All,
Add to my initial post , the error which is getting logged is -
<14/10/2011 6:35:22 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<14/10/2011 6:35:33 PM EST> <Info> <Management> <BEA-141223> <The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.>
<14/10/2011 6:35:33 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.
     at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
     at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
     at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
     at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
     at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
     at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
     at weblogic.Server.main(Server.java:71)
Regards,
Avi

Using node manager to make adminserver run as windows service.....

Similar Messages

Maybe you are looking for