Tuxedo commands

psadmin - applicaiton server - tuxedo command line

boot commands:

> boot -y (boot the domain normally, if there is an error encountered continue to boot the domain.

Unlike if you boot via psadmin it will shut the domain down)

> boot -y -w (This a fast boot, as the -w switch states to boot all the servers in parallel, and not one by one)

> boot -g JSLGRP( using the -g option states that you are going to boot by server group, every server in tuxedo is assigned to an individual server group)

boot -g PUBSUB

boot -g JREPGRP

> boot -i 10 (every server has an individual server id assigend to it, you can get this info when you do a server stats from psadmin and look under the SRVID column)

shutdown commands:

Eaisest to hardest

> stop -y (this means stop the application server normally, and bring everything down cleanly and clean up IPC)

> stop -y -c (This means stop the application server normally even if clients are attached)

> stop -y -c -w 0 (This means stop the application server normally even if clients are attached and the -w stands for wait 0 seconds to do it shutdown now)

> stop -y -c -w 0 -k KILL (This is the worst form of ahutdown as this sends a KILL signal to Tuxedo, and shoudl only be used as a last resort.) If you elicit this command you must then repeat the command stop -y -c -w 0 as this will then bring down the BBL and clean upi IPC. When you use the kill the BBL does not have time to cleanup IPC as this is a forced kill, so to ensure that nothing for the doamin exists in IPC you have to shutdown the BBL.

---------------------------- Other stop commands------------------------------------------------------------------------------------------------------

> stop -g JSLGRP (using the -g option states that you are going to stop by server group, every server in tuxedo is assigned to an individual server group

> stop -g PUBSUB

LOOK AT FOR TUNING

> stop -i 10

You can also use the stop command if you want to stop an server that is stuck trying to execute a ICPanel. If you see memory going up on the machine you can see if there are any process or PSAPPSRVs spinning trying to execute a panel request. If you look at task mananger a see a request consuming a lot of memory compared to the other server procsses you can assume that the server is spinning on a Panel or someother request.

suspend (susp) {-q qaddress | -g groupname | -i srvid | -s service |

-I interface} ...

---------------------------------------------------------------------------

Suspend the indicated resources.

> help psc

printservice (psc) [-m machine] [-g groupname] [-i srvid] [-q qaddress]

[-s service] [-a {0|1|2}]

---------------------------------------------------------------------------

Print information for the specified service.

resume (res) {-q qaddress | -g groupname | -i srvid | -s service |

-I interface} ...

---------------------------------------------------------------------------

Resume (unsuspend) the indicated resources.