|
| Problem | Customer experience trying to autostart WebSphere® Application Server on Solaris®; what they learned. | | | | Solution | Customer starting WebSphere Application Server from /etc/rc3 had to make the following changes to overcome problems starting WebSphere Application Server:- start WebSphere Application Server from the installed directory:
- Had to change working directory in the startup script (startupServer.sh script). For example, after:
WAS_HOME=/opt/WebSphere/AppServer export WAS_HOME
Add the following line:
Note: Symbolic links do not work for starting from any other directory - It is also recommended that WebSphere Application Server be started using
$nohup startupServer.sh & - It is also recommended that you verify that your database server (such as, DB2®) has already started using something like:
$ db2 connect to was and testing the return code of the command. In a script, this might look something like: #--------------------------------------------------------------- DBuser=db2inst1 # Appropriate Database instance owner DBalias=was # WebSphere repository name DBpwd=PASSWORD # Appropriate Database password SUFFIX="" # For local database, none is necessary
if [[ -n $DBpwd ]]; then SUFFIX="user $DBuser using $DBpwd" fi su - $DBuser "db2 connect to $DBalias $SUFFIX" RC=$?
if [ $RC -ne 0 ];then echo "Unable to connect to the WebSphere repository." echo "Return code = $RC" echo "Please correct the problem, and try again." exit $RC fi #---------------------------------------------------------------
| |
| | | Historical Number | PMR 15694
49r
000 | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Administrative Console (all non-scripting) Operating system(s): Solaris Software version: 3.5 Software edition: Standard, Advanced Reference #: 1046439 IBM Group: Software Group Modified date: 2004-12-16
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|