Shutdown script for Weblogic admin & managed servers

Greetings,
I am new to weblogic and am using it on a new box with OID. I am in the process of writing a shutdown script to shut down all processes on the box when it is restarted, I think this is better than just pulling the plug. I have learned about and turned on t3 protocols and used WLST to tore credentials in WebLogicKey.properties & WebLogicConfig.properties file so things are working properly. What I can't find is how to shut down the managed server using WLST and am also wondering if it is better to invoke the stopManagedWebLogic.sh and the stopWebLogic.sh scripts form the shell or from the WLST tool, if indeed that is possible. If soemone has such scripts they would be willing to share that would be much appreciated.
Thank you.
Bill Wagman

"One question, Rene, I see in your scripts you are storing username/password combinations.
I have used the storeUserConfig () command to create a WebLogicConfig.properties file and a WebLogicKey.properties file to avoid that issue.
Is there a reason you have not done this?"
No, what you did with the storeUserConfig, to prevent needing to store the unencrypted username
and password in your WLST scripts is good. One thing to note is that the key files are extremely sensitive
in that they allow any user to use the configuration file to authenticate as the user stored in the configuration
file. You should store the key files in a secure location so that only the authorized users have access to them (this
is also what you do with scripts that have unencrypted username and password in them). You probably have
an environment (operating system) in which only authorized users can reach the sensitive data.

Similar Messages

Shutdown script for Weblogic?

Hi,
I am looking for weblogic shutdown script?
Can anybody point me to the script if one is available.
Thanks in advance
Subba Reddy

just use the admnin utility from a shell and bat/cmd file. here's the
command:
java weblogic.Admin <url> SHUTDOWN system <password>
you may get the usage by just typing:
java weblogic.Admin
jason
Original Message <<<<<<<<<<<<<<<<<<On 3/10/00, 9:42:47 PM, subba reddy <[email protected]> wrote
regarding shutdown script for Weblogic?:
Hi,
I am looking for weblogic shutdown script?
Can anybody point me to the script if one is available.
Thanks in advance
Subba Reddy

Scripts for starting/stopping managed servers

All,
Could someone provide me with some sample scripts for starting/stopping managed Weblogic servers? I'm specifically looking for ways to start/stop them WITHOUT starting the AdminServer. I'm running WLS 10.3.6 on Windows Server 2003, and I have NodeManager set to start automatically as a Windows service.
I know how to set my managed servers up as Windows services so that they will start automatically at boot, but this requires the AdminServer to be running, which I do not want. I just want a few scripts for starting/stopping the managed servers (and maybe some hints as to how to make them start automatically without starting the AdminServer).
Thanks in advance,
Tom

Hello Puneet,
Admin console is an web application deployed into AdminServer. Hence if you shutdown AdminServer then you wouldn't able to access Admin console.
Managed Server would function in MSI mode, however you will not be able to make any configuration or administration activities like deployment , any configuration changes , etc.
Hello PRISM,
Can you confirm your requirement about why you don't want AdminServer to be running?
As I said, you will loose the administration capability if you don't have admin server running.
Regards
Rosario

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

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

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

Weblogic.Admin command for stopping all Managed Servers in cluster

Hello All,
I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
I am looking for a way to do that using java weblogic.Admin utility
Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
Thanks
Weblogic Consultant

hi sir,
I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
If u want to use WLST for starting managed servers and clusters
check the follwing steps.
1. java weblogic.WLST
2. startNodeManager()
3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
4. TAKE ANOTHER COMMAND PROMPT
java weblogic.WLST
5. start('man1','Server') or start('man1','Server','localhost:7003')
6. start('mycluster','Cluster')
7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
8.shutdown('mycluster','Cluster')
regards
abhi
Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

Startup/Shutdown script for OBIEE 11g on Linux

Hi all,
as a follow-up to [url http://forums.oracle.com/forums/thread.jspa?messageID=4546010]an earlier thread by some fine gentleman, I have improved the original startup/shutdown script for Linux a bit, making sure that all processes are handled correctly. The script has been tested and works fine on CentOS 5.5 with Oracle BI 11.1.1.3.0 in a clustered configuration. Instructions:
Manual start/stop:
> service obiee start
> service obiee stop
> service obiee status
Automatic start/stop during boot sequence:
> chkconfig --add obiee
> chkconfig obiee on
Note that in order for the procedure to go through smoothly, you need to provide the admin credentials (username/password, defaulting to weblogic/weblogic) in three different places:
1. In configuration file <FMW_HOME>/user_projects/domains/<domain name>/servers/AdminServer/security/boot.properties for the administration server;
2. In script <FMW_HOME>/user_projects/domains/<domain name>/bin/startManagedWebLogic.sh (variables WLS_USER and WLS_PW) for the managed server;
3. In the startup script itself (variables BIEE_USER and BIEE_PASSWD) for shutting down the managed server.
Complete logs are available in /var/log/obiee-start (-stop).log files.
Please comment as necessary,
Chris
#!/bin/bash
# File:    /etc/init.d/obiee
# Purpose: Start and stop Oracle Business Intelligence 11g components.
# chkconfig: 2345 99 10
# description: Manage OBIEE service.
# These values must be adapted to your environment.
ORACLE_OWNR=oracle                  # Local Unix user running OBIEE
ORACLE_FMW=/home/oracle/biee        # Deployment root directory
BIEE_USER=<username>                # BIEE administrator name
BIEE_PASSWD=<password>              # BIEE administrator password
BIEE_DOMAIN=<domain name>           # Domain name
BIEE_INSTANCE=instance1             # Instance name
BIEE_SERVER=bi_server1              # Server name
BIEE_MANAGER_URL=<hostname>:7001    # Admin server URL (hostname:port)
# These should require no change.
WL_PATH=$ORACLE_FMW/wlserver_10.3/server/bin
BIEE_PATH=$ORACLE_FMW/user_projects/domains/$BIEE_DOMAIN/bin
ORACLE_INSTANCE=$ORACLE_FMW/instances/$BIEE_INSTANCE
export ORACLE_INSTANCE
START_LOG=/var/log/obiee-start.log
STOP_LOG=/var/log/obiee-stop.log
SUBSYS=obiee
start() {
    echo "********************************************************************************"
    echo "Starting Admin Server on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$BIEE_PATH/startWebLogic.sh" &
    wait_for "Server started in RUNNING mode"
    echo "********************************************************************************"
    echo "Starting Node Manager on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$WL_PATH/startNodeManager.sh" &
    wait_for "socket listener started on port"
    echo "********************************************************************************"
    echo "Starting Managed Server $BIEE_SERVER on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$BIEE_PATH/startManagedWebLogic.sh $BIEE_SERVER http://$BIEE_MANAGER_URL" &
    wait_for "Server started in RUNNING mode"
    echo "********************************************************************************"
    echo "Starting BI components on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$ORACLE_INSTANCE/bin/opmnctl startall"
    echo "********************************************************************************"
    echo "OBIEE start sequence completed on $(date)"
    echo "********************************************************************************"
stop() {
    echo "********************************************************************************"
    echo "Stopping BI components on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$ORACLE_INSTANCE/bin/opmnctl stopall"
    echo "********************************************************************************"
    echo "Stopping Managed Server $BIEE_SERVER on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$BIEE_PATH/stopManagedWebLogic.sh $BIEE_SERVER t3://$BIEE_MANAGER_URL $BIEE_USER $BIEE_PASSWD"
    echo "********************************************************************************"
    echo "Stopping Node Manager on $(date)"
    echo "********************************************************************************"
    pkill -TERM -u $ORACLE_OWNR -f "weblogic\\.NodeManager"
    echo "********************************************************************************"
    echo "Stopping Admin Server on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$BIEE_PATH/stopWebLogic.sh"
    echo "********************************************************************************"
    echo "OBIEE stop sequence completed on $(date)"
    echo "********************************************************************************"
wait_for() {
    res=0
    while [[ ! $res -gt 0 ]]
    do
        res=$(tail -5 "$START_LOG" | fgrep -c "$1")
        sleep 5
    done
case "$1" in
    start)
        echo "********************************************************************************"
        echo "Starting Oracle Business Intelligence on $(date)"
        echo "Logs are sent to $START_LOG"
        echo "********************************************************************************"
        start &> $START_LOG &
        touch /var/lock/subsys/$SUBSYS
    stop)
        echo "********************************************************************************"
        echo "Stopping Oracle Business Intelligence on $(date)"
        echo "Logs are sent to $STOP_LOG"
        echo "********************************************************************************"
        stop &> $STOP_LOG
        rm -f /var/lock/subsys/$SUBSYS
    status)
        echo "********************************************************************************"
        echo "Oracle BIEE components status...."
        echo "********************************************************************************"
        su $ORACLE_OWNR -c "$ORACLE_INSTANCE/bin/opmnctl status"
    restart)
        $0 stop
        $0 start
        echo "Usage: $(basename $0) start|stop|restart|status"
        exit 1
esac
exit 0

You can use WLST to start/stop BI Services and it works on both Linux and Windows.
Following link has the sample -
http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10541/admin_api.htm#CDEFAHDD

Re: Precompiling JSP with admin/managed servers

Thanks, but I'm not doing any copying.
          The admin/managed-server communication copies things to the managed server,
          which then always recompiles the pages when hit.
          -Greg
          Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
          www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
          "Robert Coonrad" <[email protected]> wrote in message
          news:[email protected]...
          >
          > check out post 8366...i found that i was not preserving
          > the lastmodified date on my jsps and this was causing
          > unnecessary re-compilation.
          >
          > hope it helps...
          > bobc
          >
          > "Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
          > >I believe I have exhausted all permutations of EARing/notEARing,
          > >WARing/notWARing, placing precompiled jsp class files in WEB-INF/classes,
          > >placing them in a static location and setting workingDir to that
          location,
          > >combinations of the above.
          > >
          > >No matter what, the managed server re-compiles pages the first time they
          > >are
          > >hit. Non admin/managed-server I have no problems.
          > >
          > >Can anyone from BEA comment on this problem? Or give me a workaround
          > >for
          > >getting a cluster working with precompiled jsps?
          > >
          > >-Greg
          > >
          > >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
          > >news:[email protected]...
          > >> Grrr... The JSP engine is extremely frustrating! I've spent many hours
          > >> fighting the "staleness" checker in WL. I've been through all of the
          > >> newsgroup messages pertaining to pre-compiling, etc., and I've gotten
          > >> pre-compilation working on single-server deployments, but admin/managed
          > >> server deployments have me beat.
          > >>
          > >> WL6.1, SP1, Solaris
          > >>
          > >> I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
          > >> place. The fixed place contains pre-compiled versions of all jsps
          > >made on
          > >> that machine using jspc not 20 minutes earlier using the JSP files
          > >in the
          > >> exploded EAR file used by the admin server as the model for managed
          > >> servers.. The managed servers are on the same machine.
          > >>
          > >> When the admin server gives an application to a managed server, the
          > >managed
          > >> server creates a temporary directory containing all of the webapp
          > >> components, etc. The file timestamps on these files is the set by
          > >the
          > >> copying process to the time of the managed server boot (why?!?!????!?),
          > >so
          > >> the staleness check always thinks they are new and could care less
          > >what
          > >> precompiled jsps I have in my workingDir, the WEB-INF/classes
          directory,
          > >or
          > >> anywhere else. The pageCheckSeconds=-1 seems to be completely ignored
          > >in
          > >> this scenario.
          > >>
          > >> If I tell the managed server to precompile everything on boot (about
          > >45
          > >> minutes for this app) it will create versions of the classes that match
          > >th
          > >e
          > >> new JSP file timestamps, but this does not even survive a reboot of
          > >the
          > >> managed server because it AGAIN creates a new temp version of
          everything
          > >on
          > >> the next reboot with new timestamps.
          > >>
          > >> If I wait for the managed server to boot and find the directory like
          > >> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
          > >copy
          > >> (via cp -pr to retain timestamps) all of the original webapp components
          > >on
          > >> top of the temp versions, the staleness checker is happy and the
          > >> pre-compiled versions work fine.
          > >>
          > >> There HAS to be a way to package pre-compiled versions of the JSPs
          > >in the
          > >> "model" application in the admin server and keep from having to
          precompile
          > >> the JSPs on every managed server every time managed server is booted..
          > >>
          > >> It would help if we had a way to bypass the staleness checking
          > >completely..
          > >> Or you guys should make the timestamps on the files copied by the
          > >> admin/managed deployment process match properly so the staleness
          checker
          > >> doesn't think the JSP is different.
          > >>
          > >> It would also help if the engineer who wrote this could explain the
          > >rules
          > >> being implemented by the staleness checker. So far all the messages
          > >in
          > >the
          > >> newsgroup have amounted to point solutions for problems without a good
          > >> understanding of what the engine is checking for and/or doing under
          > >the
          > >> covers. Looking at the generated .java files for the JSP pages helps,
          > >but
          > >> it is not good enough...
          > >>
          > >> Anyone out there have a working admin/managed server JSP application?
          > >> -Greg
          > >>
          > >> -----------------------------------------------------------
          > >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
          > >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
          > >>
          > >>
          > >>
          > >
          > >
          >


The admin/managed-server communication copies things to the managed server, which then always recompiles the pages when hit.
          This is a known issue and is fixed. The timestamps of the compiled classes was not being preserved when extracted from the war file used to distribute to the managed servers. This will be available in WLS6.1 Service Pack 3 - and there is a temporary patch available for SP2. Please ask your friendly BEA support person for it (you can refer to CR058946)
          I'd give you the patch myself, but they like to keep track of these things...
          Regards,
          Alex
          "Girish" <[email protected]> wrote in message news:[email protected]...
          >
          > "Aditya Kiran Gavvala" <[email protected]> wrote:
          > >Greg,
          > >
          > >I have been following your posts, because our application deployment
          > >ran
          > >into exact same problem you ran into. I had spent a full two days
          > >researching into the problem. And I figured the solution. Hope this
          > >helps.
          > >
          > >Here are my discoveries:
          > >
          > >The following applies only to the following environment:
          > >OS: Linux (perhaps for Win/Unix/Solaris etc)
          > >WLS 6.0 SP2 ( no rolling patches): I found Rolling Patch2 (RP2) not useful
          > >for this problem.
          > >Clustered environment with Admin/Managed servers
          > >
          > >- When you compile JSP using weblogic.jspc compiler it puts the JSP file
          > >timestamp into the compiled class. You can see it in the generated java
          > >file
          > >(you need to supply -keepgenerated switch to jspc)
          > >
          > >- When a request is made to a JSP page after the application is deployed,
          > >it
          > >seems to be retrieving this timestamp from the compiled class file and
          > >comparing it with the JSP file timestamp. If they dont match a compile
          > >command gets run by the server. Thereby you see a compile happening at
          > >run
          > >time.
          > >
          > >- If you have exploded directory deployment, when you start the managed
          > >servers they create a ".war" file (under some temp dir) with all the
          > >JSP
          > >source files going into the file. You can notice this by looking into
          > >the
          > >server log file. Therefore all JSP source files get a brand new timestamp
          > >in
          > >the archive (a timestamp later than what was put class files by
          > >weblogic.jspc). So, the server at run time sees that the timestamp in
          > >the
          > >class file is older than the JSP source file and runs a recompile. So
          > >DONT
          > >DO EXPLODED directory deployment if your environment is as described
          > >in this
          > >post.
          > >
          > >- If you have ".war" file deployment, you will not have a problem. At
          > >the
          > >start up time managed server still creates "".war" file under a temp
          > >directory however it seems to be copying the content of the your ".war"
          > >file. So, the timestamps of JSP remain the same as they were before.
          > >SO NO
          > >RE-COMPILATION.
          > >
          > >- Another important thing to remember is to make sure you specify the
          > >workingDir in the weblogic.xml file. That is where the precompiled class
          > >files should reside. This should be any directory the server uses as
          > >scratch
          > >pad to compile classes or find (pre)compiled classes. This is not a
          > >directory inside your .war file is what I am trying to get at.
          > >
          > >Hope this helps,
          > >Aditya
          > >
          > >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
          > >news:[email protected]...
          > >> Thanks, but I'm not doing any copying.
          > >>
          > >> The admin/managed-server communication copies things to the managed
          > >server,
          > >> which then always recompiles the pages when hit.
          > >>
          > >> -Greg
          > >>
          > >> -----------------------------------------------------------
          > >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
          > >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
          > >>
          > >> "Robert Coonrad" <[email protected]> wrote in message
          > >> news:[email protected]...
          > >> >
          > >> > check out post 8366...i found that i was not preserving
          > >> > the lastmodified date on my jsps and this was causing
          > >> > unnecessary re-compilation.
          > >> >
          > >> > hope it helps...
          > >> > bobc
          > >> >
          > >> > "Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
          > >> > >I believe I have exhausted all permutations of EARing/notEARing,
          > >> > >WARing/notWARing, placing precompiled jsp class files in
          > >WEB-INF/classes,
          > >> > >placing them in a static location and setting workingDir to that
          > >> location,
          > >> > >combinations of the above.
          > >> > >
          > >> > >No matter what, the managed server re-compiles pages the first time
          > >they
          > >> > >are
          > >> > >hit. Non admin/managed-server I have no problems.
          > >> > >
          > >> > >Can anyone from BEA comment on this problem? Or give me a workaround
          > >> > >for
          > >> > >getting a cluster working with precompiled jsps?
          > >> > >
          > >> > >-Greg
          > >> > >
          > >> > >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
          > >> > >news:[email protected]...
          > >> > >> Grrr... The JSP engine is extremely frustrating! I've spent many
          > >hours
          > >> > >> fighting the "staleness" checker in WL. I've been through all
          > >of the
          > >> > >> newsgroup messages pertaining to pre-compiling, etc., and I've
          > >gotten
          > >> > >> pre-compilation working on single-server deployments, but
          > >admin/managed
          > >> > >> server deployments have me beat.
          > >> > >>
          > >> > >> WL6.1, SP1, Solaris
          > >> > >>
          > >> > >> I've done the pageCheckSeconds=-1 and the workingDir is set to
          > >a
          > >fixed
          > >> > >> place. The fixed place contains pre-compiled versions of all
          > >jsps
          > >> > >made on
          > >> > >> that machine using jspc not 20 minutes earlier using the JSP files
          > >> > >in the
          > >> > >> exploded EAR file used by the admin server as the model for managed
          > >> > >> servers.. The managed servers are on the same machine.
          > >> > >>
          > >> > >> When the admin server gives an application to a managed server,
          > >the
          > >> > >managed
          > >> > >> server creates a temporary directory containing all of the webapp
          > >> > >> components, etc. The file timestamps on these files is the set
          > >by
          > >> > >the
          > >> > >> copying process to the time of the managed server boot
          > >(why?!?!????!?),
          > >> > >so
          > >> > >> the staleness check always thinks they are new and could care
          > >less
          > >> > >what
          > >> > >> precompiled jsps I have in my workingDir, the WEB-INF/classes
          > >> directory,
          > >> > >or
          > >> > >> anywhere else. The pageCheckSeconds=-1 seems to be completely
          > >ignored
          > >> > >in
          > >> > >> this scenario.
          > >> > >>
          > >> > >> If I tell the managed server to precompile everything on boot
          > >(about
          > >> > >45
          > >> > >> minutes for this app) it will create versions of the classes that
          > >match
          > >> > >th
          > >> > >e
          > >> > >> new JSP file timestamps, but this does not even survive a reboot
          > >of
          > >> > >the
          > >> > >> managed server because it AGAIN creates a new temp version of
          > >> everything
          > >> > >on
          > >> > >> the next reboot with new timestamps.
          > >> > >>
          > >> > >> If I wait for the managed server to boot and find the directory
          > >like
          > >> > >> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
          > >> > >copy
          > >> > >> (via cp -pr to retain timestamps) all of the original webapp
          > >components
          > >> > >on
          > >> > >> top of the temp versions, the staleness checker is happy and the
          > >> > >> pre-compiled versions work fine.
          > >> > >>
          > >> > >> There HAS to be a way to package pre-compiled versions of the
          > >JSPs
          > >> > >in the
          > >> > >> "model" application in the admin server and keep from having to
          > >> precompile
          > >> > >> the JSPs on every managed server every time managed server is
          > >booted..
          > >> > >>
          > >> > >> It would help if we had a way to bypass the staleness checking
          > >> > >completely..
          > >> > >> Or you guys should make the timestamps on the files copied by
          > >the
          > >> > >> admin/managed deployment process match properly so the staleness
          > >> checker
          > >> > >> doesn't think the JSP is different.
          > >> > >>
          > >> > >> It would also help if the engineer who wrote this could explain
          > >the
          > >> > >rules
          > >> > >> being implemented by the staleness checker. So far all the messages
          > >> > >in
          > >> > >the
          > >> > >> newsgroup have amounted to point solutions for problems without
          > >a
          > >good
          > >> > >> understanding of what the engine is checking for and/or doing
          > >under
          > >> > >the
          > >> > >> covers. Looking at the generated .java files for the JSP pages
          > >helps,
          > >> > >but
          > >> > >> it is not good enough...
          > >> > >>
          > >> > >> Anyone out there have a working admin/managed server JSP application?
          > >> > >> -Greg
          > >> > >>
          > >> > >> -----------------------------------------------------------
          > >> > >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
          > >> > >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
          > >> > >>
          > >> > >>
          > >> > >>
          > >> > >
          > >> > >
          > >> >
          > >>
          > >>
          > >
          > >
          >
          [att1.html]

Shutdown script for awesome wm

I`m writing a shutdown script for my awesome wm.
it looks like this
[c!/bin/bash
ACTION=`zenity --width=90 --height=200 --list --radiolist --text="Select logout action" --title="Logout" --column "Choice" --column "Action" TRUE Shutdown FALSE Reboot FALSE LockScreen FALSE Suspend`
if [ -n "${ACTION}" ];then
case $ACTION in
Shutdown)
#zenity --question --text "Are you sure you want to halt?" &&
dbus-send --system --print-reply \
--dest=org.freedesktop.ConsoleKit \
/org/freedesktop/ConsoleKit/Manager \
org.freedesktop.ConsoleKit.Manager.Stop
Reboot)
#zenity --question --text "Are you sure you want to reboot?" && gksudo reboot
dbus-send --system --print-reply \
--dest=org.freedesktop.ConsoleKit \
/org/freedesktop/ConsoleKit/Manager \
org.freedesktop.ConsoleKit.Manager.Restart
Suspend)
#gksudo pm-suspend
dbus-send --system --print-reply --dest=org.freedesktop.Hal \
/org/freedesktop/Hal/devices/computer \
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
LockScreen)
slock
esac
fi
and i makedd it executable with chmod +x. But it sims that she is not working.When i run it as root the script works.And when i run it like user onli suspend semams to working.

You don't have to use the deprecated hal! Here are my scripts which I use(d). All you need is
exec ck-launch-session awesome
in your .xinitrc.
shutdown
#!/bin/bash
dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop
reboot
#!/bin/bash
dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart
hibernate
#!/bin/bash
dbus-send --system --print-reply --dest="org.freedesktop.DeviceKit.Power" /org/freedesktop/DeviceKit/Power org.freedesktop.DeviceKit.Power.Hibernate
and suspend
#!/bin/bash
dbus-send --system --print-reply --dest="org.freedesktop.DeviceKit.Power" /org/freedesktop/DeviceKit/Power org.freedesktop.DeviceKit.Power.Suspend
Last edited by Army (2010-12-25 20:42:09)

Shutdown script for linux

Hi,
I'm looking for a shutdown script for linux to put it in crontab and another for startup. Do you have any ?
Thanks.

OK, you can cron following commands (assume that all Oracle related env variables are set. We are setting ORACLE_SID just to ensure that we will be working with the right instance):
59 7 * * * su - oracle -c "export ORACLE_SID=ORCL; echo 'startup' | sqlplus -s '/ as sysdba' >>/dev/null" 2>&1
31 16 * * * su - oracle -c "export ORACLE_SID=ORCL; echo 'shutdown immediate' | sqlplus -s '/ as sysdba' >>/dev/null" 2>&1

Startup and Shutdown scripts for OCS 9.0.4 on Windows?

Hi,
I wanted to know if startup and shutdown scripts for OCS 9.0.4 on Windows are available.
I am thinking something like the ocsctl_sample scripts that OCS10g included.
I have checked the OCS 9.0.4 documentation and not a lot of information for the windows platform is avaiable.
Any information will be appreciated.
Thanks,
Ana

There is no scripts that comes with 9.0.4.
One possibility is to just write the commands you normally use in a batch-file, but note that then you have no checking, and if OCS runs on several machines you should have some checking for required processes etc.
We are using some scripts that does this, but I'm not shure where they came from, possibly from Metalink or from this forum. Try a search. Our scripts are changed quite a bit for our needs, but I might be able to find the original ones.

Error in shutdown script for bea weblogic

We have this error in the shutdown script of our bea weblogic:
./stopWebLogic.sh[33]: -Xms256m: not found.
using the Oracle OCI database driver
Shutdown initiated
The shutdown sequence has been initiated.the script is as follows:
echo "using the Oracle OCI database driver"
export ORACLE_HOME=/opt/oracle/product/8.1.7
export NLS_LANG=AMERICAN_AMERICA.UTF8
export ORACLE_CLIENT_VERSION=817
export ORACLE_API_VERSION=8
PATH=$PATH:$ORACLE_HOME/bin
SHARED_LIBRARY_PATH=$WEBLOGIC_HOME/lib/hpux11:$WEBLOGIC_HOME/lib/hpux11/oci$ORACLE_CLIENT_VERSION\_$ORACLE_API_VERSION:$ORACLE
_HOME/lib
PATH=$JDK_HOME/bin:$PATH
export PATH
# Set application specific variables
DOMAIN_NAME=eGovStarters
SERVER_NAME=MyServer
WLS_PW=weblogic
# change to domain directory
cd $WEBLOGIC_HOME/config/$DOMAIN_NAME
# Allow other users in group to see created files - i.e. logfiles
umask 027
# Set system classpath initially to contain WebLogic product JARs
CLASSPATH=$WEBLOGIC_HOME:$WEBLOGIC_HOME/lib/weblogic.jar
#!/bin/sh
# Weblogic start script for egovernment
# Based on Colin Brick's initial version
# Modified 02/04/03 - Colin Brick
#       - included settings for Oblix from using SSO Assembly Test as example
# Set General environment variables (Should normally not be changed)
#Java settings
JDK_HOME=/opt/bea/jdk131/
export JDK_HOME
JAVACMD=java
JAVA_OPTIONS=""-server -Xms1024m -Xmx1024m -Xmn320m -XX:SurvivorRatio=8 -Xverbosegc:file=/opt/bea/wlserver6.1/config/eGovStart
ers/logs/gc.log -Dweblogic.system.gc.enabled=false ""
export JAVA_OPTIONS
WEBLOGIC_PORT=51080
#Bea settings
BEA_HOME=/opt/bea
export BEA_HOME
WEBLOGIC_HOME=/opt/bea/wlserver6.1
export WEBLOGIC_HOME
BEA_SECURITY_POLICY=/opt/bea/wlserver6.1/lib/weblogic.policy
export BEA_SECURITY_POLICY
#Oracle settings
echo "using the Oracle OCI database driver"
export ORACLE_HOME=/opt/oracle/product/8.1.7
export NLS_LANG=AMERICAN_AMERICA.UTF8
export ORACLE_CLIENT_VERSION=817
export ORACLE_API_VERSION=8
PATH=$PATH:$ORACLE_HOME/bin
SHARED_LIBRARY_PATH=$WEBLOGIC_HOME/lib/hpux11:$WEBLOGIC_HOME/lib/hpux11/oci$ORACLE_CLIENT_VERSION\_$ORACLE_API_VERSION:$ORACLE
_HOME/lib
PATH=$JDK_HOME/bin:$PATH
export PATH
# Set application specific variables
DOMAIN_NAME=eGovStarters
SERVER_NAME=MyServer
WLS_PW=weblogic
# change to domain directory
cd $WEBLOGIC_HOME/config/$DOMAIN_NAME
# Allow other users in group to see created files - i.e. logfiles
umask 027
# Set system classpath initially to contain WebLogic product JARs
CLASSPATH=$WEBLOGIC_HOME:$WEBLOGIC_HOME/lib/weblogic.jar
domain_NAME=eGovStarters
SERVER_NAME=MyServer
WLS_PW=weblogic
# change to domain directory
cd $WEBLOGIC_HOME/config/$DOMAIN_NAME
# Allow other users in group to see created files - i.e. logfiles
umask 027
# Set system classpath initially to contain WebLogic product JARs
CLASSPATH=$WEBLOGIC_HOME:$WEBLOGIC_HOME/lib/weblogic.jar
#Set the shared library path
if [ -n "$SHLIB_PATH" ]; then
        SHLIB_PATH=$SHLIB_PATH:$SHARED_LIBRARY_PATH
else
        SHLIB_PATH=$SHARED_LIBRARY_PATH
fi
export SHLIB_PATH
# Start weblogic
# change to weblogic home
cd $WEBLOGIC_HOME
PATH=$WL_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:$PATH
$JAVACMD -classpath $CLASSPATH -Dbea.home=$BEA_HOME -Dweblogic.Domain=$DOMAIN_NAME -Dweblogic.Name=MyServer weblogic.Admin -ur
l t3://localhost:$WEBLOGIC_PORT -username system -password $WLS_PW SHUTDOWNIt has obviously something to do with the line
JAVA_OPTIONS=""-server -Xms1024m -Xmx1024m -Xmn320m -XX:SurvivorRatio=8 -Xverbosegc:file=/opt/bea/wlserver6.1/config/eGovStart
ers/logs/gc.log -Dweblogic.system.gc.enabled=false ""I googled for this Xms1024m, Xmx1024m and it turns out to be for memory management for the java virtual machine.
I don't know why it sais it can't find "-Xms256m" since it's not in the script.
Anyone with some experience in this field who can help me out?

./stopWebLogic.sh[33]: -Xms256m: not found.
this can be produced by something like this:
javaoptions="-Xms256m" // or other option too
$javacmd $javaoptions
Now if javacmd has not been set, then $javacmd will be evaluated to the empty string, and the program to look for is the first part in $javaoptions, -Xms256m in our case.

Best practice to restart weblogic and managed servers after changing pass

hi
i need to know if have an installation with the following structer what is the best practice to restart the servers after we change weblogic password ?and i know that i should change boot.properties with the new password ,is there anything else to change ? please advise .
oracle access manager &oid (dose it affected by weblogic password change ?)
thank you
Edited by: hsweiss on Jul 31, 2012 10:45 AM

the order is to restart:All managed servers and followed by Admin server
If your weblogic server is integrated with oid, you need to change the credentilas in both the places ie weblogic server(boot.properties) and idm server
if your weblogic server is using your internal ldap for the authentication, your idm and oam wil not effect with this change
if you change the boot.properties file that is enough, you don't need to change anywhere

Precompiling JSP with admin/managed servers

Grrr... The JSP engine is extremely frustrating! I've spent many hours
          fighting the "staleness" checker in WL. I've been through all of the
          newsgroup messages pertaining to pre-compiling, etc., and I've gotten
          pre-compilation working on single-server deployments, but admin/managed
          server deployments have me beat.
          WL6.1, SP1, Solaris
          I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
          place. The fixed place contains pre-compiled versions of all jsps made on
          that machine using jspc not 20 minutes earlier using the JSP files in the
          exploded EAR file used by the admin server as the model for managed
          servers.. The managed servers are on the same machine.
          When the admin server gives an application to a managed server, the managed
          server creates a temporary directory containing all of the webapp
          components, etc. The file timestamps on these files is the set by the
          copying process to the time of the managed server boot (why?!?!????!?), so
          the staleness check always thinks they are new and could care less what
          precompiled jsps I have in my workingDir, the WEB-INF/classes directory, or
          anywhere else. The pageCheckSeconds=-1 seems to be completely ignored in
          this scenario.
          If I tell the managed server to precompile everything on boot (about 45
          minutes for this app) it will create versions of the classes that match the
          new JSP file timestamps, but this does not even survive a reboot of the
          managed server because it AGAIN creates a new temp version of everything on
          the next reboot with new timestamps.
          If I wait for the managed server to boot and find the directory like
          .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically copy
          (via cp -pr to retain timestamps) all of the original webapp components on
          top of the temp versions, the staleness checker is happy and the
          pre-compiled versions work fine.
          There HAS to be a way to package pre-compiled versions of the JSPs in the
          "model" application in the admin server and keep from having to precompile
          the JSPs on every managed server every time managed server is booted..
          It would help if we had a way to bypass the staleness checking completely..
          Or you guys should make the timestamps on the files copied by the
          admin/managed deployment process match properly so the staleness checker
          doesn't think the JSP is different.
          It would also help if the engineer who wrote this could explain the rules
          being implemented by the staleness checker. So far all the messages in the
          newsgroup have amounted to point solutions for problems without a good
          understanding of what the engine is checking for and/or doing under the
          covers. Looking at the generated .java files for the JSP pages helps, but
          it is not good enough...
          Anyone out there have a working admin/managed server JSP application?
          -Greg
          Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
          www.oreilly.com/catalog/entjbeans3 or www.titan-books.com


          check out post 8366...i found that i was not preserving
          the lastmodified date on my jsps and this was causing
          unnecessary re-compilation.
          hope it helps...
          bobc
          "Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
          >I believe I have exhausted all permutations of EARing/notEARing,
          >WARing/notWARing, placing precompiled jsp class files in WEB-INF/classes,
          >placing them in a static location and setting workingDir to that location,
          >combinations of the above.
          >
          >No matter what, the managed server re-compiles pages the first time they
          >are
          >hit. Non admin/managed-server I have no problems.
          >
          >Can anyone from BEA comment on this problem? Or give me a workaround
          >for
          >getting a cluster working with precompiled jsps?
          >
          >-Greg
          >
          >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
          >news:[email protected]...
          >> Grrr... The JSP engine is extremely frustrating! I've spent many hours
          >> fighting the "staleness" checker in WL. I've been through all of the
          >> newsgroup messages pertaining to pre-compiling, etc., and I've gotten
          >> pre-compilation working on single-server deployments, but admin/managed
          >> server deployments have me beat.
          >>
          >> WL6.1, SP1, Solaris
          >>
          >> I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
          >> place. The fixed place contains pre-compiled versions of all jsps
          >made on
          >> that machine using jspc not 20 minutes earlier using the JSP files
          >in the
          >> exploded EAR file used by the admin server as the model for managed
          >> servers.. The managed servers are on the same machine.
          >>
          >> When the admin server gives an application to a managed server, the
          >managed
          >> server creates a temporary directory containing all of the webapp
          >> components, etc. The file timestamps on these files is the set by
          >the
          >> copying process to the time of the managed server boot (why?!?!????!?),
          >so
          >> the staleness check always thinks they are new and could care less
          >what
          >> precompiled jsps I have in my workingDir, the WEB-INF/classes directory,
          >or
          >> anywhere else. The pageCheckSeconds=-1 seems to be completely ignored
          >in
          >> this scenario.
          >>
          >> If I tell the managed server to precompile everything on boot (about
          >45
          >> minutes for this app) it will create versions of the classes that match
          >th
          >e
          >> new JSP file timestamps, but this does not even survive a reboot of
          >the
          >> managed server because it AGAIN creates a new temp version of everything
          >on
          >> the next reboot with new timestamps.
          >>
          >> If I wait for the managed server to boot and find the directory like
          >> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
          >copy
          >> (via cp -pr to retain timestamps) all of the original webapp components
          >on
          >> top of the temp versions, the staleness checker is happy and the
          >> pre-compiled versions work fine.
          >>
          >> There HAS to be a way to package pre-compiled versions of the JSPs
          >in the
          >> "model" application in the admin server and keep from having to precompile
          >> the JSPs on every managed server every time managed server is booted..
          >>
          >> It would help if we had a way to bypass the staleness checking
          >completely..
          >> Or you guys should make the timestamps on the files copied by the
          >> admin/managed deployment process match properly so the staleness checker
          >> doesn't think the JSP is different.
          >>
          >> It would also help if the engineer who wrote this could explain the
          >rules
          >> being implemented by the staleness checker. So far all the messages
          >in
          >the
          >> newsgroup have amounted to point solutions for problems without a good
          >> understanding of what the engine is checking for and/or doing under
          >the
          >> covers. Looking at the generated .java files for the JSP pages helps,
          >but
          >> it is not good enough...
          >>
          >> Anyone out there have a working admin/managed server JSP application?
          >> -Greg
          >>
          >> -----------------------------------------------------------
          >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
          >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
          >>
          >>
          >>
          >
          >

Startup/Shutdown script for OBIEE 11.1.1.5.0 on Linux

There was a very good thread on start/stop scripts for Oracle BI 11.1.1.3.0 that can be found at
https://forums.oracle.com/forums/thread.jspa?messageID=9896816#9896816Now OBI11.1.1.5.0 is out and I tried to use the scripts in the post to start OBI 11.1.1.5.0 after system reboot. I did the following
1) saved the scripts modified with my environemnt variables in /etc/init.d
2) login as root
3) issue command, and got in std out right away
# service obiee start
Starting Oracle Business Intelligence on Tue Sep 27 10:39:31 PDT 2011
Logs are sent to /var/log/obiee-start.log
4) check the log file
[oracle@cchdb ~]$ tail -f /var/log/obiee-start.log
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<Sep 27, 2011 10:39:54 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 27, 2011 10:39:54 AM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 27, 2011 10:39:54 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
5) Check running processes
[root@cchdb oracle]# ps -fe|grep obiee
root 9332 1 0 10:39 pts/2 00:00:00 /bin/bash /etc/init.d/obiee start
oracle 9452 9179 0 10:39 pts/1 00:00:00 tail -f /var/log/obiee-start.log
root 9481 9305 0 10:40 pts/2 00:00:00 grep obiee
OBI is not started. Can some one help ?

Tried various things and has a work around.
First of all, cannot make WLST work for me. Then tried manually step by step as described in reference https://forums.oracle.com/forums/thread.jspa?messageID=9896816#9896816 that is in fact agree with document e10541.
1) Start Admin Server and response to prompt to username/password
<BI Domain Home>/bin/startWebLogic.sh
2) Start node manager
$WL_PATH/startNodeManager.sh
3) Start managed Server with Weblogic Server Admin Console
4) Start System Components with opmnctl
./opmnctl startall This works with the following notes1) Do step one in backgroumd not work, cannot response the username/password prompt properly.
2) If change WLS_USER and WLS_PW in <BI Domain Home>/bin/startManagedWebLogic.sh as in the reference cited abover, step 1 still prompt for username and stops right after username is provided.
3) Step 3 does not work if use command line
<BI Domain Home>/bin/startManagedWebLogic.sh bi_server1 http://<admin_server_host_name>:7001
Has to use UI tool Weblogic Server Admin Console. Question1) How to provide username/password to startWebLogic.sh to allow run it in background
2) How to provide username/password to startManagedWebLogic.sh to allow run it in background

WLS61-WinNT: Admin/Managed servers on same machine with NodeManager?

Hi,
I'm trying to set up a development environment with a Admin server
that controls at least one Managed server. I can start the Admin
server (7001) successfully, and "startNodeManager" seems to work fine
on the default port 5555. No clustering is being done. Only
DefaultWebApp is available.
I'm starting "setEnv" and "startWebLogic" from
C:\dev\bea\wlserver6.1\config\devdomain
and "startNodeManager" from
C:\dev\bea\wlserver6.1\config
I have a Machine, "devmachine", assigned to port 5555 (thus attaching
it to the NodeManager) using the default config files.
I have 2 Servers created:
"adminserver", which listens on port 7001 (no great surprise), and
"devserver", which listens on port 7011. I have also tried
"devserver" on port 5555.
DefaultWebApp has chosen both Servers.
When I go to the Console, right-click on "devserver", and select
"Start this server...", I get the "Are you sure?" page.
Clicking "Yes", I get messages on the "startNodeManager" console:
<Date><Info><Nodemanager@localhost:5555><WindowsProcessControl: online
successfully invoked on server 'devserver', pid: 488>
This sounds good, but the console browser returns:
java.lang.NoClassDefFoundError: weblogic/Server
Exception in thread "main"
<Date><Info><Nodemanager@localhost:5555><WindowsProcessControl: online
successfully invoked on server 'devserver', pid: 488>
StartNodeManager's output confirms that "weblogic.jar" is in the
classpath.
It's location is: .\lib\weblogic.jar
Clicking on the Servers branch confirms that 'devserver:7011' is not
running, and that 'adminserver:7001' is running.
I believe that I'm making some sort of simple configuration error, but
I have been unable to find any documentation that clarifies this
problem.
Has anyone gotten this Admin/Managed combination to work on 1 physical
machine? If so, am I simply not matching ports in the config.xml file
correctly? Am I missing something obvious?
Many Thanks!
Jeff

Hi,
It may not be obvious, but a clean install seemed to solve it. A
wacky config issue? The world may never know...or care. :>
Jeff
[email protected] (Jeff Murdoch) wrote in message news:<[email protected]>...
Hi,
I'm trying to set up a development environment with a Admin server
that controls at least one Managed server. I can start the Admin
server (7001) successfully, and "startNodeManager" seems to work fine
on the default port 5555. No clustering is being done. Only
DefaultWebApp is available.
I'm starting "setEnv" and "startWebLogic" from
C:\dev\bea\wlserver6.1\config\devdomain
and "startNodeManager" from
C:\dev\bea\wlserver6.1\config
I have a Machine, "devmachine", assigned to port 5555 (thus attaching
it to the NodeManager) using the default config files.
I have 2 Servers created:
"adminserver", which listens on port 7001 (no great surprise), and
"devserver", which listens on port 7011. I have also tried
"devserver" on port 5555.
DefaultWebApp has chosen both Servers.
When I go to the Console, right-click on "devserver", and select
"Start this server...", I get the "Are you sure?" page.
Clicking "Yes", I get messages on the "startNodeManager" console:
<Date><Info><Nodemanager@localhost:5555><WindowsProcessControl: online
successfully invoked on server 'devserver', pid: 488>
This sounds good, but the console browser returns:
java.lang.NoClassDefFoundError: weblogic/Server
Exception in thread "main"
<Date><Info><Nodemanager@localhost:5555><WindowsProcessControl: online
successfully invoked on server 'devserver', pid: 488>
StartNodeManager's output confirms that "weblogic.jar" is in the
classpath.
It's location is: .\lib\weblogic.jar
Clicking on the Servers branch confirms that 'devserver:7011' is not
running, and that 'adminserver:7001' is running.
I believe that I'm making some sort of simple configuration error, but
I have been unable to find any documentation that clarifies this
problem.
Has anyone gotten this Admin/Managed combination to work on 1 physical
machine? If so, am I simply not matching ports in the config.xml file
correctly? Am I missing something obvious?
Many Thanks!
Jeff

Shutdown script for Weblogic admin & managed servers

Similar Messages

Maybe you are looking for