RE: Re: Disabling console in WLS 6.1

"Well just deleting console.war from .wlstaging donot solve it. I found out console.war is copied from weblogic.jar (as it is bundled there.
Also I seems if I remove console.war from weblogic.jar and try to run the server it gives me following error:
*************************************************************************** The WebLogic Server did not start up properly. Exception raised: weblogic.common.internal.VersioningError: No WebLogic packages defined in CLASSPATH weblogic.common.internal.VersioningError: No WebLogic packages defined in CLASSPATH at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:39) at weblogic.version.<clinit>(version.java:18) at weblogic.t3.srvr.T3Srvr.checkAccess(T3Srvr.java:277) %

why do you want to disable the console ? anyways, its protected by the system user.
if you still want to do it, you could change the name of the console.war in the
config\mydomain\.wlstaging directory or edit the weblogic.xml file of the
console.war file to change the security role assignment. This can be done by
removing the principal-name elements from the weblogic.xml file which map to the
role name - admin.
cheers,
Mihir
Tarkeshwar Thakur wrote:
Hi,
I want to disable console in my installation of WLS 6.1. But it seems there
is no handle onto it. Unlike 6.0, config.xml does not have web-application entry
for console.
Any idea how to achieve this?
Thanks in advance,
Tarkeshwar

Similar Messages

  • Weblogic 4.5.1 disabling console output on server

    Is there a property file setting which will disable console output on
    the weblogic log?
    Any help would be much appreciated

    Rob Woollen wrote:
    I develop and run WebLogic on Linux with IBM's JDK 1.1.8.
    Sun and Blackdown both have Java2 that are preliminary versions. I had
    some problems with the Sun version, but the Blackdown 1.2.2 vm seems pretty
    good.
    -- Rob
    Tim Clotworthy wrote:
    Hi,
    We currently use 4.5.1 on Linux with JDK 1.1.7b. Has anyone did the same
    only with JDK2.0. I realize its not supported by weblogic on Linux, but
    would like to know whether anyone has tried it anyway and how it worked out.
    Thanks. TC
    Hi,
    I am running WL 5.1 on RedHat 6.1 with the JDK 1.2.2 RC4 from Blackdown.
    Touch wood, I haven't had major issues yet, other than really basic ones. Of
    course, things get interesting when you begin to realise the little bits and
    pieces that are supported on other platforms, but not on Linux, such as the lack
    of apache support (even though it is forthcoming in 5.1 GA from what I
    understand).
    Prashanth Nandavanam

  • Disabling Console or set it to only work on a different port.

    Is there a way to disable the console or have it only work on a different port
    in WLS 6.1?
    The only way I've figured out to disable it is to remove the whole console application
    from the system.

    Yeshwant <[email protected]> wrote in message news:<[email protected]>...
    The console is simply a webapplication and as such there is no way to have it work on
    another port. It will run on the same port the appserver is running on .
    If you don't need it just remove it .
    yeshwant
    Steven JOb wrote:
    Is there a way to disable the console or have it only work on a different port
    in WLS 6.1?
    The only way I've figured out to disable it is to remove the whole console application
    from the system.
    Just a wild guess.
    I have not try this but it looks very promising. Did you try to expand
    the console.war file and then modify the weblogic.xml to remove
    "system" from it and put in your own user, and then update the war and
    jar back. In this way, only your special user can access it.
    Regards
    drit
    Freelance Code Inspector / Java Developer
    http://www.geocities.com/doc_i_t/CodeInspectionService.html

  • Could not open console in WLS 7

    Hi, all
    I am using WLS 7 and I can start the server within JBuilder
    but when I start the server outside JBuilder , I can not open
    the console window and can not run application deployed in
    WLS 7.
    Any idea?
    Thanks in advance.

    whats the error message. Do you see any warnings, exceptions while starting up
    the application.
    A thread dump could also help in figuring if it is stuck someplace
    anand
    In article <[email protected]>, Chris Wahl wrote:
    Hi, all
    I am using WLS 7 and I can start the server within JBuilder
    but when I start the server outside JBuilder , I can not open
    the console window and can not run application deployed in
    WLS 7.
    Any idea?
    Thanks in advance.

  • Where to put "jbo.debugoutput=console" in WLS?

    Hi gang
    I'd like to turn the ADF BC debug output on via the "jbo.debugoutput=console" flag, for a standalone WebLogic Server (WLS) 10.3 ADF 11g application install.
    Section 6.3.7 of the Fusion 11g guide shows how to turn this on via JDeveloper (http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/bcqueryresults.htm#CHDBBEEB), but how do I turn it on for an application deployed to WLS? Is there a WLS console feature available for doing this?
    Cheers,
    CM.

    They normally are written into the tmp directory. You should get a message like Diagnostics: (Properties (re)loaded) Routing diagnostics to File: /tmp/bc4j61464.log in your server log file.
    The files are all names bc4jnnnn.log at some points in the application live cycle new files are generated automatically. So you have to check the log to find the actual one.
    Timo

  • Disable caching of WLS HTML/JSP

    I have JSP which performs some action and based on that either presents the HTML or forwards the request to another JSP. This works Ok first, but subsequent time if I try to go to first JSP, it goes directly to second JSP. Seems WLS is caching the HTML.
              

              cache is disabled by default.
              Refer to cache tag.
              http://e-docs.bea.com/wls/docs70/jsp/customtags.html#cache
              Rajeev Arora <[email protected]> wrote:
              >I have JSP which performs some action and based on that either presents
              >the HTML or forwards the request to another JSP. This works Ok first,
              >but subsequent time if I try to go to first JSP, it goes directly to
              >second JSP. Seems WLS is caching the HTML.
              

  • [SOLVED] Disable console framebuffer

    Edit: I discovered that I was dealing with KMS rather than framebuffering, please disregard.
    Last edited by alphaniner (2011-01-12 17:28:25)

    Ok after getting vague help at best from irc.mozilla.org I went grepping. I grepped xulrunner-1.9.0.11/chrome and firefox-3.0/chrome for all occurences of 'console.xul' and when I found one, I went into the corresponding file and commented it out. Problem solved! (In a horrible way)
    This means I can't access it even if I wanted to. But that's ok because many console extensions make the built in console obsolete. I suppose the way to do this without wasting space would be to find out how to compile xulrunner and firefox so that they come with no console. But I imagine that would be difficult.

  • WLS 7 - need separate port for console

    Hi,
    I can't find way to configure this for the life of me. Hopefully
    someone can point me to some docs and page numbers...
    I want to configure the WLS 7 server to host my web applications on
    port 80, but I want the administration console hosted on a
    different port (say 7001).
    How do I do this??

    Wayne W. Scott wrote:
    David Orriss, Jr. wrote:
    Hi,
    I can't find way to configure this for the life of me. Hopefully someone can point
    me to some docs and page numbers...
    I want to configure the WLS 7 server to host my web applications on port 80, but I
    want the administration console hosted on a different port (say 7001).
    How do I do this??
    Use the console. The default port for the admin console is 7001.
    Try going to support.bea.com and in the box next to the "Ask" button,
    enter "weblogic server 7.0 console port configuration". Several hits
    will lead to
    relevant parts of the documentation.
    http://e-docs.bea.com/wls/docs70/ConsoleHelp/servers.html#1116254
    I'll check other sources.
    Wayne Scott
    Port 80 is quite special. I was about to caution you about using it,
    but wanted to get some details first.
    /wws
    ====
    http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=3db72aac%40newsgroups.bea.com
    It complains because on Unix-es only priv user (root) can listen on ports <1000.
    You can start it as 'root' and configure WLS to change uid/gid to a non-priv
    user after binding to port 80 (using console it is in Unix Machine configuration).
    "mucucu" <[email protected]> wrote in message
    news:[email protected]...
    >
    > Our Weblogic 6.1 SP3 on HP-UX 11 works fine on port 7001.
    >
    > In the console, we changed the port to port 80 and shut it down. When we tried
    > to restart WLS, it refused to start complaining that port 80 was already used
    > by another process. This is what the log said :
    >
    > ===================================
    > ..
    > <Oct 23, 2002 1:51:31 PM EDT> <Emergency> <WebLogicServer> <Unable to create a
    > server socket for port: 80. java.net.BindException: Permission denied Perhaps
    > another process is using port 80.>
    > <Oct 23, 2002 1:51:31 PM EDT> <Emergency> <WebLogicServer> <The WebLogic Server
    > is no longer listening for connections. You should probably restart it.>
    > <Oct 23, 2002 1:51:31 PM EDT> <Alert> <WebLogicServer> <Server shutdown has been
    > requested by system>
    > <Oct 23, 2002 1:51:31 PM EDT> <Alert> <WebLogicServer> <The shutdown sequence
    > has been initiated.>
    > ..
    > ====================================
    >
    > Port 80 is not used by any process on the box where WLS is (no web server).
    >
    > First question is : How to start WLS on port 80 ?
    >
    > Second question : If it is not possible to start WLS on port 80 for whatever
    > reason, how do we go back to the default 7001 ? (We can not do it from the console
    > because WLS refuses to start in the first place. So, is there a way to manually
    > change the port in one of the properties or config file, and what file is it ?)
    >
    Dimitri

  • [Fwd: wls 7 console terribly slow ? but why]

    Forwarding your message to the console newsgroup if they have any
    recommendations.
    Thanks,
    -satya
    -------- Original Message --------
    Subject: wls 7 console terribly slow ? but why
    Date: 25 May 2004 00:14:07 -0700
    From: chris <[email protected]>
    Reply-To: chris <[email protected]>
    Newsgroups: weblogic.developer.interest.management
    hi *,
    i installed bea 7 to migrate from 6 to 7 and my biggest problem is that
    console
    of wls is terribly slow!
    what are the greates pitfalls when configuring wls concerning console speed?
    i got 6 servers configured not all of them are present now (are placed
    in another
    network yet)
    my version 7 sp2
    thx for any help

    Forwarding your message to the console newsgroup if they have any
    recommendations.
    Thanks,
    -satya
    -------- Original Message --------
    Subject: wls 7 console terribly slow ? but why
    Date: 25 May 2004 00:14:07 -0700
    From: chris <[email protected]>
    Reply-To: chris <[email protected]>
    Newsgroups: weblogic.developer.interest.management
    hi *,
    i installed bea 7 to migrate from 6 to 7 and my biggest problem is that
    console
    of wls is terribly slow!
    what are the greates pitfalls when configuring wls concerning console speed?
    i got 6 servers configured not all of them are present now (are placed
    in another
    network yet)
    my version 7 sp2
    thx for any help

  • Wls 7 console terribly slow ? but why

    hi *,
    i installed bea 7 to migrate from 6 to 7 and my biggest problem is that console
    of wls is terribly slow!
    what are the greates pitfalls when configuring wls concerning console speed?
    i got 6 servers configured not all of them are present now (are placed in another
    network yet)
    my version 7 sp2
    thx for any help

    Mac OS X updates wouldn't update the SuperDrive - that would have to come from a separate firmware update. Updates would/could change the DiscRecording parts of the OS however.
    Can you try burning a disc in the Finder using the Mac's built-in software set to maximum rather than Toast? What result do you get?
    Media is also important as is the format of the disc:
    DVD+R DL (2.4x)
    DVD-R, DVD+R (8x)
    DVD-RW, DVD+RW (4x)
    CD-R (24x)
    CD-RW (16x)

  • Disable servlet reload

              I need to disable servlet reload(WLS 7 SP4) for performance reason. I set the
              servlet-reload-check-secs to -1 in the container-descriptor of the web.xml of
              my war file. However when I deploy my war file, from the admin console the "Reload
              Period" is set to 1. Is there a way to make the deployment set the default "Reload
              Period" to -1 during deployment? I hate to deploy, change "Reload Period" from
              console, shutdown server, them restart server. Thanks.
              

    Daniel Lo wrote:
              > I need to disable servlet reload(WLS 7 SP4) for performance reason. I set the
              > servlet-reload-check-secs to -1 in the container-descriptor of the web.xml of
              > my war file. However when I deploy my war file, from the admin console the "Reload
              > Period" is set to 1. Is there a way to make the deployment set the default "Reload
              > Period" to -1 during deployment? I hate to deploy, change "Reload Period" from
              > console, shutdown server, them restart server. Thanks.
              You can use the following in your web.xml
              <context-param>
              <param-name>weblogic.servlet.reloadCheckSecs</param-name>
              <param-value>-1</param-value>
              </context-param>
              Nagesh
              

  • Issue with backup and recovery of WLS

    I have installed WLS 10.3.6 in my 64-bit Linux box, now I am trying to take backup my server. I have a web-application deployed to my WLS, the path to my war file was something like:
    <home_dir>/install_files/myapp.war
    Now to take backup I ran tar command on my current Linux box, now I copied the .tar files to my new Linux box and extracted it. When I am starting my weblogic server it is looking for the war file from the path <home_dir>/install/myapp.war which does not exist on my new machine. So I logged into Admin console of WLS on my new machine and trying to change the path for myapp.war by clikcing update button. But I am getting this error when I change the path:
    weblogic.management.ManagementException: [Deployer:149007]New source location, '/u01/Oracle/install_files/myapp.war', cannot be deployed to configured application, 'myapp'. The application source is at '<home_dir>/myapp.war'. Changing the source location is not allowed for a previously attempted deployment. Try deploying without specifying the source.
    Update operation failed - no deployments changed.
    Please help me how to deploy my files. I'm expecting backup and recovery option should also take care of deployed files but it is not happening in my case, is that wrong?

    1. There is no specific order, but last to go down should be CMS and first to come up should be CMS.
    @echo off
    Stop Business Objects Services
    echo
    net stop "BOBJCrystalReportApplicationServer"
    net stop "BOBJEventServer"
    net stop "BOBJProgramServer"
    net stop "BOBJOutputFileServer"
    net stop "BOBJProcessServer"
    net stop "BOBJInputFileServer"
    net stop "BOBJDestinationServer"
    net stop "BOBJCrystalReportspageserver"
    net stop "BOBJJobServer_Report"
    net stop "BOBJCentralMS"
    exit
    Similarly to Start services, instead of stop use start and put CentralMS at the top and save it as a batch file.
    2. Jobs running when the server goes down will fail, other recurring jobs will wait till the server comes up.
    3. Yes, backup File Store & Database.
    4. Not sure about the default password for My SQL, you should be able to backup the MySQL database, I have done that once.
    5. Backup FileStore & Database.

  • Viewing an MBean on the administration console

    I have registered an MBean on a WebLogic 6.0 server. Now I need to know how
    to view this MBean and run the methods
    of the class represented by this MBean possibly from the Administration
    Console. I want some way to run the methods as
    I could on the HtmlAdaptorServer for the SUN JMX Reference Implementation.
    Thank you.
    T. Pei

    When do you think we will have it? We really want this done (for run-time
    configuration, changing variables, etc.).
    news:3a7f3758$[email protected]..
    Admin console in WLS 6.0 does not support automatic extensibility for user
    MBeans registered to WLS server. You can only access them programmatically
    by getting the MBean from the MBeanServer in the WLS server.
    This functionality is being considered for future releases.
    news:[email protected]..
    I have registered an MBean on a WebLogic 6.0 server. Now I need to knowhow
    to view this MBean and run the methods
    of the class represented by this MBean possibly from the Administration
    Console. I want some way to run the methods as
    I could on the HtmlAdaptorServer for the SUN JMX ReferenceImplementation.

  • Cookie problem in IE when login in on Admin Console

    Hello,
    I have been able to login on the Admin Console of WLS 7.0 with Internet
    Explorer 6.0, but since yesterday, my IE always gives me the following
    message:
    "The Weblogic Server administration console requires that browsers support
    session cookies. Please update the browser configuration and try again."
    Has anyone ever encountered this too? What setting did you change in IE for
    this to work again? I think I tried changing everything in the Security and
    the Privacy tab, but still no go.
    Ringo

    I've solved the problem changing the machine name, because my previous name contained underscores.

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

Maybe you are looking for

  • How do I resolve a (-50) error message?

    When I try to share a music video with iDVD, it returns the error message, "Unable to prepare project for publishing. The project could not be prepared for publishing because an error occurred. (-50)" I tried sharing with iTunes and Media Browser, bu

  • Apple's disgusting policy for defective HD replacement

    I have a late 2006 MacBook that has a dead HD. Unfortunately, 4 days after my external backup HD was stolen, my MB HD died. The data was not recoverable at my local authorized service facility. Because I had 4 years of family photos on the HD, I deci

  • How to install X-Fi Autio Panel etc?

    Hello Until recently I used windows XP, and after a clean install, I installed the updated XP audio driver from creative site, then the programs (Console Launcher, Audio Panel, THX options and whatelse I chose from the list). However, now I use windo

  • User exit export parameter

    Hi Now we setup po mail output. But we found when po relased, the release person become the po mail sender. this is not we wanted. We checked with sap, they mentioned There is a user exit in program RVCOMFZZ 'userexit_komkbea_fill'.   In this user ex

  • Add Channel Mixer functionality to LR

    Something I often do is shoot IR with my Sigma SD-14 by removing the hot mirror/"dust cover." The resulting images are pink-magenta-yellow. Doing a monochrome conversion in LR really doesn't work, whether auto or something else. Grainy, noisy, looks