Debugging Node Manager

Where does the node manager keep its log files? I am trying to start a managed server
on a remote machine - but it fails. I cannot find anything in any of the log files
that helps me work out what the problem is. (I have it running as a service - I guess
I could run it from the console - but this wont help me in a production environment)
Are there different log levels with the Node Manager (or, better still, some way
to turn debugging/verbose on)?
(I have looked in D:\bea\weblogic700\common\nodemanager\* for the log files - there
are log files but nothing useful in them (no error messages - nothing))
Cheers,
Nick

Yes.
Try "java weblogic.nodemanager.NodeManager help"
This will print nodemanager's help usage.
I understand that you want to run NM as an NT service.
But are you able to start managed servers from admin console?
This may help to troubleshoot the problem.
Kumar
Nick Minutello wrote:
Cheers. Thanks.
Are all the debug options for Weblogic documented somewhere?
-Nick
prasen <[email protected]> wrote:
Most common problem in NodeMgr is SSLHandShake failure. Here is a list
of command which
I use:
-Dweblogic.nodemanager.debugLevel=90
-Dssl.debug=true
-Dweblogic.StdoutDebugEnabled=true
-Dweblogic.nodemanager.javaHome=c:\jdk1.3.1_02
-Dweblogic.security.SSL.trustedCAKeyStore=C:\weblogicdev\src_131sj\server\lib\cacerts
Nick Minutello wrote:
Where does the node manager keep its log files? I am trying to start amanaged server
on a remote machine - but it fails. I cannot find anything in any of thelog files
that helps me work out what the problem is. (I have it running as a service- I guess
I could run it from the console - but this wont help me in a productionenvironment)
Are there different log levels with the Node Manager (or, better still,some way
to turn debugging/verbose on)?
(I have looked in D:\bea\weblogic700\common\nodemanager\* for the logfiles - there
are log files but nothing useful in them (no error messages - nothing))
Cheers,
Nick

Similar Messages

  • Enable Node Manager debug using WLST

    Hi,
    I would like to enable debug for node manager using WLST instead of using the Admin console - by selecting the check box for "Debug Enabled" property under Environment > Machine > Configuration > Node Manager in the Admin console.
    I could locate the MBean name to 'NodeManagerMBean' and the property to 'DebugEnabled', but I'm not sure how to script it.
    Can anybody please guide me?
    Thanks in advance
    Edited by: vikascv on Apr 29, 2009 9:23 AM

    Here you go
    Enable Node Manager debug using WLST
    <a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free at Togotutor)
    def connection_to_Admin():
    try:
    connect(username, password, URL)
    except wlst.WLSTException, ex:
    print "Caught exception while connecting: %s" % ex
    else:
    print "------- Connected successfully! ---------"
    connection_to_Admin() #Calling the connect Function
    edit()
    startEdit()
    cd('/Machines/MS1/NodeManager/Machine_1')
    cmo.setDebugEnabled(true)
    activate()
    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><</td>

  • How to configure Node manager on Linux on ssl port

    Hi,
    I have installed SOA BPM 11.1.1.3 on linux with ssl enabled. I am trying to configure Node Manager but it's not working.
    Here are the steps I did to configure.
    1. Created a machine
    2. Added managed servers to the machine i.e. soa,bam
    3. Enroll domain using nmEnroll using
    cd $BEA_HOME/user_projects/domains/<domain_name>/bin/
    . setDomainEnv.sh
    java weblogic.WLST
    wls> connect(’weblogic’,'weblogic1’, ‘t3://mymachine.mydomain:7001’)
    wls> nmEnroll(’$BEA_HOME/user_projects/domains/<domain_name>’, ‘$BEA_HOME/wlserver_<version>/common/nodemanager’)
    here 7001 is the admin server non-ssl port but when I try 7002 ssl port it doesn't connect. But I need to enroll it on ssl port as I have ssl enabled.
    4. reset the node manager user/password same as weblogic console
    5. started the node manager using $WL_HOME\server\bin\startNodeManager.sh
    But when I log back into console and try to start my manage server it gives the following error
    SEVERE: java.io.FileNotFoundException: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/./config/jps-config.xml (No such file or directory)
    <Aug 6, 2010 5:30:16 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.I did not add my Admin server to be part of the machine.
    Any help if I am missing anything or doing anything wrong.
    Thanks

    Hi,
    Do I need to add Admin Server also part of the Machine where I added bam,soa servers. I tried again following the steps but gets the below error again. Appreciate if someone can list the steps as the docs are a bit vague:
    <Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh >
    Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
    INFO: Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh
    <Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Working directory is '/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain'>
    Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
    '/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/servers/bam_server1/logs/bam_server1.out'
    <Aug 6, 2010 6:14:02 PM> <INFO> <wcbpm_domain> <bam_server1> <Server failed during startup so will not be restarted>
    Aug 6, 2010 6:14:02 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Aug 6, 2010 6:14:02 PM> <WARNING> <Exception while starting server 'bam_server1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
            at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
            at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
            at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
            at weblogic.nodemanager.server.Handler.run(Handler.java:70)
            at java.lang.Thread.run(Thread.java:619)
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    Unknown option or illegal argument: -XX:+UseParallelGC.
    Please check for incorrect spelling or review documentation of startup options.
    Could not create the Java virtual machine.
    <Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <Waiting for the process to die: 590>
    <Aug 6, 2010 6:14:02 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>Don't know if I hve missed any steps in node manager configuration.
    Thanks

  • WLS 10.3: Node Manager  error while starting managed server

    Hi,
    I get the following error when trying to start a managed server using Node Manager from the Admin console on WLS 10.3
    Error:
    <27/11/2009 3:21:34 PM> <Info> <NodeManager> <Server output log file is "/opt/osb/osb_env/domains/DevVVDomain/servers/dev_osb_server1/logs/dev_osb_server1.out">
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: grep: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: uname: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: : grepuname: : not foundnot found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: uname/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: : not foundgrep
    : not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: grep: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: uname: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: expr: not found
    /opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: test: argument expected
    <27/11/2009 3:21:35 PM> <Debug> <NodeManager> <Waiting for the process to die: null>
    <27/11/2009 3:21:35 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
    <27/11/2009 3:21:35 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>My nodemanager.properties file looks like this:
    DomainsFile=/opt/osb/osb1031/wlserver_10.3/common/nodemanager/nodemanager.domains
    LogLimit=0
    PropertiesVersion=10.3
    javaHome=/opt/osb/osb1031/jrockitR27.6.5-32
    AuthenticationEnabled=true
    NodeManagerHome=/opt/osb/osb1031/wlserver_10.3/common/nodemanager
    JavaHome=/opt/osb/osb1031/jrockitR27.6.5-32/jre
    LogLevel=INFO
    DomainsFileEnabled=true
    StartScriptName=startWebLogic.sh
    ListenAddress=mcsdev3
    NativeVersionEnabled=false
    ListenPort=5556
    LogToStderr=true
    SecureListener=false
    LogCount=1
    StopScriptEnabled=true
    QuitEnabled=false
    LogAppend=true
    StateCheckInterval=500
    CrashRecoveryEnabled=false
    StartScriptEnabled=true
    LogFile=/opt/osb/osb1031/wlserver_10.3/common/nodemanager/nodemanager.log
    LogFormatter=weblogic.nodemanager.server.LogFormatter
    ListenBacklog=50
    StopScriptName=stopWeblogic.shPlease let me know what additional configuration is required to get the server started properly
    Regards
    Vikas

    Found a workaround:
    Manually, add PATH (and probably the other environment variables also) to
    ${WLS_HOME}/common/bin/commEnv.sh.

  • 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

  • Where do I find the "Node Manager" service?

    Can anyone tell me where to find the "Node Manager Service" In Call Manager 5.1.2 or IPCC 4.5?
    My db_CRA database in IPCC is not updating the real time ICD statistics table and Bug CSCsc09160 seems to indicate that stopping and starting the "Node Managers" may fix the issue.
    From the bug report:
    Symptom:
    Under the db_cra two tables (RtCSQsSummary and RtICDStatistics) are not updating. They stop updating concurrently with engine failovers and reboots. Only a hard reboot or a
    service failover brings them back into an active state.
    When the RtCSQsSummary and RtICDStatistics tables do update on the
    primary DB they do not update on the secondary DB and the data on them
    doesnt get refreshed.
    Conditions:
    stopping Node manager on node 1, data fails to be written to node 2. Then when we start NM back up on node 1 data is still not written to either data store
    Workaround:
    Not much as a workaround, because the solution requirs stop on both Node
    Managers and bring up node 1 first and the data starts writing to DB
    again.
    Thanks,
    Brian

    Post Author: jsanzone
    CA Forum: Authentication
    Sven,
    The reference to Session Manager is more of a concept of operations versus an entity.  The portion of code that you copied and pasted in your post is actually part of the verbiage used in an ASP script that BusinessObjects expects you to create in order for you to obtain your objective.  You can use this coding to create your own customized script or you might be able to search around on the web for a more complete solution.

  • Multiple Node Manager Instances and servers sharing the same domain home.

    Hi,
    We have a 8 man server weblogic cluster spread over 4 machines. Each machine runs 2 man servers each.
    Each of the machine is configured to run node manager.
    We use shared storage accessible to all 8 servers and all 8 man servers have the same domain_home.
    Lets call it W:/domain
    Now the problem we are facing is that node manager running on 1 machine is trying to access/control a managed server on a different machine after a machine restart.
    eg.
    ManServer1 Home : W:/domain/servers/server1 ====> runs on Machine 1
    ManServer2Home : W:/domain/servers/server2 ====> runs on Machine 2
    Problem is node manager on machine 1 is trying to restart man server 2. The path W:/domain/servers/server2 is accessible to Machine 1.
    After a restart, what I assume is happening is that the nodemanager is checking all servers folder under Domain_Home/Servers and trying to restart servers instead of restarting only those which it should start. The config file has the server and machine assignment done correctly. Is there a way to make this configuration towork. Or do we need to create different domain_home's for different man servers like
    Domain_Home for MS1: W:/domain/MS1 ( Server Home would be : W:/domain/MS1/servers/MS1)
    Domain_Home for MS2: W:/domain/MS2 ( Server Home would be : W:/domain/MS2/servers/MS2)
    Regards,
    Atheek
    Edited by: atheek1 on 03-May-2010 00:27

    Thanks - We have tried putting 2 dad entries in file, but not sure how you connect. You only specify a port number, so how does it connect that to a db???

  • Accessing an EJB 3.0 Enterprise Bean and Node Manager

    Hi to all
    I have got a problem in using Local(Remote) EJB Interface in Weblogic. I use Node Manager.
    I have two servers:
    1. AdminServer (working on port 7001)
    2. Server1 (working on port 7003 under node manager control)
    I have one EAR application file. This file contains jars with ejb 3.0. One jar called jarnumber1.jar is deployed on AdminServer. Second jar called jarnumber2.jar id deployed on Server1.
    jarnumber1.jar constains EJBBean1 class.
    jarnumber2.jar constains EJBBean2 class.
    I want call EJBBean2 from EJBBean1 but I can't. I got exception 'NamingException'.
    Example source code:
    @Stateless(mappedName = "EJBBean1")
    public class EJBBean1implements EJBBean1Remote {
    @EJB private EJBBean2Remote eJBBean2Remote ; //injection doesn't work
    I also tried method described here: http://middlewaremagic.com/weblogic/?p=5665 but it doesn't work.
    AminServer has own JNDI Tree and Server1 has own JNDI Tree. It's seems to be that EJBBean1 can't see EJBBean2 from second JDNI tree.
    Pleas help me.
    With Regards,
    ZK

    Please try the following code:
    HelloEJBBean.java:
    @Stateless(name="Hello")
    @Remote(value={Hello.class})
    public class HelloEJBBean implements Hello {  ... }
    hello.jsp:
    Context ctx = new InitialContext();
    Hello h = (Hello)ctx.lookup("ejb/Hello");
    web.xml:
    <ejb-ref>
    <ejb-ref-name>ejb/Hello</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <remote>fi.kronodoc.test.model.Hello</remote>
    </ejb-ref>
    i think you should also define jndi mappings for the references in orion-ejb-jar.xml and orion-web.xml but for some reason it seems to be working also without these.

  • After I do Node Manager nmConnect(...) I can no longer start a managed svr

    I am running 10.3.2 on both windown and redhat
    I have a domain with AdminServer and one managed server.
    I can start AdminServer from the shell with startWebLogic.cmd
    I can log into the web based 'console'
    I can go to Environment -> Servers and start/shutdown the managed server.
    If I use WLST and...
    connect('user', 'pass', 't3://localhost:7001')
    nmEnroll('fullPathToDomainDir')
    I am still OK, I can still use the console to start and stop the managed server and I can so WLST start('managedSever')
    I stop running the AdminServer from the shell - it is no longer running.
    Now, I want to start the AdminServer with Node Manager, so (with WLST)...
    nmConnect('user','pass','localhost','5556','domainName)
    I get the error...
    'Cannot connect to Node Manager: Access to domain 'domainname' for user 'user' denied
    As suggested elsewhere, I go and edit nm_password.properties and change the hashed user/pass to
    username=user
    password=pass
    I go back to WLST, now nmConnect works!!!
    I can then do..
    nmStart('AdminServer')
    The AdminServer start, I go to the web console, and I try to start the managed server, I get...
    'For server managedServer, the Node Manager associated with machine machineName is not reachable'
    So it looks like the re-hashed password from nmConnect(...), while it works for WLST, it no longer works for the console.
    Bottom line, I can get either get the console to start the managed server (if I do WLST connect(...) + nmEnroll(...)) or I can get WLST to start the servers (if I reset nm_password.properties and do nmConnect), but I can not get WLST to start the AdminServer and have the AdminSever console start the managed server.
    I know for a fact that others have run into this, but in the threads I found, the thread stops before a soluton is posted.
    Anyone know about this issue?
    Regards

    There are a couple of things you need to keep in mind:
    -- There is one and only one valid username / passwrod for connecting to the node manager.
    -- When you use nmEnroll, the username / password placed in the nm_password.properties file is taken from the admin server, hashed an placed in the nm_password file.
    -- When you edit the nm_password.properties, and place the line "enter in username=user / password='pass',", in clear text, you have over ridden the U/P \thje admin server knows.
    That is why you have a situation, oen of the two works but never both at the same time.
    What you need to do is:
    -- Log in to the WL Console.
    -- in the Domain Tree, click at teh root level, which is the domain name.
    -- Under the security tab, under advanced there is a node manager username / password.
    -- Click on "Lock and edit", and change those to match what you are using through WLST.
    -- Activate changes.
    -- Just to make sure all is well, use nmEnroll to re enroll the node manager again , this way the nm_password.properties file will be set up correctly.
    Now, both the WL Console should be able to talk to the node manager as well as nmConnect('user','pass','localhost','5556','domainName) would succeed.
    Also, if you want to use node manager to start /servers, make sure you edit the file ( $WL_HOME/common/nodemanager/nodemanager.properties) and change the line
    StartScriptEnabled=false
    to
    StartScriptEnabled=true
    This will ensure all the proper class paths and properties etc needed are set up when using the node manager.
    You would need to bounce the node manager for this change t take effect
    Hope this helps.

  • I can not start a remote server via Node Manager

     

    There is a workaround to this problem. The issue seems to be
    that when the node manager tries to start the managed server
    it can not find java.exe in the system path. So please go to
    Control Panel->System->...->Environment, and modify your PATH
    system environment variable to include the java bin directory
    in it.
    Then try using the node manager again to start the managed
    servers and you should have no problems.
    We are aware of the issue and working on having a fix for it.
    Savvas
    "Rakesh Chauhan" <[email protected]> wrote:
    >
    Hey Guys!
    I am using WLS6.1 on WIN2000 boxes. And I am getting the same error on
    the Admin
    console when I try to start any of the two
    managed servers.
    <Sep 25,2001 1:39:12 PM EDT> <Info> <[email protected]:7002><WindowsProcessControl:
    online successfully invoked on server 'server90', pid: 0> The interesting thing is that when I start managed server of its own,
    it is started
    successfully and you can Stop the managed
    server from the Admin Console.
    Really frusted, I hope I have configured everything correctly. Can somebody
    help
    me out ?
    Thanks Rakesh
    "Martin Matthews" <[email protected]> wrote:
    This message is simply a message from the Admin Server saying that it
    has asked
    NodeManager on the remote machine to start a certain server.
    To see the logs for server startup then you can find these either on
    the Admin
    machine at WL_HOME/config/NodeManagerClientLogs/<ManagedServerName>/*.log
    or on the remote machine at
    WL_HOME/config/NodeManagerLogs/<ManagedServerName>/*.log
    Cheers
    Martin
    "Paul Nixon" <[email protected]> wrote:
    I also would like to know the answer to the question below from Vincent.
    I am getting
    this message in the Admin console from either of my two managed servers
    whenever
    the console has successfully contacted the Node Manager in managed
    server
    host.
    The Node Manager logs themselves also report "online successful". What
    doesn't
    seem to happen is WebLogic startup and I haven't found any error log
    that explains
    why.
    I have set the Remote Startup parameters correctly [I think] for both
    managed
    servers so cannot see what further is required.
    Any input appreciated.
    Paul.
    "Vincent Ducret" <[email protected]> wrote:
    Hi everybody,
    When I try to start a remote WLS 6.1 server from my computer, I receive
    the message
    below in my WLS administration console. The Node manager is runningon
    the remote
    machine and correctly configured, I hope!
    What does this message mean ???
    Thanks for your help
    Vincent
    <21 août 01 10:19:17 CEST> <Info> <[email protected]:5555>
    <WindowsProcessControl:
    online successfully invoked on server 'testserver', pid: 0>

  • Configuration issue in node manager ( Oracle Weblogics 11g )

    Hello Everyone,
    We have developed an Admin server and a Managed server. Both are working fine. When we tried to implement node manager concept in it, we were partially unsuccessful to make this task completed.
    Under Environment -> Machines -> machine_name -> Under Monitoring tab
         We could see status as inactive.
    Sequence of Steps we followed:-
         - Create new Machine ( Environment -> machine )
         - added Managed Server to the Machine
         - In Managed Server, Environment variable is set. Invoked WLST. Enrolled domain_home to wls_home/common/nodemanager

    This is the scenario which i followed, kindly read it . . you will get clear idea. .
    Machine 1 - Admin Server
    Machine 2 - Managed Server
    In Admin server, Environments -> server -> Machine 2 has been added. I am able to start and stop managed services.
    Node Manager:-
    In Machine 1 ( Admin server ) - Environments -> machine -> create -> In listener address ( gave ip address of machine 2 ) -> in listerner port -> 5556.
         - Environments -> machine -> select - created machine ->configuration -> servers -> add maanged server - machine 2.
    In Machine 2 ( Managed Server ) - In WLS_HOME/server/bin -> ./setENV**.sh -> Invoke wlst -> Used connect cmd to get connect admin url in WLST -> executed enroll cmd
         - Then executed ./startnodemanager.sh script
    We assume that now under Environment -> Machine -> Machine_Name -> monitoring -> status should be reachable but for me its inactive. I found this message - weblogic.nodemanager.NMConnectException.
    =================================================================================================================
    Now below you will find node manager logs and properties file
    Log viewed when ./startnodemanager.sh is executed
    + CLASSPATH=/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/home/oracle/oracle11g/Middleware
    + '[' '!' -z '' ']'
    + '[' '!' -z '' ']'
    + export CLASSPATH
    + export PATH
    + cd /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
    + set -x
    + '[' '' '!=' '' ']'
    + '[' '' '!=' '' ']'
    + /home/oracle/oracle11g/Middleware/jdk160_29/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Dcoherence.home=/home/oracle/oracle11g/Middleware/coherence_3.7 -Dbea.home=/home/oracle/oracle11g/Middleware -Xverify:none -Xverify:none -Djava.security.policy=/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/home/oracle/oracle11g/Middleware/jdk160_29 weblogic.NodeManager -v
    <Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
    Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap
    INFO: Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
    <Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'>
    Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServer <init>
    INFO: Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'
    Node manager v10.3
    Configuration settings:
    NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
    ListenAddress=
    ListenPort=5556
    ListenBacklog=50
    SecureListener=false
    AuthenticationEnabled=true
    NativeVersionEnabled=true
    CrashRecoveryEnabled=false
    JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
    StartScriptEnabled=false
    StopScriptEnabled=false
    StartScriptName=startWebLogic.sh
    StopScriptName=
    LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
    LogLevel=INFO
    LogLimit=0
    LogCount=1
    LogAppend=true
    LogToStderr=true
    LogFormatter=weblogic.nodemanager.server.LogFormatter
    DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
    DomainsFileEnabled=true
    StateCheckInterval=500
    UseMACBroadcast=false
    DomainRegistrationEnabled=false
    DomainsDirRemoteSharingEnabled=false
    Domain name mappings:
    TestDomain -> /home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
    <Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>
    Oct 12, 2012 4:01:54 PM weblogic.nodemanager.server.Listener run
    INFO: Plain socket listener started on port 5556
    nodemanager.log
    <Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
    <Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.prop
    erties'>
    <Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>
    more nodemanager.properties
    #Sun Oct 07 06:39:50 BST 2012
    DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
    LogLimit=0
    PropertiesVersion=10.3
    DomainsDirRemoteSharingEnabled=false
    javaHome=/home/oracle/oracle11g/Middleware/jdk160_29
    AuthenticationEnabled=true
    NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
    JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
    LogLevel=INFO
    DomainsFileEnabled=true
    StartScriptName=startWebLogic.sh
    ListenAddress=
    NativeVersionEnabled=true
    ListenPort=5556
    LogToStderr=true
    SecureListener=false
    LogCount=1
    DomainRegistrationEnabled=false
    StopScriptEnabled=false
    QuitEnabled=false
    LogAppend=true
    StateCheckInterval=500
    CrashRecoveryEnabled=false
    StartScriptEnabled=false
    LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
    LogFormatter=weblogic.nodemanager.server.LogFormatter
    ListenBacklog=50
    -bash-3.2$
    more nodemanager.domains#
    #Fri Oct 12 16:00:36 BST 2012
    TestDomain=/home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
    -bash-3.2$
    All these were found in Admin Server. . . Kindly provide ur suggestions . .

  • OBIEE 11g (11.1.1.5.0) - Issue with starting Node Manager

    Hi,
    Have anyone faced an issue with starting Node Manager in OBIEE 11g (11.1.1.5.0)? OS is 64 bit Linux, WebLogic is 10.3.5. I used the software-install method and followed by running config.sh. Everything completed successfully. I updated the catalog and rpd location in the FMW control screen.
    To get it activated I bounced services and when I try to start Node Manager it gives below error --
    <Aug 30, 2011 2:02:42 PM CDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Aug 30, 2011 2:02:42 PM> <SEVERE> <Fatal error in node manager server>
    java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
    at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
    at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
    at weblogic.NodeManager.main(NodeManager.java:31)
    Aug 30, 2011 2:02:42 PM weblogic.nodemanager.server.NMServer main
    SEVERE: Fatal error in node manager server
    java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
    at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
    at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
    at weblogic.NodeManager.main(NodeManager.java:31)
    + set +x
    I see the same issue reported in ML OBIEE 11g - Node manager fails to start upon upgrade [ID 1329442.1] and WebLogic Server: Node Manager Startup is Failing with java.io.IOException: Unsupported cypher suite [ID 1329260.1] I tried to modify commEnv.sh. But it didnt help me.
    Please let me know if anyone have faced similar issue and what exactly did you do to resolve it.
    Cherrish Vaidiyan
    Edited by: Cherrish on Aug 30, 2011 3:14 PM

    Hi,
    There are Two types of Cipher suites --- Certicom Cipher Suite and SunJSSE Equivalent Cipher Suite. And with Weblogic 10.3.5, you are using Sun JSSE Cipher Suite, and by default Node Manager uses the Certicom Cipher Suite.
    In the nodemanager.properties, Add CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5, save and restart Node Manager.
    Reference Metalink Note: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager [ID 1307325.1]
    Cherrish Vaidiyan

  • Unable to initialize Node Manager on Weblogic 11g (10.3.5) Linux env..

    Hello,
    I worked earlier on Weblogic 8.1 and after a long gap I am coming back to Weblogic Server.
    And I tried to install & setup Weblogic Server 11g R1 (10.3.5). I successfully installed WL 11g on a Linux machine, configured the domain, and admin server without any problem. I created a managed server on the Console and tried to initialize the node manager to be able to start the managed server. I am getting the following error message repeatedly. And I did not select SSL connection, while setting up the environment.
    Can someone help me resolve this issue?
    <Sep 13, 2011 12:19:31 PM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.>
    javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
    at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
    at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
    at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
    at com.certicom.tls.record.ReadHandler.read(Unknown Source)
    at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
    at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
    at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
    at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
    at java.io.InputStreamReader.read(InputStreamReader.java:167)
    at java.io.BufferedReader.fill(BufferedReader.java:136)
    at java.io.BufferedReader.readLine(BufferedReader.java:299)
    at java.io.BufferedReader.readLine(BufferedReader.java:362)
    at weblogic.nodemanager.server.Handler.run(Handler.java:71)
    at java.lang.Thread.run(Thread.java:662)
    Sep 13, 2011 12:19:31 PM weblogic.nodemanager.server.Handler run

    Can you see what listen address you have given to Node Manager in console or in config.xml?
    <machine xsi:type="unix-machineType">
    <name>Servername</name>
    <node-manager>
    <name>Servername</name>
    <listen-address>localhost</listen-address>
    </node-manager>
    </machine>
    Another way to start Managed server is to use startManaged.sh script.

  • Node Manager not starting UCM Server automatically

    Hi All,
    I have configured Node Manager to start and stop UCM 11g server.
    But whenever, I am restarting the host OS - Windows server 2003 64 bit, it does not start the UCM managed server, automatically.
    I am running two managed servers on the same host OS, the first UCM manages server, starts automatically on every restart.
    The second managed UCM server, does not start. I need to then manually start the managed server. There are no errors logged, and the manual start of the managed server happens without any issues.
    As a workaround, I tried starting the managed server from Windows scheduler, but it does not start the server as well. I wrote a script like -
    Myscript.cmd
    call E:\..\user_projects\domains\prod_domain\bin\setDomainEnv.cmd
    java weblogic.WLST c:\start....\ServerStart.py
    scheduled the script (myscript.cmd) to run from the Windows Scheduler.
    Any pointers would be very helpful. Are there any known issues, if there are two managed servers, and one starts automatically, which affects the starting of the second managed server?
    I see the following error in the log file -
    <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

    Hi Avi,
    Give a cross check to your ServerStart.py
    As the error states The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist
    In your ServerStart.py you might have specified as follows
    sh start MAnagedWeblogic.sh server=PRD_UCM_Server1
    While these are the list of Server you have in your weblogic
    PRDAdminServer,
    PRD_UCM_server1,(You have Specified in your command PRD_UCM_Server1
    PRD_IBR_server1
    The Command should be as follows
    sh start ManagedWeblogic.sh server=PRD_UCM_server1
    This should help
    Regards
    Fabian

  • 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.

Maybe you are looking for

  • Won't Update Apps

    The App Store says that it won't update my apps because they were bought on a different user or because it was refunded or canceled. I am trying to update Pages, iPhoto, Garage Band, iMovie, Keynote, and Numbers so they came with my computer, which i

  • How do you eamail or text video that is too long?

    i video taped a skit my kids did at summer camp, and it is too long to email or SMS.  How can you sync it and send as attachment?

  • Weblogic server using jdbc-odbc bridge

    I want to connect to database through jdbc-odbc bridge.I am using web logic server. When i creating new jdbc connection pool a error comes that driver class is not on classpath. how i rectify this problem? how I make weblogic to recognize sun.jdbc.od

  • When typing on laptop hand hits something, screen changes,lose current page??

    When typing on my laptop keyboard, sometimes the palm of my hand will hit some keys, don't know what or where, and my page might change or I lose what I have typed. Does this have anything to do with the "hot keys" on my key board for my Toshiba comp

  • Spry conditionals Break in Safari

    I have two conditionals; spry:choose="spry:choose" spry:when ="'{@contactName}' != '' && '{@contactEmail}'!= '' " spry:when ="'... spry:when ="'... AND spry:if ="'{spec}' != '' "... They work great in Firefox and,Yes, even Internet Explorer . But in