Booting admin processes ...
exec BBL -A :
CMDTUX_CAT:1863: INFO: Process ID=2636 Assume failed (timeout).

At the time of writing, there is nothing in Customer Connection for this, and a google search wasn’t particularly helpful either. So I had to resort to a technique from pre-Google days – i.e. work it out myself. Thankfully it wasn’t too difficult.

The config setting we’re after is TM_BOOTTIMEOUT at by default it is 60 seconds. This can be changed in psappsrv.ubx (which serves as a template for the App Server config). Scroll to the bottom and look for:

# ----------------------------------------------------------------------
*PS_ENVFILE
TM_BOOTTIMEOUT=60
TM_RESTARTSRVTIMEOUT=60
TM_BOOTPRESUMEDFAIL=Y

The line in Red is the one which requires changing, I’ve set mine to 120 seconds. Reconfigure your App Server (you don’t have to make any changes, it just needs to re-read the UBX file) and you’re good to go. If you have doubts as to whether it’s picked up the altered value, look in the TUXLOG.xxxxxx file in your App Server logs directory. The TM_BOOTTIMEOUT is logged there every time you boot an App Server.

It looks like this:

Once you’ve done a little bit of config (no more than 15 minutes, and it’s just config, there’s nothing additional to install) you just point the web browser on your client PC to a URL and it loads up the above screen.

You drop down the Domain menu to choose which App Server or Process Scheduler to administer, then use it to start and stop the domain, or you can do individual processes if you prefer. (For example, on my current client site we have a developer who frequently hangs the domain by using all of the PSAPPSERV processes during debugging. Using this tool, we could change the Max App Servers setting and then boot a couple of extra App Servers, all in a few clicks and without rebooting the domain.)

These are the steps I took to get the Admin Console running (substitute your own machine names and ports where appropriate):

1. for each app server and process scheduler you wish to administer, edit the *.ubx file under either the app serv or proc sched directories. Go to the PS_ENVFILE section and add:
   PS_SERVDIR={$PS_SERVDIR}
PS_SERVER_CFG={$PS_SERVDIR}{FS}{CFGFILE}
2. locate the webgui.ini file under <tuxedo install directory>\udataobj\webgui\ and in the second section add a line for each domain you wish to administer (i.e. a line for each app server or process scheduler). There are instructions in file, but the line will look something like this.
   DOMAIN=HR9DMO;D:\pshome\appserv\HR9DMO\PSTUXCFG
3. Start the Tuxedo Web Server and Listener
   cd /d d:\bea\tux*
tuxwsvr -l //vm-hr9dmo:8080 -i D:\bea\Tuxedo8.1\udataobj\tuxwsvr.ini
Wlisten
4. From your client log on to ‘http://vm-hr9dmo:8080/webguitop.html’. The username and password will be that chosen when Tuxedo was installed (likely admin/password)
5. chose the domain you wish to admin from the drop down domain menu, then you can drill down and activate/inactivate (webgui terminology for start-up/shut-down) whatever you wish.

Hope that helps. If you have any issues, I found the tuxedo website more useful than Peoplebooks or customer connection, however your mileage may vary. Also, the tuxedo helpfile is here:
<bea_home>\Tuxedo8.1\help\guiguide\index.htm

This post was edited on 7th Nov ‘07 to include corrections on the port number, as suggested by David Kurtz in his comment below.