Siebel Installations > Siebel Patch Installation on Solaris Part 3
Web Server patch Installation
Went to this folder /patch_folder/Solaris/Server/Siebel_Web_Server_Extension And after that type ./setupsol -console The output is shown below /patch_folder/Solaris/Server/Siebel_Web_Server_Extension> ./setupsol -console InstallShield Wizard
Initializing InstallShield Wizard...
Preparing Java(tm) Virtual Machine... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ................................... ...................... Running InstallShield Wizard...
|-----------|-----------|-----------|------------| 0% 25% 50% 75% 100% |||||||||||||||||||||||||||||||||||||||||||||||||| ------------------------------------------------------------------------------- Welcome to the InstallShield Wizard for Siebel Web Server Extension
The InstallShield Wizard will install Siebel Web Server Extension on your computer. To continue, choose Next.
Siebel Web Server Extension Siebel Systems
Press 1 for Next, 3 to Cancel or 4 to Redisplay [1]
------------------------------------------------------------------------------- Please select the instance you wish to patch. Note: Once a patch is applied to an instance, a sub-component associated with a product cannot be added to the patched products $Siebel_Root directory. However, after patch installation, new sub-components for the product can be installed in a new root directory and patched accordingly. This applies only for Siebel Enterprise Server subcomponents. Click on Next to continue.
[X] 1 - Patch Siebel Web Server Extension in /app_folder/javaweb/sweapp
To select an item enter its number, or 0 when you are finished: [0]
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]
Configuring uninstallers. Please wait...
|-----------|-----------|-----------|------------| 0% 25% 50% 75% 100% |||||||||||||||||||||||||||||||||||||||||||||||||
Configuring features. Please wait...
------------------------------------------------------------------------------- Siebel Web Server Extension will be installed in the following location:
/app_folder/javaweb/sweapp
with the following features:
EAPPWEB EAPPWEB\SWE EAPPWEB\CFG EAPPWEB\INSTALL EAPPWEB\CONFIG EAPPWEB\ISSRUN EAPPWEB\SWE_SIA EAPPWEB\INSTALL_SIA EAPPWEB\CONFIG_SIA
for a total size:
64.4 MB
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1]
Installing Siebel Web Server Extension. Please wait...
|-----------|-----------|-----------|------------| 0% 25% 50% 75% 100% |||||||||||||||||||||||||||||||||||||||||||||
Installing selected language packs. Please wait...
------------------------------------------------------------------------------- The InstallShield Wizard has successfully installed Siebel Web Server Extension. Choose Finish to exit the wizard.
Press 3 to Finish or 4 to Redisplay [3]
/app_folder/javaweb/sweapp upgrade.txt
/app_folder/javaweb/sweapp> cat upgrade.txt INSTALLED : 8.1.1.3 : : Wed Dec 22 13:01:52 MET 2010 INSTALLED : 8.1.1.3 : QF0356 : Tue Jan 11 16:54:38 MET 2011 INSTALLED : 8.1.1.3 : QF0364 : Tue Jan 11 16:58:55 MET 2011 INSTALLED : 8.1.1.3 : QF0312 : Fri Jan 21 10:34:30 MET 2011 INSTALLED : 8.1.1.3 : QF0312 : Wed Nov 23 15:24:12 MET 2011 INSTALLED : 8.1.1.3 : QF03BN : Wed Nov 23 17:56:05 MET 2011
Now we are done with the installation. We need to start everything.
The sequence is -
1) Web 3) GTW 4) Siebel Server
Web Server
cd //web_server_folder/sjs_http_6.1/https-ta-sfa ./start cd ../https-ta-sfa-ssl/ ./start Check netstat -an | grep 80 netstat -an | grep 443
Gateway server start (197): cd /app_folder/siebel/8.1/gtwysrvr/ . ./siebenv.sh Cd bin start_ns to check status ps -ef | grep siebsvc This command checks siebel gateway server and siebel service
Siebel server start: Log in to the Siebel Server load siebenv.sh from /app_folder/siebel/8.1/siebsrvr folder( use command . ./siebenv.sh) cd to /app_folder/siebel/8.1/siebsrvr/bin and then
./start_server -r /app_folder/siebel/8.1/siebsrvr -e ENTERPRISENAME -L ENU -g 10.152.169.196:2320 SIEBELSERVERNAME
after that type prstat and wait till the load goes up and then settles below 2% (or a very low number)
The patch installation is done! There may be a few more steps to do. Once users log into Siebel again, there will be a prompt to install new CAB files. This needs to be done twice, once at the login screen, the second time in the calendar screen. You can find all the cab files in SOLARIS (where the installers are) here $SIEBEL\siebsrvr\WEBMASTER\siebel_build\applets\
Some errors that I faced
1) ./setupsol -console
Error running install script: "Can't open /tmp/regss5a400f2:83553.pid. Cannot initialze registry server connection data."(SBL-STJ-00108)
Setup has failed and will now terminate. Please review the log file: /var/tmp/siebSetupError.log Solution: Change the owner of the pid file to Siebel and run the command again
2) /app_folder/Solaris/Server/Siebel_Web_Server_Extension ./setupsol -console
Solution: User must have write access to /var/adm/siebel. Install cannot continue.
Setup has failed and will now terminate. Please review the log file: /var/tmp/siebSetupError.log Solution: the folder /var/adm/Siebel and its contents were converted to owner –siebel
3) ./setupsol -console The wizard cannot continue because of the following error: Invalid command line option: .console is not a valid command line option (1001) (403) Solution: This happened because the command was copied from email in windows word format. It changed –console to .console We typed the command manually and ran it again.
|