Service Start Up – Automatic (Delayed) July 15, 2009
Posted by Tipster in Administration, Infrastructure, Windows.1 comment so far
I’ve been spending a little time putting together a VM using Windows Server 2008 and was pleasantly surprised to see that there is a new start-up type when configuring the PIA, App Server and Process Scheduler to start as services.
As well as Automatic, Manual and Disabled, there is now an Automatic (Delayed) option.
David Kurtz has spoken about using service dependencies, but I just want my App Server and Process Scheduler to start after the intial flurry of start-up activity has finished and everything else has calmed down.
Services that have a delayed start still start automatically, they just wait until all the services that aren’t delayed to finish before firing up.
It works a treat!
REN Server Ports on Multi-App Installations February 7, 2008
Posted by Tipster in Administration, Infrastructure, Oracle, PS Admin, PeopleSoft, PeopleTools.2 comments
When you have more than one App Server on a single machine – and they both need to run a Ren Server process – you need to adjust the port number in the same way you do for other processes (although the REN Server is easy to miss – like I did – as it’s near the bottom away from the other port numbers).
If you do boot the App Server without changing the port you’ll get an error message:
exec PSRENSRV -A -- -C psappsrv.cfg -D PADMO -S PSRENSRV : CMDTUX_CAT:1685: ERROR: Application initialization failure
tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
tmshutdown -qy
OK, you think. I know what that is, it must be a port clash. So you reconfigure the port in PSADMIN and then try to boot it again. Same error. Checking the REN Server log gives the following clue:
(ERROR) nssock: Cannot listen on port 7180. The port may already be in use.
It’s still looking on port 7180, not the new port!
The missing step is to update the database, as the port is stored there also:
UPDATE PSREN SET PORT_NUM = 7185, SSLPORT_NUM = 7148
You should then find you App Server and Ren Server boot fine.
Tolerance of slow App Server boot January 22, 2008
Posted by Tipster in Infrastructure, Oracle, PS Admin, PeopleSoft, PeopleTools, Tuxedo.6 comments
In one of the more recent versions of Tools (8.49 is the first time I’ve noticed it, but that doesn’t mean it hasn’t been around in prior versions) I’ve noticed that occasionally the boot of an Application Server will fail with an error.
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. (more…)
Get up and running with the Tuxedo Administration Console April 2, 2007
Posted by Tipster in Administration, Infrastructure, PS Admin, PeopleSoft, Tuxedo.24 comments
I think I’ve stumbled across a better way of remotely administering servers than using remote control software and PSADMIN. There’s a tool called the ‘Tuxedo Administration Console’ (or sometimes ‘WebGUI’) which does the job also.
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.)
