Similar to LoadRunner[1], OATS (Oracle Application Testing Suite)[2] provides solution enables you to define and manage your application testing process, validate application functionality, and ensure that your applications will perform under load.
At the time of installation, there are three OATS services
bash-3.2# /sbin/chkconfig --list | grep OracleATS
OracleATSAgent 0:off 1:off 2:off 3:on 4:on 5:on 6:off
OracleATSHelper 0:off 1:off 2:off 3:on 4:on 5:on 6:off
OracleATSServer 0:off 1:off 2:off 3:on 4:on 5:on 6:off
You use chkconfig to disable starting services at boot time. By default, OATS services are configured to start in runlevels 3, 4 and 5 automatically.
To disable OATS init scripts, do the following
bash-3.2# /sbin/chkconfig --list | grep OracleATS
OracleATSAgent 0:off 1:off 2:off 3:off 4:off 5:off 6:off
OracleATSHelper 0:off 1:off 2:off 3:off 4:off 5:off 6:off
OracleATSServer 0:off 1:off 2:off 3:off 4:off 5:off 6:off
Be warned that OATS support team recommends you to use the original way of service set up, not this manual way of starting or stopping services.
At the time of installation, there are three OATS services
- OracleATSAgent
- OracleATSHelper
- OracleATSServer
- chkconfig[3]
- service[4]
Checking Current Status and Startup Information
To list the current status of services, you can do:
# /sbin/service --status-all | grep OATS
OATS Agent Manager is running
OATS Helper Service is running
To list the current startup information for services, you can do:
bash-3.2# /sbin/chkconfig --list | grep OracleATS
OracleATSAgent 0:off 1:off 2:off 3:on 4:on 5:on 6:off
OracleATSHelper 0:off 1:off 2:off 3:on 4:on 5:on 6:off
OracleATSServer 0:off 1:off 2:off 3:on 4:on 5:on 6:off
Managing OATS Services Manually
You use chkconfig to disable starting services at boot time. By default, OATS services are configured to start in runlevels 3, 4 and 5 automatically.
To disable OATS init scripts, do the following
# chkconfig --level 345 OracleATSHelper off
# chkconfig --level 345 OracleATSServer off
# chkconfig --level 345 OracleATSAgent off
After you disable all OATS services, you can confirm the results with:bash-3.2# /sbin/chkconfig --list | grep OracleATS
OracleATSAgent 0:off 1:off 2:off 3:off 4:off 5:off 6:off
OracleATSHelper 0:off 1:off 2:off 3:off 4:off 5:off 6:off
OracleATSServer 0:off 1:off 2:off 3:off 4:off 5:off 6:off
Then you can manage them with "service [start|stop]" command manually:
bash-3.2# /sbin/service OracleATSAgent status
OATS Agent Manager is running
bash-3.2# /sbin/service OracleATSAgent stop
Shutting down oats-am: [ OK ]
bash-3.2# /sbin/service OracleATSAgent status
OATS Agent Manager is not running
bash-3.2# /sbin/service OracleATSAgent start
Starting oats-am: [ OK ]
bash-3.2# /sbin/service OracleATSServer start
Starting OracleATSServer:Server is starting in running mode...
bash-3.2# /sbin/service OracleATSHelper start
Starting oats-hs: [ OK ]
Final Words
Be warned that OATS support team recommends you to use the original way of service set up, not this manual way of starting or stopping services.
References
- LoadRunner
- Oracle Application Testing Suite
- Linux / Unix Command: chkconfig
- Service - run a System V init script
- Using chkconfig & /sbin/service to manage run start up scripts in RedHat
- How to Restart OATS Services (Xml and More)
- OATS: Tie All Processes Together — from OpenScript to Scenario (Xml and More)
No comments:
Post a Comment