Apache Tomcat Server

Servigistics Start-Stop Guide
Table of Contents
1
Servigistics Start ..................................................................................................................1
Servigistics Stop .................................................................. Error! Bookmark not defined.
SRPA Access ....................................................................... Error! Bookmark not defined.
1 Servigistics Start
1. Log into the application and web servers
The list of application and web servers is provided below.
2. pbrun su svgapmgr
pbrun su svgapmgr on each of the servers. SRPA pbrun su access is required.
3. Ensure apache is running on the web servers

ps -ef | grep httpd is used to see if apache is running. Sample output is shown below.
If apache is not running, exit pbrun su svgapmgr and with your own logon run the command below.
SRPA pbrun access is required.
pbrun /opt/webhost/whaeng/bin/start_apache svgapmgr
Output from the start_apache command is shown below.
Indicates Apache is Running Sample Output
[svgapmgr@g4t4604 paul_pace]$ ps -ef | grep httpd
svgapmgr 3243
1 0 Aug29 ?
00:00:27
/opt/webhost_sw/apache2.2/sbin/httpd.worker -d
/opt/webhost/svgapmgr/apache2.2 -f
/opt/webhost/svgapmgr/apache2.2/conf/httpd.conf -k start -DSSL
svgapmgr 3540 3243 0 Aug29 ?
00:21:18
svgapmgr 3546 3243 0 Aug29 ?
00:21:19
svgapmgr 3558 3243 0 Aug29 ?

00:21:18
svgapmgr 23136 17361
0 13:41 pts/0
00:00:00 grep httpd
start_apache Sample Output

[paul_pace@g9t2993 ~]$ pbrun /opt/webhost/whaeng/bin/start_apache svgapmgr
[Sun Sep 15 00:09:26 2013] [warn] worker ajp://g9t2993.houston.hp.com:8009
already used by another worker
'svgapmgr' Apache started successfully.
4. Determine on which server the Serviceguard package is enabled

/usr/local/cmcluster/bin/cmviewcl on the command line on the application servers will indicate on
which server the Serviceguard package is enabled.
Sample Output
[svgapmgr@g4t4602c paul_pace]$ /usr/local/cmcluster/bin/cmviewcl
CLUSTER
STATUS
gct44602
up
NODE
STATUS
STATE
g4t4602c
up
running
PACKAGE
STATUS
STATE
AUTO_RUN
NODE
hpspp
up
running
enabled
g4t4602c
NODE
STATUS
STATE
g4t4603c
up
running
g9t2990c
up
running
g9t2991c
up
running
[svgapmgr@g4t4602c paul_pace]$
5. Run sgFailover.sh start on the Serviceguard enabled server

If a Servigistics slave AutoPilot (AP) is running on the application server sgFailover.sh start will stop
the slave. As discussed in further detail below, when a server is added to the Serviceguard cluster the
job svgAPSlave.sh is run to start a Servigistics slave AutoPilot.
sgFailover.sh start will then start the Servigistics master AP and stop and restart the Servigistics
tomcat servers on the web servers. ssh is utilized to allow svgapmgr to log into the web servers and
run /opt/webhost/local/Servigistics/Servigistics/bin/stopAll.sh and then
/opt/webhost/local/Servigistics/Servigistics/bin/startAll.sh to stop and restart the WebUI (tomcat) on
the web servers.
cd /opt/app/Servigistics/Servigistics/bin
./sgFailover.sh start
On the AP-master server ensure that the AP is running:

ps -ef | grep java | grep Servi
On the web server ensure that the tomcat WebUI is running:

ps -ef | grep tomcat | grep Servi
Sample sgFailover.sh start Output
[svgapmgr@g4t4602c bin]$ ./sgFailover.sh start
Stopping AP slave...
AP slave stopped.
Starting AP master...
AP master started.
Recycling Web UI on all web servers. This will take about 5 minutes...
Stopping Web UI on server 1...

Web UI on server 1 stopped.
Starting Web UI on server 1...
Web UI on server 1 started.
runRecycleUI.sh complete. Exit 0.
Recycle complete.
sgFailover_server1.sh complete. Exit 0.
[svgapmgr@g4t4602c bin]$
Master-AP Check
[svgapmgr@g4t4602c bin]$ ps -ef | grep java | grep Servi
svgapmgr 32103
1 5 14:08 pts/0
00:01:30 /opt/app/jdk1.6.0_38/bin/java
-Xms1024m -Xmx49152m -XX:MaxPermSize=24576m -cp
/opt/app/Servigistics/Servigistics/AutoPilot/AutoPilotServer.jar:/opt/app/Ser
vigistics/Servigistics/lib/* Dservigistics.loadprops=/opt/app/Servigistics/Servigistics/AutoPilot/AutoPilo
tServer_HP_APM1.properties Dlog4j.configuration=file:/opt/app/Servigistics/Servigistics/AutoPilot/log4j_
debug_HP_APM1.properties com.svg.core.autopilot.Application
WebUI tomcat check

[svgapmgr@g4t4604 bin]$ ps -ef | grep tomcat | grep Servi
svgapmgr 26380
1 9 14:08 ?
00:02:00
/opt/webhost/local/jdk1.6.0_38/bin/java Djava.util.logging.config.file=/opt/webhost/local/tomcat6/conf/logging.proper
ties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager Xms1024m -Xmx49152m -XX:MaxPermSize=24576m Dservigistics.loadprops=/opt/webhost/local/Servigistics/Servigistics/WebUI/We
bUI.properties Dlog4j.configuration=file:/opt/webhost/local/Servigistics/Servigistics/WebUI/
log4j_debug.properties -Dservigistics.home=/opt/webhost/local/Servigistics Djavax.net.ssl.trustStore=/opt/webhost/local/Servigistics/Servigistics/WebUI/
webserver.keystore -Djavax.net.ssl.trustStorePassword=webserver Djava.awt.headless=true Djava.endorsed.dirs=/opt/webhost/local/tomcat6/endorsed -classpath
/opt/webhost/local/tomcat6/bin/bootstrap.jar Dcatalina.base=/opt/webhost/local/tomcat6 Dcatalina.home=/opt/webhost/local/tomcat6 Djava.io.tmpdir=/opt/webhost/local/tomcat6/temp
org.apache.catalina.startup.Bootstrap start
[svgapmgr@g4t4604 bin]$
6. Alternative master AP start

Application Master AP Server
./ runAutoPilot_HP_APM*.sh start
On the AP-master server ensure that the AP is running:

WebUI start
On each of the web servers:
cd /opt/webhost/local/Servigistics/Servigistics/bin
./stopAll.sh
Wait 30 seconds to 1 minutes to allow the shutdown to complete.
Check: ps -ef | grep tomcat | grep Servi
./startAll.sh &
On the web server ensure that the tomcat WebUI is running:
ps -ef | grep tomcat | grep Servi
Sample Master-AP Check (HP_APM*)
svgapmgr 32103
1 5 14:08 pts/0
tServer_HP_APM1.properties Dlog4j.configuration=file:/opt/app/Servigistics/Servigistics/AutoPilot/log4j_
debug_HP_APM1.properties com.svg.core.autopilot.Application
WebUI tomcat check

[svgapmgr@g4t4604 bin]$ ps -ef | grep tomcat | grep Servi
svgapmgr 26380
1 9 14:08 ?
00:02:00
/opt/webhost/local/jdk1.6.0_38/bin/java Djava.util.logging.config.file=/opt/webhost/local/tomcat6/conf/logging.proper
ties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager Xms1024m -Xmx49152m -XX:MaxPermSize=24576m Dservigistics.loadprops=/opt/webhost/local/Servigistics/Servigistics/WebUI/We
bUI.properties Dlog4j.configuration=file:/opt/webhost/local/Servigistics/Servigistics/WebUI/
log4j_debug.properties -Dservigistics.home=/opt/webhost/local/Servigistics Djavax.net.ssl.trustStore=/opt/webhost/local/Servigistics/Servigistics/WebUI/
webserver.keystore -Djavax.net.ssl.trustStorePassword=webserver Djava.awt.headless=true Djava.endorsed.dirs=/opt/webhost/local/tomcat6/endorsed -classpath
/opt/webhost/local/tomcat6/bin/bootstrap.jar Dcatalina.base=/opt/webhost/local/tomcat6 Dcatalina.home=/opt/webhost/local/tomcat6 Djava.io.tmpdir=/opt/webhost/local/tomcat6/temp
org.apache.catalina.startup.Bootstrap start
[svgapmgr@g4t4604 bin]$
7. Start slave AP on non master-AP application servers

On the remaining servers in the Serviceguard cluster the Servigistics slave AutoPilot should be started.
Application Slave AP Servers

./runAutoPilot_HP_APS*.sh start
On the AP-slave servers ensure that the slave AP is running:
Sample runAutoPilot_HP_APS*.sh start Output
[svgapmgr@g4t4603c bin]$ ./runAutoPilot_HP_APS2.sh start

POST START-UPDATING PID
runAutoPilot_HP_APS2.sh complete. Exit 0.
[svgapmgr@g4t4603c bin]$ No properties path set - looking for
transactions.properties in classpath...
transactions.properties not found - looking for jta.properties in
classpath...
Failed to open transactions properties file - using default values
2013-09-13 14:42:49,749[main] WARN org.jgroups.stack.Configurator SHARED_LOOPBACK property down_thread was deprecated and is ignored
2013-09-13 14:42:49,749[main] WARN org.jgroups.stack.Configurator SHARED_LOOPBACK property up_thread was deprecated and is ignored
2013-09-13 14:42:49,825[main] WARN org.jgroups.stack.Configurator - GMS
property join_retry_timeout was deprecated and is ignored
property shun was deprecated and is ignored
------------------------------------------------------------------GMS: address=g4t4603c-58908, cluster=Infinispan-Cluster

------------------------------------------------------------------2013-09-13 14:43:29,269[main] WARN org.jgroups.stack.Configurator - GMS
property join_retry_timeout was deprecated and is ignored
property shun was deprecated and is ignored
Sample Slave-AP Check (HP_APS*)

svgapmgr 9536
1 36 14:42 pts/0
tServer_HP_APS2.properties Dlog4j.configuration=file:/opt/app/Servigistics/Servigistics/AutoPilot/log4j_
debug_HP_APS2.properties com.svg.core.autopilot.Application
8. Log into Servigistics

URL: https://hpspp.houston.hp.com/WebUI/
Possible Issues:
1.
2.
3.
4.
SiteMinder
GSLB (Global Site Load Balancer)
User not set up in Servigistics
User not set to External
9. Check Autopilot Status

a. Planning Tab select Process Status
b. Planning Tab select Process Status
Possible Issues
1. False Failed AP
2. False Inactive AP
Solution
False Failed AP
Delete from ipcs_server where TYPE='AUTO_PILOT' and Status!='Active'
False Inactive AP
select * from ipcs_server
delete from ipcs_server where serverid in (2,3)
Where the correct serverid are the server IDs which false Inactive APs are

Apache Tomcat Server

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Apache Tomcat Server

Caricato da

Copyright:

Formati disponibili

Servigistics Start-Stop Guide

Servigistics Start ..................................................................................................................1

Servigistics Stop .................................................................. Error! Bookmark not defined.

SRPA Access ....................................................................... Error! Bookmark not defined.

3. Ensure apache is running on the web servers

svgapmgr 3558 3243 0 Aug29 ?

00:00:00 grep httpd

start_apache Sample Output

4. Determine on which server the Serviceguard package is enabled

5. Run sgFailover.sh start on the Serviceguard enabled server

On the AP-master server ensure that the AP is running:

On the web server ensure that the tomcat WebUI is running:

Stopping Web UI on server 1...

WebUI tomcat check

6. Alternative master AP start

On the AP-master server ensure that the AP is running:

WebUI tomcat check

7. Start slave AP on non master-AP application servers

Application Slave AP Servers

[svgapmgr@g4t4603c bin]$ ./runAutoPilot_HP_APS2.sh start

------------------------------------------------------------------GMS: address=g4t4603c-58908, cluster=Infinispan-Cluster

Sample Slave-AP Check (HP_APS*)

8. Log into Servigistics

9. Check Autopilot Status

b. Planning Tab select Process Status

Potrebbero piacerti anche